I have a weird issue/bug.

The Fix Common Problem Plugin says 👇🏻

 

Clicking on Scheduler page takes me to the page where there is no setting for parity checks 👇🏻

 

I remember there used to be more settings on that page before. I just upgraded from 6.12.15 to 7.1.2, am I missing something here.

 

Thanks in advance for the help.

Attach your Diagnostics file to a new post in this thread.  (I can assure that there is a section for scheduling  a Parity check in v7..1.2)

Do you have an array assigned?

On 5/19/2025 at 10:09 AM, Frank1940 said:

Attach your Diagnostics file to a new post in this thread.  (I can assure that there is a section for scheduling  a Parity check in v7..1.2)

On 5/19/2025 at 10:10 AM, JorgeB said:

Do you have an array assigned?

@Frank1940 -

Thanks for the reply, I don't believe this needs a diagnostics log. I don't see any errors in logs. I am open to providing it if I can sanitize my personal info. Please let me know how to do that.

I would like to believe your assurance, but it is not there on the page. I also restarted server 2 times, no dice.

Attaching the screen zoomed out to show there are only 2 options on that page.

@JorgeB -

Yes there is an array of course, multiple pools. I am upgrading from previous version. No Parity drive though, I only do a Read-Check every 3 months usually.

Thanks

Created a new thread as suggested by @Frank1940

Thanks in advance.

You dont have a parity drive.

Edit: In case it wasnt obvious, you need parity to check the parity.

I do absolutely have no clue why you perform regular read-checks, as its pointless as there is nothing to check against and since when your drive fails, its gone and that will happen as soon as you try to read anything from the disk at any point. Get a single parity drive at least to have some sort of protection against drive failure

Edited May 21, 20251 yr by Mainfrezzer

3 hours ago, Mainfrezzer said:

You dont have a parity drive.

Edit: In case it wasnt obvious, you need parity to check the parity.

I do absolutely have no clue why you perform regular read-checks, as its pointless as there is nothing to check against and since when your drive fails, its gone and that will happen as soon as you try to read anything from the disk at any point. Get a single parity drive at least to have some sort of protection against drive failure

The Parity Check settings not showing under Settings->Scheduler if you do not have a parity drive is definitely a recent change.

Not sure I completely agree though that doing a Read Check is pointless as it at least proves all drives can be read without error. Much easier than performing an extended SMART test on all drives. In my view the section should still appear, but it should point out that it is only a Read Check, and any fields that are irrelevant to a Read check such as the option to Write Corrections should be hidden or disabled.

Yep, looks like it's now missing if there's no parity, not sure if it was done on purpose or accidental, will try to find out, but I agree with Itimpi that it would be good to have the option to schedule a read check.

6 hours ago, Unraid-arr said:

Created a new thread as suggested by @Frank1940

Thanks in advance.

I didn't say to do this. What I said was:

On 5/19/2025 at 10:09 AM, Frank1940 said:

Attach your Diagnostics file to a new post in this thread

This requested that you post the Diagnostics in a new post in this thread. (A thread is a series of posts for a single topic/discussion. You are reading my new post in your thread right now.) The reason for this is that if you simply an edit an existing post in this thread, anyone following this thread never receives notification that anything occurred in this thread! With a new post, any follower will see notification of that action. It also serves as a 'bump' to the thread to move it to the top of the page in the sub-forum which makes it more likely that more folks will notice your thread and look at it. ( @Unraid-arr, I am not picking on on you with this long explanation but writing it so that other Forum users realize how things work and why editing a post to add new information is a bad idea if you want keep your thread active.)

Edited May 21, 20251 yr by Frank1940

4 hours ago, itimpi said:

The Parity Check settings not showing under Settings->Scheduler if you do not have a parity drive is definitely a recent change.

2 hours ago, JorgeB said:

Yep, looks like it's now missing if there's no parity, not sure if it was done on purpose or accidental, will try to find out, but I agree with Itimpi that it would be good to have the option to schedule a read check.

it happend 4 months ago and was done on purpose

Show parity schedule only when parity disk(s) are present · unraid/webgui@cccdae7 · GitHub

Edited May 21, 20251 yr by Mainfrezzer
4 not 5

Looks like FCP plugin just needs to be updated to recognize that a parity disk is not installed and to instead recommend running a read check or just removed.

11 hours ago, Mainfrezzer said:

You dont have a parity drive.

Edit: In case it wasnt obvious, you need parity to check the parity.

I do absolutely have no clue why you perform regular read-checks, as its pointless as there is nothing to check against and since when your drive fails, its gone and that will happen as soon as you try to read anything from the disk at any point. Get a single parity drive at least to have some sort of protection against drive failure

7 hours ago, itimpi said:

The Parity Check settings not showing under Settings->Scheduler if you do not have a parity drive is definitely a recent change.

Not sure I completely agree though that doing a Read Check is pointless as it at least proves all drives can be read without error. Much easier than performing an extended SMART test on all drives. In my view the section should still appear, but it should point out that it is only a Read Check, and any fields that are irrelevant to a Read check such as the option to Write Corrections should be hidden or disabled.

6 hours ago, JorgeB said:

Yep, looks like it's now missing if there's no parity, not sure if it was done on purpose or accidental, will try to find out, but I agree with Itimpi that it would be good to have the option to schedule a read check.

3 hours ago, Mainfrezzer said:

it happend 4 months ago and was done on purpose

Show parity schedule only when parity disk(s) are present · unraid/webgui@cccdae7 · GitHub

2 hours ago, MowMdown said:

Looks like FCP plugin just needs to be updated to recognize that a parity disk is not installed and to instead recommend running a read check or just removed.

@Mainfrezzer — I liked the read-check scheduling, I am not sure why this functionality is removed. It gives me a choice to schedule the read checks per my schedule.

I am not sure if you are trying to be snarky but, It is not obvious as parity check doubled as read-checks if parity drive is not present. I don't need a parity drive for my pool, so I don't have it.

Also, if unraid doesn't want people to do a read-check on a schedule remove the colored history section on main page which turns red if you don't do parity/read-check for 90 days.

@itimpi — thanks for the response, you worded it better than me. I agree with everything you said.

@MowMdown — yes, FCP can be updated to have a better language. But importantly I would like this functionality back to do scheduled read-checks.

Thanks everyone!

Edited May 21, 20251 yr by Unraid-arr

4 hours ago, Frank1940 said:

I didn't say to do this. What I said was:

This requested that you post the Diagnostics in a new post in this thread. (A thread is a series of posts for a single topic/discussion. You are reading my new post in your thread right now.) The reason for this is that if you simply an edit an existing post in this thread, anyone following this thread never receives notification that anything occurred in this thread! With a new post, any follower will see notification of that action. It also serves as a 'bump' to the thread to move it to the top of the page in the sub-forum which makes it more likely that more folks will notice your thread and look at it. ( @Unraid-arr, I am not picking on on you with this long explanation but writing it so that other Forum users realize how things work and why editing a post to add new information is a bad idea if you want keep your thread active.)

Thanks @Frank1940 for the response, much appreciated. I was not sure where you wanted me to post. It was confusing for me. I like this explanation, and thanks for the details.

You can now schedule read checks again in 7.2.0-beta.1 and newer.