Re: OBSD 4.1 drops to ddb with cdd0: error 22 on component 0 (and 1 (mirror))
On Sat, 2007-06-16 at 15:00 +0200, Marius Hooge wrote: Of course I did.. I just replaced the PSU with a spare one i got lying around. - It didn't work out. (Can a PSU even cause such errors?) A failing PSU is perhaps the least obvious hardware failure of all, because it looks like some combination of everything else. Been there, done that. -- Shawn K. Quinn [EMAIL PROTECTED]
Re: OBSD 4.1 drops to ddb with cdd0: error 22 on component 0 (and 1 (mirror))
Hi Maxim, Thanks for your suggestion, but I have 'enough' RAM installed and didn't configure a swap partition. There's only one partition on the mirror and I use it as /home. I did more tests and I figured out that one of my mirrored drives causes read errors, which in turn causes the CCD/kernel to panic. Marius Maxim Belooussov wrote: Hi Marius, My OpenBSD 4.1 Generic i386 box occasionally freezes completely, without any warning. Sorry for a dumb question, but is your swap located on raid? If yes, could system have a problem trying to mirror it? (disclaimer: I'm just a user, not developer, + very limited experience with raid setups) Maxim
Re: OBSD 4.1 drops to ddb with cdd0: error 22 on component 0 (and 1 (mirror))
Brian A. Seklecki wrote: This is the expected behavior for a failure on a CCD component. Try In this case, is there a difference between expected and desired behavior? cutting the SATA cable to a live system some time; watch the kernel panic there as well. Suddenly it cant stat() / or read/write from swap. Maybe this should be mentioned in the FAQ. (I expected it to run with one device and attract the admins/roots attention in a another way. In my case, the only way to recover was a hard reset.) You're playing with fire with CCD anyway: RAID0. The stuff in 4.1 wasn't touched for months...6, 10, 11, 11, look at the time between commits. There's some new recent activity. Things that old don't have to be bad..? At least I thought/was told so. Try RAIDFrame w/ raid0 for a little-more-active development. I considered raid frame, too, but didn't want to build a new kernel. But I'll give it a shot. Thank you. ~BAS Marius
Re: OBSD 4.1 drops to ddb with cdd0: error 22 on component 0 (and 1 (mirror))
This is the expected behavior for a failure on a CCD component. Try cutting the SATA cable to a live system some time; watch the kernel panic there as well. Suddenly it cant stat() / or read/write from swap. You're playing with fire with CCD anyway: RAID0. The stuff in 4.1 wasn't touched for months...6, 10, 11, 11, look at the time between commits. There's some new recent activity. Try RAIDFrame w/ raid0 for a little-more-active development. ~BAS On Thu, 2007-06-14 at 15:56 +0200, Marius Hooge wrote: Hi, I don't know how to handle this: My OpenBSD 4.1 Generic i386 box occasionally freezes completely, without any warning. No Ctrl+Mod1+F1 or any other key-combination, no ssh or ping works. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
Re: OBSD 4.1 drops to ddb with cdd0: error 22 on component 0 (and 1 (mirror))
On 6/16/07, Marius Hooge [EMAIL PROTECTED] wrote: Can at least someone tell me, why I get no replies? probably because nobody can help. sometimes things don't work out.
Re: OBSD 4.1 drops to ddb with cdd0: error 22 on component 0 (and 1 (mirror))
Can at least someone tell me, why I get no replies? (Is it because I mentioned rtorrent or because I didn't buy the cd-set from the last release? Or should I start with a troll next time? - I don't get it. I read every manual I could find regarding that issue and used Google for hours without finding anything useful. Yet I realize that nobody is entitled to get an answer..?) Sorry for the noise.
Re: OBSD 4.1 drops to ddb with cdd0: error 22 on component 0 (and 1 (mirror))
On 6/14/07, Marius Hooge [EMAIL PROTECTED] wrote: I issued trace and ps and... don't have a clue what to do now. I considered overheating of my CDD-Mirror, but smartctl reports below 40 degrees C. Have you considered PSU or other hardware failure? -- ach
Re: OBSD 4.1 drops to ddb with cdd0: error 22 on component 0 (and 1 (mirror))
Have you considered PSU or other hardware failure? Of course I did.. I just replaced the PSU with a spare one i got lying around. - It didn't work out. (Can a PSU even cause such errors?) I dunno, but I think replacing every single component one at a time is the last way I _should_ go? I'll do a full test with smartmontools later, but it shouldn't hang itself 'just' because of some write failure, should it? Again, I've just became comfortable *using* OpenBSD - but as far as I understand, is the fact that it dropped to ddb a prove for a bug? Should I use sendbug(1)? What do you suggest?
OBSD 4.1 drops to ddb with cdd0: error 22 on component 0 (and 1 (mirror))
Hi, I don't know how to handle this: My OpenBSD 4.1 Generic i386 box occasionally freezes completely, without any warning. No Ctrl+Mod1+F1 or any other key-combination, no ssh or ping works. This happened several times over the past 3 days. The last time, I left it at ttyC0 - nothing happened. About ~30min after I started rtorrent it dropped to ddb with these lines: ccd0: error 22 on component 0 ccd0: error 22 on component 1 (mirror) [..] I issued trace and ps and... don't have a clue what to do now. I considered overheating of my CDD-Mirror, but smartctl reports below 40 degrees C. Could a fdisk-misconfiguration cause this kind of errors? Disk failure? Thanks in advance for anything that could help! Marius Here's the dmesg: (I know it has dublicate lines, but I rather leave it as it is, instead of cutting out something important..) x10: irq 10, address 00:c0:df:07:72:dd rlphy0 at rl0 phy 0: RTL internal PHY uhci0 at pci0 dev 16 function 0 VIA VT83C572 USB rev 0x80: irq 11 usb0 at uhci0: USB revision 1.0 uhub0 at usb0 uhub0: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1 at pci0 dev 16 function 1 VIA VT83C572 USB rev 0x80: irq 11 usb1 at uhci1: USB revision 1.0 uhub1 at usb1 uhub1: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2 at pci0 dev 16 function 2 VIA VT83C572 USB rev 0x80: irq 5 usb2 at uhci2: USB revision 1.0 uhub2 at usb2 uhub2: VIA UHCI root hub, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0 at pci0 dev 16 function 3 VIA VT6202 USB rev 0x82: irq 10 usb3 at ehci0: USB revision 2.0 uhub3 at usb3 uhub3: VIA EHCI root hub, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered viapm0 at pci0 dev 17 function 0 VIA VT8235 ISA rev 0x00 iic0 at viapm0 iic0: addr 0x2f 00=00 02=0f 03=00 04=00 06=0f 07=00 08=00 0a=06 0b=00 0c=00 0d=07 0e=84 0f=00 10=c0 11=11 12=00 13=60 pciide0 at pci0 dev 17 function 1 VIA VT82C571 IDE rev 0x06: ATA133, channel 0 configured to compatibility, channel 1 configured to compatibility atapiscsi0 at pciide0 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: TSSTcorp, CD/DVDW TS-H552B, TS03 SCSI0 5/cdrom removable wd0 at pciide0 channel 0 drive 1: CF 8GB wd0: 1-sector PIO, LBA, 7935MB, 16250976 sectors cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 wd0(pciide0:0:1): using PIO mode 4, DMA mode 2 wd1 at pciide0 channel 1 drive 0: SAMSUNG SP1654N wd1: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd2 at pciide0 channel 1 drive 1: SAMSUNG SP1613N wd2: 16-sector PIO, LBA48, 152627MB, 312581808 sectors wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 5 wd2(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 5 auvia0 at pci0 dev 17 function 5 VIA VT8233 AC97 rev 0x50: irq 5 ac97: codec id 0x414c4720 (Avance Logic ALC650) ac97: codec features 20 bit DAC, 18 bit ADC, Realtek 3D audio0 at auvia0 isa0 at mainbus0 isadma0 at isa0 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 pms0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pms0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 lm0 at isa0 port 0x290/8: W83697HF npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask ef65 netmask ef65 ttymask ffe7 pctr: user-level cycle counter enabled mtrr: Pentium Pro MTRR support dkcsum: wd0 matches BIOS drive 0x80 dkcsum: wd1 matches BIOS drive 0x81 dkcsum: wd2 matches BIOS drive 0x82 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 WARNING: / was not properly unmounted ccd0: error 22 on component 0 ccd0: error 22 on component 1 (mirror) ccd0: error 22 on component 0 panic: biodone already Stopped at Debugger+0x4: leave RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb Debugger(127fff30,0,200,d7c7f6a4,40) at Debugger+0x4 panic(d067d5ae,d194c4d4,4b2ca,d7c7f6a4,2000) at panic+0x63 biodone(d7c7f6a4,d194c400,d190fb50,0,d074f9c0) at biodone+0xdb wdstrategy(d7c7f6a4,2,e92929f0,d032e15d,3e00) at wdstrategy+0x87 spec_strategy(e92929e8,1,0,0,127fff20) at spec_strategy+0x33 spec_vnoperate(e92929e8,200,e9292a30,d030e477,d0738dc0) at spec_vnoperate+0x16 VOP_STRATEGY(d7c7f6a4,d1afea50,1,1) at VOP_STRATEGY+0x25 ccdstart(d195b000,d7f4e360,d1975500,0,0) at ccdstart+0x19a ccdstrategy(d7f4e360,d196d000,d7ec7060,0,0) at ccdstrategy+0x84 spec_strategy(e9292ae8,d195594c,d194d5a8,e9292ac4,d048ac4e) at spec_strategy+0x33 spec_vnoperate(e9292ae8,d194d000,1,0,0) at spec_vnoperate+0x16 ufs_strategy(e9292ae8,e9292b9c,6401,d194d810,d0738dc0) at
