Swapping from a 4TB parity to 8TB when the parity sync begins it still only shows 4TB and the speed of the sync ranges from 10-35mb/s... very new to Unraid and Nas setup in general please be easy on me if this is a stupid issue LOL Please see screen shots and diagnostics report 

hittnas-diagnostics-20220311-0848.zip

Edited March 11, 20224 yr by Thitt0927

On mobile now so can't look at Diagnostics yet. 

 

Why didn't you fix your unmountable disk 2 before making any other changes? 

 

Also, is disk 3 external? USB NOT recommended for array or pools 

Not sure what happened with Disk 2, it was fine then I rebooted and did not notice it until I uploaded this screenshot.  yes that is a USB drive It was when I was first playing with unraid just have never replaced it yet.

Edited March 11, 20224 yr by Thitt0927

Why does it say disk2 is btrfs when all of your other array disks are xfs? Is that even correct? Default for array disks is XFS so you would have had to intentionally change it if that disk really is supposed to be btrfs.

9 minutes ago, trurl said:

Why does it say disk2 is btrfs when all of your other array disks are xfs? Is that even correct? Default for array disks is XFS so you would have had to intentionally change it if that disk really is supposed to be btrfs.

I have Disk 2 back online now.  as far as btrfs vs xfs not sure why.. I do not remember changing anything when setting up it.  once I get parity back I plan to remove disk 2 and disk 3..  I have a 4tb and 6tb on deck to replace them  Parity sync is still extremely slow and the size mismatch is still present... Thank you for your replies!  I appreciate any help!

Edited March 11, 20224 yr by Thitt0927

A lot of dumps in your syslog, seems related to disks. Maybe a controller issue?

 

4 minutes ago, Thitt0927 said:

once I get parity back I plan to remove disk 2 and disk 3

Since these have little or no data on them, you could just New Config and build parity without them.

 

You seem to have a lot of disks for someone just starting, and since some are small, I am guessing some are not new. Do any have SMART warnings on the Dashboard page?

 

I think I would just remove those small disks also. Each additional disk is an additional point of failure, and they aren't adding much.

 

Not sure about parity size, maybe it isn't upsized until rebuild is complete.

 

Your appdata and system shares are on the array. You want these all on one of your fast pools and set to stay there so your docker/VM performance won't be impacted by slower parity array and so your array disks can spin down since these shares always have open files.

 

Unraid driver is crashing, this sometimes happens with some hardware/kernel combinations, you can try updating to v6.10-rc3 to see if it helps.

4 minutes ago, trurl said:

 

5 minutes ago, trurl said:

You seem to have a lot of disks for someone just starting, and since some are small, I am guessing some are not new. Do any have SMART warnings on the Dashboard page?

I started a messing unraid a few months ago.  everything was running with no issues so I had been adding disks.  I started wanting to get disks larger than my 4tb parity thats when I decided to replace it with an 8tb today and when issues started.   there are no SMART warnings on the dashboard.   

 

 

 

 

1 minute ago, JorgeB said:

Unraid driver is crashing, this sometimes happens with some hardware/kernel combinations, you can try updating to v6.10-rc3 to see if it helps.

I will give that a try Thank you 

 

Forgot to mention, size issue could be unrelated, but difficult to analyze the current log due to spam, post new diags with rc3 to see if it's better.

9 minutes ago, JorgeB said:

Forgot to mention, size issue could be unrelated, but difficult to analyze the current log due to spam, post new diags with rc3 to see if it's better.

updated os here are the new diags.  only other odd thing is now my cache drives say invalid config.. but i can worry about that later 

 

hittnas-diagnostics-20220311-1032.zip

nobody answered the initial question "why is Parity still using 4Tb only?" yet, so I try to add my explanation:

 

The Parity drive must be the largest in the array because it stores the addes sums of all sector data of the data disk. Initially it is fully wiped out with zeros, then the "parity regeneration" task will start and it will read every sector of the data disks, sum those up and store the result on the parity disk.

If a data disk is smaller than the current position, it is skipped for this reading.

At the end, all sectors of the parity drive that have a correspondinf sector of a data drive, will be used, the remaining sectors are untouched and still show zeros.

So if you largest data disk now is only 4 tb the parity drive also will only be used up to this point, 4Tb.

 

But the reason for this ("the parity drive needs to be the largest disk in the array") is that now you can add new disks or exchange old one with disks up to 8 Tb in size.

 

So, its like an investment into the future, it will then safe you a lot of time (no need to regenerate everything, just refill the new disk up to the size of the old one or just add a new empty drive instantly)

 

Good news is that the crashing is gone, how is the speed?

 

Pool issues are the result of a duplicate filesystem on the unassigned disk (sdl), I guess that's old parity? Wiping/reformatting/disconnecting it should fix that, after rebooting.

Just now, JorgeB said:

Good news is that the crashing is gone, how is the speed?

 

Pool issues are the result of a duplicate filesystem on the unassigned disk (sdl), I guess that's old parity? Wiping/reformatting/disconnecting it should fix that, after rebooting.

speed is still pretty slow sitting around 38-40 mb/s I assume it should be a bit faster than that.

T

4 minutes ago, Michael Meiszl said:

nobody answered the initial question "why is Parity still using 4Tb only?" yet, so I try to add my explanation:

 

The Parity drive must be the largest in the array because it stores the addes sums of all sector data of the data disk. Initially it is fully wiped out with zeros, then the "parity regeneration" task will start and it will read every sector of the data disks, sum those up and store the result on the parity disk.

If a data disk is smaller than the current position, it is skipped for this reading.

At the end, all sectors of the parity drive that have a correspondinf sector of a data drive, will be used, the remaining sectors are untouched and still show zeros.

So if you largest data disk now is only 4 tb the parity drive also will only be used up to this point, 4Tb.

 

But the reason for this ("the parity drive needs to be the largest disk in the array") is that now you can add new disks or exchange old one with disks up to 8 Tb in size.

 

So, its like an investment into the future, it will then safe you a lot of time (no need to regenerate everything, just refill the new disk up to the size of the old one or just add a new empty drive instantly)

 

Thank you.. so if i am understanding this correctly since the original parity was 4tb that is what it is rebuilding onto the new 8tb drive and i should not worry that the sync shows 4tb 

7 minutes ago, JorgeB said:

duplicate filesystem on the unassigned disk (sdl), I guess that's old parity?

No, it's a duplicate of disk2, so after wiping it there might still be issues with parity because there's only one btrfs array disk, likely also the reason parity is only showing 4TB, post new diags after fixing sdl and rebooting.

9 minutes ago, Michael Meiszl said:

Initially it is fully wiped out with zeros

No it doesn't do that. It would take a long time and no point since it is just going to overwrite the whole disk with parity.

10 minutes ago, Thitt0927 said:

38-40 mb/s I assume it should be a bit faster than that.

Possibly, but with USB and older disks in the array it might not, you can run the the disk speed docker to check disk performance.

7 minutes ago, Thitt0927 said:

speed is still pretty slow sitting around 38-40 mb/s I assume it should be a bit faster than that.

Parity sync is as fast as the slowest disk. My guess is that your USB disk is making the parity sync extremely slow.

 

1 hour ago, trurl said:

Since these have little or no data on them, you could just New Config and build parity without them.

 

You seem to have a lot of disks for someone just starting, and since some are small, I am guessing some are not new. Do any have SMART warnings on the Dashboard page?

 

I think I would just remove those small disks also. Each additional disk is an additional point of failure, and they aren't adding much.

You can stop the current parity build, then go to New Config and create a new array without those disks and rebuild parity.

9 minutes ago, trurl said:

You can stop the current parity build, then go to New Config and create a new array without those disks and rebuild parity.

This may sound like my best course of action.. couple questions.. how do I start a new config? did not seem obvious to me.  Will it keep all my docker settings? 

New Config only allows you to reset disk assignments, doesn't change anything else about your settings.

 

https://wiki.unraid.net/Manual/Tools#New_Config

1 hour ago, trurl said:

New Config only allows you to reset disk assignments, doesn't change anything else about your settings.

 

https://wiki.unraid.net/Manual/Tools#New_Config

Thank you this is solved all my original issues parity sync is running at 130 mb/s and shows the correct size...the issue i have now is once i did the new config one my my drives is showing unmountable/ wrong or no file system.  any insight on that?  Again thank you for solving the other issues

disregard my last question that drive was my old parity drive.

You can format the disk in Main - Array Operation and it will become a 4TB data disk. You don't even have to wait for parity sync to complete.