Date: Wed, 4 Feb 2004 06:37:11 -0800 (PST) From: "Scott I. Remick" <scott@sremick.net> To: Sergey 'DoubleF' Zaharchenko <doublef@tele-kom.ru> Cc: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: "Cannot find file system superblock" error - how to recover? Message-ID: <20040204143712.96647.qmail@web41110.mail.yahoo.com> In-Reply-To: <20040204172844.77123521@Hal.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Sergey 'DoubleF' Zaharchenko <doublef@tele-kom.ru> wrote: > And /dev/ad2s1e? bash-2.05b# mount -r /dev/ad2s1e /data mount: /dev/ad2s1e on /data: incorrect super block bash-2.05b# fsck /dev/ad2s1e ** /dev/ad2s1e BAD SUPER BLOCK: MAGIC NUMBER WRONG LOOK FOR ALTERNATE SUPERBLOCKS? [yn] y USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes 416 BAD I=2 412 BAD I=3 424 BAD I=4 414 BAD I=4 417 BAD I=5 INCORRECT BLOCK COUNT I=4257794 (8928 should be 9952) CORRECT? [yn] Hmmm that looks more promising, although I'm not sure exactly what it's trying to warn me about, or how bad things are from that, so I'm going to leave it there for now. :) And if I remember correctly, even though fsck has used an alternate superblock to perform the repair process, it hasn't actually replaced the master superblock with the alternate one, so I'd still need to fix that manually somehow... correct?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040204143712.96647.qmail>