From owner-freebsd-questions Thu Aug 9 1:10:46 2001 Delivered-To: freebsd-questions@freebsd.org Received: from fester.unkempt.net (cm623478-a.ftwrth1.tx.home.com [24.4.14.251]) by hub.freebsd.org (Postfix) with ESMTP id 00BF137B403 for ; Thu, 9 Aug 2001 01:10:40 -0700 (PDT) (envelope-from brandt@unkempt.net) Received: from rufus (cm479045-b.ftwrth1.tx.home.com [24.17.141.136]) by fester.unkempt.net (8.9.3/8.9.3) with SMTP id DAA62546 for ; Thu, 9 Aug 2001 03:16:05 -0500 (CDT) (envelope-from brandt@unkempt.net) Message-ID: <00b101c1210f$c10152c0$888d1118@home.com> From: "Brandt" To: Subject: Ack! Disk Problems, Need Help Date: Thu, 9 Aug 2001 15:11:53 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00AE_01C120E5.9F779B20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_00AE_01C120E5.9F779B20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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=20 "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=20 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 ------=_NextPart_000_00AE_01C120E5.9F779B20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
About a week ago I had some memory go = bad causing=20 my box to reboot
about 15 times in a two hour = period.  Since, I=20 have replaced the memory,
but when attempting to boot, I get the = old "please=20 run fsck manually".
 
No Problem, the root file system was = cleaned up=20 with no problems.  But
when fsck attempted to correct /var and = /usr, no=20 luck.  fsck returns a
"incorrect super block, bad magic = number"=20 error.
 
The only documentation I've been ible = to find was=20 on docs.freebsd.org, stating
that 'fsck -b 32 /filesystem' should do = the trick=20 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,=20 33, 34 (up to 47)
 
 
Any Ideas what I might be able to do to = salvage the=20 data from these partitions?
FreeBSD 4.3 R by the way
 
-Brandt
------=_NextPart_000_00AE_01C120E5.9F779B20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message