Jump to content

Error 206 when backing up to Lacie FW 2.0TB HD

Recommended Posts

I replaced a Lacie 1.0TB firewire external hd with a new 2.0TB model from Lacie and now get a "can't write, dirty heads, Error 206" error message as retrospect 6.1 stops backing up just at the end of the first volume.(latest workgroup version)

Backing up local drives on the server.

Link to comment
Share on other sites

Oh, if you are hoping the perhaps someone on the Forum might to offer helpful suggestions, you'll need to provide detailed information regarding your hardware/software, things you've done and seen in the past, etc etc etc.


For example, what Type of Backup Set are you using?


Does the error happen no matter what Source you are using? Even if it's a single folder with only a few kilobytes of data, defined as a Subvolume?


Did this same configuration work before you changed out hardware?



Link to comment
Share on other sites

Thanks Dave, point well taken. here is the info:


The same configuration worked fine before with the 1.0TB Lacie Firewire HD. I replaced it with a larger 2.0TB unit from lacie.

Because there is more data to back up now. I tried partitioning the drive, replacing the FW cable, switching to a different FW 800 bus, switching back to a slower FW400 Bus, all with the same result. I finally went back to my office and got my own Lacie 1.0TB drive (1 week old) and put it in that place, the backup now works fine just as it did before the 2TB was put in Place. I checked at dantz to see if mabie a driver update may address the issue but it appears that none are offered for newer FW HD configurations or sizes.


It does happen if I change the source. Such as changing the order of the volumes retro starts with. Retro reports the error after approx. 50GB of data is written to the set file.


Mac Server PPC G5 Dual core 2.3Ghz, Server OS 10.4.9 (10.4.10 Updated to w/same result), 2 internal drives/volumes, 6 external firewire drives/volumes, (all single partition) 2 are for backup only. (one is for 7 client machines backup set)

the other is to backup the server volumes (the 2TB in question)


I think the single folder (source) would be successful although I have not tried that yet.


If I understand you correctly, the backup set type would be "file".


The retrospect Version is 6.1.126 (Workgroup) and the clients are 6.1.130 (no problems w/clients)


I am leaning to the conclusion that this may be a bad drive. However, apples disk util. and disk warrior don't report problems.


Thanks a bunch.

Link to comment
Share on other sites

If you can write a File Backup set to one hard drive, but writing a File Backup Set to a different hard drive fails with a 206 error, it would point pretty conclusively to a hardware error. Since the computer, bus, cable etc are all shown to work, and the only thing you change is the case, power supply and OEM hard drive(s), then that's where you should be looking.


From a Retrospect standpoint, there's not much special about writing a File Backup Set to one physical hard drive and another; Retrospect sees the volume as presented by the OS, and writes to it. That being said, I have seen hard drives listed in RDU change lists before, which is counterintuitive to me.


Too many people seem to report problems with the power supplies on these large Lacie units. Try switching the power supply from the known good one to this one (after checking for matching specs, of course).


Note also that using RAID 0 as a place to store backup information is unwise; a set of two stripped disks has double the chance of failure then a single drive does. So it would be important for you to have secondary and even tertiary backups of your valuable data. The universe is cruel; the day your server hard drive crashes could very well be the day one of the drives in the Lacie goes dead too, rendering your backup unusable.

Link to comment
Share on other sites

There are PCI-X RAID controllers for your G5 that will allow you to combine SATAII drives into RAID 5.


HighPoint RocketRAID cards claim Mac OSX compatibility, and have both internal and external connection models. Get an eSATA case (or two) and make a hardware controlled array that will give you hot swapable spare support, staggered spin-up, etc.


If you data is plentiful and valuable, it's a small price to pay.



Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...