Evening all,
I've finally added the first drive to my NAS build, after it just running the OS drive for the last month or two (was having some stability issues caused by an iffy PSU) and have found an interesting quirk/problem...of sorts.
The first drive added to the system is a Western Digital 4TB Red - WD40ERFX on a Syba SI-PEX40064 SATA3 card which uses the Marvell 88SE9215 chipset (I'm using an old 775 board, no SATA3 and only 4 ports onboard).
I copied over 2.10TB of stuff to the drive without issue using FreeFileSync from my HTPC.
However! When I checked the SMART logs (just for the sake of checking), I found I had an error...at the exact time of checking the log.
I checked again a day or two after, got another error, again at the exact time of checking the log, see the below extract from the SMART Info;
Error 2 [1] occurred at disk power-on lifetime: 38 hours (1 days + 14 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 0b 00 00 00 00 00 00 00 00 Error: ABRT
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 1d+14:55:27.743 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 1d+14:55:27.742 SMART READ LOG
2f 00 00 00 01 00 00 00 00 01 04 40 08 1d+14:55:27.711 READ LOG EXT
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 1d+14:55:27.710 SMART WRITE LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 1d+14:55:27.709 SMART WRITE LOG
Error 1 [0] occurred at disk power-on lifetime: 12 hours (0 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 0b 00 00 00 00 00 00 00 00 Error: ABRT
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 12:33:09.171 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e0 00 08 12:33:09.171 SMART READ LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 12:33:09.171 SMART READ LOG
b0 00 d6 00 01 00 00 00 c2 4f e0 00 08 12:33:09.170 SMART WRITE LOG
b0 00 d5 00 01 00 00 00 c2 4f e1 00 08 12:33:09.170 SMART READ LOG
So, it looks like accessing the SMART info, is actually causing a SMART error. O.o
Now, while I have no doubt that my drive is working absolutely fine, what's causing this SMART logging issue when I read the log it's self? Is there any way of stopping it? And moreover is it any sign of potential instability?
Thanks in advance.