Re: raid dmesg output and raidctl -sv output shows differrent status for raidframe mirror on OpenBSD 4.0 amd64
On 3/8/07, Greg Oster [EMAIL PROTECTED] wrote: Siju George writes: On 3/8/07, Greg Oster [EMAIL PROTECTED] wrote: 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... Yes done that! == # disklabel wd0 # Inside MBR partition 3: type A6 start 63 size 234436482 # /dev/rwd0c: type: ESDI disk: ESDI/IDE disk label: ST3120827AS flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 234441648 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 314590563 4.2BSD 2048 16384 328 # Cyl 0*- 3120 b:204624 3145968swap # Cyl 3121 - 3323 c: 234441648 0 unused 0 0 # Cyl 0 -232580 d: 231085953 3350592RAID # Cyl 3324 -232575* # disklabel wd1 # Inside MBR partition 3: type A6 start 63 size 234436482 # /dev/rwd1c: type: ESDI disk: ESDI/IDE disk label: ST3120827AS flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 234441648 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 314590563 4.2BSD 2048 16384 328 # Cyl 0*- 3120 b:204624 3145968swap # Cyl 3121 - 3323 c: 234441648 0 unused 0 0 # Cyl 0 -232580 d: 231085953 3350592RAID # Cyl 3324 -232575* # === 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... yup Followed these steps. copied everything from /dwv/wd0a to /dev/raid0a ( except the raid.conf file ) entered into single user mode and used disklabel ( m option ) to change the disklabel. rebooted things are fine :-) Do you think this setup is bad actually? Nope... just needs a disklabel change and it should work... Yes!1 it is working Greg :-) Thanks a million! = Kernelized RAIDframe activated raid0 (root): (RAID Level 1) total number of sectors is 231085824 (112834 MB) as root dkcsum: wd0 matches BIOS drive 0x80 dkcsum: wd1 matches BIOS drive 0x81 swapmount: no device = # 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: 200612010, Mod Counter: 964 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: 200612010, Mod Counter: 964 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. # === it did suffer a few uncerimonious reboots due to power failure too :-) recovered all the time by re writing parity! Thankyou so much once again :-) This was great help! Kind Regards siju ==++Full dmesg OpenBSD 4.0 (GENERIC.RAID2) #0: Fri Nov 24 20:28:14 IST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.RAID2 real mem = 1039593472 (1015228K) avail mem = 878211072 (857628K) using 22937 buffers containing 104165376 bytes (101724K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xfc650 (54 entries) bios0: Acer Aspire Series cpu0 at mainbus0: (uniprocessor) cpu0: AMD
Re: raid dmesg output and raidctl -sv output shows differrent status for raidframe mirror on OpenBSD 4.0 amd64
On 3/8/07, Greg Oster [EMAIL PROTECTED] wrote: Siju George writes: In my dmesg at one point it says == Kernelized RAIDframe activated dkcsum: wd0 matches BIOS drive 0x80 dkcsum: wd1 matches BIOS drive 0x81 root on wd0a So this gets printed from autoconf.c but it *shouldn't* since boothowto |= RB_DFLTROOT; in rf_openbsdkintf.c should cause the setroot() function to bail before printing the above So for some reason it's not calling the appropriate bits in rf_buildroothack() in rf_openbsdkintf.c But exactly why, I have no idea... [snip] Could you please shed any light on why my root device is not raid0 but wda0 still? No idea right now.. if you build a kernel with RAIDDEBUG defined and send the dmesg from that, I might be able to provide additional info... alright thankyou :-) here is it. hope it will help you see more into the issue :-) === OpenBSD 4.0 (GENERIC.RAID.DEBUG) #0: Thu Mar 8 16:37:40 IST 2007 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.RAID.DEBUG real mem = 1039593472 (1015228K) avail mem = 878206976 (857624K) using 22937 buffers containing 104165376 bytes (101724K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xfc650 (54 entries) bios0: Acer Aspire Series cpu0 at mainbus0: (uniprocessor) cpu0: AMD Athlon(tm) 64 Processor 3400+, 2193.90 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 ATI RS480 Host rev 0x10 ppb0 at pci0 dev 1 function 0 ATI RS480 PCIE rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Radeon XPRESS 200 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pciide0 at pci0 dev 17 function 0 ATI IXP400 SATA rev 0x80: DMA pciide0: using irq 11 for native-PCI interrupt pciide0: port 0: device present, speed: 1.5Gb/s wd0 at pciide0 channel 0 drive 0: ST3120827AS wd0: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 6 pciide0: port 1: device present, speed: 1.5Gb/s wd1 at pciide0 channel 1 drive 0: ST3120827AS wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd1(pciide0:1:0): using BIOS timings, Ultra-DMA mode 6 pciide1 at pci0 dev 18 function 0 ATI IXP400 SATA rev 0x80: DMA pciide1: using irq 5 for native-PCI interrupt ohci0 at pci0 dev 19 function 0 ATI IXP400 USB rev 0x80: irq 4, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: ATI OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1 at pci0 dev 19 function 1 ATI IXP400 USB rev 0x80: irq 4, version 1.0, legacy support usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: ATI OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0 at pci0 dev 19 function 2 ATI IXP400 USB2 rev 0x80: irq 4 usb2 at ehci0: USB revision 2.0 uhub2 at usb2 uhub2: ATI EHCI root hub, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered piixpm0 at pci0 dev 20 function 0 ATI IXP400 SMBus rev 0x81: SMI iic0 at piixpm0 unknown at iic0 addr 0x2f not configured pciide2 at pci0 dev 20 function 1 ATI IXP400 IDE rev 0x80: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility azalia0 at pci0 dev 20 function 2 ATI IXP450 HD Audio rev 0x01: irq 5 azalia0: host: High Definition Audio rev. 1.0 azalia0: codec: Realtek ALC880 (rev. 8.0), HDA version 1.0 audio0 at azalia0 pcib0 at pci0 dev 20 function 3 ATI IXP400 ISA rev 0x80 ppb1 at pci0 dev 20 function 4 ATI IXP400 PCI rev 0x80 pci2 at ppb1 bus 2 re0 at pci2 dev 3 function 0 Realtek 8169 rev 0x10: irq 5, address 00:16:17:20:2a:a6 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 pchb1 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00 pchb2 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00 pchb3 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00 pchb4 at pci0 dev 24 function 3 AMD AMD64 Misc Cfg rev 0x00 isa0 at pcib0 isadma0 at isa0 com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
Re: raid dmesg output and raidctl -sv output shows differrent status for raidframe mirror on OpenBSD 4.0 amd64
Siju George writes: On 3/8/07, Greg Oster [EMAIL PROTECTED] wrote: Siju George writes: In my dmesg at one point it says == Kernelized RAIDframe activated dkcsum: wd0 matches BIOS drive 0x80 dkcsum: wd1 matches BIOS drive 0x81 root on wd0a So this gets printed from autoconf.c but it *shouldn't* since boothowto |= RB_DFLTROOT; in rf_openbsdkintf.c should cause the setroot() function to bail before printing the above So for some reason it's not calling the appropriate bits in rf_buildroothack() in rf_openbsdkintf.c But exactly why, I have no idea... [snip] Could you please shed any light on why my root device is not raid0 but wda0 still? No idea right now.. if you build a kernel with RAIDDEBUG defined and send the dmesg from that, I might be able to provide additional info... alright thankyou :-) here is it. hope it will help you see more into the issue :-) [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 limit. 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 ?? 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...) Later... Greg Oster
Re: raid dmesg output and raidctl -sv output shows differrent status for raidframe mirror on OpenBSD 4.0 amd64
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 limit. 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? is there any hope of fixing it now? Will the raid be functioning right actually? Do you want me to recreate it with FS_RAID? == # disklabel wd0d # /dev/rwd0d: type: ESDI disk: ESDI/IDE disk label: ST3120827AS flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 234441648 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 314590563 4.2BSD 2048 16384 328 # Cyl 0*- 3120 b:204624 3145968swap # Cyl 3121 - 3323 c: 234441648 0 unused 0 0 # Cyl 0 -232580 d: 231085953 3350592 4.2BSD 2048 16384 328 # Cyl 3324 -232575* # disklabel wd1d # /dev/rwd1d: type: ESDI disk: ESDI/IDE disk label: ST3120827AS flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 16383 total sectors: 234441648 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 314590563 4.2BSD 2048 16384 328 # Cyl 0*- 3120 b:204624 3145968swap # Cyl 3121 - 3323 c: 234441648 0 unused 0 0 # Cyl 0 -232580 d: 231085953 3350592 4.2BSD 2048 16384 328 # Cyl 3324 -232575* # disklabel raid0 # /dev/rraid0c: type: RAID disk: raid label: fictitious flags: bytes/sector: 512 sectors/track: 128 tracks/cylinder: 8 sectors/cylinder: 1024 cylinders: 225669 total sectors: 231085824 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # microseconds track-to-track seek: 0 # microseconds drivedata: 0 16 partitions: # sizeoffset fstype [fsize bsize cpg] a: 3145728 0 4.2BSD 2048 16384 323 # Cyl 0 - 3071 b: 4194304 3145728swap # Cyl 3072 - 7167 c: 231085824 0 unused 0 0 # Cyl 0 -225669* d: 2097152 7340032 4.2BSD 2048 16384 323 # Cyl 7168 - 9215 e: 4194304 9437184 4.2BSD 2048 16384 323 # Cyl 9216 - 13311 f: 12582912 13631488 4.2BSD 2048 16384 323 # Cyl 13312 - 25599 g: 125829120 26214400 4.2BSD 2048 16384 323 # Cyl 25600 -148479 h: 79042304 152043520 4.2BSD 2048 16384 323 # Cyl 148480 -225669* i: 2031616 2097152 unused 0 0 # Cyl 2048 - 4031 j: 2031616 2097152 unused 0 0 # Cyl 2048 - 4031 k: 2031616 2097152 unused 0 0 # Cyl 2048 - 4031 l: 2031616 2097152 unused 0 0 # Cyl 2048 - 4031 # = 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? Do you think this setup is bad actually? Thankyou so much Kind Regards Siju
Re: raid dmesg output and raidctl -sv output shows differrent status for raidframe mirror on OpenBSD 4.0 amd64
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
Re: raid dmesg output and raidctl -sv output shows differrent status for raidframe mirror on OpenBSD 4.0 amd64
On 3/6/07, Greg Oster [EMAIL PROTECTED] wrote: Siju George writes: It's working just fine... just probably telling you a bit more than you really wanted to know :) Later... Greg, Seeing that you work on RAIDFRAME let me dare to ask you one more thing :-) In my dmesg at one point it says == Kernelized RAIDframe activated dkcsum: wd0 matches BIOS drive 0x80 dkcsum: wd1 matches BIOS drive 0x81 root on wd0a Shouldn't the root be on raid0a ? Since the dmesg again shows === raid0 (root) === and raidctl shows = Autoconfig: Yes Root partition: Yes for both drives? I get now Raid 1 running on all partitions except the / partition by the following fstab entries == # cat /etc/fstab /dev/wd0a / ffs rw 1 1 /dev/raid0b none swap sw 0 0 /dev/raid0d /home ffs rw,nodev,nosuid,softdep 1 2 /dev/raid0e /tmp ffs rw,nodev,nosuid,softdep 1 2 /dev/raid0f /usr ffs rw,nodev,softdep 1 2 /dev/raid0g /var ffs rw,nodev,nosuid,softdep 1 2 /dev/raid0h /Backup ffs rw,nodev,nosuid,softdep 1 2 = The kernel configurations I made to compile the Raid Kernel are == # cat /usr/src/sys/arch/amd64/conf/GENERIC.RAID2 # include arch/amd64/conf/GENERIC option RAID_AUTOCONFIG pseudo-device raid4 # === I did do the = raidctl -A root raid0 == command too. Could you please shed any light on why my root device is not raid0 but wda0 still? Thankyou so much ( especially for the simple make file introduction on your website ) kind Regards Siju For my Full dmesg OpenBSD 4.0 (GENERIC.RAID2) #0: Fri Nov 24 20:28:14 IST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.RAID2 real mem = 1039593472 (1015228K) avail mem = 878211072 (857628K) using 22937 buffers containing 104165376 bytes (101724K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xfc650 (54 entries) bios0: Acer Aspire Series cpu0 at mainbus0: (uniprocessor) cpu0: AMD Athlon(tm) 64 Processor 3400+, 2193.94 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 ATI RS480 Host rev 0x10 ppb0 at pci0 dev 1 function 0 ATI RS480 PCIE rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Radeon XPRESS 200 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pciide0 at pci0 dev 17 function 0 ATI IXP400 SATA rev 0x80: DMA pciide0: using irq 11 for native-PCI interrupt pciide0: port 0: device present, speed: 1.5Gb/s wd0 at pciide0 channel 0 drive 0: ST3120827AS wd0: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 6 pciide0: port 1: device present, speed: 1.5Gb/s wd1 at pciide0 channel 1 drive 0: ST3120827AS wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd1(pciide0:1:0): using BIOS timings, Ultra-DMA mode 6 pciide1 at pci0 dev 18 function 0 ATI IXP400 SATA rev 0x80: DMA pciide1: using irq 5 for native-PCI interrupt ohci0 at pci0 dev 19 function 0 ATI IXP400 USB rev 0x80: irq 4, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: ATI OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1 at pci0 dev 19 function 1 ATI IXP400 USB rev 0x80: irq 4, version 1.0, legacy support usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: ATI OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0 at pci0 dev 19 function 2 ATI IXP400 USB2 rev 0x80: irq 4 usb2 at ehci0: USB revision 2.0 uhub2 at usb2 uhub2: ATI EHCI root hub, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered piixpm0 at pci0 dev 20 function 0 ATI IXP400 SMBus rev 0x81: SMI iic0 at piixpm0 unknown at iic0 addr 0x2f not configured pciide2 at pci0 dev 20 function 1 ATI IXP400 IDE rev 0x80: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility azalia0 at pci0 dev 20 function 2 ATI IXP450 HD Audio rev 0x01: irq 5 azalia0: host: High Definition Audio rev. 1.0 azalia0: codec: Realtek ALC880 (rev. 8.0), HDA version 1.0
Re: raid dmesg output and raidctl -sv output shows differrent status for raidframe mirror on OpenBSD 4.0 amd64
Siju George writes: On 3/6/07, Greg Oster [EMAIL PROTECTED] wrote: Siju George writes: It's working just fine... just probably telling you a bit more than you really wanted to know :) Later... Greg, Seeing that you work on RAIDFRAME let me dare to ask you one more thing :-) In my dmesg at one point it says == Kernelized RAIDframe activated dkcsum: wd0 matches BIOS drive 0x80 dkcsum: wd1 matches BIOS drive 0x81 root on wd0a Shouldn't the root be on raid0a ? I don't know what OpenBSD is in with respect to root-on-RAID. Since the dmesg again shows === raid0 (root) === and raidctl shows = Autoconfig: Yes Root partition: Yes for both drives? what does 'mount' say for '/'? RAIDframe used to do a bit of 'hijacking' of the boot disk in order to get itself in as /, but I don't know the details in OpenBSD... [snip] Could you please shed any light on why my root device is not raid0 but wda0 still? That part is specific to OpenBSD... Thankyou so much ( especially for the simple make file introduction on your website ) kind Regards Siju For my Full dmesg OpenBSD 4.0 (GENERIC.RAID2) #0: Fri Nov 24 20:28:14 IST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC. RAID2 real mem = 1039593472 (1015228K) avail mem = 878211072 (857628K) using 22937 buffers containing 104165376 bytes (101724K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xfc650 (54 entries) bios0: Acer Aspire Series cpu0 at mainbus0: (uniprocessor) cpu0: AMD Athlon(tm) 64 Processor 3400+, 2193.94 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36 ,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 ATI RS480 Host rev 0x10 ppb0 at pci0 dev 1 function 0 ATI RS480 PCIE rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Radeon XPRESS 200 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pciide0 at pci0 dev 17 function 0 ATI IXP400 SATA rev 0x80: DMA pciide0: using irq 11 for native-PCI interrupt pciide0: port 0: device present, speed: 1.5Gb/s wd0 at pciide0 channel 0 drive 0: ST3120827AS wd0: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 6 pciide0: port 1: device present, speed: 1.5Gb/s wd1 at pciide0 channel 1 drive 0: ST3120827AS wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd1(pciide0:1:0): using BIOS timings, Ultra-DMA mode 6 pciide1 at pci0 dev 18 function 0 ATI IXP400 SATA rev 0x80: DMA pciide1: using irq 5 for native-PCI interrupt ohci0 at pci0 dev 19 function 0 ATI IXP400 USB rev 0x80: irq 4, version 1.0, legacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: ATI OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1 at pci0 dev 19 function 1 ATI IXP400 USB rev 0x80: irq 4, version 1.0, legacy support usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: ATI OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0 at pci0 dev 19 function 2 ATI IXP400 USB2 rev 0x80: irq 4 usb2 at ehci0: USB revision 2.0 uhub2 at usb2 uhub2: ATI EHCI root hub, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered piixpm0 at pci0 dev 20 function 0 ATI IXP400 SMBus rev 0x81: SMI iic0 at piixpm0 unknown at iic0 addr 0x2f not configured pciide2 at pci0 dev 20 function 1 ATI IXP400 IDE rev 0x80: DMA, channel 0 configured to compatibility, channel 1 configured to compatibility azalia0 at pci0 dev 20 function 2 ATI IXP450 HD Audio rev 0x01: irq 5 azalia0: host: High Definition Audio rev. 1.0 azalia0: codec: Realtek ALC880 (rev. 8.0), HDA version 1.0 audio0 at azalia0 pcib0 at pci0 dev 20 function 3 ATI IXP400 ISA rev 0x80 ppb1 at pci0 dev 20 function 4 ATI IXP400 PCI rev 0x80 pci2 at ppb1 bus 2 re0 at pci2 dev 3 function 0 Realtek 8169 rev 0x10: irq 5, address 00:16:17:20:2a:a6 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 2 pchb1 at pci0 dev 24 function 0 AMD AMD64 HyperTransport rev 0x00 pchb2 at pci0 dev 24 function 1 AMD AMD64 Address Map rev 0x00 pchb3 at pci0 dev 24 function 2 AMD AMD64 DRAM Cfg rev 0x00 pchb4 at pci0 dev 24 function 3 AMD AMD64 Misc
Re: raid dmesg output and raidctl -sv output shows differrent status for raidframe mirror on OpenBSD 4.0 amd64
Siju George writes: On 3/6/07, Greg Oster [EMAIL PROTECTED] wrote: Siju George writes: It's working just fine... just probably telling you a bit more than you really wanted to know :) Later... Greg, Seeing that you work on RAIDFRAME let me dare to ask you one more thing :-) Bah... I hit the Send button on that last email sooner than I wanted to :( In my dmesg at one point it says == Kernelized RAIDframe activated dkcsum: wd0 matches BIOS drive 0x80 dkcsum: wd1 matches BIOS drive 0x81 root on wd0a So this gets printed from autoconf.c but it *shouldn't* since boothowto |= RB_DFLTROOT; in rf_openbsdkintf.c should cause the setroot() function to bail before printing the above So for some reason it's not calling the appropriate bits in rf_buildroothack() in rf_openbsdkintf.c But exactly why, I have no idea... [snip] Could you please shed any light on why my root device is not raid0 but wda0 still? No idea right now.. if you build a kernel with RAIDDEBUG defined and send the dmesg from that, I might be able to provide additional info... Thankyou so much ( especially for the simple make file introduction on your website ) :) Later... Greg Oster
raid dmesg output and raidctl -sv output shows differrent status for raidframe mirror on OpenBSD 4.0 amd64
Hi, The dmesg Output Shows Clean: Yes for both Raid Components as shown below 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: 820 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: 820 Clean: Yes Status: 0 raid0 (root) = but raidctl shows Clean: No as shown below Could Some one tell me why this is so? it is the same state even after reboots. Which one should i beleive? Is the Raid not working properly? = # 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: 200612010, Mod Counter: 825 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: 200612010, Mod Counter: 825 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. # = Thankyou so much :-) Kind Regards Siju For the full dmesg == # dmesg OpenBSD 4.0 (GENERIC.RAID2) #0: Fri Nov 24 20:28:14 IST 2006 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.RAI D2 real mem = 1039593472 (1015228K) avail mem = 878211072 (857628K) using 22937 buffers containing 104165376 bytes (101724K) of memory mainbus0 (root) bios0 at mainbus0: SMBIOS rev. 2.3 @ 0xfc650 (54 entries) bios0: Acer Aspire Series cpu0 at mainbus0: (uniprocessor) cpu0: AMD Athlon(tm) 64 Processor 3400+, 2193.90 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF LUSH,MMX,FXSR,SSE,SSE2,SSE3,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB 64b/line 1 6-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 32 4KB entries fully associative, 8 4MB entries fully associative pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 ATI RS480 Host rev 0x10 ppb0 at pci0 dev 1 function 0 ATI RS480 PCIE rev 0x00 pci1 at ppb0 bus 1 vga1 at pci1 dev 5 function 0 ATI Radeon XPRESS 200 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) pciide0 at pci0 dev 17 function 0 ATI IXP400 SATA rev 0x80: DMA pciide0: using irq 11 for native-PCI interrupt pciide0: port 0: device present, speed: 1.5Gb/s wd0 at pciide0 channel 0 drive 0: ST3120827AS wd0: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 6 pciide0: port 1: device present, speed: 1.5Gb/s wd1 at pciide0 channel 1 drive 0: ST3120827AS wd1: 16-sector PIO, LBA48, 114473MB, 234441648 sectors wd1(pciide0:1:0): using BIOS timings, Ultra-DMA mode 6 pciide1 at pci0 dev 18 function 0 ATI IXP400 SATA rev 0x80: DMA pciide1: using irq 5 for native-PCI interrupt ohci0 at pci0 dev 19 function 0 ATI IXP400 USB rev 0x80: irq 4, version 1.0, l egacy support usb0 at ohci0: USB revision 1.0 uhub0 at usb0 uhub0: ATI OHCI root hub, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1 at pci0 dev 19 function 1 ATI IXP400 USB rev 0x80: irq 4, version 1.0, l egacy support usb1 at ohci1: USB revision 1.0 uhub1 at usb1 uhub1: ATI OHCI root hub, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0 at pci0 dev 19 function 2 ATI IXP400 USB2 rev 0x80: irq 4 usb2 at ehci0: USB revision 2.0 uhub2 at usb2 uhub2: ATI EHCI root hub, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered piixpm0 at pci0 dev 20 function 0 ATI IXP400 SMBus rev 0x81: SMI iic0 at piixpm0 unknown at iic0 addr 0x2f not configured pciide2 at pci0 dev 20 function 1 ATI IXP400 IDE rev 0x80: DMA, channel 0 conf igured to compatibility, channel 1 configured to compatibility azalia0 at pci0 dev 20 function 2 ATI IXP450 HD Audio rev 0x01: irq 5 azalia0: host: High Definition Audio rev. 1.0 azalia0: codec: Realtek ALC880 (rev. 8.0), HDA version 1.0 audio0 at azalia0 pcib0 at pci0 dev 20 function 3 ATI IXP400 ISA rev 0x80 ppb1
Re: raid dmesg output and raidctl -sv output shows differrent status for raidframe mirror on OpenBSD 4.0 amd64
Siju George writes: Hi, The dmesg Output Shows Clean: Yes for both Raid Components as shown below 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: 820 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: 820 Clean: Yes Status: 0 raid0 (root) = but raidctl shows Clean: No as shown below Could Some one tell me why this is so? it is the same state even after reboots. The value Yes or No comes directly from the component labels on the disks. If the parity is known good (i.e. the set is clean) when the RAID sets are unconfigured (actually, when the last open partition is unmounted), then the value in the component labels will be set to Yes. When a RAID set is configured and a partition is opened/mounted, the value is the component labels will be set to no. And so unless things get unmounted/unconfigured correctly, the value will remain at no until the parity gets checked. What you are seeing here is: a) the values reported by dmesg are from *before* any partitions on raid0 get opened. So if the RAID set was known clean, you'll see a value of Yes printed for each component, because that's what they got set to at the last shutdown/unmount/unconfigure/etc. b) the values reported by raidctl are from *after* a partition on raid0 has been opened (even 'raidctl -vs raid0' ends up opening /dev/raid0c or whatever, resulting in that clean flag being changed from Yes to No). So it will always say No here, since that will be the current value in the component labels. Which one should i beleive? Both of them :) They are both correct for the time at which they are examining the datapoint in question. That said, the line to really care about is this one: Parity status: clean Is the Raid not working properly? It's working just fine... just probably telling you a bit more than you really wanted to know :) Later... Greg Oster
Re: raid dmesg output and raidctl -sv output shows differrent status for raidframe mirror on OpenBSD 4.0 amd64
On 3/6/07, Greg Oster [EMAIL PROTECTED] wrote: Siju George writes: Is the Raid not working properly? It's working just fine... just probably telling you a bit more than you really wanted to know :) Thanks a million Greg :-) I really appreciate your Detailed reply :-)) Kind Regards Siju
