Date: Thu, 9 Aug 2001 15:11:53 -0500 From: "Brandt" <brandt@unkempt.net> To: <freebsd-questions@freebsd.org> Subject: Ack! Disk Problems, Need Help Message-ID: <00b101c1210f$c10152c0$888d1118@home.com>
index | next in thread | raw e-mail
[-- Attachment #1 --] About a week ago I had some memory go bad causing my box to reboot about 15 times in a two hour period. Since, I have replaced the memory, but when attempting to boot, I get the old "please run fsck manually". No Problem, the root file system was cleaned up with no problems. But when fsck attempted to correct /var and /usr, no luck. fsck returns a "incorrect super block, bad magic number" error. The only documentation I've been ible to find was on docs.freebsd.org, stating that 'fsck -b 32 /filesystem' should do the trick when this error occurs. But this returns >fsck -b 32 /dev/ad1s2 Alternate super block location: 32 ** /dev/ad1s2 CANNOT READ: BLK 32 CONTINUE? [yn] If I continue, I get THE FOLLOWING DISK SECTORS COULD NOT BE READ: 32, 33, 34 (up to 47) Any Ideas what I might be able to do to salvage the data from these partitions? FreeBSD 4.3 R by the way -Brandt [-- Attachment #2 --] <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=iso-8859-1" http-equiv=Content-Type> <META content="MSHTML 5.00.2614.3500" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face=Arial size=2>About a week ago I had some memory go bad causing my box to reboot</FONT></DIV> <DIV><FONT face=Arial size=2>about 15 times in a two hour period. Since, I have replaced the memory,</FONT></DIV> <DIV><FONT face=Arial size=2>but when attempting to boot, I get the old "please run fsck manually".</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>No Problem, the root file system was cleaned up with no problems. But</FONT></DIV> <DIV><FONT face=Arial size=2>when fsck attempted to correct /var and /usr, no luck. fsck returns a </FONT></DIV> <DIV><FONT face=Arial size=2>"incorrect super block, bad magic number" error.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>The only documentation I've been ible to find was on docs.freebsd.org, stating</FONT></DIV> <DIV><FONT face=Arial size=2>that 'fsck -b 32 /filesystem' should do the trick when this error occurs.</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>But this returns</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>>fsck -b 32 /dev/ad1s2</FONT></DIV> <DIV><FONT face=Arial size=2>Alternate super block location: 32</FONT></DIV> <DIV><FONT face=Arial size=2>** /dev/ad1s2</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>CANNOT READ: BLK 32</FONT></DIV> <DIV><FONT face=Arial size=2>CONTINUE? [yn]</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>If I continue, I get </FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>THE FOLLOWING DISK SECTORS COULD NOT BE READ: 32, 33, 34 (up to 47)</FONT></DIV> <DIV> </DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>Any Ideas what I might be able to do to salvage the data from these partitions?</FONT></DIV> <DIV><FONT face=Arial size=2>FreeBSD 4.3 R by the way</FONT></DIV> <DIV> </DIV> <DIV><FONT face=Arial size=2>-Brandt</FONT></DIV></BODY></HTML>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00b101c1210f$c10152c0$888d1118>