From nobody@FreeBSD.ORG  Thu Aug 24 23:50:45 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 739FA37B42C; Thu, 24 Aug 2000 23:50:45 -0700 (PDT)
Message-Id: <20000825065045.739FA37B42C@hub.freebsd.org>
Date: Thu, 24 Aug 2000 23:50:45 -0700 (PDT)
From: Dave_Hardman@bigpond.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: On first boot, filesystem failed, startup aborted
X-Send-Pr-Version: www-1.0

>Number:         20833
>Category:       i386
>Synopsis:       On first boot, filesystem failed, startup aborted
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 25 00:00:01 PDT 2000
>Closed-Date:    Mon Mar 12 19:43:53 PST 2001
>Last-Modified:  Mon Mar 12 19:44:38 PST 2001
>Originator:     David Hardman
>Release:        4.1
>Organization:
>Environment:
FreeBSD 4.1-RELEASE FreeBSD 4.1-RELEASE #0; Fri July 28 14:30:31 GMT 2000
jkh@Ref4.freebsd.org:/usr/src/sys/compile/GENERIC i386
>Description:
On bootup the output reads:
mount: /dev/ad1s2a on /: specified device does not  match mounted device
Mounting /etc/fstab filesystem failed, startup aborted.
The command 'mount' reports / mounted as wd1s2a, all others as ad....

The same thing happens with 4.0, but not with 3.5. It also occurs if 3.5 
is upgraded to 4.1.
>How-To-Repeat:
Boot up.
>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Fri Aug 25 02:25:32 PDT 2000 
State-Changed-Why:  
So the question is, where di your system get the idea that it should use 
something called wd1, when since 4.0-RELEASE, ad1 has been the name for  
that ATA device? 

Is this a source upgrade?  If not, did you import an old fstab?  Can you 
show us your fstab? 


http://www.freebsd.org/cgi/query-pr.cgi?pr=20833 

From: David Hardman <Dave_Hardman@bigpond.com>
To: sheldonh@freebsd.org
Cc:  
Subject: Re: i386/20833: On first boot, filesystem failed, startup aborted
Date: Sat, 26 Aug 2000 12:09:02 +1100

 On Fri, 25 Aug 2000, you wrote (in part):
 >[....]
 > Is this a source upgrade?  If not, did you import an old fstab?  Can you
 > show us your fstab?
 
 I first upgraded from 3.5 to 4.1, then installed 4.1, then installed
 4.0. Both the upgrade and both the new installation had the same
 problem. I installed 4.1 a number of times always with the same result.
 On upgrade or installation I only used the installation program.
 At the moment I have 3.5 installed and also a minimal 4.1.
 
 I could only find 2 references to wd as the name; in dmesg and mount.
 
 The last line of the 4.1 dmesg reads:
 Mounting root from ufs:wd1s2a
 
 fstab is:
 /dev/ad1s1b	none	swap	sw	0	0
 /dev/ad1s2a	/	ufs	rw	1	1
 /dev/ad1s2f	/usr	ufs	rw	2	2
 /dev/ad1s2e	/var	ufs	rw	2	2
 /dev/acd0c	/cdrom cd9660  ro, noauto 0	         0
 proc		/proc	procfs	rw	0	0
 
 The output of mount is:
 wd1s2a on / (ufs, local, read-only, reads: sync 72 async 2)
 /dev/ad1s2f on /usr (ufs, local, writes: sync 2 async 2)
 /dev/ad1s2e on /var (            ditto                             )
 procfs on /proc  (procfs, local)
 
 
 There was an identical problem mentioned in the BSD-questions mailing
 list on, I think, 1 Aug, by Roderick Person when upgrading from 4.0 to
 4.1.
 
 
 
   > 
 > http://www.freebsd.org/cgi/query-pr.cgi?pr=20833
 -- 
 Dave Hardman 
 Canberra, Australia
 
 
State-Changed-From-To: feedback->closed 
State-Changed-By: des 
State-Changed-When: Mon Mar 12 19:43:53 PST 2001 
State-Changed-Why:  
Stale boot blocks and/or loader. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=20833 
>Unformatted:
