Subject: Re: Odd dmesg log messages
To: None <explorer@flame.org>
From: Sarton O'Brien <bsd-xen@roguewrt.org>
List: current-users
Date: 12/05/2007 11:27:29
Hi Michael,

explorer@flame.org wrote:
> The raid0 messages are pretty obvious.  I have raid0 auto-conf'd
> via raidctl, and I have raid0.conf in /etc.  The WARNING one confuses me...
>
> raid0: RAID Level 1
> raid0: Components: /dev/wd0g /dev/wd1g
> raid0: Total Sectors: 566273088 (276500 MB)
> WARNING: double match for boot device (wd0, wd1)
> boot device: wd0
> root on wd0a dumps on wd0b
> root file system type: ffs
> raid0: Device already configured!
>
> I suspect I can find the source (I can commit after all, if I can't grep
> I'd really be lame) but when I find it, I will be tempted to make it clear
> about what was searching for the boot device, and why it thinks either can be
> it.
>
> --Michael
>   

Looks like it may be a misconfiguration or disk duplication? Here is my 
raid1 dmesg output:

Component on: wd0a: 781422705
   Row: 0 Column: 0 Num Rows: 1 Num Columns: 2
   Version: 2 Serial Number: 2007001 Mod Counter: 251
   Clean: No Status: 0
   sectPerSU: 128 SUsPerPU: 1 SUsPerRU: 1
   RAID Level: 1  blocksize: 512 numBlocks: 781422592
   Autoconfig: Yes
   Contains root partition: Yes
   Last configured as: raid0
Component on: wd1a: 781422705
   Row: 0 Column: 1 Num Rows: 1 Num Columns: 2
   Version: 2 Serial Number: 2007001 Mod Counter: 251
   Clean: No Status: 0
   sectPerSU: 128 SUsPerPU: 1 SUsPerRU: 1
   RAID Level: 1  blocksize: 512 numBlocks: 781422592
   Autoconfig: Yes
   Contains root partition: Yes
   Last configured as: raid0
Found: wd0a at 0
Found: wd1a at 1
RAID autoconfigure
Configuring raid0:
Starting autoconfiguration of RAID set...
Looking for 0 in autoconfig
Found: wd0a at 0
Looking for 1 in autoconfig
Found: wd1a at 1
raid0: allocating 20 buffers of 65536 bytes.
raid0: RAID Level 1
raid0: Components: /dev/wd0a /dev/wd1a
raid0: Total Sectors: 781422592 (381554 MB)
raid0: configured ok
boot device: raid0
root on raid0a dumps on raid0b


So to me (I am a raidframe novice), it looks like the raidframe IDs are 
identical so therefore it is unable to determine which disk is which and 
falls back to wd0.

I could be completely wrong but your raid is failing to initialise 
completely (observing the additional steps in my dmesg) and is not 
recognised as a valid boot device with  'WARNING: double match for boot 
device (wd0, wd1)' possibly meaning one disk in the raid set is 
indistinquishable from the other.

Sarton