JorgeB
-
Posts
67,504 -
Joined
-
Last visited
-
Days Won
707
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
No, but you don't even need to do them for a failed disk, just if you don't have enough ports to have both connected, you also don't need to start the array with the disk unassigned, just stop array, assign new disk, start array.
-
UNRAID showing wrong data utilization in webui for cache pool
JorgeB commented on r3dlobst3r's report in Prereleases
Known issue, should be fixed on next release, more info here. -
Best bet for disk8 is to check if the actual disk is mounting with UD, same as you did before with another disk, if yes just do a new config and re-sync parity (ideally after finding out whatever is causing the read errors, or at least try doing it with a different PSU, controller or cables).
-
I don't like to assume anything.
-
If it's using the same NIC yes.
-
There are Xeon CPUs with a GPU, models ending in G.
-
8th/9th gen requires a different chipset, same as desktop boards, e.g https://www.supermicro.com/en/products/motherboard/X11SCH-F. But still no i5/i7 since those don't support ECC.
-
It can. Those boards don't support i5/i7, you need a Xeon E3 v5/v6
-
Changed Status to Closed Changed Priority to Other
-
This looks like a general support issue, copied the report to the general support forum, please continue discussion there, if it turns out it really is a bug we can re-open this.
-
Parity in Unraid is real-time, regardless of using disk or user shares, just make sure you don't copy from user shares to disk shares or vice-versa.
-
This suggests otherwise:
-
There's also corruption in the cache filesystem, backup any data on cache then re-format, restore data and recreate docker image again. P.S. Ryzen with overclocked RAM is known to corrupt data in some cases, btrfs is very sensitive to RAM errors, see here for more info.
-
That's how it normally is before anything breaks, any hardware can go wrong at any time, though in that case LSI firmware update is unlikely to help, but it also won't hurt.
-
Much better, but still some fluctuation in the beginning.
-
Probably the best, you could also do it in place then delete the old one but might not have enough space.
-
If you have one try with a different NIC, ideally one from Intel.
-
VM page unresponsive but VMs kept working and possible gpu passthrough issue
JorgeB commented on RichMD's report in Prereleases
Changed Priority to Other -
One thing you can try now is to update LSI to latest firmware: mpt2sas_cm1: LSISAS2116: FWVersion(17.00.01.00) Current one is 20.00.07.00
-
I'm not saying it's the PSU, I'm saying there's a hardware problem and until you fix it you'll continue to have troubles, it could be a cable, it could be the controller, it could be power, etc, very difficult to diagnose remotely or without start swapping some hardware around.
-
That why I mentioned earlier:
-
Try swapping both cables with another disk (so that this disk starts using a different SATA port) and post new diags if it still happens. FYI these disks as SMR, just in case you notice write performance isn't as good as expected.
-
Then it's likely a bad disk.
-
Yes, if you assign static IP addresses.
-
That's low, with gigabit you should easily get line speed, or very close to that, try differente NICs/cables/switch
