JorgeB
-
Posts
67,556 -
Joined
-
Last visited
-
Days Won
707
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
While the controller is bottlenecking a little it's not the issue, please post diags during a parity check, make sure no other array activity is going on, there were some small writes to the array in the previous diags.
-
Also don't forget to unmount old cache from UD before re-assigning.
-
The FAQ mentions in bold that: You only had one cache slot. Unassign current cache, start the array, stop the array, set cache slots to 2, assign old cache (there can't be an "all data on this device will be deleted" warning), start array, check old cache is mounting correctly, stop array, now you can replace.
-
Something wasn't done correctly, please post diags.
-
You need to use the parity swap procedure.
-
Like mentioned single data drive is a special case where Unraid detects that and works same as raid1. https://forums.unraid.net/topic/74962-2-drive-system-mirror-or-parity/?tab=comments#comment-690816
-
This a a board/kernel issue, disable IOMMU if not needed, look for a BIOS update and/or try different PCIe slot for the HBA. Also, since btrfs is showing corruption errors good idea to run memtest.
-
Yes, no current HDD can get close to those speeds, only if using SSDs you'd need to worry.
-
With just parity and one data drive Unraid works in raid1.
-
Parity swap is not for upgrading just parity, for that you just assign the new parity and start the array, if you want to keep the old parity 100% valid in case something happens do the re-sync in maintenance mode.
-
You can just download the beta from here and update manually.
-
Main issue appears to be disks 3 and 4, check/replace cables, but your also using a Marvell controller and SATA port multiplier, we don't recommend either, especialy not both together,
-
Disks are Formatted with type 2 protection You need to remove this, you can just google it.
-
Disks are Formatted with type 2 protection You need to remove this, you can just google it.
-
You'd need to do another new config and this time don't check "parity is already valid" OR unassign both parity disks, start the array, stop the array, re-assign both and start the array to begin the parity sync.
-
That means parity isn't valid, if it's not it would be faster to sync it instead of doing a correcting check. Stop the array, click on that disk and change the filesystem to "encrypted-xfs", then start the array and format it (any data on data disk will be deleted).
-
They won't be if "parity is already valid" is checked, though you still get the warning. You can leave as auto, it should auto-detect.
-
Ooh, and since they are encrypted it will ask for a new encrypton key, just enter the current one twice.
-
You can do a new config: -Tools -> New Config -> Retain current configuration: All -> Apply You'll need to reassign disks 8 and 9, check "parity is already valid" and start the array, then run a parity check.
-
Can’t access GUI remotely after upgrade
JorgeB replied to cambriancatalyst's topic in General Support
We don't have an organization , we are just users, thanks are enough. -
Yes, they ruin on the background, but avoid heavy i/o or they will take much longer.
-
Being detected and mounting are different things, see if they mount outside the array, unassign both disks, start the array, and see if they with UD plugin.
-
That's never good if there wasn't any unclean shutdown, but if the second check didn't find more errors not much else you can do now, see if future checks find more.
-
Run also the controller benchmark and post the results, make sure the screenshot shows the link speed.
-
Network related crash, simply your LAN config as much as possible.
