Date: Sat, 29 Jun 2002 01:02:36 -0400 From: Jake Burkholder <jake@locore.ca> To: William Lloyd <wlloyd@slap.net> Cc: freebsd-sparc@FreeBSD.ORG Subject: HEADS UP Re: Ultra 5 problems Message-ID: <20020629010236.G71376@locore.ca> In-Reply-To: <000501c21d4c$97ed5a70$0264a8c0@slap.net>; from wlloyd@slap.net on Wed, Jun 26, 2002 at 01:03:51PM -0700 References: <000501c21d4c$97ed5a70$0264a8c0@slap.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> group. I did a make buildworld yesterday and it worked fine. kernel has
> some error with setrootbyname failed. This is all with latest -current
I just figured out what this problem is. For some reason, when
ATA_STATIC_ID is defined, the ata driver probes the cmd646 controller
in ultra 5s and ultra 10s as ata2, which makes the first ata drive
show up as ad4, rather than ad0 as one would expect.
So, if you build a new kernel and get this error mounting root:
Mounting root from ufs:/dev/ad0a
setrootbyname failed
ffs_mountroot: can't find rootvp
Root mount failed: 6
Manual root filesystem specification:
<fstype>:<device> Mount <device> using filesystem <fstype>
eg. ufs:da0a
? List valid disk boot devices
<empty line> Abort manual input
Look at the drive probes just above and you will probably see your drive
on ad4:
ad4: 4103MB <ST34342A> [8894/15/63] at ata2-master WDMA2
To fix this, boot kernel.old, comment out options ATA_STATIC_ID from
your kernel config and rebuild your kernel. ATA_STATIC_ID has been
removed from GENERIC in rev 1.23.
Jake
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-sparc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020629010236.G71376>