Date: Tue, 28 Dec 1999 10:53:10 -0500 (EST) From: John Baldwin <jhb@FreeBSD.org> To: keith@mail.telestream.com Cc: freebsd-questions@FreeBSD.org Subject: RE: bad blocks Message-ID: <199912281553.KAA57781@server.baldwin.cx> In-Reply-To: <Pine.LNX.4.10.9912272254430.11982-100000@mail.telestream.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28-Dec-99 keith@mail.telestream.com wrote: > Well after reading through the mail archives I get the impression that if > you have and error from fsck like this > > "BAD SUPER BLOCK. VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST > ALTERNATE." > > That the disk is swish cheeze.. I can't believe that since these are new > drives as of two months ago. I run fsck and it's marked clean and I can > mount it. Then on reboot I have to run fsck again to be able to mount it. > It's on a RAID-5 array that up to now was working fine. A power failure > forced the reboot and from then on fsck dies on boot forcing a manual > fsck. > > Any idea? You might have a bad sector in the superblock. I had a disk that only had 1 bad sector, but it was in the superblock. It gave an error like this until I finally repartitioned and newfs'd the drive. > Keith -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912281553.KAA57781>