Drobo kaputt (schon wieder) [Update2]Drobo failed (again) [Update2]

Heute morgen wurde ich mal wieder von einer “leeren” Drobo überrascht. Alle Daten in einem kaputten ext3 und keiner der Backup-Blöcke funktional. Gparted fand zwar die Partition, aber fsck.ext3 verweigerte die Arbeit. Nun macht testdisk seine Scans wieder.

[Update 2009/04/01] So wie es akutell aussieht ist das journal vom ext3 zerstört. Der fsck wurde mit einem komplett leeren Dateisystem beendet. Ich hatte zuvor ein Image der “Platte” gezogen. Als nächstes werde ich eine der Platten aus der Drobo ausbauen und direkt in der Linuxkiste scannen.

[Update 2009/04/22] Ich habe nun eine der Festplatten aus der Drobo direkt in meine Linuxkiste gesteckt. photorec hat viele Dateien gefunden, aber der Inhalt ist ein ziemlicher Remix und damit unbrauchbar. Ich werde jetzt mal testdisk drauflos lassen.This morning I was surprised again with an “empty” Drobo. All data in a broken ext3, with none of the backup blocks working. Gparted did find the partion, but fsck.ext3 refused to work. testdrive is now doing its scans.

[Update 2009/04/01] As it currently looks like, the complete ext3 journal has been broken. Running fsck did result in a complete empty filesystem. I did a image copy before the fsck. Next step is getting one of the disks out of the Drobo and scan it directly in the linux box.

[Update 2009/04/22] I moved on of the disks out of the drobo into a linux box directly. photorec discovered a lot of the files, but the content got a remix and is mostly useless. I will now try to use testdisk on it.

Drobo – Currently stable

I did some checks again for a longer period of time. Currently I was putting lots of gigabyte on it and also a hugh amount of files.
It seems to be running stable.
Next step will be rsnapshot every hour onto it.

See previous story.

I did some checks again for a longer period of time. Currently I was putting lots of gigabyte on it and also a hugh amount of files.
It seems to be running stable.
Next step will be rsnapshot every hour onto it.

See previous story.

Drobo failing

Drobo

Drobo

I bought a Drobo Version 2 with USB2.0 and Firewire 800. Additionally I got two 1 TB Samsung HD103UJ drives. Installed fine and running like charm. But after putting a lot of data on it, the filesystem corrupted. I managed to get the most data back with the help of testdrive and Photorec.

So I tried again with a lunsize of 2TB and a freshly formatted ext3. I used the droboutils from sourceforge to access the drobo itself. I again copied stuff on to the drobo and it work without errors.

But I have had to reboot my linux host due to kernel update and the filesystem, which was unmounted correctly, was corrupted again and fsck.ext3 was not able to check it. I again spent a week of testdrive and photorec on the device. But my data was gone. A loss of about 600 GByte. Great pain.

[Update: See Drobo currently stable]

Drobo

Drobo

I bought a Drobo Version 2 with USB2.0 and Firewire 800. Additionally I got two 1 TB Samsung HD103UJ drives. Installed fine and running like charm. But after putting a lot of data on it, the filesystem corrupted. I managed to get the most data back with the help of testdrive and Photorec. So I tried again with a lunsize of 2TB and a freshly formatted ext3. I used the droboutils from sourceforge to access the drobo itself. I again copied stuff on to the drobo and it work without errors. But I have had to reboot my linux host due to kernel update and the filesystem, which was unmounted correctly, was corrupted again and fsck.ext3 was not able to check it. I again spent a week of testdrive and photorec on the device. But my data was gone. A loss of about 600 GByte. Great pain.
[Update: See Drobo currently stable]
Continue reading