Date: Thu, 5 Dec 2002 20:29:01 -0500 From: Jason Morgan <jwm-freebsd@sentinelchicken.net> To: freebsd-questions@FreeBSD.org Subject: Re: vinum and a BAD SUPER BLOCK: MAGIC NUMBER WRONG Message-ID: <20021206012901.GN88435@sentinelchicken.net> In-Reply-To: <20021206005955.GE52058@wantadilla.lemis.com> References: <20021206003618.GK88435@sentinelchicken.net> <20021206005955.GE52058@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes, that was the problem - coupled with my ignorance. When I tried removing these before, I still had an error, which was caused by a mistake in my moving /usr and /var. Thanks for the help and thanks for vinum. -Jason On Fri, Dec 06, 2002 at 11:29:55AM +1030, Greg 'groggy' Lehey wrote: > On Thursday, 5 December 2002 at 19:36:18 -0500, Jason Morgan wrote: > > OK, I am installing vinum for the first time and have run into trouble. > > > > Setup: > > > > FreeBSD 4.7-RELEASE > > 2 WD 80GB IDE drives, ad0 and ad2 > > > > I used this page to help me through my setup: > > > > http://org.netbase.org/vinum-mirrored.html > > > > I have followed Case 2, which is a basic setup of one drive mirroring the > > other (RAID-1 right?). I am not trying to mirror the root partition, and > > have a minimal install on ad0s1a. > > > > The setup hase gone just fine, but when I reboot, I get this: > > > > [snip] > > /dev/ad2s1e: BAD SUPER BLOCK: MAGIC NUMBER WRONG > > /dev/ad2s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY > > [snip] > > /dev/ad0s1e: BAD SUPER BLOCK: MAGIC NUMBER WRONG > > /dev/ad0s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY > > > > At that point it goes in single user mode. > > OK, this looks like a problem with the howto. After you put a Vinum > drive on the slices, you no longer have a file system. You need to > remove the entries for these slices in /etc/fstab and replace them > with entries for the Vinum volumes. The howto tells you to add the > entries for the Vinum volumes, but not to remove the old ones. > > > I've tried fooling with fstab and even reinstalling (new machine, no > > data to be lost), but I keep getting the same problem. Could this be > > a problem with my newfs usage: > > > > newfs -v /dev/vinum/usr > > newfs -v /dev/vinum/var > > newfs -v /dev/vinum/public > > That looks OK. > > > Last thing; When I run vinum and issue the list command, it says > > everything is 'up', including ad0s1e and ad2s1e. > > Vinum doesn't say that ad0s1e and ad2s1e are up. It's the drives > located on those slices which are up. > > Greg > -- > When replying to this message, please copy the original recipients. > If you don't, I may ignore the reply or reply to the original recipients. > For more information, see http://www.lemis.com/questions.html > See complete headers for address and phone numbers 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?20021206012901.GN88435>