November 3, 200916 yr When I run a manual parity check is was very slow only some kb :-( :-( and there are lot of errors in the logfile, can some guru here look at this and see what problem there are ? Byt the first parity disc was successfully, I think EDIT Some data of the system MB: Gigabyte MA74GM-S2H AMD ATHLON II X2 245 Socket AM3 Kingston 2GB DDR2 800MHz OK parity /dev/sda WDC_WD15EADS-00S2B0_WD-WCAVY0802799 OK /dev/md1 /mnt/disk1 /dev/sdb WDC_WD10EADS-00L5B1_WD-WCAU4D312833 OK /dev/md2 /mnt/disk2 /dev/sdc SAMSUNG_HD501LJ_S0MUJ1FPB81643 OK /dev/md3 /mnt/disk3 /dev/sdd SAMSUNG_HD103UJ_S13PJ1KQ612827 OK /dev/md4 /mnt/disk4 /dev/hdc WDC_WD15EADS-00R6B0_WD-WCAVY0164770 The attached file is a winrar file that I changed the extension to .zip EDIT I reboot the system and now is doing a Parity-Check at 50,722 KB/sec, so it's looks OK, but I hope this will fix all the errors, or should I do something more after this to be sure everything is good ? Running server : version: 4.5-beta7
November 3, 200916 yr When I run a manual parity check is was very slow only some kb :-( :-( and there are lot of errors in the logfile, can some guru here look at this and see what problem there are ? Byt the first parity disc was successfully, I think EDIT Some data of the system MB: Gigabyte MA74GM-S2H AMD ATHLON II X2 245 Socket AM3 Kingston 2GB DDR2 800MHz OK parity /dev/sda WDC_WD15EADS-00S2B0_WD-WCAVY0802799 OK /dev/md1 /mnt/disk1 /dev/sdb WDC_WD10EADS-00L5B1_WD-WCAU4D312833 OK /dev/md2 /mnt/disk2 /dev/sdc SAMSUNG_HD501LJ_S0MUJ1FPB81643 OK /dev/md3 /mnt/disk3 /dev/sdd SAMSUNG_HD103UJ_S13PJ1KQ612827 OK /dev/md4 /mnt/disk4 /dev/hdc WDC_WD15EADS-00R6B0_WD-WCAVY0164770 The attached file is a winrar file that I changed the extension to .zip EDIT I reboot the system and now is doing a Parity-Check at 50,722 KB/sec, so it's looks OK, but I hope this will fix all the errors, or should I do something more after this to be sure everything is good ? Running server : version: 4.5-beta7 Your disk4 was failing, and being reset, and failing, being reset, failing, etc. It had been downgraded to PIO mode in an attempt to make it readable. You should suspect the cable used to connect to it first, and the drive second. This is the disk: Nov 2 22:13:16 Tower kernel: md: import disk4: [22,0] (hdc) WDC WD15EADS-00R6B0 WD-WCAVY0164770 offset: 63 size: 1465138552 The errors start soon thereafter: Nov 3 07:22:39 Tower kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274071, sector=2930274071 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x25 Nov 3 07:22:39 Tower kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274071, sector=2930274071 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x25 Nov 3 07:22:39 Tower kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274071, sector=2930274071 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x25 Nov 3 07:22:39 Tower kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274071, sector=2930274071 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x25 Nov 3 07:22:39 Tower kernel: hdc: DMA disabled Nov 3 07:22:39 Tower kernel: ide1: reset: success Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274071, sector=2930274071 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x29 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274071, sector=2930274071 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x29 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274071, sector=2930274071 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x29 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274071, sector=2930274071 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x29 Nov 3 07:22:39 Tower kernel: ide1: reset: success Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274071, sector=2930274071 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: end_request: I/O error, dev hdc, sector 2930274071 Nov 3 07:22:39 Tower kernel: md: disk4 read error Nov 3 07:22:39 Tower kernel: handle_stripe read error: 2930274008/1, count: 1 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274079, sector=2930274079 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274079, sector=2930274079 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274079, sector=2930274079 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274079, sector=2930274079 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: ide1: reset: success Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274079, sector=2930274079 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274079, sector=2930274079 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274079, sector=2930274079 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274079, sector=2930274079 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: ide1: reset: success Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274079, sector=2930274079 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: end_request: I/O error, dev hdc, sector 2930274079 Nov 3 07:22:39 Tower kernel: md: disk4 read error Nov 3 07:22:39 Tower kernel: handle_stripe read error: 2930274016/1, count: 1 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274087, sector=2930274087 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274087, sector=2930274087 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274087, sector=2930274087 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274087, sector=2930274087 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: ide1: reset: success Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274087, sector=2930274087 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274087, sector=2930274087 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274087, sector=2930274087 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274087, sector=2930274087 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: ide1: reset: success Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274087, sector=2930274087 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: end_request: I/O error, dev hdc, sector 2930274087 Nov 3 07:22:39 Tower kernel: md: disk4 read error Nov 3 07:22:39 Tower kernel: handle_stripe read error: 2930274024/1, count: 1 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274095, sector=2930274095 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274095, sector=2930274095 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274095, sector=2930274095 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274095, sector=2930274095 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: ide1: reset: success Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274095, sector=2930274095 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274095, sector=2930274095 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274095, sector=2930274095 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274095, sector=2930274095 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: ide1: reset: success Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274095, sector=2930274095 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: end_request: I/O error, dev hdc, sector 2930274095 Nov 3 07:22:39 Tower kernel: md: disk4 read error Nov 3 07:22:39 Tower kernel: handle_stripe read error: 2930274032/1, count: 1 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274103, sector=2930274103 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274103, sector=2930274103 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:39 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274103, sector=2930274103 Nov 3 07:22:39 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274103, sector=2930274103 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: ide1: reset: success Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274103, sector=2930274103 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274103, sector=2930274103 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274103, sector=2930274103 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274103, sector=2930274103 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: ide1: reset: success Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274103, sector=2930274103 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: end_request: I/O error, dev hdc, sector 2930274103 Nov 3 07:22:40 Tower kernel: md: disk4 read error Nov 3 07:22:40 Tower kernel: handle_stripe read error: 2930274040/1, count: 1 Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274111, sector=2930274111 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274111, sector=2930274111 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274111, sector=2930274111 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274111, sector=2930274111 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: ide1: reset: success Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274111, sector=2930274111 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274111, sector=2930274111 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274111, sector=2930274111 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274111, sector=2930274111 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: ide1: reset: success Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: status=0x51 { DriveReady SeekComplete Error } Nov 3 07:22:40 Tower kernel: hdc: task_pio_intr: error=0x10 { SectorIdNotFound }, LBAsect=2930274111, sector=2930274111 Nov 3 07:22:40 Tower kernel: hdc: possibly failed opcode: 0x24 Nov 3 07:22:40 Tower kernel: end_request: I/O error, dev hdc, sector 2930274111 Nov 3 07:22:40 Tower kernel: md: disk4 read error
November 3, 200916 yr Author Ok, need it to reboot again, after I changed BIOS for my 5:th SATA disc, that I have problem with , I enabled AHCI :-) this was not enabled before ... But when the server starts up, I can't longer stop the array from the GUI, nothing happens... What can that be ? A new syslog is attached ....
November 3, 200916 yr Author Hi! I have found my problem way I can't stopp the server , It's my disk3, when I only have paritydisk,disk1 and disk2 the it works, but when I add disk3 the its fail, see the results from smartctl test, its the sdd that's is my disk3. Please I hope someone can help me to see what I have for problem. :-( EDIT Now I have tested to remove my parity disc, and have all the data disc connected, the its looks OK in the GUI, So could it be that the system do something about parity, and that's way I cant stop the array ? So should I have the system on with all disc during the night and see if something is fixed ? I don't know what's going on :-(
November 3, 200916 yr Author OK, Now I have downgrade to version: 4.4.2 and I have now set up my discs and started the Parity-Sync. I will come back tomorrow and report what happened, It's soon time to go to sleep , I live in Sweden. Have a nice day Peter EDIT I attached the new logfile for version 4.4.2 :-)
November 3, 200916 yr You were bit hard by the Gigabyte HPA curse! What follows is going to be a little speculative, forgive me for that, but this is my current theory as to what happened. You initially had your second WD 1.5TB drive (serial # ending in 70) configured in the BIOS to emulate an IDE disk, so was assigned hdc for its Device ID. It already has a Gigabyte HPA installed on it, so its reported size is 2930275055 sectors, while its true size is 2930277168 sectors, from here on known as _5055 and _7168. There is one quirk that the IDE modules have that the SATA modules do not, and that is that the IDE modules actually try to disable an HPA if found. Unfortunately, it DID NOT WORK, although it then reported to the kernel and unRAID that the size was now _7168. When you performed the parity sync, all was well until near the very end at _4071. It looks like the actual disk reads were in 512KB blocks, and although _4071 is a good and valid sector, it is just within the last 512K of the drive's reported max of _5055. The low level read beginning at _4071 included the sectors just past _5055, and that almost certainly explains the very serious SectorIDNotFound errors that were then returned. The system then proceeds in 4K steps all the way to the end of the true disk size, with the same errors all the way. By returning the SectorIDNotFound error, the drive is indicating that a requested sector number is out of range. In your second syslog, you had changed the BIOS setting to AHCI for all of the drives, and therefore hdc (Disk 4) was no longer found. That disk was now sde, a SATA drive ID, and just had to be reassigned on the Devices page (something you probably did not know). When the array started without it, Disk 4 was missing, probably a red ball, and was only usable as a virtual disk. Your third syslog shows you downgraded to v4.4.2, essentially equivalent to the current betas, so I don't see any advantage either way, just your preference. The latest release does include a number of fixes, but is not a material change from v4.4.2, at least as to fundamental array management, which is all you are concerned with here. The older kernel in v4.4.2 picks up the flash drive sooner, as sda, which bumps the Device IDs for all of your hard drives, not an important issue, but something to be aware of. For example, your parity drive moved from sda to sdb. You reset the array config, essentially starting fresh, and added the WD 1.5TB drive as a new drive, a good idea by the way, because it could now write a correct MBR with the actual usable drive size in it. When you started the array, it wrote a corrected MBR (with corrected partition table) to Disk 4, then found the original Reiser file system formatted on it, and accepted it (which makes me a little nervous), and is proceeding to build parity now. I don't see any reason why it should fail this time, so I *think* you are OK now. To be completely safe, you might want to run reiserfsck on Disk 4, see the Check Disk File systems page. You commented that you had a problem with Disk 3, but I don't see anything at all wrong with it. The 4 SMART reports were all good. But the SMART report you really want to check is the one that has been causing all of the trouble, the new WD 1.5TB drive with serial ending in 70, sdf in the latest v4.4.2 array. Please see the UnRAID Topical Index, HPA section for more information on the Gigabyte HPA issue. You need to be very aware of it, because you are in some danger of further issues with it. Your parity drive, a WD 1.5TB with serial# ending in 99, is connected to the first onboard SATA port, with no HPA currently. The troublesome WD 1.5TB discussed above (with serial ending in 70) is connected to the fifth port, with a Gigabyte HPA installed on it. The Samsung 1TB drive is connected to the fourth port, and also has a Gigabyte HPA on it. What I would recommend is to swap the SATA cables between the first and fourth SATA ports (either end, does not matter which), in other words swap the cables between the parity drive and the Samsung 1TB drive. That should in my opinion make the parity drive safer. I don't want to dissuade users from Gigabyte boards, they are still very good and recommended boards, but they do have this HPA issue, that MUST be planned around. I'm sorry you had to deal with it.
November 4, 200916 yr Author Thanks Rob! You are my hero Now I only need to arrange my disc, and make new parity I was checking the failing disc in my windows7 pc and no errors on the disc, so I'm planning to add this disc again. I was so close to go over to WHS after this problem, but if this works then I'm happy, And I would also thank all of you that answers all newbies question, you are so GOOOOD EDIT One more thing, when everything is upp and running with all my dsc, I'm planned uppgrade again to latest beta, is there anything I need to be careful with ? you say there was different name of the disc ?Best Regards Peter
November 4, 200916 yr EDIT One more thing, when everything is upp and running with all my dsc, I'm planned uppgrade again to latest beta, is there anything I need to be careful with ? you say there was different name of the disc ?Best Regards Peter I think what rob said was that one (or maybe a couple of yours disks were in IDE emulated mode which makes them appear as hdx where x is the drive letter. It appears you went into the BIOS and switched the drive to AHCI mode which made it appear as sdx where x is the drive letter. unRAID did not know what to do with itself and therefore presented you with the situation you had. You could have gone to the Devices screen and assigned the drives and they probably would have come back up no problem.
November 4, 200916 yr Author Hi I have add all my the disc and my parity disc is now on /dev/sdf, but it's looks like there is a HPA on that, but I'm not sure, please look into the attached syslog file. I have started a parity sync anyway, so we will see.... I hope that's is OK now. If I have a HPA on my parity disc? , how can I remove it ? EDIT Look here ..... different size and I hope my parity disc is OK. parity ata-WDC_WD15EADS-00S2B0_WD-WCAVY0802799 37°C 1,465,138,552 disk4 ata-WDC_WD15EADS-00R6B0_WD-WCAVY0164770 30°C 1,465,137,496 BR Peter
November 4, 200916 yr This lists the parity as a little larger so the HPA appears to be just on that disk4. You are OK because you just lose a little space on the data drive. You could move that drive to a different motherboard and remove the HPA but it's not really worth the effort and it may appear again on another drive in the future. Besides, the parity must be at least as large as the largest data disk. If the drive you assign as the parity had a HPA unRAID would not allow you to start the array... Peter
November 4, 200916 yr Author Thanks Peter, And a nice name you have So what you say I'm good, and the size on my parity is OK, what I can see so is that the biggest disc anyway. I did some hd param data from enmeny , but I don't this say anything, or ? Peter
November 5, 200916 yr Author During the night my system have done the parity check, and no errors found So I'm happy And everythinig works perfect together with my TviX, the only thing I need to look into is that the server don't show upp in my network when browsing using Windows 7. But all disc is mapped in my Explorer so it's easy now to put newfiles to the server. The unRAID looks much promising. BR Peter
November 5, 200916 yr Author Everything looks like its running good now I wish that NFS will become an alternative to samba, it's looks like media extender ,like mine TviX manage high bit-rate BD movies much better with NFS. Now I need to have this disc outside the unRAID, and it should be so great if it's possible to stream also this high bitrate movies from my unRAID box But the I need to upgrade to PRO version, is it possible to upgrade from plus to pro without to pay the price for PRO, just a upgrade price ? Thanks for all help
November 5, 200916 yr is it possible to upgrade from plus to pro without to pay the price for PRO, just a upgrade price ? Yes, they have a upgrade price here: http://www.lime-technology.com/joomla/products/registration-keys It is not very clear whether you get two upgraded keys for $59, or if it is $59 each.
Archived
This topic is now archived and is closed to further replies.