April 27, 201214 yr Here we go. Firstly unmenu isn't working in Firefox all of a sudden. I get the Main page, but as soon as I go to another topic (ie syslog) im send to openDNS's "no results" page. So without a syslog I can't trouble shoot my next problem... I think I accidently upgraded to version 11 a while back. Any advice?
April 27, 201214 yr Thanks for that. ok - here it is... basically, disk1 has stopped responding. Could be a failed drive. Could be a loose cable, could be a bad port on the disk controller. Apr 27 16:06:16 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Apr 27 16:06:16 Tower kernel: ata1.00: failed command: READ DMA EXT Apr 27 16:06:16 Tower kernel: ata1.00: cmd 25/00:00:57:bc:c0/00:04:dd:00:00/e0 tag 0 dma 524288 in Apr 27 16:06:16 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 27 16:06:16 Tower kernel: ata1.00: status: { DRDY } Apr 27 16:06:16 Tower kernel: ata1: hard resetting link Apr 27 16:06:17 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Apr 27 16:06:17 Tower kernel: ata1.00: configured for UDMA/133 Apr 27 16:06:17 Tower kernel: ata1.00: device reported invalid CHS sector 0 Apr 27 16:06:17 Tower kernel: ata1: EH complete Apr 27 16:06:17 Tower login[2383]: invalid password for `root' on `pts/0' from `192.168.1.8' Apr 27 16:06:37 Tower login[2383]: ROOT LOGIN on `pts/0' from `192.168.1.8' Apr 27 16:06:47 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Apr 27 16:06:47 Tower kernel: ata1.00: failed command: READ DMA EXT Apr 27 16:06:47 Tower kernel: ata1.00: cmd 25/00:00:57:bc:c0/00:04:dd:00:00/e0 tag 0 dma 524288 in Apr 27 16:06:47 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 27 16:06:47 Tower kernel: ata1.00: status: { DRDY } Apr 27 16:06:47 Tower kernel: ata1: hard resetting link Apr 27 16:06:48 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Apr 27 16:06:48 Tower kernel: ata1.00: configured for UDMA/133 Apr 27 16:06:48 Tower kernel: ata1.00: device reported invalid CHS sector 0 Apr 27 16:06:48 Tower kernel: ata1: EH complete Apr 27 16:07:18 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Apr 27 16:07:18 Tower kernel: ata1.00: failed command: READ DMA EXT Apr 27 16:07:18 Tower kernel: ata1.00: cmd 25/00:00:57:bc:c0/00:04:dd:00:00/e0 tag 0 dma 524288 in Apr 27 16:07:18 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 27 16:07:18 Tower kernel: ata1.00: status: { DRDY } Apr 27 16:07:18 Tower kernel: ata1: hard resetting link Apr 27 16:07:19 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Apr 27 16:07:19 Tower kernel: ata1.00: configured for UDMA/133 Apr 27 16:07:19 Tower kernel: ata1.00: device reported invalid CHS sector 0 Apr 27 16:07:19 Tower kernel: ata1: EH complete Apr 27 16:07:49 Tower kernel: ata1: limiting SATA link speed to 1.5 Gbps Apr 27 16:07:49 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Apr 27 16:07:49 Tower kernel: ata1.00: failed command: READ DMA EXT Apr 27 16:07:49 Tower kernel: ata1.00: cmd 25/00:00:57:bc:c0/00:04:dd:00:00/e0 tag 0 dma 524288 in Apr 27 16:07:49 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 27 16:07:49 Tower kernel: ata1.00: status: { DRDY } Apr 27 16:07:49 Tower kernel: ata1: hard resetting link Apr 27 16:07:50 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 27 16:07:50 Tower kernel: ata1.00: configured for UDMA/133 Apr 27 16:07:50 Tower kernel: ata1.00: device reported invalid CHS sector 0 Apr 27 16:07:50 Tower kernel: ata1: EH complete Apr 27 16:08:20 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Apr 27 16:08:20 Tower kernel: ata1.00: failed command: READ DMA EXT Apr 27 16:08:20 Tower kernel: ata1.00: cmd 25/00:00:57:bc:c0/00:04:dd:00:00/e0 tag 0 dma 524288 in Apr 27 16:08:20 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 27 16:08:20 Tower kernel: ata1.00: status: { DRDY } Apr 27 16:08:20 Tower kernel: ata1: hard resetting link Apr 27 16:08:21 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 27 16:08:21 Tower kernel: ata1.00: configured for UDMA/133 Apr 27 16:08:21 Tower kernel: ata1.00: device reported invalid CHS sector 0 Apr 27 16:08:21 Tower kernel: ata1: EH complete Apr 27 16:08:51 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Apr 27 16:08:51 Tower kernel: ata1.00: failed command: READ DMA EXT Apr 27 16:08:51 Tower kernel: ata1.00: cmd 25/00:00:57:bc:c0/00:04:dd:00:00/e0 tag 0 dma 524288 in Apr 27 16:08:51 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Apr 27 16:08:51 Tower kernel: ata1.00: status: { DRDY } Apr 27 16:08:51 Tower kernel: ata1: hard resetting link Apr 27 16:08:52 Tower kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 27 16:08:52 Tower kernel: ata1.00: configured for UDMA/133 Apr 27 16:08:52 Tower kernel: ata1.00: device reported invalid CHS sector 0 Apr 27 16:08:52 Tower kernel: sd 1:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 Apr 27 16:08:52 Tower kernel: sd 1:0:0:0: [sda] Sense Key : 0xb [current] [descriptor] Apr 27 16:08:52 Tower kernel: Descriptor sense data with sense descriptors (in hex): Apr 27 16:08:52 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Apr 27 16:08:52 Tower kernel: 00 00 00 00 Apr 27 16:08:52 Tower kernel: sd 1:0:0:0: [sda] ASC=0x0 ASCQ=0x0 Apr 27 16:08:52 Tower kernel: sd 1:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 dd c0 bc 57 00 04 00 00 Apr 27 16:08:52 Tower kernel: end_request: I/O error, dev sda, sector 3720395863 Apr 27 16:08:52 Tower kernel: ata1: EH complete Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395800/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395808/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395816/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395824/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395832/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395840/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395848/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395856/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395864/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395872/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395880/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395888/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395896/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395904/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395912/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395920/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395928/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395936/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395944/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395952/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error Apr 27 16:08:52 Tower kernel: handle_stripe read error: 3720395960/1, count: 1 Apr 27 16:08:52 Tower kernel: md: disk1 read error power down, re-seat the cables to the drive, power up and see if it can be responsive. type: smartctl -a /dev/sda for its device. As far as openDNS, it appears as if your router is sending you somewhere you do not expect. An entirely different issue. Joe L.
April 27, 201214 yr Author OK will do. I just had the drive working for the last half hour (my son was watching Modern Family on itunes which is on disk 1 so I know it was working. Now itunes has frozen and in myMain I'm getting Apr 27 17:42:34 Tower kernel: handle_stripe read error: 3000780136/1, count: 1 (Errors) Apr 27 17:42:34 Tower kernel: md: disk1 read error (Errors) Apr 27 17:42:34 Tower kernel: handle_stripe read error: 3000780144/1, count: 1 (Errors) Apr 27 17:42:34 Tower kernel: md: disk1 read error (Errors) Apr 27 17:42:34 Tower kernel: handle_stripe read error: 3000780152/1, count: 1 (Errors) Apr 27 17:42:34 Tower kernel: md: disk1 read error (Errors) Apr 27 17:42:34 Tower kernel: handle_stripe read error: 3000780160/1, count: 1 (Errors) Apr 27 17:42:34 Tower kernel: md: disk1 read error (Errors) Apr 27 17:42:34 Tower kernel: handle_stripe read error: 3000780168/1, count: 1 (Errors) Apr 27 17:42:34 Tower kernel: md: disk1 read error (Errors) etc. I've worked out Firefox too..
April 27, 201214 yr Author OK I've reset each of the drives in their caddies and restarted it. Disk 1 is working at this stage. Here's the most recent logs
April 27, 201214 yr Author The drive is still showing 'Green'. What does 'ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors)' mean? Is it possible to run smart tests from within the Unraid system or would I have to take the drive out of the bay and run it on a computer?
April 27, 201214 yr You are having problems reading from that drive...the parity drive is allowing you to watch Family Guy. A write hasn't failed to the drive yet, which is why it is still green.
April 27, 201214 yr Is it possible to run smart tests from within the Unraid system or would I have to take the drive out of the bay and run it on a computer? You can run them from unMENU--> <disk management> tab or telnet http://lime-technology.com/wiki/index.php/Troubleshooting#Obtaining_a_SMART_report Bet you'll find some "Current_Pending_Sector" in the raw value column
April 27, 201214 yr Author Here's what I got. Can you help with interpretation please!? smart_test.txt
April 27, 201214 yr Well, if you looked at it you would see SMART overall-health self-assessment test result: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. That is a result of this. It has already re-allocated 2003 sectors... and the normalized value of "1" is below the failure threshold of "5" 5 Reallocated_Sector_Ct 0x0033 001 001 005 Pre-fail Always FAILING_NOW 2003 Oh yes, there are two more sectors waitin to be re-allocated as well when next written 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 2 Basically, your disk has failed. Joe L.
April 28, 201214 yr Author Man I am stupid ... I didn't even SEE that. Thanks so SO much for helping out an old fool. Now to read up on replacing the drive... before I ask more blatantly obvious questions!
April 28, 201214 yr Man I am stupid ... I didn't even SEE that. Thanks so SO much for helping out an old fool. Now to read up on replacing the drive... before I ask more blatantly obvious questions! That part is easy. Stop the array power down replace the failing drive with one that is as big. (The replacement can be bigger than the failed drive, as long as it is not bigger than your existing parity drive) Power up. unRAID will notice the replacement and probably not start until you check the checkbox that indicates "I'm sure" Press "Start" and let it re-construct the data onto the replacement drive. On older versions of unRAID, if you used the same port, you would not need to use the disk assignment page. On newer versions, you may have use the disk assignment page to assign the replacement disk to the slot in the array tha held the failing drive. Joe L.
April 29, 201214 yr Author all done! Can't believe how simple it was to restore from Parity. SO glad I went with UnRaid. Thanks again
Archived
This topic is now archived and is closed to further replies.