JorgeB
-
Posts
67,386 -
Joined
-
Last visited
-
Days Won
705
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
I mentioned running out of memory, not memory errors, but these last diags don't have that and still there's the same error: Jan 29 00:31:46 Tower shfs: shfs: ../lib/fuse.c:1450: unlink_node: Assertion `node->nlookup > 1' failed. I have no idea what this error means, don't remember seeing it before, maybe @limetechknows what this is about?
-
OK, in that case suggest swapping both cables (or slot) with another disk to rule that out and then re-sync parity.
-
Please create a bug report for this.
-
That's what happens by default, vdisks are created sparse.
-
You can use: cp --sparse=always /path/to/source /path/to/dest
-
This. Also still a good idea to run memtest.
-
It wouldn't assuming the problem happens with the array stopped, if not you'd need to re-assign the drives same as they were, still wouldn't affect your data, as long as you don't assign a data drive as parity.
-
There's no risk in doing a new config, unless you assign a data disk as parity, and it's even more safe lately with the keep assignments option. You could do a new config, re-order data drives as you wish, unassign parity2, check parity is already valid before starting the array and it would be protected since start, then after starting the array at least one time re-add parity2 and sync it.
-
No, I didn't even noticed that, I'm saying to try a new config, i..e, another flash with stock Unraid, to make sure it's not a config issue.
-
Pool is full of checksum errors, you need to backup anything important and reformat, there are some recovery options here if needed. So many errors suggest a hardware problem, btrfs doesn't do well with RAM issues, it would be a good idea to run memtest, also make sure RAM isn't overclocked, respect max speed depending on config:
-
And if you use a new empty flash drive? Can be with a trial key.
-
That is just for the cache pool, but if you're using single parity you can move drives around after doing a new config while keeping parity valid.
-
[6.8.0] Unraid crashing/freezing under systained network reads
JorgeB replied to ShinseiTom's topic in General Support
That's a flash drive problem, run chkdsk, if more issues it could be failing, also make you're using a USB 2.0 port. -
Please post the diagnostics: Tools -> Diagnostics
-
The disk looks fine but the emulated disk is showing empty, is that expected or did you format it?
-
Please post the diagnostics: Tools -> Diagnostics
-
Have you tried booting in safe mode?
-
Currently there are more 199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 1238 So likely there's still a problem, swap ports with another disk and see if errors stop increasing.
-
Best to post in the Unbalance support thread.
-
It is now, it was hidden.
-
I meant cache="only"
-
For SSDs the 9300-8i or 9400-8i would be best.
-
Except with SSDs they will all perform similarly, so I would recommend going for a 9211-8i or 9207-8i.
-
You can enable "prefer" and then run the mover (docker and VM services need to be stopped first), once the mover finishes you can change to cache="no", but it can also be left as "prefer", enable GUI help for a detailed explanations of the differences.
-
They can usually be found on ebay for a reasonable price, look for one that specifies IT mode, e.g. this one is considered a reputable seller, and in that case it's plug'n play. If your server has swappable bays, then yes, but it would be best to swap to bays that don't use the same mini SAS cable, one cable connects to 4 bays.
