NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: 5.0 rc2+ raid1 setup - booting off raid not working



We've done a bit more looking into this and it appears that my problem manifests itself as a failure of RAID autoconfiguration.

Not sure why though ...

Symptom :

Before a reboot :

raidctl -v -C ./raid0.conf raid0


raidctl -A root raid0
raid0: Autoconfigure: Yes
raid0: Root: Yes


raidctl -s raid0
Components:
          component0: failed
           /dev/wd1a: optimal
No spares.
component0 status is: failed.  Skipping label.
Component label for /dev/wd1a:
   Row: 0, Column: 0, Num Rows: 0, Num Columns: 0
   Version: 0, Serial Number: 0, Mod Counter: 102
   Clean: No, Status: 0
   sectPerSU: 0, SUsPerPU: 0, SUsPerRU: 0
   Queue size: 0, blocksize: 0, numBlocks: 0
   RAID Level:
   Autoconfig: Yes
   Root partition: Yes
   Last configured as: raid0
Parity status: DIRTY
Reconstruction is 100% complete.
Parity Re-write is 100% complete.
Copyback is 100% complete.


raid0 is this :

START array
1 2 0

START disks
absent
/dev/wd1a

START layout
128 1 1 1

START queue
fifo 100


reboot the box and this happens (if just booting off wd0, wd1 boot fails) :
 raidctl -s raid0
raidctl: ioctl (RAIDFRAME_GET_INFO) failed: Device not configured


This shows up in /var/log/messages when the raid is configured using raidctl -C :

Mar 12 14:07:37 newbox /netbsd: Hosed component: absent
Mar 12 14:07:37 newbox /netbsd: raid0: Ignoring absent
Mar 12 14:07:37 newbox /netbsd: raid0: Component /dev/wd1a being configured at c
ol: 1
Mar 12 14:07:37 newbox /netbsd: Column: 0 Num Columns: 0
Mar 12 14:07:37 newbox /netbsd: Version: 0 Serial Number: 0 Mod Counter: 97
Mar 12 14:07:37 newbox /netbsd: Clean: No Status: 0
Mar 12 14:07:37 newbox /netbsd: Column out of alignment for: /dev/wd1a
Mar 12 14:07:37 newbox /netbsd: Number of columns do not match for: /dev/wd1a
Mar 12 14:07:37 newbox /netbsd: /dev/wd1a is not clean!
Mar 12 14:07:37 newbox /netbsd: raid0: There were fatal errors
Mar 12 14:07:37 newbox /netbsd: raid0: Fatal errors being ignored.
Mar 12 14:07:37 newbox /netbsd: raid0: RAID Level 1
Mar 12 14:07:37 newbox /netbsd: raid0: Components: component0[**FAILED**] /dev/w
d1a
Mar 12 14:07:37 newbox /netbsd: raid0: Total Sectors: 625142272 (305245 MB)
Mar 12 14:07:51 newbox /netbsd: raid0: New autoconfig value is: 1
Mar 12 14:07:51 newbox /netbsd: raid0: New rootpartition value is: 1


I don't think that matters though?

wd1's disklabel :
disklabel wd1
# /dev/rwd1d:
type: ESDI
disk: ST3320613AS
label: fictitious
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 16
sectors/cylinder: 1008
cylinders: 620181
total sectors: 625142448
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0           # microseconds
track-to-track seek: 0  # microseconds
drivedata: 0

5 partitions:
#        size    offset     fstype [fsize bsize cpg/sgs]
a: 625142385 63 RAID # (Cyl. 0*- 620180) c: 625142385 63 unused 0 0 # (Cyl. 0*- 620180) d: 625142448 0 unused 0 0 # (Cyl. 0 - 620180)



raid0's disklabel :

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

4 partitions:
#        size    offset     fstype [fsize bsize cpg/sgs]
a: 616751840 0 4.2BSD 0 0 0 # (Cyl. 0 - 602296*) b: 8390432 616751840 swap # (Cyl. 602296*- 610490*) d: 625142272 0 unused 0 0 # (Cyl. 0 - 610490*)


Box details :

 uname -a
NetBSD newbox.bl.echidna.id.au 5.0_RC2 NetBSD 5.0_RC2 (GENERIC) #0: Sat Mar 7 10:28:57 UTC 2009 builds%b6.netbsd.org@localhost:/home/builds/ab/netbsd-5/amd64/200903070000Z-obj/home/builds/ab/netbsd-5/src/sys/arch/amd64/compile/GENERIC amd64

Any clues?

Carl








Home | Main Index | Thread Index | Old Index