Date: Sun, 20 Oct 2002 21:24:35 -0500 (CDT) From: Forrest Cahoon <forrest@abstractfactory.org> To: andrew@cream.org Cc: freebsd-questions@FreeBSD.org Subject: Re: Install problem -- can't mount disk Message-ID: <20021020.212435.39150113.forrest@abstractfactory.org> In-Reply-To: <3DB3584E.3070705@cream.org> References: <20021018.232535.92592630.forrest@abstractfactory.org> <3DB3584E.3070705@cream.org>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Andrew Boothman <andrew@cream.org>
Subject: Re: Install problem -- can't mount disk
Date: Mon, 21 Oct 2002 02:28:46 +0100
> Forrest Cahoon wrote:
> > The machine boots, but when it gets to the disk mounting part, here's
> > what I see:
> >
> > Mounting root from ufs:/dev/ad0s1a
> > no such device 'ad'
> > setrootbyname failed
> > ffs_mountroot: can't find rootvp
> > Root mount failed: 6
> >
> > Then I get taken to the mountroot> prompt.
>
> Do you see your IDE controllers (ad devices) appear during the boot?
Since I really don't know what I'm looking for here, I've just typed
in the entire boot sequence; there are a few things that look
suspicious, but I have no clue what's related to the disk:
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.7-RELEASE #0: Wed Oct 9 15:08:34 GMT 2002
root@builder.freebsdmall.com:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium/P54C (90.20-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x525 Stepping = 5
Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
real memory = 16777216 (16384K bytes)
config> di sn0
config> di lnc0
config> di ie0
config> di fe0
config> di cs0
config> di bt0
config> di aic0
config> di aha0
config> di adv0
config> q
avail memory = 11362304 (11096K bytes)
bios32: Bad BIOS32 Service Directory
Preloaded elf kernel "kernel" at 0xc050f000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc050f09c.
Intel Pentium detected, installing workaround for F00F bug
md0: Malloc disk
pcibios: No call entry point
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
isab0: <Intel 82378ZB PCI to ISA bridge> at device 2.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <RZ 100? ATA controller !WARNING! buggy chip data loss possible> port 0
x364-0x367,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 10.0 on pci0
atapci0: Busmastering DMA not supported
atapci0: Busmastering DMA disabled
ata2: at 0x1f0 on atapci0
ata2: unable to allocate interrupt
device_probe_and_attach: ata2 attach returned 6
ata3: at 0x170 on atapci0
ata3: unable to allocate interrupt
device_probe_and_attach: ata3 attach returned 6
orm0: <Option ROM> at iomem 0xc0000-0xc7fff on isa0
ep0: <3Com #C509-TP EtherLink III> at port 0x310-0x31f irq 11 on isa0
ep0: Ethernet address 00:a0:24:3a:84:33
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at prot 0x60,0x64 on isa0
atkbd0: <AT keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
vga0: <Generic ISA VGA> at port 0x3b0-0x3cf iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA (mono) <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: cannot reserve I/O port range
Mounting root from ufs:/dev/ad0s1a
no such device 'ad'
setrootbyname failed
ffs_rootmount: can't mount rootvp
Root mount failed: 6
Manual root filesystem specification:
<fstype>:<device> Mount <device> using filesystem <fstype>
eg. ufs:/dev/da0s1a
? List valid disk boot devices
<empty line> Abort manual input
mountroot>
> Are there any other messages related to the controllers that get
> displayed? I guess the, "no such device 'ad'", error is pretty
> self-explanatory it can't find your IDE controller.
Well, yeah. But why the heck would this be? Am I not booting the
same kernel that's on kern.flp? When I booted from the floppy for the
install, it certainly sees the hard disk. Fdisk sees it; the
partitions get formatted; a bunch of stuff gets copied from CD onto
it. So why can't it see the hard disk partitions when it's booting
from ... hey waitaminnit ... the hard disk?
The mind boggles.
> Andrew.
>
Forrest
--
forrest@abstractfactory.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021020.212435.39150113.forrest>