Good day, I found out the problem. Here is the fstab and df -h
ftl21# df -h Filesystem Size Used Avail Capacity Mounted on /dev/raid0a 3.9G 34.5M 3.7G 1% / /dev/raid0d 7.9G 6.0K 7.5G 0% /tmp /dev/raid0e 7.9G 4.1M 7.5G 0% /var /dev/raid0f 7.9G 1.5G 6.0G 20% /usr /dev/raid0g 7.9G 3.0M 7.5G 0% /var/www /dev/raid0h 66.7G 6.6M 63.4G 0% /home ftl21# more /etc/fstab /dev/raid0a / ffs rw 1 1 /dev/raid0b none swap sw 0 0 /dev/raid0d /tmp ffs rw,nodev,nosuid,softdep 1 2 /dev/raid0e /var ffs rw,nodev,nosuid,softdep 1 2 /dev/raid0f /usr ffs rw,nodev,softdep 1 2 /dev/raid0g /var/www ffs rw,nodev,nosuid,softdep 1 2 /dev/raid0h /home ffs rw,nodev,nosuid,softdep 1 2 The notes I sent earlier work perfectly!!! The problem was me -- for some inexplicable reason, I had a # in front of option RAID_AUTOCONFIG while compiling the kernel. I was commenting out some of the other options and must have accidentally commented out this as well. So from the various messages you sent, it looks like all you have to do is modify your fstab in /etc (from /dev/raid0a) to look something like the one above. Vijay On Tue, 2006-21-11 at 13:45 +0530, Siju George wrote: > On 11/18/06, Joachim Schipper <[EMAIL PROTECTED]> wrote: > > On Fri, Nov 17, 2006 at 02:57:46PM +0530, Siju George wrote: > > > On 11/15/06, Vijay Sankar <[EMAIL PROTECTED]> wrote: > > > >Good day, > > > > > > > >Hope this helps, > > > > > > > > > > Yup some final confusions :-( > > > > > > The raid seems to be working fine. But how do I access the RAID > > > partitions? > > > it seems I have 3 copies of the OpenBSD system on "wd0a" and "wd1a" > > > and also raid0a > > > and how do I run on the OpenBSD system that is on "raid0" > > > I 'l explain. > > > > > > 1) I can boot both from wd0a and wd01 > > > 2) I am running the RAID kernel > > > 3) The raid is working fine :-) > > > > > > ============================================================= > > > # raidctl -sv raid0 > > > raid0 Components: > > > /dev/wd0d: optimal > > > /dev/wd1d: optimal > > > No spares. > > > Component label for /dev/wd0d: > > > > > Autoconfig: Yes > > > Root partition: Yes > > > Last configured as: raid0 > > > Component label for /dev/wd1d: > > > > > Autoconfig: Yes > > > Root partition: Yes > > > Last configured as: raid0 > > > > > ================================================================== > > > > > > but > > > # mount > > > /dev/wd0a on / type ffs (local) > > > # df -h > > > Filesystem Size Used Avail Capacity Mounted on > > > /dev/wd0a 2.0G 649M 1.2G 34% / > > > # > > > # disklabel raid0 > > > > > # mount /dev/raid0a /mnt > > > # cat /mnt/etc/fstab > > > /dev/raid0a / ffs rw 1 1 > > > > > How do I access the wd0d partitions that are Raided? > > > > Not at all, I hope. RAIDFrame is doing it's thing on wd0d, better leave > > it to it. > > > > > Do I need to mount them manually under / > > > > No, mount /dev/raid0a or somesuch. In fact, with the configuration you > > have, /dev/raid0a should be mounted *on* /. > > > > At least, if you enabled 'option RAID_AUTOCONFIG' when you compiled your > > kernel. dmesg will tell you whether or not this is the case - raidX will > > be configured before you see 'root on XXX' if it is. > > > > Note that you should not use /etc/raidX.conf in this case. > > > > Thankyou so much Joachim for the tip. > I tried without /etc/raid0.conf > > But then the raid does not autoconfigure itslef > Nor does the raid0a partition override wd0a partition as said in in > the raidctl manual :-( > > I did use RAID_AUTOCONFIG when I compiled the kernel. Is it because it > is an amd64 machine that this does not work? > > my kernel configuration file is > > ============================================================== > # cat /usr/src/sys/arch/amd64/conf/GENERIC.RAID > include "arch/amd64/conf/GENERIC" > option RAID_AUTOCONFIG > pseudo-device raid 4 > # > ================================================================ > > If I use the /etc/raid0.conf file that has > > ======================================================= > # cat /etc/raid0.conf > START array > 1 2 0 > > START disks > /dev/wd0d > /dev/wd1d > > START layout > 128 1 1 1 > > START queue > fifo 100 > # > =============================================================== > > then the kernel configures raid0 and I get the following entries in the dmesg. > but its root device is still wd0a and not raid0a > ================================================================ > Kernelized RAIDframe activated > dkcsum: wd0 matches BIOS drive 0x80 > dkcsum: wd1 matches BIOS drive 0x81 > root on wd0a > rootdev=0x0 rrootdev=0x300 rawdev=0x302 > 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: 200611210 Mod Counter: 61 > 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: 200611210 Mod Counter: 61 > Clean: Yes Status: 0 > raid0 (root) > # > ======================================================================= > > =====================================================================# > raidctl -sv raid0 > raid0 Components: > /dev/wd0d: optimal > /dev/wd1d: optimal > No spares. > Component label for /dev/wd0d: > Row: 0, Column: 0, Num Rows: 1, Num Columns: 2 > Version: 2, Serial Number: 200611210, Mod Counter: 70 > Clean: No, Status: 0 > sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1 > Queue size: 100, blocksize: 512, numBlocks: 231085824 > RAID Level: 1 > Autoconfig: Yes > Root partition: Yes > Last configured as: raid0 > Component label for /dev/wd1d: > Row: 0, Column: 1, Num Rows: 1, Num Columns: 2 > Version: 2, Serial Number: 200611210, Mod Counter: 70 > Clean: No, Status: 0 > sectPerSU: 128, SUsPerPU: 1, SUsPerRU: 1 > Queue size: 100, blocksize: 512, numBlocks: 231085824 > RAID Level: 1 > Autoconfig: Yes > Root partition: Yes > Last configured as: raid0 > Parity status: clean > Reconstruction is 100% complete. > Parity Re-write is 100% complete. > Copyback is 100% complete. > # > ======================================================================= > > If I delete the /etc/raid0.conf file as you said it still boots from > wd0a and not raid0a. > Also worse the raid0a does not autoconfigure :-( > as shown below ( after a reboot without /etc/raid0.conf) > ======================================================================== > > # raidctl -sv raid0 > raidctl: ioctl (RAIDFRAME_GET_INFO) failed > # > Kernelized RAIDframe activated > dkcsum: wd0 matches BIOS drive 0x80 > dkcsum: wd1 matches BIOS drive 0x81 > root on wd0a > rootdev=0x0 rrootdev=0x300 rawdev=0x302 > # > ======================================================================= > > Any Idea what could have gone wong? > > Thankyou so much > > Kind Regards > > Siju > -- Vijay Sankar, M.Eng., P.Eng. ForeTell Technologies Limited 59 Flamingo Avenue, Winnipeg, MB, Canada R3J 0X6 Phone: 204 885 9535, E-Mail: [EMAIL PROTECTED]
