Skip site navigation (1)Skip section navigation (2)
Date:      22 Jul 2004 18:50:21 -0000
From:      Mark Diekhans <markd@Kermodei.com>
To:        freebsd-questions@freebsd.org
Subject:   5.2.1 GEOM fails to create RAID disk after install
Message-ID:  <20040722185021.58437.qmail@osprey.kermodei.com>

next in thread | raw e-mail | index | archive | help

I am trying to install 5.2.1 on a system with a Promise Ultra-133 TX2000
IDE RAID controller with RAID 1 on two disks.  

The install goes smoothly, however when the system reboots, it hangs on:

        Mounting root from ufs:/dev/ar0s1a

fixed-ing in and building a new kernel from the RELENG_5_2 branch causes a
`setrootbyname failed' at this point and goes to the mountroot prompt.
The messages from this kernel indicate that GEOM didn't configure
the ar0 as it did with the floppy kernel.

Enclosed are the related dmesg from the kernels.  Any idea what's going
on? 

thanks!

floppy install kernel
---------------------
FreeBSD 5.2.1-RELEASE #0: Mon Feb 23 20:57:17 GMT 2004
...
atapci0: <Intel PIIX4 UDMA33 controller> port 0xd800-0xd80f at device 4.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
...
atapci1: <Promise PDC20271 UDMA133 controller> port 0xa400-0xa40f,0xa800-0xa803,0xb000-0xb007,0xb400-0xb403,0xb800-0xb807 mem 0xe1800000-0xe180ffff irq 12 at device 10.0 on pci0
atapci1: [MPSAFE]
ata2: at 0xb800 on atapci1
ata2: [MPSAFE]
ata3: at 0xb000 on atapci1
ata3: [MPSAFE]
...
GEOM: create disk ad4 dp=0xc2020160
ad4: 58644MB <Maxtor 6Y060L0> [119150/16/63] at ata2-master UDMA133
GEOM: create disk ad6 dp=0xc201f960
ad6: 58644MB <Maxtor 6Y060L0> [119150/16/63] at ata3-master UDMA133
GEOM: create disk ar0 dp=0xc1ff89e0
ar0: 58174MB <ATA RAID1 array> [7416/255/63] status: READY subdisks:
 disk0 READY on ad4 at ata2-master
 disk1 READY on ad6 at ata3-master
Mounting root from ufs:/dev/md0
==============================================================================
RELENG_5_2  2004/07/21
---------------------
FreeBSD 5.2.1-RELEASE-p9 #0: Wed Jul 21 07:03:30 PDT 2004
...
atapci0: <Intel PIIX4 UDMA33 controller> port 0xd800-0xd80f at device 4.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
...
atapci1: <Promise PDC20271 UDMA133 controller> port 0xa400-0xa40f,0xa800-0xa803,0xb000-0xb007,0xb400-0xb403,0xb800-0xb807 mem 0xe1800000-0xe180ffff irq 12 at device 10.0 on pci0
atapci1: [MPSAFE]
ata2: reset tp1 mask=03 ostat0=50 ostat1=00
ata2-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00
ata2-slave:  stat=0x00 err=0x01 lsb=0x00 msb=0x00
ata2: reset tp2 mask=03 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
ata2: at 0xb800 on atapci1
ata2: [MPSAFE]
ata3: reset tp1 mask=03 ostat0=50 ostat1=00
ata3-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00
ata3-slave:  stat=0x00 err=0x01 lsb=0x00 msb=0x00
ata3: reset tp2 mask=03 stat0=50 stat1=00 devices=0x1<ATA_MASTER>
ata3: at 0xb000 on atapci1
ata3: [MPSAFE]
...
ata2-master: pio=0x0c wdma=0x22 udma=0x46 cable=80pin
ata2-master: setting PIO4 on Promise PDC20271 chip
ata2-master: setting UDMA133 on Promise PDC20271 chip
GEOM: create disk ad4 dp=0xc203f460
ad4: <Maxtor 6Y060L0/YAR41VW0> ATA-7 disk at ata2-master
ad4: 58644MB (120103200 sectors), 119150 C, 16 H, 63 S, 512 B
ad4: 16 secs/int, 1 depth queue, UDMA133
GEOM: new disk ad4
ata3-master: pio=0x0c wdma=0x22 udma=0x46 cable=80pin
ata3-master: setting PIO4 on Promise PDC20271 chip
ata3-master: setting UDMA133 on Promise PDC20271 chip
GEOM: create disk ad6 dp=0xc203f260
ad6: <Maxtor 6Y060L0/YAR41VW0> ATA-7 disk at ata3-master
ad6: 58644MB (120103200 sectors), 119150 C, 16 H, 63 S, 512 B
ad6: 16 secs/int, 1 depth queue, UDMA133
[0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:119137977
[1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
[2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
[3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
GEOM: Configure ad4s1, start 32256 length 60998644224 end 60998676479
GEOM: new disk ad6
GEOM: Configure ad4s1a, start 0 length 536870912 end 536870911
GEOM: Configure ad4s1b, start 536870912 length 1073741824 end 1610612735
GEOM: Configure ad4s1c, start 0 length 60998644224 end 60998644223
GEOM: Configure ad4s1d, start 1610612736 length 1073741824 end 2684354559
GEOM: Configure ad4s1e, start 2684354560 length 8589934592 end 11274289151
GEOM: Configure ad4s1f, start 11274289152 length 34359738368 end 45634027519
GEOM: Configure ad4s1g, start 45634027520 length 15364616704 end 60998644223
[0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:119137977
[1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
[2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
[3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
GEOM: Configure ad6s1, start 32256 length 60998644224 end 60998676479
GEOM: Configure ad6s1a, start 0 length 536870912 end 536870911
GEOM: Configure ad6s1b, start 536870912 length 1073741824 end 1610612735
GEOM: Configure ad6s1c, start 0 length 60998644224 end 60998644223
GEOM: Configure ad6s1d, start 1610612736 length 1073741824 end 2684354559
GEOM: Configure ad6s1e, start 2684354560 length 8589934592 end 11274289151
GEOM: Configure ad6s1f, start 11274289152 length 34359738368 end 45634027519
GEOM: Configure ad6s1g, start 45634027520 length 15364616704 end 60998644223
Mounting root from ufs:/dev/ar0s1a
setrootbyname failed
ffs_mountroot: can't find rootvp
Root mount failed: 6





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040722185021.58437.qmail>