[Plugin] Spin Down SAS Drives


doron

Recommended Posts

On 7/1/2021 at 3:10 PM, billington.mark said:

Is there a reason the Constellation ES.3 is currently #'d from the exclusion list if its still misbehaving?

Going from experience and after the fact, the Seagate constellation range is all over the place, with in particular the 3TB drives having horrible reliability (brought 4 drives off ebay, it took a total of 7 drives shipped to get 4 working ones) But the 4tb drives i brought have been fine...

They seem to have a range of great to terrible depending on capacity :P

Link to comment
  • 3 weeks later...

I have a Seagate Enterprise Capacity 6TB drive (ST6000NM0034) that will not spin down.  Anything I can provide to help determine why I will do my best to.

 

I see the following in my syslog.

 

Quote

Jul 20 09:54:09 BB-8 SAS Assist v0.85: Spinning down device /dev/sdg
Jul 20 09:54:27 BB-8 emhttpd: read SMART /dev/sdg
Jul 20 09:54:39 BB-8 kernel: mdcmd (37): set md_write_method 0
Jul 20 09:54:39 BB-8 kernel:

 

Link to comment
1 hour ago, shaunmccloud said:

I have a Seagate Enterprise Capacity 6TB drive (ST6000NM0034) that will not spin down.  Anything I can provide to help determine why I will do my best to.

 

I see the following in my syslog.

 

 

Which Unraid version are you running

Link to comment
7 hours ago, shaunmccloud said:

I have a Seagate Enterprise Capacity 6TB drive (ST6000NM0034) that will not spin down.  Anything I can provide to help determine why I will do my best to.

 

 

What Simon said. Basically, as of 6.9.2, some SAS drives (mainly Seagates) and also some SATA drives have an issue with spindown. Essentially they appear to spin down but then immediately spin back up. Not sure yet re the source of this issue, might be kernel/driver related, probably not related to the plugin (as (a) it happens with SATA drives as well and (b) some SAS drives spin down and up perfectly under 6.9.2).

  • Like 1
Link to comment
  • 4 weeks later...
4 hours ago, mike2246 said:

I have 8 of these 6TB SAS Drives ST6000NM0285 - none spin down with 6.9.2, all of my other SATA Drives (mixed array) spin down normally. anything I can do to try or just wait for 6.9.3?

One thing for sure - do not hold your breath waiting for 6.9.3 🙂 (The next stable version is going to be 6.10.0.)

More seriously: Did the spindown work for your SAS drives on 6.9.1?

Can you attach a snippet of your syslog at the time of the expected spindown?

Link to comment

My array will now spin down.

1) Removed the "Spin Down SAS Drives 0.85" plugin.

2) Upgraded to 6.10.0-rc1

3) Installed "Spin Down SAS Drives 0.85" plugin.

 

I can finally manually spin down the array and get the gray icons in the GUI.

 

Aug 14 23:13:17 DeepCore2 root: plugin: running: anonymous
Aug 14 23:13:17 DeepCore2 sas-spindown plugin: Unraid version 6.10.0-rc1 detected, using new method (emhttp hook)
Aug 14 23:13:17 DeepCore2 sas-spindown plugin: Installing SAS spindown/up script sdspin...
Aug 14 23:13:17 DeepCore2 sas-spindown plugin: Retrieved the latest exclusions file...
Aug 14 23:13:17 DeepCore2 sas-spindown plugin: Installing most recent exclusions file...
Aug 14 23:13:17 DeepCore2 sas-spindown plugin: Retrieved the latest sas-util...
Aug 14 23:13:18 DeepCore2 sas-spindown plugin: Installing sas-util...
Aug 14 23:14:31 DeepCore2 emhttpd: spinning down /dev/sdg
Aug 14 23:14:31 DeepCore2 emhttpd: spinning down /dev/sdd
Aug 14 23:14:31 DeepCore2 emhttpd: spinning down /dev/sde
Aug 14 23:14:31 DeepCore2 emhttpd: spinning down /dev/sdb
Aug 14 23:14:31 DeepCore2 emhttpd: spinning down /dev/sdf
Aug 14 23:14:31 DeepCore2 emhttpd: spinning down /dev/sdc
Aug 14 23:14:31 DeepCore2 SAS Assist v0.85: Spinning down device /dev/sdd
Aug 14 23:14:31 DeepCore2 SAS Assist v0.85: Spinning down device /dev/sde
Aug 14 23:14:31 DeepCore2 SAS Assist v0.85: Spinning down device /dev/sdg
Aug 14 23:14:31 DeepCore2 SAS Assist v0.85: Spinning down device /dev/sdb
Aug 14 23:14:31 DeepCore2 SAS Assist v0.85: Spinning down device /dev/sdf
Aug 14 23:14:31 DeepCore2 SAS Assist v0.85: Spinning down device /dev/sdc
Aug 14 23:15:31 DeepCore2 kernel: mdcmd (41): set md_num_stripes 1280
Aug 14 23:15:31 DeepCore2 kernel: mdcmd (42): set md_queue_limit 80
Aug 14 23:15:31 DeepCore2 kernel: mdcmd (43): set md_sync_limit 5
Aug 14 23:15:31 DeepCore2 kernel: mdcmd (44): set md_write_method
Aug 14 23:16:36 DeepCore2 kernel: mdcmd (45): set md_write_method 0

Edited by SFord
Link to comment
6 hours ago, SFord said:

My array will now spin down.

1) Removed the "Spin Down SAS Drives 0.85" plugin.

2) Upgraded to 6.10.0-rc1

3) Installed "Spin Down SAS Drives 0.85" plugin.

 

I can finally manually spin down the array and get the gray icons in the GUI.

 

Aug 14 23:13:17 DeepCore2 root: plugin: running: anonymous
Aug 14 23:13:17 DeepCore2 sas-spindown plugin: Unraid version 6.10.0-rc1 detected, using new method (emhttp hook)
Aug 14 23:13:17 DeepCore2 sas-spindown plugin: Installing SAS spindown/up script sdspin...
Aug 14 23:13:17 DeepCore2 sas-spindown plugin: Retrieved the latest exclusions file...
Aug 14 23:13:17 DeepCore2 sas-spindown plugin: Installing most recent exclusions file...
Aug 14 23:13:17 DeepCore2 sas-spindown plugin: Retrieved the latest sas-util...
Aug 14 23:13:18 DeepCore2 sas-spindown plugin: Installing sas-util...
Aug 14 23:14:31 DeepCore2 emhttpd: spinning down /dev/sdg
Aug 14 23:14:31 DeepCore2 emhttpd: spinning down /dev/sdd
Aug 14 23:14:31 DeepCore2 emhttpd: spinning down /dev/sde
Aug 14 23:14:31 DeepCore2 emhttpd: spinning down /dev/sdb
Aug 14 23:14:31 DeepCore2 emhttpd: spinning down /dev/sdf
Aug 14 23:14:31 DeepCore2 emhttpd: spinning down /dev/sdc
Aug 14 23:14:31 DeepCore2 SAS Assist v0.85: Spinning down device /dev/sdd
Aug 14 23:14:31 DeepCore2 SAS Assist v0.85: Spinning down device /dev/sde
Aug 14 23:14:31 DeepCore2 SAS Assist v0.85: Spinning down device /dev/sdg
Aug 14 23:14:31 DeepCore2 SAS Assist v0.85: Spinning down device /dev/sdb
Aug 14 23:14:31 DeepCore2 SAS Assist v0.85: Spinning down device /dev/sdf
Aug 14 23:14:31 DeepCore2 SAS Assist v0.85: Spinning down device /dev/sdc
Aug 14 23:15:31 DeepCore2 kernel: mdcmd (41): set md_num_stripes 1280
Aug 14 23:15:31 DeepCore2 kernel: mdcmd (42): set md_queue_limit 80
Aug 14 23:15:31 DeepCore2 kernel: mdcmd (43): set md_sync_limit 5
Aug 14 23:15:31 DeepCore2 kernel: mdcmd (44): set md_write_method
Aug 14 23:16:36 DeepCore2 kernel: mdcmd (45): set md_write_method 0

Which drives do you have?

Link to comment

Folks, I have just posted a new version (0.86) of the plugin.

 

This version works around an issue introduced with Unraid 6.10-rc1, where some SAS drives would spin back up immediately after being spun down. Other drives (including all of mine...) do not exhibit this behavior.

 

Turns out those drives suddenly became sensitive to a specific "sdparm" query call (get VPD), which should not (and did not in the past) affect the drive's spin status in any way.

Chances are this is a result of newer drivers bundled with the Unraid OS.

 

At any rate, the SAS drive detection logic of the plugin was rewritten in order to work around that phenomena.

 

Enjoy. Please let me know of any issues or funny stuff.

 

  • Like 1
  • Thanks 2
Link to comment
  • 2 weeks later...

G'day, I've been having a specific problem with my box for about two months now and essentially it's started after putting some SAS drives in. I don't want to point fingers yet, I'd just like some thoughts on it :) Server runs fine, things spin up and down ok until I start the windows 10 VM on my SSD. I have two log snippets here during the time things went to hell, first is with the SSD being an intel 120G sata and second being the hitachi 200G SAS (with SAS-Sata adapter) that replaced the intel SSD thinking it may have been on the way out.

The other drives in the box are Sata (including parity) except for two hitachi 2TB SAS (with SAS-Sata adapters).

Log 1: Intel 120G SSD

Spoiler

Aug 25 17:17:58 Tower SAS Assist v0.85: Spinning down device /dev/sdd
Aug 25 17:41:18 Tower emhttpd: spinning down /dev/sdj
Aug 25 17:41:18 Tower emhttpd: spinning down /dev/sdl
Aug 25 17:41:20 Tower kernel: sd 7:0:0:0: device_block, handle(0x0009)
Aug 25 17:41:20 Tower kernel: sd 7:0:2:0: device_block, handle(0x000b)
Aug 25 17:41:22 Tower kernel: sd 7:0:0:0: device_unblock and setting to running, handle(0x0009)
Aug 25 17:41:22 Tower kernel: sd 7:0:2:0: device_unblock and setting to running, handle(0x000b)
Aug 25 17:41:22 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x5000cca058787f4d)
Aug 25 17:41:22 Tower kernel: mpt2sas_cm0: removing handle(0x0009), sas_addr(0x5000cca058787f4d)
Aug 25 17:41:22 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b006630270), slot(0)
Aug 25 17:41:22 Tower kernel: sd 7:0:2:0: [sdh] Synchronizing SCSI cache
Aug 25 17:41:22 Tower kernel: sd 7:0:2:0: [sdh] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Aug 25 17:41:22 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221103000000)
Aug 25 17:41:22 Tower kernel: mpt2sas_cm0: removing handle(0x000b), sas_addr(0x4433221103000000)
Aug 25 17:41:22 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b006630270), slot(3)
Aug 25 17:41:23 Tower kernel: sd 7:0:4:0: device_block, handle(0x000d)
Aug 25 17:41:23 Tower kernel: sd 7:0:6:0: device_block, handle(0x000f)
Aug 25 17:41:23 Tower kernel: sd 7:0:7:0: device_block, handle(0x0010)
Aug 25 17:41:24 Tower kernel: sd 7:0:4:0: device_unblock and setting to running, handle(0x000d)
Aug 25 17:41:24 Tower kernel: sd 7:0:4:0: [sdj] Synchronizing SCSI cache
Aug 25 17:41:24 Tower kernel: sd 7:0:4:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Aug 25 17:41:24 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221104000000)
Aug 25 17:41:24 Tower kernel: mpt2sas_cm0: removing handle(0x000d), sas_addr(0x4433221104000000)
Aug 25 17:41:24 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b006630270), slot(4)
Aug 25 17:41:25 Tower kernel: sd 7:0:6:0: device_unblock and setting to running, handle(0x000f)
Aug 25 17:41:25 Tower kernel: sd 7:0:7:0: device_unblock and setting to running, handle(0x0010)
Aug 25 17:41:25 Tower kernel: sd 7:0:6:0: [sdl] Synchronizing SCSI cache
Aug 25 17:41:25 Tower kernel: sd 7:0:6:0: [sdl] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Aug 25 17:41:25 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221106000000)
Aug 25 17:41:25 Tower kernel: mpt2sas_cm0: removing handle(0x000f), sas_addr(0x4433221106000000)
Aug 25 17:41:25 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b006630270), slot(6)
Aug 25 17:41:25 Tower kernel: sd 7:0:7:0: [sdm] Synchronizing SCSI cache
Aug 25 17:41:25 Tower kernel: sd 7:0:7:0: [sdm] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Aug 25 17:41:25 Tower emhttpd: read SMART /dev/sdj
Aug 25 17:41:25 Tower emhttpd: read SMART /dev/sdh
Aug 25 17:41:25 Tower emhttpd: read SMART /dev/sdd
Aug 25 17:41:25 Tower emhttpd: read SMART /dev/sdl
Aug 25 17:41:25 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221107000000)
Aug 25 17:41:25 Tower kernel: mpt2sas_cm0: removing handle(0x0010), sas_addr(0x4433221107000000)
Aug 25 17:41:25 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b006630270), slot(7)
Aug 25 17:41:26 Tower emhttpd: read SMART /dev/sdm
Aug 25 17:41:57 Tower kernel: sd 7:0:5:0: attempting task abort!scmd(0x00000000d98b7b2d), outstanding for 30220 ms & timeout 30000 ms
Aug 25 17:41:57 Tower kernel: sd 7:0:5:0: [sdk] tag#1849 CDB: opcode=0x2a 2a 00 00 6d a2 58 00 00 08 00
Aug 25 17:41:57 Tower kernel: scsi target7:0:5: handle(0x000e), sas_address(0x4433221105000000), phy(5)
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1814 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=14s
Aug 25 17:41:57 Tower kernel: scsi target7:0:5: enclosure logical id(0x500605b006630270), slot(5)
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1814 CDB: opcode=0x28 28 00 0b 1d ec 98 00 00 80 00
Aug 25 17:42:01 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186510488 op 0x0:(READ) flags 0x80700 phys_seg 15 prio class 0
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: task abort: SUCCESS scmd(0x00000000d98b7b2d)
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1833 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=20s
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1833 Sense Key : 0x2 [current]
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1833 ASC=0x4 ASCQ=0x0
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1833 CDB: opcode=0x2a 2a 00 00 6d a2 e0 00 00 08 00
Aug 25 17:42:01 Tower kernel: blk_update_request: I/O error, dev sdk, sector 7185120 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
Aug 25 17:42:01 Tower kernel: Buffer I/O error on dev sdk, logical block 898140, lost async page write
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1834 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=20s
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1834 Sense Key : 0x2 [current]
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1834 ASC=0x4 ASCQ=0x0
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1834 CDB: opcode=0x2a 2a 00 03 f4 8f 30 00 00 80 00
Aug 25 17:42:01 Tower kernel: blk_update_request: I/O error, dev sdk, sector 66359088 op 0x1:(WRITE) flags 0x800 phys_seg 16 prio class 0
Aug 25 17:42:01 Tower kernel: Buffer I/O error on dev sdk, logical block 8294886, lost async page write
Aug 25 17:42:01 Tower kernel: Buffer I/O error on dev sdk, logical block 8294887, lost async page write
Aug 25 17:42:01 Tower kernel: Buffer I/O error on dev sdk, logical block 8294888, lost async page write
Aug 25 17:42:01 Tower kernel: Buffer I/O error on dev sdk, logical block 8294889, lost async page write
Aug 25 17:42:01 Tower kernel: Buffer I/O error on dev sdk, logical block 8294890, lost async page write
Aug 25 17:42:01 Tower kernel: Buffer I/O error on dev sdk, logical block 8294891, lost async page write
Aug 25 17:42:01 Tower kernel: Buffer I/O error on dev sdk, logical block 8294892, lost async page write
Aug 25 17:42:01 Tower kernel: Buffer I/O error on dev sdk, logical block 8294893, lost async page write
Aug 25 17:42:01 Tower kernel: Buffer I/O error on dev sdk, logical block 8294894, lost async page write
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1835 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=34s
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1835 Sense Key : 0x2 [current]
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1835 ASC=0x4 ASCQ=0x0
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1835 CDB: opcode=0x2a 2a 00 00 6d a2 58 00 00 08 00
Aug 25 17:42:01 Tower kernel: blk_update_request: I/O error, dev sdk, sector 7184984 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1836 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1836 Sense Key : 0x2 [current]
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1836 ASC=0x4 ASCQ=0x0
Aug 25 17:42:01 Tower kernel: sd 7:0:5:0: [sdk] tag#1836 CDB: opcode=0x28 28 00 0b 1d ec 98 00 00 08 00
Aug 25 17:42:01 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186510488 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=4020, sector_sz=512)
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1840 CDB: opcode=0x28 28 00 0b 1d ec 98 00 00 08 00
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1840 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1840 Sense Key : 0x2 [current]
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1840 ASC=0x4 ASCQ=0x0
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1840 CDB: opcode=0x28 28 00 0b 1d ec 98 00 00 08 00
Aug 25 17:42:02 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186510488 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=32732, sector_sz=512)
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1841 CDB: opcode=0x28 28 00 00 87 ca 30 00 00 40 00
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1841 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1841 Sense Key : 0x2 [current]
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1841 ASC=0x4 ASCQ=0x0
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1841 CDB: opcode=0x28 28 00 00 87 ca 30 00 00 40 00
Aug 25 17:42:02 Tower kernel: blk_update_request: I/O error, dev sdk, sector 8899120 op 0x0:(READ) flags 0x80700 phys_seg 8 prio class 0
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=4064, sector_sz=512)
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1842 CDB: opcode=0x28 28 00 00 87 ca 30 00 00 08 00
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1842 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1842 Sense Key : 0x2 [current]
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1842 ASC=0x4 ASCQ=0x0
Aug 25 17:42:02 Tower kernel: sd 7:0:5:0: [sdk] tag#1842 CDB: opcode=0x28 28 00 00 87 ca 30 00 00 08 00
Aug 25 17:42:02 Tower kernel: blk_update_request: I/O error, dev sdk, sector 8899120 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 25 17:42:03 Tower kernel: sd 7:0:5:0: [sdk] tag#1848 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:03 Tower kernel: sd 7:0:5:0: [sdk] tag#1848 Sense Key : 0x2 [current]
Aug 25 17:42:03 Tower kernel: sd 7:0:5:0: [sdk] tag#1848 ASC=0x4 ASCQ=0x0
Aug 25 17:42:03 Tower kernel: sd 7:0:5:0: [sdk] tag#1848 CDB: opcode=0x28 28 00 0b 1d ec 98 00 00 08 00
Aug 25 17:42:03 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186510488 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 25 17:42:03 Tower kernel: sd 7:0:5:0: [sdk] tag#1850 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:03 Tower kernel: sd 7:0:5:0: [sdk] tag#1850 Sense Key : 0x2 [current]
Aug 25 17:42:03 Tower kernel: sd 7:0:5:0: [sdk] tag#1850 ASC=0x4 ASCQ=0x0
Aug 25 17:42:03 Tower kernel: sd 7:0:5:0: [sdk] tag#1850 CDB: opcode=0x28 28 00 00 87 ca 30 00 00 08 00
Aug 25 17:42:03 Tower kernel: blk_update_request: I/O error, dev sdk, sector 8899120 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Aug 25 17:42:04 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=4060, sector_sz=512)
Aug 25 17:42:04 Tower kernel: sd 7:0:5:0: [sdk] tag#1795 CDB: opcode=0x28 28 00 0b 1d ec 98 00 00 08 00
Aug 25 17:42:04 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=4064, sector_sz=512)
Aug 25 17:42:04 Tower kernel: sd 7:0:5:0: [sdk] tag#1796 CDB: opcode=0x28 28 00 00 87 ca 30 00 00 08 00
Aug 25 17:42:12 Tower emhttpd: read SMART /dev/sdc
Aug 25 17:42:14 Tower kernel: scsi_io_completion_action: 4 callbacks suppressed
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1818 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1818 Sense Key : 0x2 [current]
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1818 ASC=0x4 ASCQ=0x0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1818 CDB: opcode=0x2a 2a 00 00 2d 10 00 00 00 40 00
Aug 25 17:42:14 Tower kernel: print_req_error: 4 callbacks suppressed
Aug 25 17:42:14 Tower kernel: blk_update_request: I/O error, dev sdk, sector 2953216 op 0x1:(WRITE) flags 0x100000 phys_seg 8 prio class 0
Aug 25 17:42:14 Tower kernel: buffer_io_error: 17 callbacks suppressed
Aug 25 17:42:14 Tower kernel: Buffer I/O error on dev sdk, logical block 369152, lost async page write
Aug 25 17:42:14 Tower kernel: Buffer I/O error on dev sdk, logical block 369153, lost async page write
Aug 25 17:42:14 Tower kernel: Buffer I/O error on dev sdk, logical block 369154, lost async page write
Aug 25 17:42:14 Tower kernel: Buffer I/O error on dev sdk, logical block 369155, lost async page write
Aug 25 17:42:14 Tower kernel: Buffer I/O error on dev sdk, logical block 369156, lost async page write
Aug 25 17:42:14 Tower kernel: Buffer I/O error on dev sdk, logical block 369157, lost async page write
Aug 25 17:42:14 Tower kernel: Buffer I/O error on dev sdk, logical block 369158, lost async page write
Aug 25 17:42:14 Tower kernel: Buffer I/O error on dev sdk, logical block 369159, lost async page write
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1819 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1819 Sense Key : 0x2 [current]
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1819 ASC=0x4 ASCQ=0x0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1819 CDB: opcode=0x2a 2a 00 00 2e 9a 60 00 00 40 00
Aug 25 17:42:14 Tower kernel: blk_update_request: I/O error, dev sdk, sector 3054176 op 0x1:(WRITE) flags 0x100000 phys_seg 8 prio class 0
Aug 25 17:42:14 Tower kernel: Buffer I/O error on dev sdk, logical block 381772, lost async page write
Aug 25 17:42:14 Tower kernel: Buffer I/O error on dev sdk, logical block 381773, lost async page write
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1820 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1820 Sense Key : 0x2 [current]
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1820 ASC=0x4 ASCQ=0x0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1820 CDB: opcode=0x2a 2a 00 00 6d a2 50 00 00 20 00
Aug 25 17:42:14 Tower kernel: blk_update_request: I/O error, dev sdk, sector 7184976 op 0x1:(WRITE) flags 0x100000 phys_seg 4 prio class 0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1821 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1821 Sense Key : 0x2 [current]
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1821 ASC=0x4 ASCQ=0x0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1821 CDB: opcode=0x2a 2a 00 00 6d a2 e0 00 00 10 00
Aug 25 17:42:14 Tower kernel: blk_update_request: I/O error, dev sdk, sector 7185120 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1822 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1822 Sense Key : 0x2 [current]
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1822 ASC=0x4 ASCQ=0x0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1822 CDB: opcode=0x2a 2a 00 00 6f 8d 98 00 00 98 00
Aug 25 17:42:14 Tower kernel: blk_update_request: I/O error, dev sdk, sector 7310744 op 0x1:(WRITE) flags 0x100000 phys_seg 19 prio class 0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1823 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1823 Sense Key : 0x2 [current]
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1823 ASC=0x4 ASCQ=0x0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1823 CDB: opcode=0x2a 2a 00 00 71 bb 30 00 00 08 00
Aug 25 17:42:14 Tower kernel: blk_update_request: I/O error, dev sdk, sector 7453488 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1824 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1824 Sense Key : 0x2 [current]
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1824 ASC=0x4 ASCQ=0x0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1824 CDB: opcode=0x2a 2a 00 00 71 c8 88 00 00 08 00
Aug 25 17:42:14 Tower kernel: blk_update_request: I/O error, dev sdk, sector 7456904 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1825 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1825 Sense Key : 0x2 [current]
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1825 ASC=0x4 ASCQ=0x0
Aug 25 17:42:14 Tower kernel: sd 7:0:5:0: [sdk] tag#1825 CDB: opcode=0x2a 2a 00 03 7c 0a c8 00 01 00 00
Aug 25 17:42:14 Tower kernel: blk_update_request: I/O error, dev sdk, sector 58460872 op 0x1:(WRITE) flags 0x100000 phys_seg 32 prio class 0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1841 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1841 Sense Key : 0x2 [current]
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1841 ASC=0x4 ASCQ=0x0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1841 CDB: opcode=0x2a 2a 00 0b 14 74 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: blk_update_request: I/O error, dev sdk, sector 185890008 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 0
Aug 25 17:42:32 Tower kernel: buffer_io_error: 65 callbacks suppressed
Aug 25 17:42:32 Tower kernel: Buffer I/O error on dev sdk, logical block 23236251, lost async page write
Aug 25 17:42:32 Tower kernel: Buffer I/O error on dev sdk, logical block 23236252, lost async page write
Aug 25 17:42:32 Tower kernel: Buffer I/O error on dev sdk, logical block 23236253, lost async page write
Aug 25 17:42:32 Tower kernel: Buffer I/O error on dev sdk, logical block 23236254, lost async page write
Aug 25 17:42:32 Tower kernel: Buffer I/O error on dev sdk, logical block 23236255, lost async page write
Aug 25 17:42:32 Tower kernel: Buffer I/O error on dev sdk, logical block 23236256, lost async page write
Aug 25 17:42:32 Tower kernel: Buffer I/O error on dev sdk, logical block 23236257, lost async page write
Aug 25 17:42:32 Tower kernel: Buffer I/O error on dev sdk, logical block 23236258, lost async page write
Aug 25 17:42:32 Tower kernel: Buffer I/O error on dev sdk, logical block 23236259, lost async page write
Aug 25 17:42:32 Tower kernel: Buffer I/O error on dev sdk, logical block 23236260, lost async page write
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1842 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1842 Sense Key : 0x2 [current]
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1842 ASC=0x4 ASCQ=0x0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1842 CDB: opcode=0x2a 2a 00 0b 14 78 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: blk_update_request: I/O error, dev sdk, sector 185891032 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1843 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1843 Sense Key : 0x2 [current]
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1843 ASC=0x4 ASCQ=0x0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1843 CDB: opcode=0x2a 2a 00 0b 14 7c d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: blk_update_request: I/O error, dev sdk, sector 185892056 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1844 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1844 Sense Key : 0x2 [current]
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1844 ASC=0x4 ASCQ=0x0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1844 CDB: opcode=0x2a 2a 00 0b 14 80 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: blk_update_request: I/O error, dev sdk, sector 185893080 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1845 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1845 Sense Key : 0x2 [current]
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1845 ASC=0x4 ASCQ=0x0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1845 CDB: opcode=0x2a 2a 00 0b 14 84 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: blk_update_request: I/O error, dev sdk, sector 185894104 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1846 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1846 Sense Key : 0x2 [current]
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1846 ASC=0x4 ASCQ=0x0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1846 CDB: opcode=0x2a 2a 00 0b 14 88 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: blk_update_request: I/O error, dev sdk, sector 185895128 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1847 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1847 Sense Key : 0x2 [current]
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1847 ASC=0x4 ASCQ=0x0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1847 CDB: opcode=0x2a 2a 00 0b 14 8c d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: blk_update_request: I/O error, dev sdk, sector 185896152 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1848 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1848 Sense Key : 0x2 [current]
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1848 ASC=0x4 ASCQ=0x0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1848 CDB: opcode=0x2a 2a 00 0b 14 90 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: blk_update_request: I/O error, dev sdk, sector 185897176 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1849 CDB: opcode=0x2a 2a 00 0b 14 94 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1849 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1849 Sense Key : 0x2 [current]
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1849 ASC=0x4 ASCQ=0x0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1849 CDB: opcode=0x2a 2a 00 0b 14 94 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: blk_update_request: I/O error, dev sdk, sector 185898200 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1850 CDB: opcode=0x2a 2a 00 0b 14 98 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1850 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1850 Sense Key : 0x2 [current]
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1850 ASC=0x4 ASCQ=0x0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1850 CDB: opcode=0x2a 2a 00 0b 14 98 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: blk_update_request: I/O error, dev sdk, sector 185899224 op 0x1:(WRITE) flags 0x104000 phys_seg 128 prio class 0
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1851 CDB: opcode=0x2a 2a 00 0b 14 9c d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1852 CDB: opcode=0x2a 2a 00 0b 14 a0 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1801 CDB: opcode=0x2a 2a 00 0b 14 d4 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1802 CDB: opcode=0x2a 2a 00 0b 14 d8 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1803 CDB: opcode=0x2a 2a 00 0b 14 dc d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1804 CDB: opcode=0x2a 2a 00 0b 14 e0 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1817 CDB: opcode=0x2a 2a 00 0b 15 14 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1818 CDB: opcode=0x2a 2a 00 0b 15 18 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1819 CDB: opcode=0x2a 2a 00 0b 15 1c d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1820 CDB: opcode=0x2a 2a 00 0b 15 20 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1838 CDB: opcode=0x2a 2a 00 0b 15 68 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1839 CDB: opcode=0x2a 2a 00 0b 15 6c d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1840 CDB: opcode=0x2a 2a 00 0b 15 70 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1841 CDB: opcode=0x2a 2a 00 0b 15 74 d8 00 04 00 00
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:32 Tower kernel: sd 7:0:5:0: [sdk] tag#1792 CDB: opcode=0x2a 2a 00 0b 15 b0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1808 CDB: opcode=0x2a 2a 00 0b 15 c0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1809 CDB: opcode=0x2a 2a 00 0b 15 c4 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1810 CDB: opcode=0x2a 2a 00 0b 15 c8 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1811 CDB: opcode=0x2a 2a 00 0b 15 cc d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1734 CDB: opcode=0x2a 2a 00 0b 16 00 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1735 CDB: opcode=0x2a 2a 00 0b 16 04 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1736 CDB: opcode=0x2a 2a 00 0b 16 08 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1737 CDB: opcode=0x2a 2a 00 0b 16 0c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1755 CDB: opcode=0x2a 2a 00 0b 16 54 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1756 CDB: opcode=0x2a 2a 00 0b 16 58 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1757 CDB: opcode=0x2a 2a 00 0b 16 5c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1758 CDB: opcode=0x2a 2a 00 0b 16 60 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1771 CDB: opcode=0x2a 2a 00 0b 16 94 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1772 CDB: opcode=0x2a 2a 00 0b 16 98 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1773 CDB: opcode=0x2a 2a 00 0b 16 9c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1774 CDB: opcode=0x2a 2a 00 0b 16 a0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1787 CDB: opcode=0x2a 2a 00 0b 16 d4 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1788 CDB: opcode=0x2a 2a 00 0b 16 d8 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1789 CDB: opcode=0x2a 2a 00 0b 16 dc d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1790 CDB: opcode=0x2a 2a 00 0b 16 e0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1739 CDB: opcode=0x2a 2a 00 0b 17 14 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1740 CDB: opcode=0x2a 2a 00 0b 17 18 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1741 CDB: opcode=0x2a 2a 00 0b 17 1c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1742 CDB: opcode=0x2a 2a 00 0b 17 20 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1755 CDB: opcode=0x2a 2a 00 0b 17 54 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1756 CDB: opcode=0x2a 2a 00 0b 17 58 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1757 CDB: opcode=0x2a 2a 00 0b 17 5c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1758 CDB: opcode=0x2a 2a 00 0b 17 60 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1771 CDB: opcode=0x2a 2a 00 0b 17 94 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1772 CDB: opcode=0x2a 2a 00 0b 17 98 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1773 CDB: opcode=0x2a 2a 00 0b 17 9c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1774 CDB: opcode=0x2a 2a 00 0b 17 a0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1787 CDB: opcode=0x2a 2a 00 0b 17 d4 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1788 CDB: opcode=0x2a 2a 00 0b 17 d8 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1789 CDB: opcode=0x2a 2a 00 0b 17 dc d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1790 CDB: opcode=0x2a 2a 00 0b 17 e0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1739 CDB: opcode=0x2a 2a 00 0b 18 14 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1740 CDB: opcode=0x2a 2a 00 0b 18 18 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1741 CDB: opcode=0x2a 2a 00 0b 18 1c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1742 CDB: opcode=0x2a 2a 00 0b 18 20 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1755 CDB: opcode=0x2a 2a 00 0b 18 54 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1756 CDB: opcode=0x2a 2a 00 0b 18 58 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1757 CDB: opcode=0x2a 2a 00 0b 18 5c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1758 CDB: opcode=0x2a 2a 00 0b 18 60 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1771 CDB: opcode=0x2a 2a 00 0b 18 94 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1772 CDB: opcode=0x2a 2a 00 0b 18 98 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1773 CDB: opcode=0x2a 2a 00 0b 18 9c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1774 CDB: opcode=0x2a 2a 00 0b 18 a0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1787 CDB: opcode=0x2a 2a 00 0b 18 d4 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1788 CDB: opcode=0x2a 2a 00 0b 18 d8 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1789 CDB: opcode=0x2a 2a 00 0b 18 dc d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1790 CDB: opcode=0x2a 2a 00 0b 18 e0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1739 CDB: opcode=0x2a 2a 00 0b 19 14 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1740 CDB: opcode=0x2a 2a 00 0b 19 18 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1741 CDB: opcode=0x2a 2a 00 0b 19 1c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1742 CDB: opcode=0x2a 2a 00 0b 19 20 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1762 CDB: opcode=0x2a 2a 00 0b 19 70 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1763 CDB: opcode=0x2a 2a 00 0b 19 74 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1764 CDB: opcode=0x2a 2a 00 0b 19 78 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1765 CDB: opcode=0x2a 2a 00 0b 19 7c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1780 CDB: opcode=0x2a 2a 00 0b 19 b8 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1781 CDB: opcode=0x2a 2a 00 0b 19 bc d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1782 CDB: opcode=0x2a 2a 00 0b 19 c0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1783 CDB: opcode=0x2a 2a 00 0b 19 c4 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1747 CDB: opcode=0x2a 2a 00 0b 1a 34 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1748 CDB: opcode=0x2a 2a 00 0b 1a 38 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1749 CDB: opcode=0x2a 2a 00 0b 1a 3c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1750 CDB: opcode=0x2a 2a 00 0b 1a 40 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1763 CDB: opcode=0x2a 2a 00 0b 1a 74 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1764 CDB: opcode=0x2a 2a 00 0b 1a 78 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1765 CDB: opcode=0x2a 2a 00 0b 1a 7c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1766 CDB: opcode=0x2a 2a 00 0b 1a 80 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1783 CDB: opcode=0x2a 2a 00 0b 1a c4 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1784 CDB: opcode=0x2a 2a 00 0b 1a c8 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1785 CDB: opcode=0x2a 2a 00 0b 1a cc d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1786 CDB: opcode=0x2a 2a 00 0b 1a d0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1735 CDB: opcode=0x2a 2a 00 0b 1b 04 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1736 CDB: opcode=0x2a 2a 00 0b 1b 08 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1737 CDB: opcode=0x2a 2a 00 0b 1b 0c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1738 CDB: opcode=0x2a 2a 00 0b 1b 10 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1768 CDB: opcode=0x2a 2a 00 0b 1b 88 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1769 CDB: opcode=0x2a 2a 00 0b 1b 8c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1770 CDB: opcode=0x2a 2a 00 0b 1b 90 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1771 CDB: opcode=0x2a 2a 00 0b 1b 94 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1784 CDB: opcode=0x2a 2a 00 0b 1b c8 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1785 CDB: opcode=0x2a 2a 00 0b 1b cc d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1786 CDB: opcode=0x2a 2a 00 0b 1b d0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1787 CDB: opcode=0x2a 2a 00 0b 1b d4 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1736 CDB: opcode=0x2a 2a 00 0b 1c 08 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1737 CDB: opcode=0x2a 2a 00 0b 1c 0c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1738 CDB: opcode=0x2a 2a 00 0b 1c 10 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1739 CDB: opcode=0x2a 2a 00 0b 1c 14 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1752 CDB: opcode=0x2a 2a 00 0b 1c 48 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1753 CDB: opcode=0x2a 2a 00 0b 1c 4c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1754 CDB: opcode=0x2a 2a 00 0b 1c 50 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1755 CDB: opcode=0x2a 2a 00 0b 1c 54 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1768 CDB: opcode=0x2a 2a 00 0b 1c 88 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1769 CDB: opcode=0x2a 2a 00 0b 1c 8c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1770 CDB: opcode=0x2a 2a 00 0b 1c 90 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1771 CDB: opcode=0x2a 2a 00 0b 1c 94 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1787 CDB: opcode=0x2a 2a 00 0b 1c d4 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1788 CDB: opcode=0x2a 2a 00 0b 1c d8 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1789 CDB: opcode=0x2a 2a 00 0b 1c dc d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1790 CDB: opcode=0x2a 2a 00 0b 1c e0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1739 CDB: opcode=0x2a 2a 00 0b 1d 14 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1740 CDB: opcode=0x2a 2a 00 0b 1d 18 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1741 CDB: opcode=0x2a 2a 00 0b 1d 1c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1742 CDB: opcode=0x2a 2a 00 0b 1d 20 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1755 CDB: opcode=0x2a 2a 00 0b 1d 54 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1756 CDB: opcode=0x2a 2a 00 0b 1d 58 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1757 CDB: opcode=0x2a 2a 00 0b 1d 5c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1758 CDB: opcode=0x2a 2a 00 0b 1d 60 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1771 CDB: opcode=0x2a 2a 00 0b 1d 94 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1772 CDB: opcode=0x2a 2a 00 0b 1d 98 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1773 CDB: opcode=0x2a 2a 00 0b 1d 9c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1774 CDB: opcode=0x2a 2a 00 0b 1d a0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1791 CDB: opcode=0x2a 2a 00 0b 1d e4 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1728 CDB: opcode=0x2a 2a 00 0b 1d e8 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1729 CDB: opcode=0x2a 2a 00 0b 1d ec d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1730 CDB: opcode=0x2a 2a 00 0b 1d f0 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1743 CDB: opcode=0x2a 2a 00 0b 1e 24 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1744 CDB: opcode=0x2a 2a 00 0b 1e 28 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1745 CDB: opcode=0x2a 2a 00 0b 1e 2c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1746 CDB: opcode=0x2a 2a 00 0b 1e 30 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1759 CDB: opcode=0x2a 2a 00 0b 1e 64 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524212, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1760 CDB: opcode=0x2a 2a 00 0b 1e 68 d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524252, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1761 CDB: opcode=0x2a 2a 00 0b 1e 6c d8 00 04 00 00
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] Unaligned partial completion (resid=524256, sector_sz=512)
Aug 25 17:42:34 Tower kernel: sd 7:0:5:0: [sdk] tag#1762 CDB: opcode=0x2a 2a 00 0b 1e 70 d8 00 04 00 00
Aug 25 17:42:38 Tower kernel: sd 7:0:5:0: device_block, handle(0x000e)
Aug 25 17:42:40 Tower kernel: sd 7:0:5:0: device_unblock and setting to running, handle(0x000e)
Aug 25 17:42:40 Tower kernel: print_req_error: 641 callbacks suppressed
Aug 25 17:42:40 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186555896 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
Aug 25 17:42:40 Tower kernel: buffer_io_error: 83226 callbacks suppressed
Aug 25 17:42:40 Tower kernel: Buffer I/O error on dev sdk, logical block 23319487, lost async page write
Aug 25 17:42:40 Tower kernel: Buffer I/O error on dev sdk, logical block 23319488, lost async page write
Aug 25 17:42:40 Tower kernel: Buffer I/O error on dev sdk, logical block 23319489, lost async page write
Aug 25 17:42:40 Tower kernel: Buffer I/O error on dev sdk, logical block 23319490, lost async page write
Aug 25 17:42:40 Tower kernel: Buffer I/O error on dev sdk, logical block 23319491, lost async page write
Aug 25 17:42:40 Tower kernel: Buffer I/O error on dev sdk, logical block 23319492, lost async page write
Aug 25 17:42:40 Tower kernel: Buffer I/O error on dev sdk, logical block 23319493, lost async page write
Aug 25 17:42:40 Tower kernel: Buffer I/O error on dev sdk, logical block 23319494, lost async page write
Aug 25 17:42:40 Tower kernel: Buffer I/O error on dev sdk, logical block 23319495, lost async page write
Aug 25 17:42:40 Tower kernel: Buffer I/O error on dev sdk, logical block 23319496, lost async page write
Aug 25 17:42:40 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186556920 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
Aug 25 17:42:40 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186557944 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
Aug 25 17:42:40 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186558968 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
Aug 25 17:42:40 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186559992 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
Aug 25 17:42:40 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186561016 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
Aug 25 17:42:40 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186562040 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
Aug 25 17:42:40 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186563064 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
Aug 25 17:42:40 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186564088 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
Aug 25 17:42:40 Tower kernel: blk_update_request: I/O error, dev sdk, sector 186565112 op 0x1:(WRITE) flags 0x4800 phys_seg 128 prio class 0
Aug 25 17:42:41 Tower kernel: sd 7:0:5:0: [sdk] Synchronizing SCSI cache
Aug 25 17:42:41 Tower kernel: sd 7:0:5:0: [sdk] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Aug 25 17:42:41 Tower kernel: mpt2sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x4433221105000000)
Aug 25 17:42:41 Tower kernel: mpt2sas_cm0: removing handle(0x000e), sas_addr(0x4433221105000000)
Aug 25 17:42:41 Tower kernel: mpt2sas_cm0: enclosure logical id(0x500605b006630270), slot(5)
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=976832408
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=976845408
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396536
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396544
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396552
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396560
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396568
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396576
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396584
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396592
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396600
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396608
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396616
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396624
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396632
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396640
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396648
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396656
Aug 25 17:42:43 Tower kernel: md: disk0 read error, sector=3306396664
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=976832408
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=976832408
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=976832408
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=976845408
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=976845408
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=976845408
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=2930298120
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=2930298120
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=2930298120
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396536
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396536
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396536
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396544
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396544
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396544
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396552
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396552
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396552
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396560
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396560
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396560
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396568
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396568
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396568
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396576
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396576
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396576
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396584
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396584
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396584
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396592
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396592
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396592
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396600
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396600
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396600
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396608
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396608
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396608
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396616
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396616
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396616
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396624
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396624
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396624
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396632
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396632
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396632
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396640
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396640
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396640
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396648
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396648
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396648
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396656
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396656
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396656
Aug 25 17:42:43 Tower kernel: md: disk5 read error, sector=3306396664
Aug 25 17:42:43 Tower kernel: md: disk6 read error, sector=3306396664
Aug 25 17:42:43 Tower kernel: md: disk7 read error, sector=3306396664
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120
Aug 25 17:42:51 Tower kernel: md: disk0 read error, sector=2930298120

This log has a few drives spitting read errors, but the consistent problem between all the box crashes is disk0, the parity.

 

Log 2: Hitachi 200G SSD

Spoiler

Aug 28 03:41:23 Tower emhttpd: shcmd (257909): echo 128 > /sys/block/sdc/queue/nr_requests
Aug 28 03:41:23 Tower emhttpd: shcmd (257910): echo 128 > /sys/block/sdb/queue/nr_requests
Aug 28 03:41:23 Tower emhttpd: shcmd (257911): echo 128 > /sys/block/sde/queue/nr_requests
Aug 28 03:41:23 Tower emhttpd: shcmd (257912): echo 128 > /sys/block/sdi/queue/nr_requests
Aug 28 03:41:23 Tower emhttpd: shcmd (257913): echo 128 > /sys/block/sdd/queue/nr_requests
Aug 28 03:41:23 Tower emhttpd: shcmd (257913): exit status: 1
Aug 28 03:41:23 Tower emhttpd: shcmd (257914): echo 128 > /sys/block/sdm/queue/nr_requests
Aug 28 03:41:23 Tower emhttpd: shcmd (257915): echo 128 > /sys/block/sdl/queue/nr_requests
Aug 28 03:41:23 Tower emhttpd: shcmd (257916): echo 128 > /sys/block/sdf/queue/nr_requests
Aug 28 03:41:23 Tower emhttpd: shcmd (257917): echo 128 > /sys/block/sdj/queue/nr_requests
Aug 28 03:41:23 Tower kernel: mdcmd (41): set md_num_stripes 1280
Aug 28 03:41:23 Tower kernel: mdcmd (42): set md_queue_limit 80
Aug 28 03:41:23 Tower kernel: mdcmd (43): set md_sync_limit 5
Aug 28 03:41:23 Tower kernel: mdcmd (44): set md_write_method
Aug 28 03:41:47 Tower kernel: mdcmd (45): nocheck pause
Aug 28 03:41:52 Tower kernel: scsi 4:0:8:0: Direct-Access     HITACHI  HUS72403CLAR3000 C370 PQ: 0 ANSI: 6
Aug 28 03:41:52 Tower kernel: scsi 4:0:8:0: SSP: handle(0x0009), sas_addr(0x5000cca058787f4d), phy(0), device_name(0x5000cca058787f4f)
Aug 28 03:41:52 Tower kernel: scsi 4:0:8:0: enclosure logical id (0x500605b006630270), slot(0)
Aug 28 03:41:52 Tower kernel: scsi 4:0:8:0: qdepth(254), tagged(1), scsi_level(7), cmd_que(1)
Aug 28 03:41:52 Tower kernel: scsi 4:0:8:0: Power-on or device reset occurred
Aug 28 03:41:52 Tower kernel: sd 4:0:8:0: Attached scsi generic sg3 type 0
Aug 28 03:41:52 Tower kernel: end_device-4:8: add: handle(0x0009), sas_addr(0x5000cca058787f4d)
Aug 28 03:41:52 Tower kernel: sd 4:0:8:0: [sdn] Spinning up disk...
Aug 28 03:41:58 Tower emhttpd: writing MBR on disk (sdf) with partition 1 offset 64, erased: 0
Aug 28 03:41:58 Tower emhttpd: re-reading (sdf) partition table
Aug 28 03:41:59 Tower kernel: ......
Aug 28 03:41:59 Tower kernel: scsi 4:0:9:0: Direct-Access     HITACHI  HUSRL402 CLAR200 C140 PQ: 0 ANSI: 6
Aug 28 03:41:59 Tower kernel: scsi 4:0:9:0: SSP: handle(0x000c), sas_addr(0x5000cca0132a3e81), phy(5), device_name(0x5000cca0132a3e83)
Aug 28 03:41:59 Tower kernel: scsi 4:0:9:0: enclosure logical id (0x500605b006630270), slot(5)
Aug 28 03:41:59 Tower kernel: scsi 4:0:9:0: qdepth(254), tagged(1), scsi_level(7), cmd_que(1)
Aug 28 03:41:59 Tower kernel: scsi 4:0:9:0: Power-on or device reset occurred
Aug 28 03:41:59 Tower kernel: sd 4:0:9:0: Attached scsi generic sg6 type 0
Aug 28 03:41:59 Tower kernel: end_device-4:9: add: handle(0x000c), sas_addr(0x5000cca0132a3e81)
Aug 28 03:41:59 Tower kernel: sd 4:0:9:0: [sdo] Spinning up disk...
Aug 28 03:42:00 Tower emhttpd: shcmd (258119): udevadm settle
Aug 28 03:42:00 Tower kernel: .
Aug 28 03:42:00 Tower kernel: sdf: sdf1
Aug 28 03:42:00 Tower emhttpd: shcmd (258120): /sbin/wipefs -a /dev/md8
Aug 28 03:42:00 Tower emhttpd: shcmd (258121): mkfs.xfs -m crc=1,finobt=1 -f /dev/md8
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028848
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028856
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028864
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028872
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028880
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028888
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028896
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028904
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028912
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028920
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028928
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028936
Aug 28 03:42:00 Tower kernel: md: disk0 read error, sector=3907028944

 

General behavior at this point after each log is infinitely expanding read errors on disk0, CPU being nearly pinned, system doesn't respond to array stop or shutdown and has to be hard off'd. As mentioned before, system is generally stable without using windows 10 VM. Said VM is passthrough'd to the SSD, if passing through to a drive with SAS drives in the mix is considered a "no-no" that would be nice to know.

 

Anything else I'll be happy to follow up with if requested.

Link to comment

@Necron, please
(a) upgrade the SAS Spindown plugin to latest version
(b) post diagnostics
© share a bit more about the setup - which drives are connected to what controller, what exactly are you passing through to your VM etc.
I suspect this doesn't have much to do with the plugin, but let's take a closer look.

Sent from my FP3 using Tapatalk

Link to comment
1 hour ago, doron said:

@Necron, please
(a) upgrade the SAS Spindown plugin to latest version
(b) post diagnostics
© share a bit more about the setup - which drives are connected to what controller, what exactly are you passing through to your VM etc.

A) It's currently doing a parity check as I was forced to unsafe shutdown. Currently SAS Spindown is uninstalled, but I'll reinstall it after parity finishes.

B) Attached

HP Microserver Gen8 // Xeon E3-1200 v2 // 16GB RAM

----- Four Sata drives inside the Gen8 enclosure

[2:0:0:0] disk ATA ST2000DM001-1E61 CC45 /dev/sdb 2.00TB

[3:0:0:0] disk ATA ST2000DM001-1E61 CC45 /dev/sdc 2.00TB

[4:0:0:0] disk ATA ST2000DL003-9VT1 CC3C /dev/sde 2.00TB

[5:0:0:0] disk ATA WDC WD10EACS-00Z 1B01 /dev/sdf 1.00TB

----- LSI SAS2008 in PCI Express - Eight external drives

[1:0:0:0] disk HITACHI HUS72403CLAR3000 C370 /dev/sdd 3.00TB -- SAS to Sata

[1:0:1:0] disk ATA WDC WD30EZRX-00D 0A80 /dev/sdg 3.00TB

[1:0:2:0] disk HITACHI HUSRL402 CLAR200 C140 /dev/sdh 200GB -- SSD SAS to Sata

[1:0:3:0] disk ATA Hitachi HDS5C302 A580 /dev/sdi 2.00TB

[1:0:4:0] disk ATA Hitachi HDS5C302 A580 /dev/sdj 2.00TB

[1:0:5:0] disk ATA WDC WD30EZRX-00D 0A80 /dev/sdk 3.00TB -- Parity

[1:0:6:0] disk ATA Hitachi HDS5C302 A5C0 /dev/sdl 2.00TB

[1:0:7:0] disk ATA Hitachi HDS5C302 A580 /dev/sdm 2.00TB

 

The 200GB SSD (and previously the 120GB Intel SSD) are passed through to the Windows 10 VM (/dev/disk/by-id/scsi-35000cca0132a3e80).

edit: Also all the CPU cores and 10752MB RAM, network bridge BR0

tower-diagnostics-20210828-0559.zip

Edited by Necron
edit area marked
Link to comment
15 hours ago, Necron said:

A) It's currently doing a parity check as I was forced to unsafe shutdown. Currently SAS Spindown is uninstalled, but I'll reinstall it after parity finishes.

 

That's fine, it's just that I saw v0.85 in your logs and wanted to point you to the latest update. Either with latest or without the plugin is fine 🙂 

 

15 hours ago, Necron said:

----- LSI SAS2008 in PCI Express - Eight external drives

[1:0:0:0] disk HITACHI HUS72403CLAR3000 C370 /dev/sdd 3.00TB -- SAS to Sata

[1:0:1:0] disk ATA WDC WD30EZRX-00D 0A80 /dev/sdg 3.00TB

[1:0:2:0] disk HITACHI HUSRL402 CLAR200 C140 /dev/sdh 200GB -- SSD SAS to Sata

 

What do you mean by "SAS to SATA"? Is this a physical adapter? Can you perhaps point to a similar product page?

 

At any rate, the next thing I'd check, in parallel with this thread, is the cabling of the drives - SAS and SATA - start with sdd and sdk but would probably go over all of them, just to be safe.

 

Link to comment
14 hours ago, doron said:

That's fine, it's just that I saw v0.85 in your logs and wanted to point you to the latest update. Either with latest or without the plugin is fine 🙂

Well, after the parity completed I cautiously booted up the VM with unraid log window on my other screen. No problems! I continued to use the VM, start/stop/pause/hibernate - no problems. I'll install the latest version of spindown, restart the box and try the same things again.

14 hours ago, doron said:

What do you mean by "SAS to SATA"? Is this a physical adapter? Can you perhaps point to a similar product page?

Yep! Image attached. Ebay link here

Spoiler

 image.thumb.png.7975457d9e75fe4acd331e87d9741a70.png

 

If I run my tests after reinstalling the plugin and the problems surface again I'd be surprised if it's a cable problem, but it never hurts to check. I'll go and have a gander when I need to hard off the machine.

 

Edited by Necron
Forgot ebay link
Link to comment
2 hours ago, Necron said:

If I run my tests after reinstalling the plugin and the problems surface again I'd be surprised if it's a cable problem, but it never hurts to check. I'll go and have a gander when I need to hard off the machine.

 

You're right. If spinning down your /dev/sdd would trigger a similar issue again, then we'd have to conclude that your drive model - HUS72403CLAR3000 - is one of those which do not properly support the STANDBY command, and, sadly, it will need to be added to the list of "excluded" drive models in the plugin. Net-net it would mean that the plugin will not be of value to you.

 

If you want, you can test for this issue, when the array is quiesced so as not to trigger another parity check. Let me know if you want to try that.

Link to comment

Last night I installed the plugin and to my surprise, everything was fine. Drives went to sleep properly, VM ran fine, etc. When I powered on my main PC this morning however, shit hit the fan again. I tried to resume the VM from pause state (how I usually handle it) and I noticed errors popping up from the log:

Spoiler

Aug 30 11:22:25 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xaed3fc28 len 8 error 5
Aug 30 11:22:46 Tower kernel: XFS: metadata IO error: 14 callbacks suppressed
Aug 30 11:22:46 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x642688 len 8 error 5
Aug 30 11:22:46 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xaed3fc28 len 8 error 5
Aug 30 11:22:46 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x4e178340 len 8 error 5
Aug 30 11:22:46 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xb00ca7b0 len 8 error 5
Aug 30 11:22:46 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x99b63650 len 8 error 5
Aug 30 11:22:46 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x1412fce80 len 8 error 5
Aug 30 11:22:46 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x884bd540 len 8 error 5
Aug 30 11:22:46 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x45c0b0d8 len 8 error 5
Aug 30 11:22:57 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x642688 len 8 error 5
Aug 30 11:22:57 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xaed3fc28 len 8 error 5
Aug 30 11:23:18 Tower kernel: XFS: metadata IO error: 14 callbacks suppressed
Aug 30 11:23:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x642688 len 8 error 5
Aug 30 11:23:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xaed3fc28 len 8 error 5
Aug 30 11:23:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x4e178340 len 8 error 5
Aug 30 11:23:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xb00ca7b0 len 8 error 5
Aug 30 11:23:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x99b63650 len 8 error 5
Aug 30 11:23:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x1412fce80 len 8 error 5
Aug 30 11:23:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x884bd540 len 8 error 5
Aug 30 11:23:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x45c0b0d8 len 8 error 5
Aug 30 11:23:36 Tower kernel: md: disk5 read error, sector=6563464
Aug 30 11:23:36 Tower kernel: md: disk0 read error, sector=6563464
Aug 30 11:23:36 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x642688 len 8 error 5
Aug 30 11:23:36 Tower kernel: md: disk5 read error, sector=2933128232
Aug 30 11:23:36 Tower kernel: md: disk0 read error, sector=2933128232
Aug 30 11:23:36 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xaed3fc28 len 8 error 5
Aug 30 11:23:36 Tower kernel: md: disk5 read error, sector=1310163776
Aug 30 11:23:36 Tower kernel: md: disk0 read error, sector=1310163776
Aug 30 11:23:36 Tower kernel: md: disk5 read error, sector=2953619376
Aug 30 11:23:36 Tower kernel: md: disk0 read error, sector=2953619376
Aug 30 11:23:36 Tower kernel: md: disk5 read error, sector=2578855504
Aug 30 11:23:36 Tower kernel: md: disk0 read error, sector=2578855504
Aug 30 11:23:36 Tower kernel: md: disk5 read error, sector=5388619392
Aug 30 11:23:36 Tower kernel: md: disk0 read error, sector=5388619392
Aug 30 11:23:36 Tower kernel: md: disk5 read error, sector=2286671168
Aug 30 11:23:36 Tower kernel: md: disk0 read error, sector=2286671168
Aug 30 11:23:36 Tower kernel: md: disk5 read error, sector=1170256088
Aug 30 11:23:36 Tower kernel: md: disk0 read error, sector=1170256088
Aug 30 11:24:07 Tower kernel: md: disk5 read error, sector=6563464
Aug 30 11:24:07 Tower kernel: md: disk0 read error, sector=6563464
Aug 30 11:24:07 Tower kernel: XFS: metadata IO error: 6 callbacks suppressed
Aug 30 11:24:07 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x642688 len 8 error 5
Aug 30 11:24:07 Tower kernel: md: disk5 read error, sector=2933128232
Aug 30 11:24:07 Tower kernel: md: disk0 read error, sector=2933128232
Aug 30 11:24:07 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xaed3fc28 len 8 error 5
Aug 30 11:24:07 Tower kernel: md: disk5 read error, sector=1310163776
Aug 30 11:24:07 Tower kernel: md: disk0 read error, sector=1310163776
Aug 30 11:24:07 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x4e178340 len 8 error 5
Aug 30 11:24:07 Tower kernel: md: disk5 read error, sector=2953619376
Aug 30 11:24:07 Tower kernel: md: disk0 read error, sector=2953619376
Aug 30 11:24:08 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xb00ca7b0 len 8 error 5
Aug 30 11:24:08 Tower kernel: md: disk5 read error, sector=2578855504
Aug 30 11:24:08 Tower kernel: md: disk0 read error, sector=2578855504
Aug 30 11:24:08 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x99b63650 len 8 error 5
Aug 30 11:24:08 Tower kernel: md: disk5 read error, sector=5388619392
Aug 30 11:24:08 Tower kernel: md: disk0 read error, sector=5388619392
Aug 30 11:24:08 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x1412fce80 len 8 error 5
Aug 30 11:24:08 Tower kernel: md: disk5 read error, sector=2286671168
Aug 30 11:24:08 Tower kernel: md: disk0 read error, sector=2286671168
Aug 30 11:24:08 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x884bd540 len 8 error 5
Aug 30 11:24:08 Tower kernel: md: disk5 read error, sector=1170256088
Aug 30 11:24:08 Tower kernel: md: disk0 read error, sector=1170256088
Aug 30 11:24:08 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x45c0b0d8 len 8 error 5
Aug 30 11:24:38 Tower kernel: md: disk5 read error, sector=6563464
Aug 30 11:24:38 Tower kernel: md: disk0 read error, sector=6563464
Aug 30 11:24:39 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x642688 len 8 error 5
Aug 30 11:24:39 Tower kernel: md: disk5 read error, sector=2933128232
Aug 30 11:24:39 Tower kernel: md: disk0 read error, sector=2933128232
Aug 30 11:24:39 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xaed3fc28 len 8 error 5
Aug 30 11:24:39 Tower kernel: md: disk5 read error, sector=1310163776
Aug 30 11:24:39 Tower kernel: md: disk0 read error, sector=1310163776
Aug 30 11:24:39 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x4e178340 len 8 error 5
Aug 30 11:24:39 Tower kernel: md: disk5 read error, sector=2953619376
Aug 30 11:24:39 Tower kernel: md: disk0 read error, sector=2953619376
Aug 30 11:24:39 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xb00ca7b0 len 8 error 5
Aug 30 11:24:39 Tower kernel: md: disk5 read error, sector=2578855504
Aug 30 11:24:39 Tower kernel: md: disk0 read error, sector=2578855504
Aug 30 11:24:39 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x99b63650 len 8 error 5
Aug 30 11:24:39 Tower kernel: md: disk5 read error, sector=5388619392
Aug 30 11:24:39 Tower kernel: md: disk0 read error, sector=5388619392
Aug 30 11:24:39 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x1412fce80 len 8 error 5
Aug 30 11:24:39 Tower kernel: md: disk5 read error, sector=2286671168
Aug 30 11:24:39 Tower kernel: md: disk0 read error, sector=2286671168
Aug 30 11:24:39 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x884bd540 len 8 error 5
Aug 30 11:24:39 Tower kernel: md: disk5 read error, sector=1170256088
Aug 30 11:24:39 Tower kernel: md: disk0 read error, sector=1170256088
Aug 30 11:24:39 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x45c0b0d8 len 8 error 5
Aug 30 11:24:54 Tower kernel: md: disk5 read error, sector=2933128232
Aug 30 11:24:54 Tower kernel: md: disk0 read error, sector=2933128232
Aug 30 11:24:54 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xaed3fc28 len 8 error 5
Aug 30 11:24:54 Tower kernel: md: disk5 read error, sector=1310163776
Aug 30 11:24:54 Tower kernel: md: disk0 read error, sector=1310163776
Aug 30 11:24:54 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x4e178340 len 8 error 5
Aug 30 11:24:54 Tower kernel: md: disk5 read error, sector=2953619376
Aug 30 11:24:54 Tower kernel: md: disk0 read error, sector=2953619376
Aug 30 11:24:54 Tower kernel: md: disk5 read error, sector=2578855504
Aug 30 11:24:54 Tower kernel: md: disk0 read error, sector=2578855504
Aug 30 11:24:54 Tower kernel: md: disk5 read error, sector=5388619392
Aug 30 11:24:54 Tower kernel: md: disk0 read error, sector=5388619392
Aug 30 11:24:54 Tower kernel: md: disk5 read error, sector=2286671168
Aug 30 11:24:54 Tower kernel: md: disk0 read error, sector=2286671168
Aug 30 11:24:54 Tower kernel: md: disk5 read error, sector=1170256088
Aug 30 11:24:54 Tower kernel: md: disk0 read error, sector=1170256088
Aug 30 11:24:54 Tower kernel: md: disk5 read error, sector=2939685032
Aug 30 11:24:54 Tower kernel: md: disk0 read error, sector=2939685032
Aug 30 11:24:54 Tower kernel: md: disk5 read error, sector=1182652840
Aug 30 11:24:54 Tower kernel: md: disk0 read error, sector=1182652840
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=6563464
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=6563464
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=1182650784
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=1182650792
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=1182650800
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=1182650808
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=1182650784
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=1182650792
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=1182650800
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=1182650808
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=10036096
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=10036104
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=10036112
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=10036120
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=10036096
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=10036104
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=10036112
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=10036120
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=5096838344
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=5096838352
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=5096838360
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=5096838368
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=5096838344
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=5096838352
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=5096838360
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=5096838368
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=3729966480
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=3729966488
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=3729966496
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=3729966504
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=3729966480
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=3729966488
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=3729966496
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=3729966504
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=960350240
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=960350248
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=960350256
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=960350264
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=960350240
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=960350248
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=960350256
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=960350264
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2578856152
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2578856160
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2578856168
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2578856176
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2578856152
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2578856160
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2578856168
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2578856176
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2628984248
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2628984256
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2628984264
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2628984272
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2628984248
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2628984256
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2628984264
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2628984272
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=1182445344
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=1182445352
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=1182445360
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=1182445368
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=1182445344
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=1182445352
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=1182445360
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=1182445368
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=5096978504
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=5096978512
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=5096978520
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=5096978528
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=5096978504
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=5096978512
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=5096978520
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=5096978528
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=3741920432
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=3741920440
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=3741920448
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=3741920456
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=3741920432
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=3741920440
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=3741920448
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=3741920456
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=3743035152
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=3743035160
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=3743035168
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=3743035176
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=3743035152
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=3743035160
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=3743035168
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=3743035176
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2284927768
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2284927776
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2284927784
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2284927792
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2284927768
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2284927776
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2284927784
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2284927792
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2286543480
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2286543488
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2286543496
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=2286543504
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2286543480
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2286543488
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2286543496
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=2286543504
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=1478586168
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=1478586176
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=1478586184
Aug 30 11:24:55 Tower kernel: md: disk5 read error, sector=1478586192
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=1478586168
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=1478586176
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=1478586184
Aug 30 11:24:55 Tower kernel: md: disk0 read error, sector=1478586192
Aug 30 11:24:55 Tower bunker: exported 3 files from /mnt/disk5. Duration: 00:00:01
Aug 30 11:25:08 Tower kernel: md: disk5 read error, sector=6563464
Aug 30 11:25:08 Tower kernel: md: disk0 read error, sector=6563464
Aug 30 11:25:08 Tower kernel: md: disk5 read error, sector=2933128232
Aug 30 11:25:08 Tower kernel: md: disk0 read error, sector=2933128232
Aug 30 11:25:08 Tower kernel: md: disk5 read error, sector=1310163776
Aug 30 11:25:08 Tower kernel: md: disk0 read error, sector=1310163776
Aug 30 11:25:08 Tower kernel: md: disk5 read error, sector=2953619376
Aug 30 11:25:08 Tower kernel: md: disk0 read error, sector=2953619376
Aug 30 11:25:08 Tower kernel: md: disk5 read error, sector=2578855504
Aug 30 11:25:08 Tower kernel: md: disk0 read error, sector=2578855504
Aug 30 11:25:08 Tower kernel: md: disk5 read error, sector=5388619392
Aug 30 11:25:08 Tower kernel: md: disk0 read error, sector=5388619392
Aug 30 11:25:08 Tower kernel: md: disk5 read error, sector=2286671168
Aug 30 11:25:08 Tower kernel: md: disk0 read error, sector=2286671168
Aug 30 11:25:08 Tower kernel: md: disk5 read error, sector=1170256088
Aug 30 11:25:08 Tower kernel: md: disk0 read error, sector=1170256088
Aug 30 11:25:18 Tower kernel: md: disk5 read error, sector=6563464
Aug 30 11:25:18 Tower kernel: md: disk0 read error, sector=6563464
Aug 30 11:25:18 Tower kernel: XFS: metadata IO error: 51 callbacks suppressed
Aug 30 11:25:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x642688 len 8 error 5
Aug 30 11:25:18 Tower kernel: md: disk5 read error, sector=2933128232
Aug 30 11:25:18 Tower kernel: md: disk0 read error, sector=2933128232
Aug 30 11:25:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xaed3fc28 len 8 error 5
Aug 30 11:25:18 Tower kernel: md: disk5 read error, sector=1310163776
Aug 30 11:25:18 Tower kernel: md: disk0 read error, sector=1310163776
Aug 30 11:25:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x4e178340 len 8 error 5
Aug 30 11:25:18 Tower kernel: md: disk5 read error, sector=2953619376
Aug 30 11:25:18 Tower kernel: md: disk0 read error, sector=2953619376
Aug 30 11:25:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0xb00ca7b0 len 8 error 5
Aug 30 11:25:18 Tower kernel: md: disk5 read error, sector=2578855504
Aug 30 11:25:18 Tower kernel: md: disk0 read error, sector=2578855504
Aug 30 11:25:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x99b63650 len 8 error 5
Aug 30 11:25:18 Tower kernel: md: disk5 read error, sector=5388619392
Aug 30 11:25:18 Tower kernel: md: disk0 read error, sector=5388619392
Aug 30 11:25:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x1412fce80 len 8 error 5
Aug 30 11:25:18 Tower kernel: md: disk5 read error, sector=2286671168
Aug 30 11:25:18 Tower kernel: md: disk0 read error, sector=2286671168
Aug 30 11:25:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x884bd540 len 8 error 5
Aug 30 11:25:18 Tower kernel: md: disk5 read error, sector=1170256088
Aug 30 11:25:18 Tower kernel: md: disk0 read error, sector=1170256088
Aug 30 11:25:18 Tower kernel: XFS (md5): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x45c0b0d8 len 8 error 5

 

Then, after the end of that snippet was a bunch of bunker: error: no export of file: yadda yadda yadda's.

After a hard-off and cooldown I rebooted it and verified that the files in the error reports were in-tact. It seems like there was a big hissy-fit between the parity drive and the SAS HDD (disk5) which started upon my resuming the SAS SSD (VM).

I'm removing the spindown plugin for now and I'll see if I can go a week without issues.

 

On 8/29/2021 at 2:20 PM, doron said:

If you want, you can test for this issue, when the array is quiesced so as not to trigger another parity check. Let me know if you want to try that.

I'm cool to try any tests you want :) I read the description of the SAS-Sata adapter and it mentions "Before buying, please check the manual to see if it supports SATA mode because it is not compatible with all SAS hard drives." This could all be the adapter's fault. I'll have a think and see what would be the cheapest/easiest way to get the adapter out of the setup. I may have to get an SFF 8088 to 4xSFF 8482 cable just to connect the two SAS drives.

Link to comment
13 hours ago, Necron said:

I'm removing the spindown plugin for now and I'll see if I can go a week without issues.

Right. If in fact the issue is as I guessed above, this exercise should go without issues - as the SAS drive(s) will simply not spin down, hence not invoking this phenomena (unable to automatically wake up from a spin down).

 

13 hours ago, Necron said:

I'm cool to try any tests you want :) I read the description of the SAS-Sata adapter and it mentions "Before buying, please check the manual to see if it supports SATA mode because it is not compatible with all SAS hard drives." This could all be the adapter's fault. I'll have a think and see what would be the cheapest/easiest way to get the adapter out of the setup. I may have to get an SFF 8088 to 4xSFF 8482 cable just to connect the two SAS drives.

Let's discuss this for a moment.

The adapter you pointed at is a physical connector adapter; it can connect a SAS drive to SAS-capable(!!) ports having SATA form factor, such as those found e.g. on some Supermicro motherboards. Those ports are not SATA ports; they are SAS ports (in fact, SAS-SATA ports, because they can "speak" SATA protocol as well). 

No adapter can connect a SAS drive to a SATA-only port.

Now, I have been assuming that you use this adapter to connect your SAS drive to a SAS controller that has SATA-style ports. Can you re-confirm that this is indeed the case.

 

Assuming we are indeed talking about SAS ports, you can 

(a) Stop the array (so as not to cause yet another parity panic)

(b) Identify the SAS drive. Let's assume it's /dev/sdX

(c) Issue these commands from a command line:

 

sdparm -C sense /dev/sdX
sg_start -rp3 /dev/sdX
sleep 2 # just in case you are copy/pasting the entire sequence
sdparm -C sense /dev/sdX
dd if=/dev/sdX of=/dev/null bs=1M count=1
sdparm -C sense /dev/sdX
# In case the above command(s) hang,... 
sg_start -rp1 /dev/sdX
sdparm -C sense /dev/sdX

Paste the results, and the accompanying syslog lines.

If there's anything except smooth run of these commands, suggest you reboot before restarting the array.

Link to comment
  • 2 weeks later...
8 hours ago, Fuggin said:

4 drives won't spin down. I assume they might be not compatible with plugin commands?

As I assume you know, the plugin handles SAS drives. I see that some of your drives are SAS and some are SATA.

Can you indicate which of your drives you are having an issue with?

Link to comment
  • 4 weeks later...
2 hours ago, Knights21 said:

I'm getting some SAS drives errors and needs some diagnostic help please.

 

It appears as though your drive misbehaves per the spin down process. "LU not ready, intervention required" means it is spun down and does not spin up automatically when an i/o is directed at it. This piece is kind of vaguely defined in the SAS protocols and different drive/ctrl/firmware combos provide different results. Your downgrading to p16 might have something to do with that.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.