OK, so 952 errors (about 450k) and 25+ hours later, I have a copy of
the hdf drive on a brand new 250GB drive thanks to dd_rescue.
I haven't tried swapping it to the array. That's the next step. I
imagine, I'll be able to mdadm --assemble --force and have it take
the 4 drives into the
Arthur Britto wrote:
On Sun, 2006-04-23 at 17:17 -0700, Tim Bostrom wrote:
I bought two extra 250GB drives - I'll try using dd_rescue as
recommended and see if I can get a good copy of hdf online.
You might want to use dd_rhelp:
http://www.kalysto.org/utilities/dd_rhelp/index.en.html
Having
On Sun, 2006-04-23 at 17:17 -0700, Tim Bostrom wrote:
I bought two extra 250GB drives - I'll try using dd_rescue as
recommended and see if I can get a good copy of hdf online.
You might want to use dd_rhelp:
http://www.kalysto.org/utilities/dd_rhelp/index.en.html
-Arthur
-
To unsubscribe
Tim Bostrom wrote:
It appears that /dev/hdf1 failed this past week and /dev/hdh1 failed back in
February.
An obvious question would be, how much have you been altering the
contents of the array since February?
I tried a mdadm --assemble --force and was able to get the following:
Molle Bestefich ([EMAIL PROTECTED]) wrote on 22 April 2006 05:54:
Tim Bostrom wrote:
raid5: Disk failure on hdf1, disabling device.
MD doesn't like to find errors when it's rebuilding.
It will kick that disk off the array, which will cause MD to return
crap (instead of stopping the array
Carlos Carvalho wrote:
Molle Bestefich ([EMAIL PROTECTED]) wrote on 22 April 2006 05:54:
Tim Bostrom wrote:
raid5: Disk failure on hdf1, disabling device.
MD doesn't like to find errors when it's rebuilding.
It will kick that disk off the array, which will cause MD to return
crap
