Hey all.

 

I an trying to remove a drive from beta13 but not replace it. I tried what the guide said but the initconfig seemed to have worked but it doesn't automatically do a parity check after I start the array.

 

How can I force a parity check via the command line?

Hey all.

 

I an trying to remove a drive from beta13 but not replace it. I tried what the guide said but the initconfig seemed to have worked but it doesn't automatically do a parity check after I start the array.

 

How can I force a parity check via the command line?

You probably did not respond to initconfig with "Yes" (capital "Y", lower case "es")

As an alternative to the command line, in the 5.0beta13 version, there is a button on the "Utils" tab to set a new disk configuration.  it is labeled as "New Config"

It invokes "initconfig" without having to go to the command line.

 

In any case, you can force a parity check by typing

/root/mdcmd check

on the command line.

 

Or, on the main web-management page, press the "Check" button. 

(There is a checkbox to its right on your version, to have unRAID correct the errors make sure it is checked first before you press the "Check" button)

 

Joe L.

Hey all.

 

I an trying to remove a drive from beta13 but not replace it. I tried what the guide said but the initconfig seemed to have worked but it doesn't automatically do a parity check after I start the array.

 

How can I force a parity check via the command line?

You probably did not respond to initconfig with "Yes" (capital "Y", lower case "es")

As an alternative to the command line, in the 5.0beta13 version, there is a button on the "Utils" tab to set a new disk configuration.  it is labeled as "New Config"

It invokes "initconfig" without having to go to the command line.

 

In any case, you can force a parity check by typing

/root/mdcmd check

on the command line.

 

Or, on the main web-management page, press the "Check" button.  

(There is a checkbox to its right on your version, to have unRAID correct the errors make sure it is checked first before you press the "Check" button)

 

Joe L.

 

I didn't include the capital the first time and nothing happened. The second time I certainly typed "Yes" and there was a slight pause and then it said "complete".

 

I will try new config later today when I am home. As for that command I tried it but it didn't do anything but in saying that I navigated to the /root/ and then ran "mdcmd check", this also did nothing. Normally I would have just run a parity check from the main menu but there is no button at the moment. I know how weird that sounds and yes I have seen the button before. The status light so to speak for the array is orange and the check button no longer exists.

 

I don't think the "initconfig" command worked therefore the system thinks that the missing disk is a failed one (bad array) and therefore I need to replace it?

 

EDIT:

I don't know why when it's the same command but the "New Config" worked, I re-assigned the drives and the parity check is running now