bogus current pend sect is 1

[Dal1980]

Hi, I've searched for previous topics with this "bogus current pend sect is 1" warning but I don't understand it.

 

I got an email alert yesterday:

Unraid Status: Warning [BORG] - bogus current pend sect is 1

Event: Unraid Cache 2 SMART health [197]
Subject: Warning [BORG] - bogus current pend sect is 1
Description: CT250MX500SSD1_1843E1D3A43F (sdc)
Importance: warning

5 hours later another email came through:

Unraid Status: Notice [BORG] - array health report [PASS]

 

Event: Unraid Status Subject: Notice [BORG] - array health report [PASS]
Description: Array has 6 disks (including parity & cache)
Importance: normal

Parity - ST6000VN0033-2EE110_ZAD7QRYX (sdf) - active 33 C [OK]
Parity2 - ST6000VN0033-2EE110_ZAD7QPEN (sdg) - active 33 C [OK]
Disk 1 - ST4000VN008-2DR166_ZGY6800C (sde) - active 28 C [OK]
Disk 2 - ST4000VN008-2DR166_ZGY6G2H7 (sdd) - active 27 C [OK]
Cache - Crucial_CT275MX300SSD1_164414826C2F (sdb) - active 30 C [OK]
Cache 2 - CT250MX500SSD1_1843E1D3A43F (sdc) - active 35 C [OK]

Parity is valid Last checked on Mon 11 May 2020 12:46:32 PM BST (2 days ago),
finding 0 errors. Duration: 10 hours, 46 minutes, 31 seconds. Average speed: 154.7 MB/s

So what was all that warning about "bogus current pend sect is 1" about?

 

Many thanks

 

[Squid]

https://forums.unraid.net/topic/69771-still-not-solved-current-pending-sector-is-1on-new-ssd-cache/?tab=comments#comment-638122

 

TLDR: Bitch to Crucial, as they seem to believe that on an SSD, a pending sector that appears and then disappears is completely normal and expected, and can't be bothered to do anything about it because quite simply they just plain don't care.

 

The "bogus" thing appears to be the smartctl program which gathers the information from the ssd covering up for Crucial's terrible firmware and alerting you that "hey, the drive says that it's bad, but we're going to take the shot and assume that it's not actually bad"

[Dal1980]

Thanks for explaining that. I appreciate it.