After upgrading to 6.9 (previously was running 6.9 RC2) i noticed that spinning up the array often leads to error messages in the log and some disk randomly dont spin up.
Sometimes it all works fine and other times 2-3 disks dont spin up.
All disks are connected to the same backplane which is connected to one port of the HBA, clicking spin up again usually works and spins up all the remaining disks.
The have noticed that my 3TB WD Red 5400RPM drive seems to spin up most of the time while my other 3 8TB Seagate 7200RPM drives randomly dont spin up on the first try.thevault-diagnostics-20210302-1247.zip
Mar 2 12:42:16 TheVault emhttpd: Spinning up all drives...
Mar 2 12:42:16 TheVault emhttpd: spinning up /dev/sdg
Mar 2 12:42:16 TheVault emhttpd: spinning up /dev/sdd
Mar 2 12:42:16 TheVault emhttpd: spinning up /dev/sde
Mar 2 12:42:16 TheVault emhttpd: spinning up /dev/sdf
Mar 2 12:42:31 TheVault kernel: sd 1:0:3:0: attempting task abort!scmd(0x000000009c45948a), outstanding for 15091 ms & timeout 15000 ms
Mar 2 12:42:31 TheVault kernel: sd 1:0:3:0: [sdg] tag#608 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e3 00
Mar 2 12:42:31 TheVault kernel: scsi target1:0:3: handle(0x000c), sas_address(0x4433221103000000), phy(3)
Mar 2 12:42:31 TheVault kernel: scsi target1:0:3: enclosure logical id(0x500605b00daaefd0), slot(1)
Mar 2 12:42:31 TheVault kernel: scsi target1:0:3: enclosure level(0x0000), connector name( )
Mar 2 12:42:33 TheVault kernel: sd 1:0:3:0: task abort: SUCCESS scmd(0x000000009c45948a)
Mar 2 12:42:33 TheVault kernel: sd 1:0:0:0: attempting task abort!scmd(0x000000002ae4c915), outstanding for 16610 ms & timeout 15000 ms
Mar 2 12:42:33 TheVault kernel: sd 1:0:0:0: [sdd] tag#6911 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e3 00
Mar 2 12:42:33 TheVault kernel: scsi target1:0:0: handle(0x0009), sas_address(0x4433221100000000), phy(0)
Mar 2 12:42:33 TheVault kernel: scsi target1:0:0: enclosure logical id(0x500605b00daaefd0), slot(3)
Mar 2 12:42:33 TheVault kernel: scsi target1:0:0: enclosure level(0x0000), connector name( )
Mar 2 12:42:35 TheVault emhttpd: read SMART /dev/nvme1n1
Mar 2 12:42:35 TheVault emhttpd: read SMART /dev/sdb
Mar 2 12:42:35 TheVault emhttpd: read SMART /dev/sdf
Mar 2 12:42:35 TheVault emhttpd: read SMART /dev/sdc
Mar 2 12:42:35 TheVault emhttpd: read SMART /dev/nvme0n1
Mar 2 12:42:35 TheVault emhttpd: read SMART /dev/sda
Mar 2 12:42:35 TheVault kernel: sd 1:0:0:0: task abort: SUCCESS scmd(0x000000002ae4c915)
Mar 2 12:42:35 TheVault kernel: sd 1:0:1:0: attempting task abort!scmd(0x00000000a8c75da9), outstanding for 18420 ms & timeout 15000 ms
Mar 2 12:42:35 TheVault kernel: sd 1:0:1:0: [sde] tag#306 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e3 00
Mar 2 12:42:35 TheVault kernel: scsi target1:0:1: handle(0x000a), sas_address(0x4433221101000000), phy(1)
Mar 2 12:42:35 TheVault kernel: scsi target1:0:1: enclosure logical id(0x500605b00daaefd0), slot(2)
Mar 2 12:42:35 TheVault kernel: scsi target1:0:1: enclosure level(0x0000), connector name( )
Mar 2 12:42:35 TheVault kernel: sd 1:0:1:0: No reference found at driver, assuming scmd(0x00000000a8c75da9) might have completed
Mar 2 12:42:35 TheVault kernel: sd 1:0:1:0: task abort: SUCCESS scmd(0x00000000a8c75da9)
thevault-diagnostics-20210302-1247.zip thevault-diagnostics-20210302-1247.zip
Recommended Comments
There are no comments to display.
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.