Boot pool is scrubbed nightly - ignores days interval value

I have a new (not upgraded from 13.0) Core 13.3 system that insists on scrubbing the boot pool every night instead of every 7 days as set. I’ve tried changing this setting to no avail. The old forum had a post but it was for Scale and is 1.5 years old. My two other 13.0 systems don’t have the problem. Anyone else seeing this behavior?

1 Like

Upgraded from 13.0-U6.1 → 13.3, and I also notice the same thing.

My boot-pool is being scrubbed every day. :flushed:

UPDATE: Just found out that iX is going to diversify into the SSD market. They want to wear out our boot-pools with incessant scrubs, so that they can sell us their in-house branded SSDs! :scream:

Or there’s a new bug introduced in Core 13.3 that causes the boot-pool to be scrubbed every day, even if we set an interval for 7 days.

1 Like

I think you’ll find that reading does not wear out an SSD, and scrubbing is reading the entire SSD. (Yes, I realize that was a joke.)

1 Like

Fixed in 13.3-U1

1 Like

Looks like my boot-poo is going to be scrubbed every day… until 13.3-U1 is released.

[insert cornholio “need tp for my bunghole” joke here]
[mods please delete this and ban me]

3 Likes

Actually this is not quite true.

Standard SSDs hold the data bits in electrical state. If you constantly read the same blocks over and over again, the electrical charge fades and has to be “renewed”. That is basically write the data again.

Now I don’t know how many reads can occur before a SSD cell has to be re-written. (And it may be vendor or SSD cell type specific.) Nor do I know if SSDs normally would move such a block as part of wear leveling.

But, YES, constant READS can were out a SSD. Of course that is nowhere close the how fast WRITES can wear out a SSD.

2 Likes

Not fixed in U1!

1 Like

Talked about a lot in TrueNAS CORE 13.0-U6.3 and 13.3-U1 Are Now Available! - #33 by eturgeon

Maybe 13.3u2?

I’ve changed my mind. I don’t want this to be fixed. I love the peace of mind knowing that my boot-pool is 100% good… every day. :smiling_face_with_tear:

From Core 13.0 and earlier, this was handled wrong. They allowed the boot-pool to only be scrubbed once per week. You could even change it to be once per month! That’s crazy. Why would anyone live dangerously like that? :scream:

1 Like

FWIW, when using mirrored USB thumb drives I scrubbed every 3 days. :wink:

1 Like

Just adding my 2 cents.

I started experiencing this after upgrading from 13.0-U6.2 to 13.3-RELEASE.
Unfortunately, 13.3-U1 didn’t fix the issue for me.

my boot-pool scrubs every day and the jobs I created for my other pools run ignoring Threshold days :frowning:

1 Like

You’re right!

My main pools are scrubbing every week, even though I have the threshold set to 35 days!

What on earth happened with the release of Core 13.3?

So it’s not just a bug with the boot-pool scrubbing every day, but it’s also a bug with all storage pools ignoring the threshold value.

buddy this is happening from september :smiley:

opened a ticket some months ago. In 02 will be fixed

1 Like

TrueNAS-13.3-U1 Core

Hi, was there a fix for this (apart from adjusting the cron timing)? I have just found out that my core system has been running scrubs every night on 2 pools and even the boot SSDs.

It completely ignores the threshold.

I think its been doing this since the 13.3 update.

So do i just change the cron? That is not very good but it’ll have to do.

Thx im sure my drives loved that. ^^ but how to stop the boot-pools from doing it ??

afaik, you can’t.
For other pools, at time i disabled scrubs at all, and i do it manually (thanks to multi report i could check how days passed everytime)

so does it even ignore the cron timing? i can just set the cron to once a month cant i?

yep, you can!

pity there is no way to stop the boot pools from doing it. I see in another post that this was fixed in 13.3 ? i have 13,3 and thats where it started afaik.

Ok i shall give it a go, will at least be able to save my main rust.

the 13.3 version is the one impacted, the U2 should have the fix, but don’t know when will be released.

1 Like