October 22, 201213 yr unRAID Server Pro 4.7 Hi guys, Would someone kindly look over my syslog for me please as I am getting errors when I boot unRaid. it looks like a network error and / or parity disk error. Last parity check ran 30+ days ago with no errors. Here is my current set up... http://vvcap.net/db/Xbv1bu7iQPNCZT6i5_VH.htm MyMain Smart...................... http://vvcap.net/db/KYW9XKY3PyRMB9SXrvLe.htp Any advise would be welcome as I don't really grasp Linux that well. Thank you EDIT I thought I would post this section in with the main faults Oct 22 12:53:29 Tower kernel: ata15: EH in SWNCQ mode,QC:qc_active 0x3 sactive 0x3 Oct 22 12:53:29 Tower kernel: ata15: SWNCQ:qc_active 0x1 defer_bits 0x2 last_issue_tag 0x1 Oct 22 12:53:29 Tower kernel: dhfis 0x1 dmafis 0x1 sdbfis 0x2 Oct 22 12:53:29 Tower kernel: ata15: ATA_REG 0x41 ERR_REG 0x40 Oct 22 12:53:29 Tower kernel: ata15: tag : dhfis dmafis sdbfis sacitve Oct 22 12:53:29 Tower kernel: ata15: tag 0x0: 1 1 0 1 Oct 22 12:53:29 Tower kernel: ata15.00: exception Emask 0x1 SAct 0x3 SErr 0x0 action 0x6 frozen Oct 22 12:53:29 Tower kernel: ata15.00: Ata error. fis:0x21 Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/40:00:20:00:00/00:00:00:00:00/40 tag 0 ncq 32768 in Oct 22 12:53:29 Tower kernel: res 41/40:0c:a8:88:e0/40:00:e8:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/20:08:a8:87:e0/00:00:e8:00:00/40 tag 1 ncq 16384 in Oct 22 12:53:29 Tower kernel: res 41/40:0c:a8:88:e0/40:00:e8:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15: hard resetting link Oct 22 12:53:29 Tower kernel: ata15: nv: skipping hardreset on occupied port Oct 22 12:53:29 Tower kernel: ata15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 22 12:53:29 Tower kernel: ata15.00: configured for UDMA/133 Oct 22 12:53:29 Tower kernel: ata15: EH complete Oct 22 12:53:29 Tower kernel: ata15: EH in SWNCQ mode,QC:qc_active 0x3 sactive 0x3 Oct 22 12:53:29 Tower kernel: ata15: SWNCQ:qc_active 0x2 defer_bits 0x1 last_issue_tag 0x1 Oct 22 12:53:29 Tower kernel: dhfis 0x2 dmafis 0x2 sdbfis 0x1 Oct 22 12:53:29 Tower kernel: ata15: ATA_REG 0x41 ERR_REG 0x40 Oct 22 12:53:29 Tower kernel: ata15: tag : dhfis dmafis sdbfis sacitve Oct 22 12:53:29 Tower kernel: ata15: tag 0x1: 1 1 0 1 Oct 22 12:53:29 Tower kernel: ata15.00: exception Emask 0x1 SAct 0x3 SErr 0x0 action 0x6 frozen Oct 22 12:53:29 Tower kernel: ata15.00: Ata error. fis:0x21 Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/20:00:70:88:e0/00:00:e8:00:00/40 tag 0 ncq 16384 in Oct 22 12:53:29 Tower kernel: res 41/40:0c:20:00:00/40:00:00:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/40:08:20:00:00/00:00:00:00:00/40 tag 1 ncq 32768 in Oct 22 12:53:29 Tower kernel: res 41/40:0c:20:00:00/40:00:00:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15: hard resetting link Oct 22 12:53:29 Tower kernel: ata15: nv: skipping hardreset on occupied port Oct 22 12:53:29 Tower kernel: ata15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 22 12:53:29 Tower kernel: ata15.00: configured for UDMA/133 Oct 22 12:53:29 Tower kernel: ata15: EH complete Oct 22 12:53:29 Tower kernel: ata15: EH in SWNCQ mode,QC:qc_active 0x7 sactive 0x7 Oct 22 12:53:29 Tower kernel: ata15: SWNCQ:qc_active 0x1 defer_bits 0x6 last_issue_tag 0x1 Oct 22 12:53:29 Tower kernel: dhfis 0x1 dmafis 0x1 sdbfis 0x2 Oct 22 12:53:29 Tower kernel: ata15: ATA_REG 0x41 ERR_REG 0x40 Oct 22 12:53:29 Tower kernel: ata15: tag : dhfis dmafis sdbfis sacitve Oct 22 12:53:29 Tower kernel: ata15: tag 0x0: 1 1 0 1 Oct 22 12:53:29 Tower kernel: ata15.00: exception Emask 0x1 SAct 0x7 SErr 0x0 action 0x6 frozen Oct 22 12:53:29 Tower kernel: ata15.00: Ata error. fis:0x21 Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/40:00:20:00:00/00:00:00:00:00/40 tag 0 ncq 32768 in Oct 22 12:53:29 Tower kernel: res 41/40:0c:70:88:e0/40:00:e8:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/38:08:c8:87:e0/00:00:e8:00:00/40 tag 1 ncq 28672 in Oct 22 12:53:29 Tower kernel: res 41/40:0c:70:88:e0/40:00:e8:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/20:10:20:87:e0/00:00:e8:00:00/40 tag 2 ncq 16384 in Oct 22 12:53:29 Tower kernel: res 41/40:0c:70:88:e0/40:00:e8:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15: hard resetting link Oct 22 12:53:29 Tower kernel: ata15: nv: skipping hardreset on occupied port Oct 22 12:53:29 Tower kernel: ata15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 22 12:53:29 Tower kernel: ata15.00: configured for UDMA/133 Oct 22 12:53:29 Tower kernel: ata15: EH complete Oct 22 12:53:29 Tower kernel: ata15: EH in SWNCQ mode,QC:qc_active 0x5 sactive 0x5 Oct 22 12:53:29 Tower kernel: ata15: SWNCQ:qc_active 0x4 defer_bits 0x1 last_issue_tag 0x2 Oct 22 12:53:29 Tower kernel: dhfis 0x4 dmafis 0x4 sdbfis 0x3 Oct 22 12:53:29 Tower kernel: ata15: ATA_REG 0x41 ERR_REG 0x40 Oct 22 12:53:29 Tower kernel: ata15: tag : dhfis dmafis sdbfis sacitve Oct 22 12:53:29 Tower kernel: ata15: tag 0x2: 1 1 0 1 Oct 22 12:53:29 Tower kernel: ata15.00: exception Emask 0x1 SAct 0x5 SErr 0x0 action 0x6 frozen Oct 22 12:53:29 Tower kernel: ata15.00: Ata error. fis:0x21 Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/c0:00:60:00:00/00:00:00:00:00/40 tag 0 ncq 98304 in Oct 22 12:53:29 Tower kernel: res 41/40:14:20:00:00/40:00:00:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/40:10:20:00:00/00:00:00:00:00/40 tag 2 ncq 32768 in Oct 22 12:53:29 Tower kernel: res 41/40:14:20:00:00/40:00:00:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15: hard resetting link Oct 22 12:53:29 Tower kernel: ata15: nv: skipping hardreset on occupied port Oct 22 12:53:29 Tower kernel: ata15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 22 12:53:29 Tower kernel: ata15.00: configured for UDMA/133 Oct 22 12:53:29 Tower kernel: ata15: EH complete Oct 22 12:53:29 Tower kernel: ata15: EH in SWNCQ mode,QC:qc_active 0x3 sactive 0x3 Oct 22 12:53:29 Tower kernel: ata15: SWNCQ:qc_active 0x3 defer_bits 0x0 last_issue_tag 0x1 Oct 22 12:53:29 Tower kernel: dhfis 0x3 dmafis 0x1 sdbfis 0x0 Oct 22 12:53:29 Tower kernel: ata15: ATA_REG 0x41 ERR_REG 0x40 Oct 22 12:53:29 Tower kernel: ata15: tag : dhfis dmafis sdbfis sacitve Oct 22 12:53:29 Tower kernel: ata15: tag 0x0: 1 1 0 1 Oct 22 12:53:29 Tower kernel: ata15: tag 0x1: 1 0 0 1 Oct 22 12:53:29 Tower kernel: ata15.00: exception Emask 0x1 SAct 0x3 SErr 0x0 action 0x6 frozen Oct 22 12:53:29 Tower kernel: ata15.00: Ata error. fis:0x21 Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/40:00:20:00:00/00:00:00:00:00/40 tag 0 ncq 32768 in Oct 22 12:53:29 Tower kernel: res 41/40:0c:60:00:00/40:00:00:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/c0:08:60:00:00/00:00:00:00:00/40 tag 1 ncq 98304 in Oct 22 12:53:29 Tower kernel: res 41/40:0c:60:00:00/40:00:00:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15: hard resetting link Oct 22 12:53:29 Tower kernel: ata15: nv: skipping hardreset on occupied port Oct 22 12:53:29 Tower kernel: ata15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 22 12:53:29 Tower kernel: ata15.00: configured for UDMA/133 Oct 22 12:53:29 Tower kernel: ata15: EH complete Oct 22 12:53:29 Tower kernel: ata15: EH in SWNCQ mode,QC:qc_active 0x3 sactive 0x3 Oct 22 12:53:29 Tower kernel: ata15: SWNCQ:qc_active 0x3 defer_bits 0x0 last_issue_tag 0x1 Oct 22 12:53:29 Tower kernel: dhfis 0x3 dmafis 0x2 sdbfis 0x0 Oct 22 12:53:29 Tower kernel: ata15: ATA_REG 0x41 ERR_REG 0x40 Oct 22 12:53:29 Tower kernel: ata15: tag : dhfis dmafis sdbfis sacitve Oct 22 12:53:29 Tower kernel: ata15: tag 0x0: 1 0 0 1 Oct 22 12:53:29 Tower kernel: ata15: tag 0x1: 1 1 0 1 Oct 22 12:53:29 Tower kernel: ata15.00: exception Emask 0x1 SAct 0x3 SErr 0x0 action 0x6 frozen Oct 22 12:53:29 Tower kernel: ata15.00: Ata error. fis:0x21 Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/c0:00:60:00:00/00:00:00:00:00/40 tag 0 ncq 98304 in Oct 22 12:53:29 Tower kernel: res 41/40:0c:20:00:00/40:00:00:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15.00: failed command: READ FPDMA QUEUED Oct 22 12:53:29 Tower kernel: ata15.00: cmd 60/40:08:20:00:00/00:00:00:00:00/40 tag 1 ncq 32768 in Oct 22 12:53:29 Tower kernel: res 41/40:0c:20:00:00/40:00:00:00:00/40 Emask 0x9 (media error) Oct 22 12:53:29 Tower kernel: ata15.00: status: { DRDY ERR } Oct 22 12:53:29 Tower kernel: ata15.00: error: { UNC } Oct 22 12:53:29 Tower kernel: ata15: hard resetting link Oct 22 12:53:29 Tower kernel: ata15: nv: skipping hardreset on occupied port Oct 22 12:53:29 Tower kernel: ata15: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Oct 22 12:53:29 Tower kernel: ata15.00: configured for UDMA/133 Oct 22 12:53:29 Tower kernel: sd 3:0:0:0: [sdp] Unhandled sense code Oct 22 12:53:29 Tower kernel: sd 3:0:0:0: [sdp] Result: hostbyte=0x00 driverbyte=0x08 Oct 22 12:53:29 Tower kernel: sd 3:0:0:0: [sdp] Sense Key : 0x3 [current] [descriptor] Oct 22 12:53:29 Tower kernel: Descriptor sense data with sense descriptors (in hex): Oct 22 12:53:29 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Oct 22 12:53:29 Tower kernel: 00 00 00 20 Oct 22 12:53:29 Tower kernel: sd 3:0:0:0: [sdp] ASC=0x11 ASCQ=0x4 Oct 22 12:53:29 Tower kernel: sd 3:0:0:0: [sdp] CDB: cdb[0]=0x28: 28 00 00 00 00 20 00 00 40 00 Oct 22 12:53:29 Tower kernel: end_request: I/O error, dev sdp, sector 32 Oct 22 12:53:29 Tower kernel: Buffer I/O error on device sdp, logical block 4 Oct 22 12:53:29 Tower kernel: Buffer I/O error on device sdp, logical block 5 Oct 22 12:53:29 Tower kernel: Buffer I/O error on device sdp, logical block 6 Oct 22 12:53:29 Tower kernel: Buffer I/O error on device sdp, logical block 7 Oct 22 12:53:29 Tower kernel: Buffer I/O error on device sdp, logical block 8 Oct 22 12:53:29 Tower kernel: Buffer I/O error on device sdp, logical block 9 Oct 22 12:53:29 Tower kernel: Buffer I/O error on device sdp, logical block 10 Oct 22 12:53:29 Tower kernel: Buffer I/O error on device sdp, logical block 11 Oct 22 12:53:29 Tower kernel: ata15: EH complete Oct 22 12:53:29 Tower ifplugd(eth0)[1730]: ifplugd 0.28 initializing. syslog-2012-10-22.txt
October 22, 201213 yr Parity is having issues. The SMART data indicates pending sectors. The safest thing to do is replace the drive and rebuild parity. Meanwhile run pre-clear on the current disk until pending sectors goes to zero. Alternatively, you can just rebuild parity and hope that the pending sectors are resolved. To rebuild the current drive: 1. Start the array with parity unassigned and then start the array with the parity disk assigned. A rebuild will begin. 2. Run a parity check. (Do this in either case.) 3. Check SMART data for pending sectors. If there are any pending sectors after the check the run preclear on the disk and rebuild. Report back if pending sectors is not zero.
October 23, 201213 yr Author Thank you dgaschk I am currently running a parity check.. http://vvcap.net/db/mNpMWmvbeU0lWPE-HWWH.htm There is one error so far, I think I will just order a new hdd for parity and in the meantime I will attempt to rebuild the parity drive when this preclear is complete. It's a while since I have purchased a hdd, can anyone recommend the best 2TB hdd deal at the moment? EDIT I stopped the array and unassigned parity, rebooted and reassigned and rebooted and a parity rebuild did not start? So for now I'm running another parity check whilst I'm at work.
October 23, 201213 yr I stopped the array and unassigned parity, rebooted and reassigned and rebooted and a parity rebuild did not start? So for now I'm running another parity check whilst I'm at work. You would have needed to Start the array with the parity disk un-assigned in the middle of that series of steps. No need to reboot. [*]Stop array [*]un-assign parity [*]Start array <- it is here where unRAID will notice the parity disk is missing and forget its old model/serial number [*]Stop array [*]re-assign parity <- it is here where unRAID will see the drive, think it is a replacement for the one unassigned. [*]Start array once more. <- parity will be calculated and the parity disk written. Because you did not start the array with the disk unassigned, unRAID never forgot the model/serial number of the parity disk. That is why it did not re-calculate parity. Joe L.
October 24, 201213 yr Author Thank you Joe L. I have now rebuilt parity as instructed and my syslog is attached. I still have pending sectors..see below . http://vvcap.net/db/eFaU20Pgk3x2e2OC43UI.htp I do not seem to have any errors when i reboot the array. If I RMA the drive with WD sending me out a drive first they want to charge me £180 which they claim is the market value. That's £70 more than I paid for it two years ago! I may try and hold out until after Xmas see if the prices of hdd's come down. syslog-2012-10-24.txt
October 25, 201213 yr An RMA should not cost anything. They will not charge you unless they don't receive the bad drive.
Archived
This topic is now archived and is closed to further replies.