Date: Fri, 24 Nov 2006 09:31:28 +0000 From: Greg Eden <greg@wholemeal.net> To: freebsd-fs@freebsd.org Subject: fsck crash: bad inode number to nextinode Message-ID: <69404A94-8EBC-4978-8EA6-32E3DB1FA6A6@wholemeal.net>
next in thread | raw e-mail | index | archive | help
Hello, I'm try to recover a RAID5 volume which was badly corrupted when a drive was removed during a rebuild. It contained about 1 TB of data and was formatted with default values under FreeBSD 6.0-R. I have used dd to image the drive onto another volume and am mounting it with mdconfig so I can work on that an not cause futher damage. However when I run fsck_ufs on the /dev/md0 partition it eventually crashes out during Phase 1 with UNKNOWN FILE TYPE I=42151497 UNEXPECTED SOFT UPDATE INCONSISTENCY CLEAR? yes fsck_ufs: bad inode number 42158080 to nextinode Is it possible to work around this to get fsck to complete? It is possible to mount the partition and some of the data is there, however most of it is not. Thanks in advance for any help. I have previously posted to freebsd- questions without a response. Greg Eden.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?69404A94-8EBC-4978-8EA6-32E3DB1FA6A6>