On Sun, Apr 13, 2008 at 04:41:41PM +0200, Fabian Keil wrote:
> On one of my i386 systems, ad1 (the disk with
> the root partition) is no longer detected.
I'm seeing something slightly different. Both disks are detected:
ad0: DMA limited to UDMA33, device found non-ATA66 cable
ad0: 78167MB <Maxtor 6Y080P0 YAR41BW0> at ata0-master UDMA33
ad1: DMA limited to UDMA33, device found non-ATA66 cable
ad1: 78167MB <Maxtor 6Y080P0 YAR41BW0> at ata0-slave UDMA33
However, the partitions on the second disk are no longer detected.
In fact, the bsdlabels for ad0s1 and ad1s1 now look suspiciously
similar, and they shouldn't! Could some cross-wiring of GEOMs have
happened?
David.
This is what the label should look like:
# /dev/ad1s1:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
c: 160086465 0 unused 0 0 # "raw" part, don't edit
d: 20971520 16 4.2BSD 2048 16384 28528
This is what it looks like with a kernel from this weekend:
sweetums# bsdlabel ad1s1
# /dev/ad1s1:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 524288 0 4.2BSD 0 0 0
b: 8333824 524288 swap
c: 160071597 0 unused 0 0 # "raw" part, don't edit
d: 524288 8858112 4.2BSD 0 0 0
e: 524288 9382400 4.2BSD 0 0 0
f: 20971520 9906688 4.2BSD 0 0 0
g: 129193389 30878208 4.2BSD 2048 16384 28528
This is what the label looks like from ad0s1
sweetums# bsdlabel ad0s1
# /dev/ad0s1:
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 524288 0 4.2BSD 0 0 0
b: 8333824 524288 swap
c: 160071597 0 unused 0 0 # "raw" part, don't edit
d: 524288 8858112 4.2BSD 0 0 0
e: 524288 9382400 4.2BSD 0 0 0
f: 20971520 9906688 4.2BSD 0 0 0
g: 129193389 30878208 4.2BSD 2048 16384 28528