"Siju George" writes: > On 3/8/07, Greg Oster <[EMAIL PROTECTED]> wrote: > > [snip] > > > Kernelized RAIDframe activated > > > Searching for raid components... > > > dkcsum: wd0 matches BIOS drive 0x80 > > > dkcsum: wd1 matches BIOS drive 0x81 > > > root on wd0a > > > rootdev=0x0 rrootdev=0x300 rawdev=0x302 > > > RAIDFRAME: protectedSectors is 64. > > > raid0: Component /dev/wd0d being configured at row: 0 col: 0 > > > Row: 0 Column: 0 Num Rows: 1 Num Columns: 2 > > > Version: 2 Serial Number: 200612010 Mod Counter: 844 > > > Clean: Yes Status: 0 > > > raid0: Component /dev/wd1d being configured at row: 0 col: 1 > > > Row: 0 Column: 1 Num Rows: 1 Num Columns: 2 > > > Version: 2 Serial Number: 200612010 Mod Counter: 844 > > > Clean: Yes Status: 0 > > > RAIDFRAME(RAID Level 1): Using 6 floating recon bufs with no head sep lim > it. > > > raid0 (root) > > > # > > > > So this is still not the output I'd expect.... what does 'disklabel wd0' > > and 'disklabel wd1' say? Are wd0d and wd1d of type FS_RAID ?? > > > > nope :-( > So that is the reason right?
Yes. > is there any hope of fixing it now? It should just work to change 4.2BSD to RAID... as long as you're never actually mounting /dev/wd0d or /dev/wd1d anywhere it'll be fine... > Will the raid be functioning right actually? > Do you want me to recreate it with FS_RAID? You should only need to tweak the disklabel. If you boot single-user you should see root on /dev/raid0a .. at that point you can mount / read-write and fix /etc/fstab if necessary. You shouldn't need to rebuild the RAID set... > ========================================================================== [snip] > ========================================================================= > > > You should > > be seeing a "Component on wd0d" and then the full component label, and that > > should be printed before the dkcsum bits... It's still almost as > > though RAID_AUTOCONFIG isn't defined... (but it is, since the > > "Searching..." line above is printed...) > > > > RAID_AUTOCONFIG is defined but for that to work the FS type shoud be > FS_RAID right? Yes... if it's not FS_RAID, then for i386/amd64/(and others) it won't even consider the partition for autoconfig... > Do you think this setup is bad actually? Nope... just needs a disklabel change and it should work... Later... Greg Oster
