JorgeB
-
Posts
67,459 -
Joined
-
Last visited
-
Days Won
706
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
Please post the diagnostics: Tools -> Diagnostics
-
It's logged at boot time as Unclean shutdown detetced But will not disappear after after a clean reboot
-
Other then the schedule one a parity check is done after any unclean shutdown.
-
Also, if this keeps growing in the future you might want to consider replacing it.
-
SMART test passed so at least for now disk is OK.
-
If the data on the emulated drive isn't available possibly there's a filesystem problem, and rebuilding won't help, if you still need help please post the diagnostics: Tools -> Diagnostics -
Yes, that was one of my suspicions, hence why I asked for the diags, since not sure the LSI BIOS would detect a 520b sector device.
-
Memtest isn't 100% reliable finding errors, only when if does find some you can be sure there are problems, not finding doesn't mean you can rule out bad RAM.
-
Sorry, don't understand the question.
-
Very unlikely the SSD is the problem for this, also don't forget you have corruption on the array disks, first candidate would be RAM, followed by the board or controller.
-
I forgot to mention that for SAS devices you need to run the tests manually: smartctl -t long /dev/sdX
-
Disk9 needs a filesystem check, but that's likely a result of the previous crashes, not what caused them, since the syslog doesn't survive a reboot best bet to catch the reason why it's crashing (if it's not a hardware issue) is by enabling the syslog server/mirror.
-
It appears dockers were stopped for the CA backup and never started back up, @Squidmight have an idea why?
-
Having issues with Docker - any idea what this error in the log means?
JorgeB replied to HALPtech's topic in General Support
Please post the diagnostics: Tools -> Diagnostics -
Do you her the drives spinning up? If yes post the Unraid diags.
-
A full disk write might fix it for now, but once a disk has issues it's more likely to have more in the near future.
-
You need to find out what's corrupting the data, or else you fix one file and you get more errors an a new one.
-
Locked since OP already re-posted on the plugin support thread.
-
Please use the existing plugin support thread:
-
SMART test failed so that drive needs to be replaced.
-
Just do a regular copy, you can use for example midnight commander (mc on the console), not sure all data will be available since it was a raid0 pool, copy what you can.
-
-
That's normal, parity swap procedure needs to be done from start to finish without any assignment changes, if there are any after the copy (or a reboot) it will be reset and you need to start over.
-
There's filesystem corruption on cache, best bet it to backup, re-format and restore any data there.
-
That doesn't make much sense, if a file starts writing to cache it will finish writing to cache, or give an error, it can't change to the array mid-write, it can if there are several files.
