MyBook Memeo & TimeMachine

I have the EXACT same problem here also with a My Book 1TB.

If I select a FAT32 format, it will work and the drive will mount correctly. But I can't use Time Machine on a FAT32 filesystem. And no matter which Apple filesystem I use (Extended journaled or not and case sensitive or not), I have this exact barber shop running forever with the 4k message.

The problem is the same either through a firewire or a USB2 connection.
I'm on Leopard.

Any idea, someone? Or did I buy this backup drive for nothinig?

- Edouard

I selected the ooption to write zeros.

It went writing 0 for 9 hours straight and at the very end, Disk Utility crashed and I'm at the samepoint as before...

BTW, when I restart Disk Utility via a command line, I get the following errors:

<pre>2007-11-03 09:52:33.655 Disk Utility[7896:10b] Error loading /Users/eboily/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Conte nts/MacOS/VirtualPCDiskImagePlugin: dlopen(/Users/eboily/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundl e/Contents/MacOS/VirtualPCDiskImagePlugin, 262): no suitable image found. Did find:
/Users/eboily/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Conte nts/MacOS/VirtualPCDiskImagePlugin: mach-o, but wrong architecture
2007-11-03 09:52:33.656 Disk Utility[7896:10b] Cannot find function pointer MacDiskImagePluginFactory for factory 4D08F98C-8968-11D6-8667-0003933E9206 in CFBundle/CFPlugIn 0x54ab60 </Users/eboily/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle> (bundle, not loaded)
2007-11-03 09:52:33.664 Disk Utility[7896:10b] ********
2007-11-03 09:52:33.672 Disk Utility[7896:10b] Disk Utility started.

2007-11-03 09:52:33.851 Disk Utility[7896:10b] * CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0x6303, name = 'com.apple.DiskUtility.ServiceProvider'
See /usr/include/servers/bootstrap_defs.h for the error codes.</pre>

I will restart the 9 hours Disk Utility zero writing and try to get the crashing info at the end...

- Edouard

I will continue this thread here since this clearly is more a Disk Utility problem than a Time Machine problem.

- Edouard

Lok at this for a workaround.

I issued an official bug report to Apple for Disk Utility and the exception generated. But, at least, we have a solution allowing us to use the HD in the meantime.

- Edouard