Hi Geert,
    If I use my backup current kernel using current sources from a month
or so ago, everything boots fine. It's just current source from now
that has a problem.
    Here's the info anyway...

prompt>raidctl -G raid0:
# raidctl config file for /dev/rraid0d

START array
# numRow numCol numSpare
1 2 0

START disks
/dev/wd1a
/dev/wd0a

START layout
# sectPerSU SUsPerParityUnit SUsPerReconUnit RAID_level_1
128 1 1 1

START queue
fifo 100

prompt>disklabel -r raid0
# /dev/rraid0d:
type: RAID
disk: raid
label: fictitious
flags:
bytes/sector: 512
sectors/track: 128
tracks/cylinder: 8
sectors/cylinder: 1024
cylinders: 476948
total sectors: 488394880
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0

7 partitions:
#        size    offset     fstype [fsize bsize cpg/sgs]
 a:   1048576         0     4.2BSD   1024  8192 43696  # (Cyl.      0 -  
1023)
 b:   8388608   1048576       swap                     # (Cyl.   1024 -  
9215)
 d: 488394880         0     unused      0     0        # (Cyl.      0 -
476948*)
 e:  33554432   9437184     4.2BSD   2048 16384 28720  # (Cyl.   9216 - 
41983)
 f: 445403264  42991616     4.2BSD   2048 16384 28832  # (Cyl.  41984 -
476948*)


prompt>disklabel -r wd0
# /dev/rwd0d:
type: unknown
disk: mydisk
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 484518
total sectors: 488395055
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0

16 partitions:
#        size    offset     fstype [fsize bsize cpg/sgs]
 a: 488394992        63       RAID                     # (Cyl.      0*-
484518*)
 b:   8388608   1048703       swap                     # (Cyl.   1040*-  
9362*)
 c: 488394992        63     unused      0     0        # (Cyl.      0*-
484518*)
 d: 488395055         0     unused      0     0        # (Cyl.      0 -
484518*)
disklabel: partitions a and b overlap

prompt>disklabel -r wd1
# /dev/rwd1d:
type: unknown
disk: mydisk
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 484518
total sectors: 488395055
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0

16 partitions:
#        size    offset     fstype [fsize bsize cpg/sgs]
 a: 488394992        63       RAID                     # (Cyl.      0*-
484518*)
 b:   8388608   1048703       swap                     # (Cyl.   1040*-  
9362*)
 c: 488394992        63     unused      0     0        # (Cyl.      0*-
484518*)
 d: 488395055         0     unused      0     0        # (Cyl.      0 -
484518*)
disklabel: partitions a and b overlap


> On Wed, Aug 23, 2006 at 06:02:57PM +1000, murray@river-styx.org wrote:
>> Hi Folks,
>>     Just tried updating my machine to current (from current of about a
>> month ago I think) on amd64. Kernel boots but fails to find init and
>> panics. I'm using a raidframe array as boot disk which I think is the
>> area having a problem. Should I send-pr?
>
> No, first provide more info, like output of "raidctl -G raid0", disklabel
> of your raid device and its components, ...  Try booting with an install
> CD
> to obtain this information.
>
> 	Geert
>