Re: Rescuing mangled RAID5 array
Hello again, On 14 Nov 2006, at 18:30, Greg Eden wrote: I'm trying to recover data from a broken RAID5 array (drive removed whilst array was rebuilding!). [snip] I'm trying dd if=/dev/da1s1d of=/raid2/rescueimage I'm trying not to equate lack of response to lack of chance of receovery! However... After 4 days dd eventually successfully created a 1.5TB image file of the trashed partition, so i can work on it without causing further damage. I successfully attached it with mdconfig. Running fsck_ufs on the resultant /dev/md0 causes fsck_ufs to eventually crash out with: UNKNOWN FILE TYPE I=42151497 UNEXPECTED SOFT UPDATE INCONSISTENCY CLEAR? yes fsck_ufs: bad inode number 42158080 to nextinode during Phase 1. Is there anyway to get around this so fsck can continue? Thanks in advance. Greg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Rescuing mangled RAID5 array
Hello I'm trying to recover data from a broken RAID5 array (drive removed whilst array was rebuilding!). What's the best way to get an image of the corrupted partition and how would I run fsck -y on the image. The corrupted partition is 1.3TB, /dev/da1s1d, usually mounted as /raid. I have another empty 2TB partition handy, /dev/da2s1d currently mounted as /raid2. Following this thread http://lists.freebsd.org/pipermail/freebsd-questions/2006-November/ 134984.html I'm trying dd if=/dev/da1s1d of=/raid2/rescueimage but it's proceeding very slowly (2MB/sec) and I'm not entirely sure I'm going to be able to mount and fix the resulting image with fsck at the end of it. So is there a faster way to clone a partition (unfortunately the drive array itself doesn't offer this functionality) and can you fsck an md mounted image. assuming i should use md to mount the image? There's nothing wrong with the drives physically, just mangled metadata I think. I can actually mount the partition readonly but many directories are missing or listed as 'Bad file descriptor'. I've copied about 20% of the data off but the most important 50% doesn't even have it's directory listed any more :( Thanks in advance for any help Greg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
