36 minutes ago, johnnie.black said:

-Assign any missing disk(s)

-Important - leave the browser on that page

 

Just to add as it might not be clear, when I said leave the browser on that page I mean the main page

Okay, just discovered something and I worry this has complicated things, apologies for not including this earlier, as I just saw this.

 

Disk5, when my array is started displays "Unmountable: No file system" but the FS column still shows btrfs in it. This is clearly not a good thing. does this change the rebuild processors we discussed before?

Edited February 6, 20188 yr by JimBob
Spelling

Is that before doing the invalid slot command? It would be best to not start the array before that.

This was before that, as my array started when I booted my by server after installing the new HBA

For clarity, I have not run the invalid disk command yet or any of those steps.

I don't know if it means anything now, since unRAID thinks parity1 is valid, parity2 and disk5 are new, then it is emulating disk5 from parity1, which you say is actually invalid.

 

The thing I am finding it hard to imagine is how you got to a point where unRAID thinks parity1 is valid.

1 minute ago, trurl said:

I don't know if it means anything now, since unRAID thinks parity1 is valid, parity2 and disk5 are new, then it is emulating disk5 from parity1, which you say is actually invalid.

 

The thing I am finding it hard to imagine is how you got to a point where unRAID thinks parity1 is valid.

 

I'm not sure if Unraid thinks parit1 is valid, as it display it as a disabled drive with a red x as seen in screenshot1. Parity1 has been invalid since my first screenshot.

OK, reviewed the screenshots again. So how can it emulate disk5 when it thinks parity1 is invalid and parity2 is new???

2 minutes ago, JimBob said:

For clarity, I have not run the invalid disk command yet or any of those steps.

OK, it doesn't matter then, if parity2 is valid it will rebuild a mountable disk5, but avoid starting the array before doing the invalid slot command, any change can cause issues.

When you look at the screen where it says disk5 is unmountable, does it still look like your first screenshot?

1 minute ago, trurl said:

OK, reviewed the screenshots again. So how can it emulate disk5 when it thinks parity1 is invalid and parity2 is new???

 

I don't think it is emulating disk5 anymore, as it describes it as unmountable and its storage size of 10TB does not get listed in the array total when it is "in" the array

Just now, trurl said:

When you look at the screen where it says disk5 is unmountable, does it still look like your first screenshot?

 

This is the current view of disk5 in my array when it is started but unassigned.

 

 

Does it normally say a new disk is unmountable? That doesn't sound right.

This disk was previously just "emulated" but down during the time of screenshot1.  This seems to be the first time, after reinstalling my new HBA that disk5 is showing as unmountable.

9 minutes ago, johnnie.black said:

it doesn't matter then, if parity2 is valid it will rebuild a mountable disk5, but avoid starting the array before doing the invalid slot command, any change can cause issues.

 

Is there any point in rebuilding disk5 to a different disk?

The HDD in disk5 is the original HDD that existed in this slot, and the only spare 10TB disk I have. So I can't rebuilt to a different disk right now.

If a spare is available it's always better, leaves the user with more options.

Another option it to do the invalid slot command "manually", that way you can check that the emulated disk looks correct before rebuilding.

That would be:

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-assign missing disk(s) you can leave parity1 unassigned for now
-check both "parity is already valid" and "maintenance mode" before starting the array
-start the array
-stop array, unassign disk5
-start array, check emulated disk5 mounts and contents look correct
-stop array, reassign disk5, also assign parity1
-start array to begin rebuild/parity sync

2 minutes ago, johnnie.black said:

Another option it to do the invalid slot command "manually", that way you can check that the emulated disk looks correct before rebuilding.

How do you do that? Same as before but don't assign disk5?

 

I see you already answered as I was typing.

3 minutes ago, johnnie.black said:

That would be:

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-assign missing disk(s) you can leave parity1 unassigned for now
-check both "parity is already valid" and "maintenance mode" before starting the array
-start the array
-stop array, unassign disk5
-start array, check emulated disk5 mounts and contents look correct
-stop array, reassign disk5, also assign parity1
-start array to begin rebuild/parity sync

 

Which do you think would be the safest option, given the scenario? These steps or the ones you detailed before?

Just now, JimBob said:

Which do you think would be the safest option, given the scenario? These steps or the ones you detailed before?

The last option, since you can at least see if the disk mounts and contents look OK before starting to rebuild it, and overwriting it.

Right! I'll begin those steps and keep you updated. Thanks again

Ok update. at step " -start array, check emulated disk5 mounts and contents look correct" the disk 5 is currently listed as "Unmountable: No file system" with a red X. That says "Disk is Missing (Disabled), Contents Emulated" when you hover over the X.

 

Which to me sounds like two bits of conflicting information. And the total array size is listed as 34TB which does not include the 10TB of disk5. SO that doesn't appear to be running in the array.

 

Is Disk5 out for the count?

Edited February 6, 20188 yr by JimBob
Adding more info