Date: Sun, 13 Aug 1995 14:19:59 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: kimc@w8hd.org, freebsd-current@freebsd.org Subject: Re: -current changed fstab or fstab changed.. Message-ID: <199508132119.OAA10951@gndrsh.aac.dev.com> In-Reply-To: <326.808325726@time.cdrom.com> from "Jordan K. Hubbard" at Aug 13, 95 07:55:26 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > > After rebuilding from -current sup'd at ~2300 UTC on 8/11 > > reboot failed when the system found these devices in the fstab: > > > > /dev/sd0a / ufs rw 1 1 > > /dev/sd0s1g /home ufs rw 1 1 > > /dev/sd0s1f /usr ufs rw 1 1 > > /dev/sd0s1e /var ufs rw 1 1 > > /dev/sd0s1b none swap sw 0 0 > > proc /proc procfs rw 0 0 > > > > When it wanted these devices: > > > > /dev/sd0a / ufs rw 1 1 > > /dev/sd0g /home ufs rw 1 1 > > /dev/sd0f /usr ufs rw 1 1 > > /dev/sd0e /var ufs rw 1 1 > > /dev/sd0b none swap sw 0 0 > > Shouldn't have, unless the slice code has suddently and catastrophically > failed. Or if during your rebuild you did: cd /dev; sh MAKEDEV all and splattered over your /dev/sds1 device entries. To recover do this: cd /dev; sh MAKEDEV all; sh MAKEDEV sd0s1 IMHO, sh MAKEDEV sd0 should _not_ remove sds1* -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508132119.OAA10951>