Date: Thu, 29 Jan 1998 21:28:07 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Douglas Ray <doug@connect.com.au> Cc: questions@FreeBSD.ORG Subject: Re: grief booting 2.2.5-R on wd0s4 Message-ID: <Pine.BSF.3.96.980129212504.1248g-100000@gdi.uoregon.edu> In-Reply-To: <199801290739.SAA01619@nara.off.connect.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 29 Jan 1998, Douglas Ray wrote: > /dev/wd0s4a on /: Specified device does not match mounted device Can you be painfully specific as to where this appears? > 2.2.5-R installed on wd0s4 (via FTP for 12h, X-DEVELOPER): > 1579 cyl, 16 heads, 63 S/T > offset size END Name PType Desc SubType FLAGS > 0 63 62 - 6 unused 0 > 63 34208 34270 wd0s1 2 fat 6 > 34271 1 34271 wd0s2 2 fat 6 > 34272 40320 74591 wd0s3 2 fat 6 > 74592 1516032 1590623 wd0s4 3 freebsd 165 C > 1590624 1008 1591631 - 6 unused 0 Those are fruity DOS partitions: one that's 1 sector long?!? > wd0s4 (777Mb) has default partitioning (but I didn't > transcribe the details) > wd0s4a / > wd0s4b swap > wd0s4e var > wd0s4f usr > > The target info appears to be ignored: > boot: 0:wd(4,a)? This isn't wd4 (first disk on tertiary controller). wd4->wd0 is probably wrapping around. > load kernel, complain about no kernel.GENERIC.config, go > through boot sequence up to just before the fsck's where it > changes the root device (and before swapon). At that point > > boot: 0:wd(4,a)kernel.GENERIC It should be just /kernel. > says > changing root device to wd4a > panic : cannot mount root > and reboots (yes, that's wd4a not wd0s4a), but Yes, that's what you told it. > boot: 0:wd(0,a)kernel.GENERIC > runs through swapon, the fsck's, and fails on the subsequent > rw re-mount of / with diagnostic message > > /dev/wd0s4a on /: Specified device does not match mounted device Hm... sounds like it's getting wd0a and wd0s4a confused. > > This is some way down the debug trail. I first saw fstab with > /dev/wd0a / > and I had to mount /wd0s4a on /mnt to update it (didn't have > man page, and "mount -w /dev/wd0s4a /" failed with the device > mismatch diagnostic), and a couple of fsck's later we can now > get to the rw re-mount point in the boot sequence. Try `mount -u /' instead of your mount command line (you're trying to mount the same device twice). What's the output of just `mount' after the error message? I assume you're getting dropped to single-user mode after the error. > Platform is digital's multia. That's a PC, right? Or have you worked some serious magic on an Alpha? :) Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980129212504.1248g-100000>