Bug 20833

Summary: On first boot, filesystem failed, startup aborted
Product: Base System Reporter: Dave_Hardman <Dave_Hardman>
Component: i386Assignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description Dave_Hardman 2000-08-25 08:00:01 UTC 
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.
Comment 1 Sheldon Hearn freebsd_committer freebsd_triage 2000-08-25 10:25:32 UTC 
State Changed
From-To: open->feedback

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?
Comment 2 Dave_Hardman 2000-08-26 02:09:02 UTC 
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
Comment 3 Dag-Erling Smørgrav freebsd_committer freebsd_triage 2001-03-13 03:43:53 UTC 
State Changed
From-To: feedback->closed

Stale boot blocks and/or loader.