-
Posts
61336 -
Joined
-
Last visited
-
Days Won
642
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by JorgeB
-
-
20 minutes ago, chybber said:
So I did run xfs_repair -v /dev/sdj (disk3)
That won't work, abort and run it again using the GUI, but without -n.
-
Try a different flash drive, just to test, no key needed, also look for a BIOS update.
-
41 minutes ago, jedimastergrant said:
Could this be an issue?
Possibly, could still be a RAM issue since memtest is only definitive if it finds errors, since you have multiple sticks try with just one, if the same try with a different one, that will basically rule out bad RAM.
-
40 minutes ago, sannitig said:
I need to run the format?
Yes.
-
Try running another filesystem check, that still looks like a filesystem problem to me, if it doesn't help, I would backup and re-format that disk, to make sure the issue is resolved.
-
This is a new array disk right? New disks added to the array need to be formatted before use, next to array stop button.
-
Run a correcting scrub on the pool and post the results.
P.S. you should change the docker network to ipvlan, since there are macvlan call traces.
-
Unfortunately there's nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
-
You just needed to check the "I'm sure" box, next to the array start button.
-
1
-
-
Not surprisingly there's nothing relevant logged, also suggesting a hardware issue.
-
15 minutes ago, Leonderi said:
taken after a its rebooted itself.
Server rebooting on its own it's almost always a hardware issue, but enable the syslog server and post that after a crash in case there's something logged.
-
26 minutes ago, RobF285 said:
2. Open Tools then New Config
You didn't need to do a new config, just what I've posted above, but that will also work.
-
Let the rebuild finish.
-
Make sure the emulated disk is mounting and contents look correct before rebuilding on top.
-
You cannot have a new parity a a new disk at the same time, what was the original array state? If there's no data to recover do a new config
-
Just rebooting should not cause issues, enable mover mover logging, run the mover, post the diagnostics.
-
Please use the existing plugin support thread:
-
19 minutes ago, kcossabo said:
not list a single DIMM as valid. I will try that though.
It will work with a single DIMM, at least it should.
-
Stop the array
unassign parity
start array
stop array
re-assign parity
start array
-
1
-
-
poll cfg is still showing as a mirror, try this:
unassign all pool devices
start array
stop array
assign only the old device
start array
stop array
now assign the new device together with the old one
start array
If this doesn't work post the output of
zpool import -
3 minutes ago, KillerK said:
I tried reducing the low critical threshold below 420 but I get an error on the values I enter.
Usually it won't accept any value, try 300, or 150.
-
If you are using a different flash drive the license needs to be transferred, you can do that yourself or contact support and have them do it.
-
Looks like it needs this module:
https://cateee.net/lkddb/web-lkddb/QEDE.html
I've asked LT to add it, hopefully for the next release.
-
24 minutes ago, UNRA1DUser said:
Is that the normal boot behavior with "Not automatically fixing this" and this big block of numbers ?
It does appear to happen with some flash drives, I see it with one of mine.
BTRFS issues
in General Support
Posted
Look in syslog for a list of corrupt file(s), those should be deleted/restored from a backup, then re-run a scrub to confirm there aren't any more errors.