June 3, 201016 yr Here's the chain of events: 1) Performed a pre-clear on a new disk overnight, the next morning I found the system had crashed and had to do a hard reboot. 2) Checked the web console afterwards and found it doing a parity check (as expected), but the cache drive was showing up as unformatted. I was running 4.5.3 and knew that there was a problem with disks incorrectly showing up as unformatted, so I just let it go until it finished the parity check. Installed 4.5.4 during the parity check so it would be updated after the next reboot. 3) This morning the parity check was finished so I rebooted, this time it showed the cache drive was missing. It showed a disk was assigned but that it was not present. I shut down, pulled the disk out of the icy dock, blew off the connectors, reinserted and booted. 4) Checked the web console again and the cache drive showed up properly. Manually invoked the mover (I had 3 ISO's on the cache drive), checked that the cache drive's read count was incrementing on the web console and went to lunch. 5) I just got back from lunch and the write count on the cache disk is huge and growing. I checked the syslog and there are all sorts of errors (see syslog below) for the cache drive (/dev/sdl). I shut down the array. I started it up again briefly to check something, and the cache disk is again showing up as unformatted. Stopped array again. I haven't seen these errors before so I'm not sure how to interpret them. One thing that I find a bit odd is that the main unRAID web console shows the cache disk is /dev/sdl, but unMenu's Disk Management page shows the disk with the same serial number is /dev/sdq. SMART (short test anyways), is showing no problems with the drive. Any ideas? Thanks! Jun 3 11:09:15 WatchTower emhttp: shcmd (55): /usr/local/sbin/mover 2>&1 | logger & Jun 3 11:09:15 WatchTower logger: mover started Jun 3 11:09:15 WatchTower logger: ./Drama/The Road.iso Jun 3 11:09:15 WatchTower logger: .d..t...... Drama/ Jun 3 11:09:15 WatchTower logger: >f.stp..... Drama/The Road.iso Jun 3 11:11:37 WatchTower kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 3 Jun 3 11:11:37 WatchTower kernel: usb 1-6: reset high speed USB device using ehci_hcd and address 3 Jun 3 11:13:57 WatchTower logger: ./Drama/PATTON.ISO Jun 3 11:13:57 WatchTower logger: .d..t...... Drama/ Jun 3 11:13:57 WatchTower logger: >f+++++++++ Drama/PATTON.ISO Jun 3 11:15:50 WatchTower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x1400000 action 0x6 frozen Jun 3 11:15:50 WatchTower kernel: ata12: SError: { Handshk TrStaTrns } Jun 3 11:15:50 WatchTower kernel: ata12.00: failed command: READ DMA EXT Jun 3 11:15:50 WatchTower kernel: ata12.00: cmd 25/00:00:17:48:5e/00:02:18:00:00/e0 tag 0 dma 262144 in Jun 3 11:15:50 WatchTower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 3 11:15:50 WatchTower kernel: ata12.00: status: { DRDY } Jun 3 11:15:50 WatchTower kernel: ata12: hard resetting link Jun 3 11:15:50 WatchTower kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 3 11:15:50 WatchTower kernel: ata12.00: configured for UDMA/133 Jun 3 11:15:50 WatchTower kernel: ata12.00: device reported invalid CHS sector 0 Jun 3 11:15:50 WatchTower kernel: ata12: EH complete Jun 3 11:16:30 WatchTower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x1000000 action 0x6 frozen Jun 3 11:16:30 WatchTower kernel: ata12: SError: { TrStaTrns } Jun 3 11:16:30 WatchTower kernel: ata12.00: failed command: READ DMA EXT Jun 3 11:16:30 WatchTower kernel: ata12.00: cmd 25/00:00:27:46:65/00:02:18:00:00/e0 tag 0 dma 262144 in Jun 3 11:16:30 WatchTower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 3 11:16:30 WatchTower kernel: ata12.00: status: { DRDY } Jun 3 11:16:30 WatchTower kernel: ata12: hard resetting link Jun 3 11:16:30 WatchTower kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 3 11:16:30 WatchTower kernel: ata12.00: configured for UDMA/133 Jun 3 11:16:30 WatchTower kernel: ata12.00: device reported invalid CHS sector 0 Jun 3 11:16:30 WatchTower kernel: ata12: EH complete Jun 3 11:17:11 WatchTower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Jun 3 11:17:11 WatchTower kernel: ata12.00: port_status 0x20280000 Jun 3 11:17:11 WatchTower kernel: ata12.00: failed command: READ DMA EXT Jun 3 11:17:11 WatchTower kernel: ata12.00: cmd 25/00:00:ef:cc:84/00:02:18:00:00/e0 tag 0 dma 262144 in Jun 3 11:17:11 WatchTower kernel: res 51/04:f9:95:d5:84/04:01:18:00:00/e0 Emask 0x3 (HSM violation) Jun 3 11:17:11 WatchTower kernel: ata12.00: status: { DRDY ERR } Jun 3 11:17:11 WatchTower kernel: ata12.00: error: { ABRT } Jun 3 11:17:11 WatchTower kernel: ata12: hard resetting link Jun 3 11:17:11 WatchTower kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 3 11:17:12 WatchTower kernel: ata12.00: configured for UDMA/133 Jun 3 11:17:12 WatchTower kernel: ata12: EH complete Jun 3 11:17:45 WatchTower kernel: ata12: limiting SATA link speed to 1.5 Gbps Jun 3 11:17:45 WatchTower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jun 3 11:17:45 WatchTower kernel: ata12.00: failed command: READ DMA EXT Jun 3 11:17:45 WatchTower kernel: ata12.00: cmd 25/00:00:ef:2a:87/00:02:18:00:00/e0 tag 0 dma 262144 in Jun 3 11:17:45 WatchTower kernel: res 40/00:f9:95:d5:84/04:01:18:00:00/e0 Emask 0x4 (timeout) Jun 3 11:17:45 WatchTower kernel: ata12.00: status: { DRDY } Jun 3 11:17:45 WatchTower kernel: ata12: hard resetting link Jun 3 11:17:45 WatchTower kernel: ata12: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 11:17:45 WatchTower kernel: ata12.00: configured for UDMA/133 Jun 3 11:17:45 WatchTower kernel: ata12: EH complete Jun 3 11:18:16 WatchTower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jun 3 11:18:16 WatchTower kernel: ata12.00: failed command: READ DMA EXT Jun 3 11:18:16 WatchTower kernel: ata12.00: cmd 25/00:00:ef:2c:87/00:02:18:00:00/e0 tag 0 dma 262144 in Jun 3 11:18:16 WatchTower kernel: res 40/00:ff:00:00:00/04:01:18:00:00/00 Emask 0x4 (timeout) Jun 3 11:18:16 WatchTower kernel: ata12.00: status: { DRDY } Jun 3 11:18:16 WatchTower kernel: ata12: hard resetting link Jun 3 11:18:21 WatchTower kernel: ata12: link is slow to respond, please be patient (ready=-19) Jun 3 11:18:26 WatchTower kernel: ata12: SRST failed (errno=-16) Jun 3 11:18:26 WatchTower kernel: ata12: hard resetting link Jun 3 11:18:31 WatchTower kernel: ata12: link is slow to respond, please be patient (ready=-19) Jun 3 11:18:36 WatchTower kernel: ata12: SRST failed (errno=-16) Jun 3 11:18:36 WatchTower kernel: ata12: hard resetting link Jun 3 11:18:36 WatchTower kernel: ata12: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 11:18:36 WatchTower kernel: ata12.00: configured for UDMA/133 Jun 3 11:18:36 WatchTower kernel: ata12.00: device reported invalid CHS sector 0 Jun 3 11:18:36 WatchTower kernel: ata12: EH complete Jun 3 11:19:07 WatchTower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jun 3 11:19:07 WatchTower kernel: ata12.00: failed command: READ DMA EXT Jun 3 11:19:07 WatchTower kernel: ata12.00: cmd 25/00:00:ef:30:87/00:02:18:00:00/e0 tag 0 dma 262144 in Jun 3 11:19:07 WatchTower kernel: res 40/00:ff:00:00:00/04:01:18:00:00/00 Emask 0x4 (timeout) Jun 3 11:19:07 WatchTower kernel: ata12.00: status: { DRDY } Jun 3 11:19:07 WatchTower kernel: ata12: hard resetting link Jun 3 11:19:12 WatchTower kernel: ata12: link is slow to respond, please be patient (ready=-19) Jun 3 11:19:17 WatchTower kernel: ata12: SRST failed (errno=-16) Jun 3 11:19:17 WatchTower kernel: ata12: hard resetting link Jun 3 11:19:22 WatchTower kernel: ata12: link is slow to respond, please be patient (ready=-19) Jun 3 11:19:27 WatchTower kernel: ata12: SRST failed (errno=-16) Jun 3 11:19:27 WatchTower kernel: ata12: hard resetting link Jun 3 11:19:27 WatchTower kernel: ata12: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 11:19:27 WatchTower kernel: ata12.00: configured for UDMA/133 Jun 3 11:19:27 WatchTower kernel: ata12.00: device reported invalid CHS sector 0 Jun 3 11:19:27 WatchTower kernel: ata12: EH complete Jun 3 11:19:58 WatchTower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jun 3 11:19:58 WatchTower kernel: ata12.00: failed command: READ DMA EXT Jun 3 11:19:58 WatchTower kernel: ata12.00: cmd 25/00:00:ef:30:87/00:02:18:00:00/e0 tag 0 dma 262144 in Jun 3 11:19:58 WatchTower kernel: res 40/00:ff:00:00:00/04:01:18:00:00/00 Emask 0x4 (timeout) Jun 3 11:19:58 WatchTower kernel: ata12.00: status: { DRDY } Jun 3 11:19:58 WatchTower kernel: ata12: hard resetting link Jun 3 11:20:03 WatchTower kernel: ata12: link is slow to respond, please be patient (ready=-19) Jun 3 11:20:08 WatchTower kernel: ata12: SRST failed (errno=-16) Jun 3 11:20:08 WatchTower kernel: ata12: hard resetting link Jun 3 11:20:08 WatchTower kernel: ata12: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 11:20:08 WatchTower kernel: ata12.00: configured for UDMA/133 Jun 3 11:20:08 WatchTower kernel: ata12.00: device reported invalid CHS sector 0 Jun 3 11:20:08 WatchTower kernel: ata12: EH complete Jun 3 11:20:39 WatchTower kernel: ata12.00: limiting speed to UDMA/100:PIO4 Jun 3 11:20:39 WatchTower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jun 3 11:20:39 WatchTower kernel: ata12.00: failed command: READ DMA EXT Jun 3 11:20:39 WatchTower kernel: ata12.00: cmd 25/00:00:ef:30:87/00:02:18:00:00/e0 tag 0 dma 262144 in Jun 3 11:20:39 WatchTower kernel: res 40/00:ff:00:00:00/04:01:18:00:00/00 Emask 0x4 (timeout) Jun 3 11:20:39 WatchTower kernel: ata12.00: status: { DRDY } Jun 3 11:20:39 WatchTower kernel: ata12: hard resetting link Jun 3 11:20:39 WatchTower kernel: ata12: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 3 11:20:39 WatchTower kernel: ata12.00: configured for UDMA/100 Jun 3 11:20:39 WatchTower kernel: ata12.00: device reported invalid CHS sector 0 Jun 3 11:20:39 WatchTower kernel: ata12: EH complete Jun 3 11:21:10 WatchTower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jun 3 11:21:10 WatchTower kernel: ata12.00: failed command: READ DMA EXT Jun 3 11:21:10 WatchTower kernel: ata12.00: cmd 25/00:00:ef:34:87/00:02:18:00:00/e0 tag 0 dma 262144 in Jun 3 11:21:10 WatchTower kernel: res 40/00:ff:00:00:00/04:01:18:00:00/00 Emask 0x4 (timeout) Jun 3 11:21:10 WatchTower kernel: ata12.00: status: { DRDY } Jun 3 11:21:10 WatchTower kernel: ata12: hard resetting link Jun 3 11:21:15 WatchTower kernel: ata12: link is slow to respond, please be patient (ready=-19) Jun 3 11:21:20 WatchTower kernel: ata12: SRST failed (errno=-16) ... Jun 3 12:35:18 WatchTower kernel: ata12: reset failed, giving up Jun 3 12:35:18 WatchTower kernel: ata12.00: disabled Jun 3 12:35:18 WatchTower kernel: ata12.00: device reported invalid CHS sector 0 Jun 3 12:35:18 WatchTower kernel: ata12: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xe frozen t4 Jun 3 12:35:18 WatchTower kernel: ata12: hotplug_status 0x4 Jun 3 12:35:18 WatchTower kernel: ata12: hard resetting link Jun 3 12:35:18 WatchTower kernel: ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 3 12:35:18 WatchTower kernel: ata12.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7 Jun 3 12:35:18 WatchTower kernel: ata12.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32) Jun 3 12:35:18 WatchTower kernel: ata12.00: configured for UDMA/133 Jun 3 12:35:18 WatchTower kernel: sd 12:0:0:0: [sdl] Result: hostbyte=0x00 driverbyte=0x08 Jun 3 12:35:18 WatchTower kernel: sd 12:0:0:0: [sdl] Sense Key : 0xb [current] [descriptor] Jun 3 12:35:18 WatchTower kernel: Descriptor sense data with sense descriptors (in hex): Jun 3 12:35:18 WatchTower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Jun 3 12:35:18 WatchTower kernel: 00 00 00 00 Jun 3 12:35:18 WatchTower kernel: sd 12:0:0:0: [sdl] ASC=0x0 ASCQ=0x0 Jun 3 12:35:18 WatchTower kernel: sd 12:0:0:0: [sdl] CDB: cdb[0]=0x28: 28 00 18 8a fb 27 00 00 08 00 Jun 3 12:35:18 WatchTower kernel: end_request: I/O error, dev sdl, sector 411761447 Jun 3 12:35:18 WatchTower kernel: Buffer I/O error on device sdl1, logical block 51470173 Jun 3 12:35:18 WatchTower kernel: sd 12:0:0:0: rejecting I/O to offline device Jun 3 12:35:18 WatchTower kernel: ata12: EH complete Jun 3 12:35:18 WatchTower kernel: sd 12:0:0:0: rejecting I/O to offline device Jun 3 12:35:18 WatchTower kernel: ata12.00: detaching (SCSI 12:0:0:0) Jun 3 12:35:18 WatchTower kernel: REISERFS abort (device sdl1): Journal write error in flush_commit_list Jun 3 12:35:19 WatchTower kernel: sd 12:0:0:0: [sdl] Synchronizing SCSI cache Jun 3 12:35:19 WatchTower kernel: sd 12:0:0:0: [sdl] Stopping disk Jun 3 12:35:19 WatchTower kernel: scsi 12:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5 Jun 3 12:35:19 WatchTower kernel: sd 12:0:0:0: [sdq] 976773168 512-byte logical blocks: (500 GB/465 GiB) Jun 3 12:35:19 WatchTower kernel: sd 12:0:0:0: [sdq] Write Protect is off Jun 3 12:35:19 WatchTower kernel: sd 12:0:0:0: [sdq] Mode Sense: 00 3a 00 00 Jun 3 12:35:19 WatchTower kernel: sd 12:0:0:0: [sdq] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 3 12:35:21 WatchTower kernel: sdq: sdq1 Jun 3 12:35:21 WatchTower kernel: sd 12:0:0:0: [sdq] Attached SCSI disk Jun 3 12:35:28 WatchTower kernel: REISERFS error (device sdl1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6 7 0x0 SD] Jun 3 12:35:29 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:36:04 WatchTower last message repeated 3 times Jun 3 12:37:08 WatchTower last message repeated 6 times Jun 3 12:37:49 WatchTower last message repeated 4 times Jun 3 12:37:49 WatchTower logger: rsync: read errors mapping "/mnt/cache/Drama/PATTON.ISO": Input/output error (5) Jun 3 12:37:49 WatchTower logger: >f..t...... Drama/PATTON.ISO Jun 3 12:37:59 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:38:40 WatchTower last message repeated 4 times Jun 3 12:39:50 WatchTower last message repeated 6 times Jun 3 12:40:20 WatchTower last message repeated 3 times Jun 3 12:40:30 WatchTower kernel: REISERFS error (device sdl1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6 7 0x0 SD] Jun 3 12:40:30 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:41:01 WatchTower last message repeated 3 times Jun 3 12:41:21 WatchTower last message repeated 2 times Jun 3 12:41:30 WatchTower logger: rsync: read errors mapping "/mnt/cache/Drama/PATTON.ISO": Input/output error (5) Jun 3 12:41:30 WatchTower logger: ERROR: Drama/PATTON.ISO failed verification -- update retained. Jun 3 12:41:30 WatchTower logger: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1040) [sender=3.0.4] Jun 3 12:41:30 WatchTower logger: ./Drama Jun 3 12:41:30 WatchTower logger: ./Animated/Fantastic Mr Fox.iso Jun 3 12:41:30 WatchTower logger: find: ./Animated/Fantastic Mr Fox.iso: Permission denied Jun 3 12:41:30 WatchTower logger: find: ./Animated/Fantastic Mr Fox.iso: Permission denied Jun 3 12:41:30 WatchTower logger: ./Animated Jun 3 12:41:30 WatchTower kernel: REISERFS error (device sdl1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6 7 0x0 SD] Jun 3 12:41:30 WatchTower kernel: REISERFS error (device sdl1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6 7 0x0 SD] Jun 3 12:41:30 WatchTower logger: .d..t...... Animated/ Jun 3 12:41:30 WatchTower logger: . Jun 3 12:41:40 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:41:42 WatchTower logger: mover finished Jun 3 12:41:50 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:42:30 WatchTower last message repeated 4 times Jun 3 12:43:31 WatchTower last message repeated 6 times Jun 3 12:43:41 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:43:49 WatchTower kernel: REISERFS error (device sdl1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6 7 0x0 SD] Jun 3 12:43:51 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:44:00 WatchTower kernel: REISERFS error (device sdl1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6 7 0x0 SD] Jun 3 12:44:01 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:44:11 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:44:12 WatchTower kernel: REISERFS error (device sdl1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6 7 0x0 SD] Jun 3 12:44:21 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:44:24 WatchTower kernel: REISERFS error (device sdl1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6 7 0x0 SD] Jun 3 12:44:31 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:44:37 WatchTower kernel: REISERFS error (device sdl1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6 7 0x0 SD] Jun 3 12:44:41 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:44:49 WatchTower kernel: REISERFS error (device sdl1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6 7 0x0 SD] Jun 3 12:44:51 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:45:01 WatchTower emhttp: disk_spinning: open: No such file or directory Jun 3 12:45:02 WatchTower kernel: REISERFS error (device sdl1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6 7 0x0 SD]
June 3, 201016 yr Here's the chain of events: 1) Performed a pre-clear on a new disk overnight, the next morning I found the system had crashed and had to do a hard reboot. 2) Checked the web console afterwards and found it doing a parity check (as expected), but the cache drive was showing up as unformatted. I was running 4.5.3 and knew that there was a problem with disks incorrectly showing up as unformatted, so I just let it go until it finished the parity check. Installed 4.5.4 during the parity check so it would be updated after the next reboot. 3) This morning the parity check was finished so I rebooted, this time it showed the cache drive was missing. It showed a disk was assigned but that it was not present. I shut down, pulled the disk out of the icy dock, blew off the connectors, reinserted and booted. 4) Checked the web console again and the cache drive showed up properly. Manually invoked the mover (I had 3 ISO's on the cache drive), checked that the cache drive's read count was incrementing on the web console and went to lunch. 5) I just got back from lunch and the write count on the cache disk is huge and growing. I checked the syslog and there are all sorts of errors (see syslog below) for the cache drive (/dev/sdl). I shut down the array. I started it up again briefly to check something, and the cache disk is again showing up as unformatted. Stopped array again. I haven't seen these errors before so I'm not sure how to interpret them. One thing that I find a bit odd is that the main unRAID web console shows the cache disk is /dev/sdl, but unMenu's Disk Management page shows the disk with the same serial number is /dev/sdq. SMART (short test anyways), is showing no problems with the drive. Any ideas? Thanks! You atached enough of the syslog to show that the disk controller timed out, attempted again and again to re-establish communications and reset the drive but had no luck. It eventually gave up trying, disconnected itself from the disk and then, when it was able to re-establish communications (the disk appeared again somehow), assigned it a different device. What was /dev/sdl now became /dev/sdq. Jun 3 12:35:18 WatchTower kernel: end_request: I/O error, dev sdl, sector 411761447 Jun 3 12:35:18 WatchTower kernel: Buffer I/O error on device sdl1, logical block 51470173 Jun 3 12:35:18 WatchTower kernel: sd 12:0:0:0: rejecting I/O to offline device Jun 3 12:35:18 WatchTower kernel: ata12: EH complete Jun 3 12:35:18 WatchTower kernel: sd 12:0:0:0: rejecting I/O to offline device Jun 3 12:35:18 WatchTower kernel: ata12.00: detaching (SCSI 12:0:0:0) Jun 3 12:35:18 WatchTower kernel: REISERFS abort (device sdl1): Journal write error in flush_commit_list Jun 3 12:35:19 WatchTower kernel: sd 12:0:0:0: [sdl] Synchronizing SCSI cache Jun 3 12:35:19 WatchTower kernel: sd 12:0:0:0: [sdl] Stopping disk Jun 3 12:35:19 WatchTower kernel: scsi 12:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5 Jun 3 12:35:19 WatchTower kernel: sd 12:0:0:0: [sdq] 976773168 512-byte logical blocks: (500 GB/465 GiB) Jun 3 12:35:19 WatchTower kernel: sd 12:0:0:0: [sdq] Write Protect is off Jun 3 12:35:19 WatchTower kernel: sd 12:0:0:0: [sdq] Mode Sense: 00 3a 00 00 Jun 3 12:35:19 WatchTower kernel: sd 12:0:0:0: [sdq] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jun 3 12:35:21 WatchTower kernel: sdq: sdq1 Jun 3 12:35:21 WatchTower kernel: sd 12:0:0:0: [sdq] Attached SCSI disk Jun 3 12:35:28 WatchTower kernel: REISERFS error (device sdl1): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [6 7 0x0 SD] Jun 3 12:35:29 WatchTower emhttp: disk_spinning: open: No such file or directory Of course, once it did the re-assignment and changed devices under the unRAID "md" driver, all attempts to communicate with the disk as /dev/sdl failed. Could be anything intermittent. A power cable, an SATA cable, the icy-dock bay itself being intermittent, or even the disk drive. It could even be the power supply not being capable to supply noise free voltages to the drive and the drive getting confused to where it would not respond. Good luck trying to isolate the actual issue. I'd first eliminate the icy-dock and cable, unless you spot something loose. Make sure you power down AND unplug the server when moving things around. Don't want you to be a candidate for the Darwin award. Joe L.
June 4, 201016 yr Author I think you nailed it. I moved the cache disk to another empty slot in a different Icy Dock and on a different SATA controller. It appears to work just fine now. So I think the disk is ok and it is probably the SATA controller, the Icy Dock, or one of the cables going to it. Interestingly, the new drive I put in to pre-clear when all this happened was in the spot above this drive, in the same IcyDock and on the same SATA controller. I'm going to keep a close eye on things, but I'm planning on rebuilding the server with components from my current HTPC when I go live with my new one, so I'm probably not going to spend much time on it since the IcyDock is the only thing that will be kept - I will try to test that thoroughly though. Thanks for your help Joe
Archived
This topic is now archived and is closed to further replies.