From owner-freebsd-current Mon Mar 9 21:00:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09938 for freebsd-current-outgoing; Mon, 9 Mar 1998 21:00:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA09908 for ; Mon, 9 Mar 1998 20:59:50 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 827 invoked from network); 10 Mar 1998 04:59:30 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 10 Mar 1998 04:59:30 -0000 Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id UAA19095; Mon, 9 Mar 1998 20:59:47 -0800 (PST) (envelope-from scottm) Date: Mon, 9 Mar 1998 20:59:47 -0800 (PST) From: Scott Michel Message-Id: <199803100459.UAA19095@mordred.cs.ucla.edu> To: ade@lovett.com, adhir@worldbank.org Subject: Re: Minor root device oddity Cc: current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, I saw this as well. Here's a temporary workaround until the patch makes it into the suppository: 1. Boot off kernel, single user 2. Mount everything: mount -a -t ufs (ignore the spooge about the root disk and fsck.) 3. TMPDIR=/var/tmp TEMPDIR=/var/tmp export TMPDIR TEMPDIR 4. Edit your configuration, change 'sd0a' to 'sd0s2a', and recompile your kernel. 5. mount /dev/sd0s2a /mnt 6. chflags noschg /mnt/kernel 7. install -c -m 555 -o root -g wheel -fschg kernel /mnt 8. reboot You should be right as rain afterwards, insulated from the current madness. Righteous burr under the saddle. Someone should have put out a bright neon sign e-mail two weeks before they checked this in. Possibly the low SNR in the current "Let's beat on Terry's stackable FS idea" caused me to miss it. >Similarly, my machine, whose root file system is on sd0s2a, claims >"changing root device to sd0s3a" during boot. I suspect someone's code is >simply off by 1... >Machine works fine, and "mount" correctly reflects the mounted partition. >My machine was also built today... >Al >On Mon, 9 Mar 1998 ade@lovett.com wrote: >> >> >> >> After a power failure (long story, don't ask :), I ended up having to >> rebuild my -current box this evening - last cvsup was at 0300 CST 03/09 >> >> On bootup, I see: >> >> ... >> changing root device to wd0s2a >> ... >> >> Which is kinda odd, since I don't actually have a slice 2 :) >> >> gorgon # fdisk wd0 >> ... >> The data for partition 1 is: >> sysid 165,(FreeBSD/NetBSD/386BSD) >> ... >> The data for partition 2 is: >> >> The data for partition 3 is: >> >> The data for partition 4 is: >> >> >> /etc/fstab references (correctly) wd0s1[ab] for mondo-large partition >> and swap respectively, and the system appears to be working fine.. >> >> gorgon # df >> Filesystem 1K-blocks Used Avail Capacity Mounted on >> /dev/wd0s1a 6376860 331579 5535133 6% / >> procfs 4 4 0 100% /proc >> ... >> >> So why is there this boot message reference to slice 2? >> >> Confused. >> -aDe >> >> -- >> Ade Lovett. -- Scott Michel | In life, there are sheep and there are UCLA Computer Science | wolves. PhD Graduate Student | ... One flogged vole later ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message