spamalam Posted December 16, 2018 Share Posted December 16, 2018 Hi, I'm seeing the following in my dmesg, and google hasn't been too fruitful on a root cause and whether I should worry. Could anyone shed some light? These are two Samsung SSDs I have, one is cache another is outside of the array. [421813.197867] sd 1:0:3:0: [sde] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [421813.197879] sd 1:0:3:0: [sde] tag#6 Sense Key : 0x5 [current] [421813.197882] sd 1:0:3:0: [sde] tag#6 ASC=0x20 ASCQ=0x0 [421813.197886] sd 1:0:3:0: [sde] tag#6 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 [421844.188480] sd 1:0:2:0: [sdd] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [421844.188483] sd 1:0:2:0: [sdd] tag#6 Sense Key : 0x5 [current] [421844.188485] sd 1:0:2:0: [sdd] tag#6 ASC=0x20 ASCQ=0x0 [421844.188489] sd 1:0:2:0: [sdd] tag#6 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 [421844.198571] sd 1:0:3:0: [sde] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [421844.198576] sd 1:0:3:0: [sde] tag#6 Sense Key : 0x5 [current] [421844.198578] sd 1:0:3:0: [sde] tag#6 ASC=0x20 ASCQ=0x0 [421844.198582] sd 1:0:3:0: [sde] tag#6 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 [421867.472422] sd 1:0:2:0: [sdd] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [421867.472427] sd 1:0:2:0: [sdd] tag#6 Sense Key : 0x5 [current] [421867.472430] sd 1:0:2:0: [sdd] tag#6 ASC=0x20 ASCQ=0x0 [421867.472433] sd 1:0:2:0: [sdd] tag#6 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 [421867.535890] sd 1:0:3:0: [sde] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [421867.535895] sd 1:0:3:0: [sde] tag#6 Sense Key : 0x5 [current] [421867.535898] sd 1:0:3:0: [sde] tag#6 ASC=0x20 ASCQ=0x0 [421867.535902] sd 1:0:3:0: [sde] tag#6 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 [421872.561126] sd 1:0:2:0: [sdd] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [421872.561136] sd 1:0:2:0: [sdd] tag#5 Sense Key : 0x5 [current] [421872.561139] sd 1:0:2:0: [sdd] tag#5 ASC=0x20 ASCQ=0x0 [421872.561143] sd 1:0:2:0: [sdd] tag#5 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 [421872.570252] sd 1:0:3:0: [sde] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [421872.570257] sd 1:0:3:0: [sde] tag#5 Sense Key : 0x5 [current] [421872.570260] sd 1:0:3:0: [sde] tag#5 ASC=0x20 ASCQ=0x0 [421872.570264] sd 1:0:3:0: [sde] tag#5 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 [421879.257931] sd 1:0:2:0: [sdd] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [421879.257941] sd 1:0:2:0: [sdd] tag#6 Sense Key : 0x5 [current] [421879.257944] sd 1:0:2:0: [sdd] tag#6 ASC=0x20 ASCQ=0x0 [421879.257948] sd 1:0:2:0: [sdd] tag#6 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 [421879.320942] sd 1:0:3:0: [sde] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [421879.320950] sd 1:0:3:0: [sde] tag#6 Sense Key : 0x5 [current] [421879.320954] sd 1:0:3:0: [sde] tag#6 ASC=0x20 ASCQ=0x0 [421879.320957] sd 1:0:3:0: [sde] tag#6 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 [421888.432468] sd 1:0:2:0: [sdd] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [421888.432477] sd 1:0:2:0: [sdd] tag#7 Sense Key : 0x5 [current] [421888.432480] sd 1:0:2:0: [sdd] tag#7 ASC=0x20 ASCQ=0x0 [421888.432483] sd 1:0:2:0: [sdd] tag#7 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 [421888.502985] sd 1:0:3:0: [sde] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 [421888.502990] sd 1:0:3:0: [sde] tag#7 Sense Key : 0x5 [current] [421888.502993] sd 1:0:3:0: [sde] tag#7 ASC=0x20 ASCQ=0x0 [421888.502997] sd 1:0:3:0: [sde] tag#7 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 beyonder-nas-diagnostics-20181216-1244.zip Link to comment
JorgeB Posted December 16, 2018 Share Posted December 16, 2018 Those errors are likely because they are on an Areca controller, try a different one, onboard Intel SATA is the best place to connect SSDs because it supports trim, just make sure it's set to AHCI. Link to comment
spamalam Posted December 16, 2018 Author Share Posted December 16, 2018 4 minutes ago, johnnie.black said: Those errors are likely because they are on an Areca controller, try a different one, onboard Intel SATA is the best place to connect SSDs because it supports trim, just make sure it's set to AHCI. Will leaving them on Areca cause a problem other than the spam? Link to comment
JorgeB Posted December 16, 2018 Share Posted December 16, 2018 14 minutes ago, spamalam said: Will leaving them on Areca cause a problem other than the spam? Probably not, but if trim doesn't work there it can also cause dome write performance degradation. Link to comment
spamalam Posted December 17, 2018 Author Share Posted December 17, 2018 I moved to the onboard as recommend, I just noticed its just SATA 3G not 6G like the SAS controller. I guess that's not going to matter so much. Is there any other config needed for SSD that's needed? Link to comment
JorgeB Posted December 17, 2018 Share Posted December 17, 2018 8 hours ago, spamalam said: Is there any other config needed for SSD that's needed? Make sure the Dynamix trim pugin is installed and scheduled to run once a day or so. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.