LEKO

ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 25635 hours (1068 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 00 00 ff ff ff 4f 00 20d+10:15:07.577 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 20d+10:15:07.577 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 20d+10:15:07.577 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 20d+10:15:07.577 READ FPDMA QUEUED 60 00 40 ff ff ff 4f 00 20d+10:15:07.577 READ FPDMA QUEUED ^^^^ I get this odd error message on one of my drive and I UNRAID keeps telling me my drive have an "error". I try to find a bit more details on that specific SMART log, but I can't find anything obvious. I reseated all SATA cables, I've been doing a couple power cycles in the last days, the error seems to "stick". I just acknowledge the error in UNRAID gui. In the past I had experienced other SMART errors and HDD, it always meant the drive was dying: and there was symptoms like slow read or odd errors reported by the OS, etc. At the moment, I'm clueless because the drive performs well and it does gives any sign of being unreliable. Drive info: Seagate BarraCuda 3.5 (CMR) ST3000DM008-2DM166 Power-on hours: 34122 (3y, 10m, 21d, 18h) Head-flying hours: 14990h+46m+24.279s

I stumble upon this thread, because my parity drive now have Current pending sector count of 2 and I could not find any meaningful information about this particular S.M.A.R.T. metric. Based on your post @John_M, it would be nice to have a nice S.M.A.R.T. counters reference document/post with any tips on how to fix our workaround those errors. Based on what you said, I'll run GRC's SpinRite on Level2 on my parity drive to force a read/write and hopefully clear this pending sector counter. Oddly enough, my parity drive is one of the newest drive of my array. My other drive reports 1 uncorrected error, I'll probably also try to do a pass with SpinRite to ensure there is no other underlying problem. tower-smart-20211029-0736.zip tower-smart-20211029-0734.zip

That's right. A one-click to remove the disk from an array. This is exactly what I want to do with my oldest and smallest disk in my array that starts to log errors. I don't want to replace it, I just want it gone. It's a 640Gb drive while others are 3Tb+.

Feb 8 15:55:49 Tower bunker: warning: SHA256 hash key mismatch (updated), /mnt/disk1/domains/CentOS/vdisk1.img was modified Feb 8 15:58:50 Tower bunker: error: SHA256 hash key mismatch, /mnt/disk1/system/docker/docker.img is corrupted Feb 8 15:58:55 Tower bunker: warning: SHA256 hash key mismatch (updated), /mnt/disk1/system/libvirt/libvirt.img was modified Feb 8 15:58:55 Tower bunker: warning: 2 corrections made, export file needs to be updated ^^^^ Just got these logs. On first check, I tough I had a problem. Then, I noticed it was normal to have these hash to fail because it is the VM image file which changes quite a bit. Would it be possible to change the default behaviour of this plugin to not check the integrity of those files? At least, users should be warned that checking integrity of all files can generate false positive.

Same problem on my freshly installed unraid. I can't install this plugin because of the MD5 hash issue.