From owner-freebsd-current Sun Aug 13 14:20:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id OAA05046 for current-outgoing; Sun, 13 Aug 1995 14:20:36 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id OAA05026 for ; Sun, 13 Aug 1995 14:20:32 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id OAA10951; Sun, 13 Aug 1995 14:19:59 -0700 From: "Rodney W. Grimes" Message-Id: <199508132119.OAA10951@gndrsh.aac.dev.com> Subject: Re: -current changed fstab or fstab changed.. To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 13 Aug 1995 14:19:59 -0700 (PDT) Cc: kimc@w8hd.org, freebsd-current@freebsd.org In-Reply-To: <326.808325726@time.cdrom.com> from "Jordan K. Hubbard" at Aug 13, 95 07:55:26 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1391 Sender: current-owner@freebsd.org Precedence: bulk > > > > > 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