I have a 6TB Seagate drive that had 8 reallocated sectors during a full metadata download on my jellyfin server and then an 8 additional when I copied the data off that drive so 16 in total. Both these operations were only reads off the drive. I did a parity check after moving all the data of the drive and then decided to stress test the drive by running 3 pre-clears on it and had no changes to pending or reallocated sectors (stayed at 16 reallocated sectors) so I believe this may have been a fluke. The SMART Threshold for the drive is 10 sectors. Is there a way to change or override the Threshold to lets say 17 so I can still use the drive and get a warning if they increase? I have tried just acknowledging the alarm but it re-alarms when the drive is spun up. I am running an additional erase and clear now to see if there is any change with a random write and a clear.

You can cick the thumbs down on the dashboard.

6 hours ago, JorgeB said:

You can cick the thumbs down on the dashboard.

I have done that it comes back every time the drive reports SMART status.

That will acknowledge the current values on the dash and keep a thumbs-up until the value changes again; it won't change any of the actual SMART values, that is not possible.

The alarm comes back in with out the reallocated sectors changing, the alarm comes in when the drives reports that the reallocated have passed the threshold. Thumbs up/down button only acknowledges the alarm temporarily and comes back in.

Once again the the thumbs up/down button does not work. There are no changes in my SMART values. I am looking for a way to change or override the threshold for reallocated sectors in such a way that if they continue to rise it will tell me. As it is now I will alarm every time the drive spins up regardless of any changes in SMART values. I believe that the reallocated sectors were a fluke as the drive has gone through multiple full clears with no changes to reallocated sectors. I don't know if the problem was caused by a bad cable connection, interference, corrupt data, or maybe even actual bad sectors but it seems to be an isolated incident.

1 hour ago, sgibbers17 said:

I believe that the reallocated sectors were a fluke as the drive has gone through multiple full clears with no changes to reallocated sectors.

It's not a fluke, that's how it works. It found some bad sectors and reallocated them, it's now done so it's normal to have no further change until more fail. Those are gone for good.

You can probably disable the notification for that on the disk page, but then I believe you won't get warned if it increases.

Edited September 1, 2025Sep 1 by Kilrah

1 hour ago, Kilrah said:

It's not a fluke, that's how it works. It found some bad sectors and reallocated them, it's now done so it's normal to have no further change until more fail. Those are gone for good.

You can probably disable the notification for that on the disk page, but then I believe you won't get warned if it increases.

Thanks. Fluke wasn't the best word for it, but it was easier to say I don't think the drive is in immediate failure and probably won't get worse for a while.

It would be nice to be able to put a new threshold in just like the temperature. I definitely don't want to disable the alarm notification because as I don't think the drive is bad now but in a few months down the road it might.

Post the SMART report for that drive; you would only get a new notification if the value changes, unless the SMART attribute shows as "FAILING NOW"

Here is a copy of my SMART report with a preclear log for 3 cycles and an erase and clear log.

9 hours ago, JorgeB said:

Post the SMART report for that drive; you would only get a new notification if the value changes, unless the SMART attribute shows as "FAILING NOW"

I don't see anything that says failing now, but I have acknowledged the alarm multiple times with no changes to attributes that I can tell.

ST6000VN0033-2EE110_ZAD7AD6B-20250902-1145.txt preclear_report_ZAD7AD6B_2025.08.30_18.34.49.txt preclear_report_ZAD7AD6B_2025.09.02_05.18.23.txt

Those should be acknowledgeable; post a screenshot of the thumbs down when hovering the mouse on top of it.

I'll see if it is back in when I get home but it hasn't come back since I finished the 3x preclear. It came in during the 3x preclear a few times but when I did the erase and clear it did not come in at all.

I had performed an extended SMART test and I could not get the alarm to come back. I did take a screenshot of the last alarm that was in the notifications. I have uploaded both the screenshot and the last SMART test report.

ST6000VN0033-2EE110_ZAD7AD6B-20250903-0919.txt

As long as you don't keep getting new notifications, you are fine, and if the reallocated sectors change, you should get a new one.

The alarm came back in with no writes or reads happening since I did the erase and clear and no changes to START attributes. Here is a screen shot of the thumbs down and the smart attributes that was asked for. It seams that acknowledge the alarm does not permanently acknowledge it. It re-alarmed when I stopped my array the drive is an unassigned drive and not connected to the array, pool, mounted, or formated. I saw a setting in the SMART setting that may help "SMART notification tolerance level" it looks like that might work but if I understand it if the threshold is 10 it just adds a percentage to that so to get the new threshold to 17 sectors I would need to set the threshold to 70% but the highest is 50%. I started and stopped my array to see if I could reproduce the error and it did come in twice in a row. I started with 5% and I haven't had the alarm come in so I guess I don't understand the setting. It also looks like its for all the attributes so I don't want to set it too high and mask another attribute problem.

The behavior with unassigned devices may be different, it should not happen with the device assigned to the array or a pool.