-
(Solved) Routing Table Persistence (Lack Of)
How can this be marked "Solved"? The solution here is one of: Changes via the GUI are persisted A very big notice on the Network settings page saying "Changes to the routing table will not persist across reboots.".
-
Parity sync with all new drives – why slow?
Ok, something's clearly wrong on my side. I pulled out one of the disks (disk2) and waited for a while and plugged it back in. While the disk was out the parity sync speed went way up (~120Mb/s, so ~10x faster) and it kept going at a decent pace when I plugged the disk back in. I ordered a new SFF-8088 cable to see if that makes any difference for the error rate. Tyvm for the help so far.
-
Parity sync with all new drives – why slow?
Here goes, thank you. minispalm-ur-diagnostics-20240516-0859.zip
-
dvdplm started following Parity sync with all new drives – why slow?
-
Parity sync with all new drives – why slow?
I think zeroing 16Tb can happen faster than 13 days. So the answer here is: it’s a user error and I should have known to create and format the data drives first and then the parity sync would have done the right thing? I have to say I’m underwhelmed by the user friendliness of Unraid. Why not provide a happy path wizard for new arrays? Or at least write down the recommended steps. This way I’m spending half of my trial period waiting for a sync that isn’t needed.
-
Parity sync with all new drives – why slow?
First time unraid user here. I have a 4-disk array configured with 1 parity drive and 3 data drives. All drives are new. Why is the parity sync slow? Surely the system knows the drives are all empty (they aren't even formatted yet, so clearly there's no data). Is there a way to manually override the default and just say "it's all good, the parity drive should just be zeroed"?
dvdplm
Members
-
Joined
-
Last visited