Thitt0927
-
Posts
14 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Thitt0927
-
-
Good morning! I had an issue yesterday that I thought I solved with communities help. Parity sync was running fine at 130 mb/s My house lost power during the parity sync. now power is back but sync is now only running at 6mb/s. diags are attached any further assistance would be appreciated!
-
4 minutes ago, trurl said:
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.
yup!! I got it all sorted and everything is working as it should! Thank you for all the help!!
-
disregard my last question that drive was my old parity drive.
-
1 hour ago, trurl said:
New Config only allows you to reset disk assignments, doesn't change anything else about your settings.
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
-
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?
-
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
-
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.
-
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
-
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
-
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.
-
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!
-
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.
-
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
Parity sync slow
in General Support
Posted
Ordered UPS today LOL... no usb in the array.. I have not done memtest