Error messages in the log, should i be concerned about something?

[Pixel5]

Hello People.

 

i have just looked into my log files and saw these error messages, before this happened i spun up one drive only to find all my drive have spun up.

I noticed no other problems so far beside that all drives have spun up for no reason, i was playing back a video file while these thing happened and everything worked fine.

 

Feb  2 11:54:30 TheVault emhttpd: spinning up /dev/sdc
Feb  2 11:54:45 TheVault kernel: sd 1:0:1:0: attempting task abort!scmd(0x0000000030d9d9e5), outstanding for 15117 ms & timeout 15000 ms
Feb  2 11:54:45 TheVault kernel: sd 1:0:1:0: [sdc] tag#6470 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e3 00
Feb  2 11:54:45 TheVault kernel: scsi target1:0:1: handle(0x000a), sas_address(0x4433221101000000), phy(1)
Feb  2 11:54:45 TheVault kernel: scsi target1:0:1: enclosure logical id(0x500605b00daaefd0), slot(2) 
Feb  2 11:54:45 TheVault kernel: scsi target1:0:1: enclosure level(0x0000), connector name(     )
Feb  2 11:54:46 TheVault kernel: sd 1:0:1:0: task abort: SUCCESS scmd(0x0000000030d9d9e5)
Feb  2 11:54:46 TheVault kernel: sd 1:0:1:0: Power-on or device reset occurred
Feb  2 11:54:47 TheVault kernel: mpt3sas_cm0: log_info(0x31110e03): originator(PL), code(0x11), sub_code(0x0e03)
Feb  2 11:54:47 TheVault kernel: mpt3sas_cm0: log_info(0x31110e03): originator(PL), code(0x11), sub_code(0x0e03)
Feb  2 11:54:47 TheVault kernel: sd 1:0:1:0: [sdc] tag#6499 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=0s
Feb  2 11:54:47 TheVault kernel: sd 1:0:1:0: [sdc] tag#6499 CDB: opcode=0x88 88 00 00 00 00 03 a3 81 1e a0 00 00 00 08 00 00
Feb  2 11:54:47 TheVault kernel: blk_update_request: I/O error, dev sdc, sector 15628050080 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Feb  2 11:54:47 TheVault emhttpd: read SMART /dev/sdc
Feb  2 11:54:47 TheVault kernel: sd 1:0:1:0: Power-on or device reset occurred
Feb  2 11:54:50 TheVault kernel: sd 1:0:1:0: Power-on or device reset occurred
Feb  2 11:56:11 TheVault emhttpd: read SMART /dev/sdb
Feb  2 11:56:17 TheVault kernel: mdcmd (180): set md_write_method 1
Feb  2 11:56:17 TheVault kernel: 
Feb  2 11:56:45 TheVault kernel: sd 1:0:3:0: attempting task abort!scmd(0x00000000d7256e7a), outstanding for 15074 ms & timeout 15000 ms
Feb  2 11:56:45 TheVault kernel: sd 1:0:3:0: [sde] tag#6490 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Feb  2 11:56:45 TheVault kernel: scsi target1:0:3: handle(0x000c), sas_address(0x4433221103000000), phy(3)
Feb  2 11:56:45 TheVault kernel: scsi target1:0:3: enclosure logical id(0x500605b00daaefd0), slot(1) 
Feb  2 11:56:45 TheVault kernel: scsi target1:0:3: enclosure level(0x0000), connector name(     )
Feb  2 11:56:46 TheVault kernel: sd 1:0:3:0: task abort: SUCCESS scmd(0x00000000d7256e7a)
Feb  2 11:56:47 TheVault kernel: sd 1:0:3:0: Power-on or device reset occurred
Feb  2 11:56:47 TheVault emhttpd: read SMART /dev/sdd
Feb  2 11:56:47 TheVault emhttpd: read SMART /dev/sde
Feb  2 11:56:47 TheVault kernel: mpt3sas_cm0: log_info(0x31110e03): originator(PL), code(0x11), sub_code(0x0e03)
Feb  2 11:56:47 TheVault kernel: mpt3sas_cm0: log_info(0x31110e03): originator(PL), code(0x11), sub_code(0x0e03)
Feb  2 11:56:47 TheVault kernel: mpt3sas_cm0: log_info(0x31110e03): originator(PL), code(0x11), sub_code(0x0e03)
Feb  2 11:56:47 TheVault kernel: mpt3sas_cm0: log_info(0x31110e03): originator(PL), code(0x11), sub_code(0x0e03)
Feb  2 11:56:47 TheVault kernel: mpt3sas_cm0: log_info(0x31110e03): originator(PL), code(0x11), sub_code(0x0e03)
Feb  2 11:56:47 TheVault kernel: sd 1:0:3:0: [sde] tag#6487 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=0s
Feb  2 11:56:47 TheVault kernel: sd 1:0:3:0: [sde] tag#6487 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 48 00 00 00 30 00 00
Feb  2 11:56:47 TheVault kernel: blk_update_request: I/O error, dev sde, sector 72 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 0
Feb  2 11:56:47 TheVault kernel: sd 1:0:3:0: [sde] tag#6486 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=0s
Feb  2 11:56:47 TheVault kernel: sd 1:0:3:0: [sde] tag#6486 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 28 00 00 00 10 00 00
Feb  2 11:56:47 TheVault kernel: blk_update_request: I/O error, dev sde, sector 40 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
Feb  2 11:56:47 TheVault kernel: sd 1:0:3:0: [sde] tag#6489 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=0s
Feb  2 11:56:47 TheVault kernel: sd 1:0:3:0: [sde] tag#6489 CDB: opcode=0x88 88 00 00 00 00 00 00 00 01 08 00 00 00 f8 00 00
Feb  2 11:56:47 TheVault kernel: blk_update_request: I/O error, dev sde, sector 264 op 0x0:(READ) flags 0x80700 phys_seg 31 prio class 0
Feb  2 11:56:47 TheVault kernel: sd 1:0:3:0: [sde] tag#6485 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=0s
Feb  2 11:56:47 TheVault kernel: sd 1:0:3:0: [sde] tag#6485 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 10 00 00 00 08 00 00
Feb  2 11:56:47 TheVault kernel: blk_update_request: I/O error, dev sde, sector 16 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Feb  2 11:56:47 TheVault kernel: sd 1:0:3:0: [sde] tag#6488 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=0x00 cmd_age=0s
Feb  2 11:56:47 TheVault kernel: sd 1:0:3:0: [sde] tag#6488 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 88 00 00 00 78 00 00
Feb  2 11:56:47 TheVault kernel: blk_update_request: I/O error, dev sde, sector 136 op 0x0:(READ) flags 0x80700 phys_seg 15 prio class 0
Feb  2 11:56:47 TheVault kernel: sd 1:0:3:0: Power-on or device reset occurred
Feb  2 11:56:53 TheVault kernel: sd 1:0:3:0: Power-on or device reset occurred

 

thevault-diagnostics-20210202-1207.zip