July 31, 201114 yr parity [_??u?T?L?L`k:_ 0°C 1,953,514,552 - - - - Command area Stopped. Upgrading parity. Start will bring the array on-line and start Parity-Sync. I'm sure I want to do this Spin Up will immediately spin up all disks. Spin Down will immediately spin down all disks. Reboot will activate a system reset. Power down will activate a clean power down. My parity drive says that on the http://tower. What is wrong with it? I deleted a line out of my boot/go script (to remove sabnzbd) and now this has happened!
July 31, 201114 yr parity [_??u?T?L?L`k:_ 0°C 1,953,514,552 - - - - Command area Stopped. Upgrading parity. Start will bring the array on-line and start Parity-Sync. I'm sure I want to do this Spin Up will immediately spin up all disks. Spin Down will immediately spin down all disks. Reboot will activate a system reset. Power down will activate a clean power down. My parity drive says that on the http://tower. What is wrong with it? I deleted a line out of my boot/go script (to remove sabnzbd) and now this has happened! we don't know. You did not attach a syslog.
July 31, 201114 yr heres a syslog in doc format. Looks like two different drives have errors, or one of them is making the other look bad because it shares the same disk controller. I can't give any more guidance, but please post the syslog as a .txt file. Can't read a .doc.
July 31, 201114 yr Author heres .txt format I hope the disk isn't ruined. I won't mind reformatting it etc. but returns are so annoying! syslog.txt
July 31, 201114 yr heres .txt format I hope the disk isn't ruined. I won't mind reformatting it etc. but returns are so annoying! You have two issues. One with /dev/sdc It seems to be disabled due to CRC errors and an inability of the disk controller to communicate with the disk: Aug 1 03:31:20 Tower kernel: sd 1:0:0:0: [sda] Attached SCSI disk Aug 1 03:31:20 Tower kernel: atiixp 0000:00:14.1: IDE controller (0x1002:0x439c rev 0x00) Aug 1 03:31:20 Tower kernel: ATIIXP_IDE 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Aug 1 03:31:20 Tower kernel: atiixp 0000:00:14.1: not 100%% native mode: will probe irqs later Aug 1 03:31:20 Tower kernel: ide0: BM-DMA at 0xff00-0xff07 Aug 1 03:31:20 Tower kernel: ide1: BM-DMA at 0xff08-0xff0f Aug 1 03:31:20 Tower kernel: Probing IDE interface ide0... Aug 1 03:31:20 Tower kernel: Probing IDE interface ide1... Aug 1 03:31:20 Tower kernel: hdd: Maxtor 6L250R0, ATA DISK drive Aug 1 03:31:20 Tower kernel: hdd: host max PIO4 wanted PIO255(auto-tune) selected PIO4 Aug 1 03:31:20 Tower kernel: hdd: UDMA/100 mode selected Aug 1 03:31:20 Tower kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Aug 1 03:31:20 Tower kernel: ide1 at 0x170-0x177,0x376 on irq 15 Aug 1 03:31:20 Tower kernel: ata2.00: exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen Aug 1 03:31:20 Tower kernel: ata2.00: irq_stat 0x08000000, interface fatal error Aug 1 03:31:20 Tower kernel: ata2: SError: { UnrecovData HostInt 10B8B BadCRC } Aug 1 03:31:20 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Aug 1 03:31:20 Tower kernel: ata2.00: cmd 60/08:00:a0:88:e0/00:00:e8:00:00/40 tag 0 ncq 4096 in Aug 1 03:31:20 Tower kernel: res 50/00:08:a0:88:e0/00:00:e8:00:00/40 Emask 0x50 (ATA bus error) Aug 1 03:31:20 Tower kernel: ata2.00: status: { DRDY } Aug 1 03:31:20 Tower kernel: ata2: hard resetting link Aug 1 03:31:20 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 1 03:31:20 Tower kernel: ata2.00: configured for UDMA/133 Aug 1 03:31:20 Tower kernel: ata2: EH complete Aug 1 03:31:20 Tower kernel: ata2.00: exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen Aug 1 03:31:20 Tower kernel: ata2.00: irq_stat 0x08000000, interface fatal error Aug 1 03:31:20 Tower kernel: ata2: SError: { UnrecovData HostInt 10B8B BadCRC } Aug 1 03:31:20 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Aug 1 03:31:20 Tower kernel: ata2.00: cmd 60/08:00:a0:88:e0/00:00:e8:00:00/40 tag 0 ncq 4096 in Aug 1 03:31:20 Tower kernel: res 50/00:08:a0:88:e0/00:00:e8:00:00/40 Emask 0x50 (ATA bus error) Aug 1 03:31:20 Tower kernel: ata2.00: status: { DRDY } Aug 1 03:31:20 Tower kernel: ata2: hard resetting link Aug 1 03:31:20 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 1 03:31:20 Tower kernel: ata2.00: configured for UDMA/133 Aug 1 03:31:20 Tower kernel: ata2: EH complete Aug 1 03:31:20 Tower kernel: ata2.00: exception Emask 0x50 SAct 0x3 SErr 0x280900 action 0x6 frozen Aug 1 03:31:20 Tower kernel: ata2.00: irq_stat 0x08000000, interface fatal error Aug 1 03:31:20 Tower kernel: ata2: SError: { UnrecovData HostInt 10B8B BadCRC } Aug 1 03:31:20 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Aug 1 03:31:20 Tower kernel: ata2.00: cmd 60/40:00:20:00:00/00:00:00:00:00/40 tag 0 ncq 32768 in Aug 1 03:31:20 Tower kernel: res 50/00:c0:60:00:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Aug 1 03:31:20 Tower kernel: ata2.00: status: { DRDY } Aug 1 03:31:20 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Aug 1 03:31:20 Tower kernel: ata2.00: cmd 60/c0:08:60:00:00/00:00:00:00:00/40 tag 1 ncq 98304 in Aug 1 03:31:20 Tower kernel: res 50/00:c0:60:00:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Aug 1 03:31:20 Tower kernel: ata2.00: status: { DRDY } Aug 1 03:31:20 Tower kernel: ata2: hard resetting link Aug 1 03:31:20 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 1 03:31:20 Tower kernel: ata2.00: configured for UDMA/133 Aug 1 03:31:20 Tower kernel: ata2: EH complete Aug 1 03:31:20 Tower kernel: ata2: limiting SATA link speed to 1.5 Gbps Aug 1 03:31:20 Tower kernel: ata2.00: exception Emask 0x50 SAct 0x3 SErr 0x280900 action 0x6 frozen Aug 1 03:31:20 Tower kernel: ata2.00: irq_stat 0x08000000, interface fatal error Aug 1 03:31:20 Tower kernel: ata2: SError: { UnrecovData HostInt 10B8B BadCRC } Aug 1 03:31:20 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Aug 1 03:31:20 Tower kernel: ata2.00: cmd 60/c0:00:60:00:00/00:00:00:00:00/40 tag 0 ncq 98304 in Aug 1 03:31:20 Tower kernel: res 50/00:40:20:00:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Aug 1 03:31:20 Tower kernel: ata2.00: status: { DRDY } Aug 1 03:31:20 Tower kernel: ata2.00: failed command: READ FPDMA QUEUED Aug 1 03:31:20 Tower kernel: ata2.00: cmd 60/40:08:20:00:00/00:00:00:00:00/40 tag 1 ncq 32768 in Aug 1 03:31:20 Tower kernel: res 50/00:40:20:00:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Aug 1 03:31:20 Tower kernel: ata2.00: status: { DRDY } Aug 1 03:31:20 Tower kernel: ata2: hard resetting link Aug 1 03:31:20 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Aug 1 03:31:20 Tower kernel: scsi 0:0:0:0: Direct-Access Corsair Voyager 3.0 1.00 PQ: 0 ANSI: 5 Aug 1 03:31:20 Tower kernel: usb-storage: device scan complete Aug 1 03:31:20 Tower kernel: sd 0:0:0:0: [sdc] 15687680 512-byte logical blocks: (8.03 GB/7.48 GiB) Aug 1 03:31:20 Tower kernel: sd 0:0:0:0: [sdc] Write Protect is off Aug 1 03:31:20 Tower kernel: sd 0:0:0:0: [sdc] Mode Sense: 03 00 00 00 Aug 1 03:31:20 Tower kernel: sd 0:0:0:0: [sdc] Assuming drive cache: write through Aug 1 03:31:20 Tower kernel: sd 0:0:0:0: [sdc] Assuming drive cache: write through Aug 1 03:31:20 Tower kernel: sdc: sdc1 Aug 1 03:31:20 Tower kernel: sd 0:0:0:0: [sdc] Assuming drive cache: write through Aug 1 03:31:20 Tower kernel: sd 0:0:0:0: [sdc] Attached SCSI removable disk Aug 1 03:31:20 Tower kernel: ata2.00: qc timeout (cmd 0xec) Aug 1 03:31:20 Tower kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) Aug 1 03:31:20 Tower kernel: ata2.00: revalidation failed (errno=-5) Aug 1 03:31:20 Tower kernel: ata2: hard resetting link Aug 1 03:31:20 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Aug 1 03:31:20 Tower kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x100) Aug 1 03:31:20 Tower kernel: ata2.00: revalidation failed (errno=-5) Aug 1 03:31:20 Tower kernel: ata2: hard resetting link Aug 1 03:31:20 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Aug 1 03:31:20 Tower kernel: ata2.00: qc timeout (cmd 0xec) Aug 1 03:31:20 Tower kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) Aug 1 03:31:20 Tower kernel: ata2.00: revalidation failed (errno=-5) Aug 1 03:31:20 Tower kernel: ata2.00: disabled The other is /dev/sdb with many failed IO requests: Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 20 00 00 40 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 32 Aug 1 03:31:20 Tower kernel: Buffer I/O error on device sdb, logical block 4 Aug 1 03:31:20 Tower kernel: Buffer I/O error on device sdb, logical block 5 Aug 1 03:31:20 Tower kernel: Buffer I/O error on device sdb, logical block 6 Aug 1 03:31:20 Tower kernel: Buffer I/O error on device sdb, logical block 7 Aug 1 03:31:20 Tower kernel: Buffer I/O error on device sdb, logical block 8 Aug 1 03:31:20 Tower kernel: Buffer I/O error on device sdb, logical block 9 Aug 1 03:31:20 Tower kernel: Buffer I/O error on device sdb, logical block 10 Aug 1 03:31:20 Tower kernel: Buffer I/O error on device sdb, logical block 11 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 60 00 00 c0 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 96 Aug 1 03:31:20 Tower kernel: Buffer I/O error on device sdb, logical block 12 Aug 1 03:31:20 Tower kernel: Buffer I/O error on device sdb, logical block 13 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 20 00 00 08 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 32 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 20 00 00 08 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 32 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 20 00 00 08 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 32 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 20 00 00 08 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 32 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 20 00 00 08 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 32 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 20 00 00 08 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 32 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 20 00 00 08 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 32 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 20 00 00 08 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 32 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 20 00 00 08 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 32 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 3f 00 00 20 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 63 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00 Aug 1 03:31:20 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 00 00 00 3f 00 00 08 00 Aug 1 03:31:20 Tower kernel: end_request: I/O error, dev sdb, sector 63 Di they share the same disk controller? or cables? Or power splitter? I would suspect noisy cabling with CRC errors, or a noisy power supply? Is it adaquate for your disks?
July 31, 201114 yr Author sda and sdb share the same power splitter. sdc has a different power source. what shall i do for my next move? btw this all has coincided with me trying to uninstall SABnzbd from my cache drive (i think in the wrong way). shall i format my parity drive, preclear it and go again? i want to reformat my old drive (sdc) and format my usb flash unraid anyway (so i can use the umenu packages for SAB/SB/CP)l.
July 31, 201114 yr sda and sdb share the same power splitter. sdc has a different power source. what shall i do for my next move? btw this all has coincided with me trying to uninstall SABnzbd from my cache drive (i think in the wrong way). shall i format my parity drive, preclear it and go again? i want to reformat my old drive (sdc) and format my usb flash unraid anyway (so i can use the umenu packages for SAB/SB/CP)l. For this exercise, forget you ever learned the words "format" or "preclear" Don't do either. You must first be able to communicate with the drives. Right now, power and cabling are suspect.
July 31, 201114 yr Author Okay, so I should check the power and cabling of the two drives? What do I check for? I'm pretty confused. I have not moved the computer or anything for cables to come loose and its been working fine for a few days.
July 31, 201114 yr Author thank you! opened the box up, did the wires separatley rather than a loop and its all good again.
Archived
This topic is now archived and is closed to further replies.