generalz Posted September 12, 2011 Share Posted September 12, 2011 Spin down stopped working for me on onboard sata ports. I started getting the errors below. Jul 26 00:30:34 Fileserver02 kernel: mdcmd (56): spindown 3 Jul 26 00:31:17 Fileserver02 kernel: ata7: exception Emask 0x10 SAct 0x0 SErr 0x1810000 action 0xe frozen Jul 26 00:31:17 Fileserver02 kernel: ata7: irq_stat 0x00400000, PHY RDY changed Jul 26 00:31:17 Fileserver02 kernel: ata7: SError: { PHYRdyChg LinkSeq TrStaTrns } Jul 26 00:31:17 Fileserver02 kernel: ata7: hard resetting link Jul 26 00:31:23 Fileserver02 kernel: ata7: link is slow to respond, please be patient (ready=0) Jul 26 00:31:27 Fileserver02 kernel: ata7: COMRESET failed (errno=-16) Jul 26 00:31:27 Fileserver02 kernel: ata7: hard resetting link Jul 26 00:31:29 Fileserver02 kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jul 26 00:31:29 Fileserver02 kernel: ata7.00: configured for UDMA/133 Jul 26 00:31:29 Fileserver02 kernel: ata7: EH complete Jul 26 00:31:29 Fileserver02 kernel: mdcmd (57): spindown 2 I purchased a new BR10i and flashed it to the latest P20 IT firmware and purchased some forward breakout cables from Monoprice and now when the drives spin down unraid seems to disable them and I have to go through the process of rebuilding the drive. Sep 11 01:12:01 Fileserver02 kernel: md: recovery thread sync completion status: 0 Sep 11 01:27:10 Fileserver02 kernel: mdcmd (30): spindown 0 Sep 11 01:30:51 Fileserver02 kernel: mdcmd (31): spindown 2 Sep 11 01:30:51 Fileserver02 kernel: mdcmd (32): spindown 3 Sep 11 01:32:52 Fileserver02 kernel: mdcmd (33): spindown 4 Sep 11 01:34:51 Fileserver02 kernel: mptbase: ioc0: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptbase_reply Sep 11 01:34:55 Fileserver02 kernel: mptbase: ioc0: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptscsih_io_done Sep 11 01:34:55 Fileserver02 kernel: mptbase: ioc0: LogInfo(0x31130000): Originator={PL}, Code={IO Not Yet Executed}, SubCode(0x0000) cb_idx mptscsih_io_done Sep 11 01:34:55 Fileserver02 kernel: mdcmd (34): spindown 2 Sep 11 01:34:55 Fileserver02 kernel: end_device-5:1: mptsas: ioc0: removing sata device: fw_channel 0, fw_id 2, phy 1,sas_addr 0x529280781744880 Sep 11 01:34:55 Fileserver02 kernel: phy-5:1: mptsas: ioc0: delete phy 1, phy-obj (0xf1b27200) Sep 11 01:34:55 Fileserver02 kernel: port-5:1: mptsas: ioc0: delete port 1, sas_addr (0x529280781744880) Sep 11 01:34:55 Fileserver02 emhttp: mdcmd: write: Invalid argument Sep 11 01:34:55 Fileserver02 kernel: md: disk2: ATA_OP e0 ioctl error: -22 Sep 11 01:34:55 Fileserver02 kernel: sd 5:0:1:0: [sdc] Synchronizing SCSI cache Sep 11 01:34:55 Fileserver02 kernel: sd 5:0:1:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00 Sep 11 01:35:04 Fileserver02 kernel: mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 2, phy 1, sas_addr 0x529280781744880 Sep 11 01:35:04 Fileserver02 kernel: scsi 5:0:6:0: Direct-Access ATA ST32000542AS CC95 PQ: 0 ANSI: 5 Sep 11 01:35:04 Fileserver02 kernel: sd 5:0:6:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Sep 11 01:35:04 Fileserver02 kernel: sd 5:0:6:0: [sdh] Write Protect is off Sep 11 01:35:04 Fileserver02 kernel: sd 5:0:6:0: [sdh] Mode Sense: 73 00 00 08 Sep 11 01:35:04 Fileserver02 kernel: sd 5:0:6:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 11 01:35:04 Fileserver02 kernel: sdh: sdh1 Sep 11 01:35:04 Fileserver02 kernel: sd 5:0:6:0: [sdh] Attached SCSI disk Sep 11 01:35:05 Fileserver02 emhttp: mdcmd: write: No such device or address Sep 11 01:35:05 Fileserver02 kernel: mdcmd (35): spindown 2 full log located here http://db.tt/owGIhXd are the drives/card just not compatable with the spin down feature? Quote Link to comment
gfjardim Posted September 12, 2011 Share Posted September 12, 2011 As I can see on the syslog, you have stopped and started the array many times before the error occour. The controller reseted the SATA link and after that, reassigned the drive path from /dev/sdc to /dev/sdh, very odd behavior. The drive linked with this error is ST32000542AS serial 5XW1ZM3Z, with a "CC95" firmware, which is odd because the last firmware for this drive model is CC35. Try moving this drive to other SATA port, repeat all steps and post the result. Probably this is caused by a bad SATA cable. Quote Link to comment
generalz Posted September 12, 2011 Author Share Posted September 12, 2011 As I can see on the syslog, you have stopped and started the array many times before the error occour. The controller reseted the SATA link and after that, reassigned the drive path from /dev/sdc to /dev/sdh, very odd behavior. The drive linked with this error is ST32000542AS serial 5XW1ZM3Z, with a "CC95" firmware, which is odd because the last firmware for this drive model is CC35. Try moving this drive to other SATA port, repeat all steps and post the result. Probably this is caused by a bad SATA cable. Yea I didn't read the instructions for the drive rebuild correctly. I thought you had to stop the array unassign and reassign the drive for it to start, once I figured out that I needed to start/ the array in between to get the rebuild going it started the rebuild. after the rebuild finished when it went to sleep the drives thats when it reset the link, so i thought the same thing bad cable and so I shut it down moved it to another cable and it changed to sdh with the same results. CC95 is what came on the retail drives, CC35 is whats on the oem drives, I have two of each. Quote Link to comment
generalz Posted September 12, 2011 Author Share Posted September 12, 2011 I did a fresh reboot with nothing started but unmenu. set all the drives to spin down in 15 minutes and waited. I refreshed the main unraid window and this is what popped up in the syslog not sure why it would want to write to that drive just refreshing the window or why if it wanted to write it didn't spin it up first. updated full log http://db.tt/KLVf4RG Sep 12 11:16:02 Fileserver02 kernel: mdcmd (65): spindown 3 Sep 12 11:16:03 Fileserver02 kernel: mdcmd (66): spindown 4 Sep 12 11:32:50 Fileserver02 kernel: mptbase: ioc0: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptbase_reply Sep 12 11:32:54 Fileserver02 kernel: end_device-1:4: mptsas: ioc0: removing sata device: fw_channel 0, fw_id 2, phy 6,sas_addr 0x529280781744880 Sep 12 11:32:54 Fileserver02 kernel: phy-1:6: mptsas: ioc0: delete phy 6, phy-obj (0xefdd8000) Sep 12 11:32:54 Fileserver02 kernel: port-1:4: mptsas: ioc0: delete port 4, sas_addr (0x529280781744880) Sep 12 11:32:54 Fileserver02 kernel: sd 1:0:5:0: [sdg] Synchronizing SCSI cache Sep 12 11:32:54 Fileserver02 kernel: sd 1:0:5:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00 Sep 12 11:32:55 Fileserver02 emhttp: mdcmd: write: No such device or address Sep 12 11:32:55 Fileserver02 kernel: mdcmd (67): spindown 2 Sep 12 11:33:04 Fileserver02 kernel: mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 2, phy 6, sas_addr 0x529280781744880 Sep 12 11:33:04 Fileserver02 kernel: scsi 1:0:6:0: Direct-Access ATA ST32000542AS CC95 PQ: 0 ANSI: 5 Sep 12 11:33:04 Fileserver02 kernel: sd 1:0:6:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Sep 12 11:33:04 Fileserver02 kernel: sd 1:0:6:0: [sdh] Write Protect is off Sep 12 11:33:04 Fileserver02 kernel: sd 1:0:6:0: [sdh] Mode Sense: 73 00 00 08 Sep 12 11:33:04 Fileserver02 kernel: sd 1:0:6:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 12 11:33:04 Fileserver02 kernel: sdh: sdh1 Sep 12 11:33:04 Fileserver02 kernel: sd 1:0:6:0: [sdh] Attached SCSI disk Sep 12 11:33:05 Fileserver02 emhttp: mdcmd: write: No such device or address Sep 12 11:33:05 Fileserver02 kernel: mdcmd (68): spindown 2 Sep 12 11:33:15 Fileserver02 emhttp: mdcmd: write: No such device or address Sep 12 11:33:15 Fileserver02 kernel: mdcmd (69): spindown 2 Sep 12 11:33:25 Fileserver02 emhttp: mdcmd: write: No such device or address Sep 12 11:33:25 Fileserver02 kernel: mdcmd (70): spindown 2 Sep 12 11:33:35 Fileserver02 emhttp: mdcmd: write: No such device or address Quote Link to comment
prostuff1 Posted September 12, 2011 Share Posted September 12, 2011 That makes me think there might be a cabling and or backplane issue. Quote Link to comment
gfjardim Posted September 12, 2011 Share Posted September 12, 2011 I did a fresh reboot with nothing started but unmenu. set all the drives to spin down in 15 minutes and waited. I refreshed the main unraid window and this is what popped up in the syslog not sure why it would want to write to that drive just refreshing the window or why if it wanted to write it didn't spin it up first. updated full log http://db.tt/KLVf4RG Sep 12 11:16:02 Fileserver02 kernel: mdcmd (65): spindown 3 Sep 12 11:16:03 Fileserver02 kernel: mdcmd (66): spindown 4 Sep 12 11:32:50 Fileserver02 kernel: mptbase: ioc0: LogInfo(0x31110d00): Originator={PL}, Code={Reset}, SubCode(0x0d00) cb_idx mptbase_reply Sep 12 11:32:54 Fileserver02 kernel: end_device-1:4: mptsas: ioc0: removing sata device: fw_channel 0, fw_id 2, phy 6,sas_addr 0x529280781744880 Sep 12 11:32:54 Fileserver02 kernel: phy-1:6: mptsas: ioc0: delete phy 6, phy-obj (0xefdd8000) Sep 12 11:32:54 Fileserver02 kernel: port-1:4: mptsas: ioc0: delete port 4, sas_addr (0x529280781744880) Sep 12 11:32:54 Fileserver02 kernel: sd 1:0:5:0: [sdg] Synchronizing SCSI cache Sep 12 11:32:54 Fileserver02 kernel: sd 1:0:5:0: [sdg] Result: hostbyte=0x01 driverbyte=0x00 Sep 12 11:32:55 Fileserver02 emhttp: mdcmd: write: No such device or address Sep 12 11:32:55 Fileserver02 kernel: mdcmd (67): spindown 2 Sep 12 11:33:04 Fileserver02 kernel: mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 2, phy 6, sas_addr 0x529280781744880 Sep 12 11:33:04 Fileserver02 kernel: scsi 1:0:6:0: Direct-Access ATA ST32000542AS CC95 PQ: 0 ANSI: 5 Sep 12 11:33:04 Fileserver02 kernel: sd 1:0:6:0: [sdh] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Sep 12 11:33:04 Fileserver02 kernel: sd 1:0:6:0: [sdh] Write Protect is off Sep 12 11:33:04 Fileserver02 kernel: sd 1:0:6:0: [sdh] Mode Sense: 73 00 00 08 Sep 12 11:33:04 Fileserver02 kernel: sd 1:0:6:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 12 11:33:04 Fileserver02 kernel: sdh: sdh1 Sep 12 11:33:04 Fileserver02 kernel: sd 1:0:6:0: [sdh] Attached SCSI disk Sep 12 11:33:05 Fileserver02 emhttp: mdcmd: write: No such device or address Sep 12 11:33:05 Fileserver02 kernel: mdcmd (68): spindown 2 Sep 12 11:33:15 Fileserver02 emhttp: mdcmd: write: No such device or address Sep 12 11:33:15 Fileserver02 kernel: mdcmd (69): spindown 2 Sep 12 11:33:25 Fileserver02 emhttp: mdcmd: write: No such device or address Sep 12 11:33:25 Fileserver02 kernel: mdcmd (70): spindown 2 Sep 12 11:33:35 Fileserver02 emhttp: mdcmd: write: No such device or address The error is definitely caused by the drive being kicked out and reinserted by the controller, this is a physical hardware issue, more likely to be triggered by a bad power/SATA cable or cable/drive connectors. Quote Link to comment
generalz Posted September 12, 2011 Author Share Posted September 12, 2011 yea I guess i need to RMA the drive. I thought it might have been the controller but since the problem follows the drive I guess that's not it. thanks for the help! Quote Link to comment
generalz Posted September 23, 2011 Author Share Posted September 23, 2011 Ugg, not sure what to do now. Looks like drive 1 started to fail? Sep 22 14:23:31 Fileserver02 kernel: sdb: sdb1 (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] Device not ready (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] Result: hostbyte=0x00 driverbyte=0x08 (System) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] Sense Key : 0x2 [current] (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] ASC=0x4 ASCQ=0x2 (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] CDB: cdb[0]=0x28: 28 00 92 02 2e 78 00 00 08 00 (Drive related) Sep 22 18:08:52 Fileserver02 kernel: end_request: I/O error, dev sdg, sector 2449616504 (Errors) Sep 22 18:08:52 Fileserver02 kernel: md: disk1 read error (Errors) Sep 22 18:08:52 Fileserver02 kernel: handle_stripe read error: 2449616440/1, count: 1 (Errors) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] Device not ready (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] Result: hostbyte=0x00 driverbyte=0x08 (System) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] Sense Key : 0x2 [current] (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] ASC=0x4 ASCQ=0x2 (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] CDB: cdb[0]=0x2a: 2a 00 92 02 2e 78 00 00 08 00 (Drive related) Sep 22 18:08:52 Fileserver02 kernel: end_request: I/O error, dev sdg, sector 2449616504 (Errors) Sep 22 18:08:52 Fileserver02 kernel: md: disk1 write error (Errors) Sep 22 18:08:52 Fileserver02 kernel: handle_stripe write error: 2449616440/1, count: 1 (Errors) Sep 22 18:08:52 Fileserver02 kernel: md: recovery thread woken up ... (unRAID engine) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] Device not ready (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] Result: hostbyte=0x00 driverbyte=0x08 (System) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] Sense Key : 0x2 [current] (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] ASC=0x4 ASCQ=0x2 (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] CDB: cdb[0]=0x28: 28 00 76 54 00 48 00 00 08 00 (Drive related) Sep 22 18:08:52 Fileserver02 kernel: end_request: I/O error, dev sdg, sector 1985216584 (Errors) Sep 22 18:08:52 Fileserver02 kernel: md: disk1 read error (Errors) Sep 22 18:08:52 Fileserver02 kernel: handle_stripe read error: 1985216520/1, count: 1 (Errors) Sep 22 18:08:52 Fileserver02 kernel: md: recovery thread has nothing to resync (unRAID engine) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] Device not ready (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] Result: hostbyte=0x00 driverbyte=0x08 (System) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] Sense Key : 0x2 [current] (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] ASC=0x4 ASCQ=0x2 (Drive related) Sep 22 18:08:52 Fileserver02 kernel: sd 9:0:4:0: [sdg] CDB: cdb[0]=0x2a: 2a 00 76 54 00 48 00 00 08 00 (Drive related) Sep 22 18:08:52 Fileserver02 kernel: end_request: I/O error, dev sdg, sector 1985216584 (Errors) Sep 22 18:08:52 Fileserver02 kernel: md: disk1 write error (Errors) Sep 22 18:08:52 Fileserver02 kernel: handle_stripe write error: 1985216520/1, count: 1 (Errors) Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.