mount problem after enabling serial console
fbsd.questions at rachie.is-a-geek.net
Mon Dec 1 23:26:25 PST 2008
On Tuesday 02 December 2008 07:41:17 Ji wrote:
> Hi all,
> I ran into a weird problem when enabling serial console on the FreeBSD
> 7.0. Your help is really appreciated.
> I installed FreeBSD 7.0 amd64 (from the CD) on a Dell R200, and then
> enabled the serial console by adding the following to
> console="comconsole vidconsole"
> And also replaced the following line on /etc/ttys
> ttyd0 "/usr/libexec/getty std.9600" dialup off secure
> ttyd0 "/usr/libexec/getty std.9600" vt220 on secure.
> During rebooting, I found that the system hangs with the following
> messages and interrupt looks totally messed up
> Trying to mount root from ufs:/dev/ad4s1a
> Manual root filesystem specification:
> <fstype>:<device> Mount <device> using filesystem <fstype>
> eg. ufs:da0s1a
> ? List valid disk boot devices
> <empty line> Abort manual input
> And to my surprise, if I keep rebooting again and again without doing
> any fixing, the problem comes and goes, which confused me.
> When the problem is not present, the serial console looks working
> normally. Can anyone help me with that? Thanks a lot.
> atapci0: <Intel ICH9 SATA300 controller> port
>0-0xbc5f irq 6 at device 31.2 on pci0
> atapci0: unable to map interrupt
> device_attach: atapci0 attach returned 6
There's your problem. Atapci0 can't get an interrupt, which is the ata
controller that controls your disk.
Problem with today's modular software: they start with the modules
and never get to the software part.
More information about the freebsd-questions