JorgeB

Yes, looks like an issue with the HBA: Apr 20 18:34:05 NAS-NG kernel: mpt2sas_cm0: fault_state(0x2622)! Apr 20 18:34:05 NAS-NG kernel: mpt2sas_cm0: sending diag reset !! Apr 20 18:34:06 NAS-NG kernel: mpt2sas_cm0: diag reset: SUCCESS Have you tried not sleeping the server? Not every hardware supports sleep/wake up correctly.

If there's no data there you can just format, it there is run a filesystem check.

Yep. It's possible.

it's

I just check the total TBW once a month or so to see if it's increasing normally.

This is part of the board, it's the IPMI function, it allows accessing the server over LAN without a keyboard/monitor, and not the reason the board is not posting, try clearing CMOS, reinserting the CPU/RAM, etc, if it still doesn't post you need to do an RMA.

Diags are after rebooting so we can't see what happened, disk looks mostly OK, but there are already some ATA errors on multiple devices: Apr 21 17:09:52 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) Apr 21 17:09:52 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Apr 21 17:09:55 Tower kernel: ata3: link is slow to respond, please be patient (ready=0) Apr 21 17:09:56 Tower kernel: ata1: COMRESET failed (errno=-16) Apr 21 17:09:56 Tower kernel: ata4: COMRESET failed (errno=-16) Apr 21 17:09:59 Tower kernel: ata3: COMRESET failed (errno=-16) This is the Intel SCU controller, which is not as rock solid as the normal one, the other 6 ports, could also be a power/connection problem.

There would have been a "all data on this device will be delete at array start" waring after the device, you just needed to stop/start array, or worst case reboot to be able to change the cache slots again.

The number of writes in the GUI is basically meaningless, it varies with the devices, what matters are the TBW, and that is fine, only a few GB were written.

Thanks, happy to report it is fixed.

Yes.

New config will never reset encryption key, that is stored on the devices, you need to re-format them.

Since you started another thread please continue discussion there: https://forums.unraid.net/topic/106667-so-my-nas-that-was-running-unraid-suddenly-has-been-reinfected-with-asmb6-ikvm-anyone-have-a-suggestion/

That is the IPMI function, you can read the manual to find out how it works, and please stop starting multiple threads for the same issue, continue discussion below.

See if you can clone it with ddrescue.

That one is supported by Unraid, diags might show the problem.

Syslog is still full of call traces, this can be a hardware issue or your hardware doesn't get along with current Linux kernel.

Diags are after rebooting so we can't see what happened, but disk looks fine and since it's mounting you can rebuild on top, before doing it you may want to replace/swap cables just to rule them out if it happens again to the same disk.

You can find which ones are the data drives by mounting them with UD, use read only mode to keep parity 100% valid, did you have single or dual parity?

You need to check filesystem on disk6, but there are a lot of other traces, and I have no idea what those are about.

Do you mean it's not posting? That would be a hardware issue and unrelated to Unraid.

Thanks for this, lost passwordless ssh due to some permission issue, and since it happened right after installing the plugin I suspected it was the problem, just tested now on another server and it happened again, this was the error logged: Apr 20 18:27:30 Tower15 sshd[15259]: Authentication refused: bad ownership or modes for directory / Rebooting solves the problem it but it should be fixed in the plugin install, I can't really help with what's needed to fix it but @Squidshould be able to help you if needed.

Apr 16 02:31:15 UnRAID kernel: md: disk4 write error, sector=5920974112 Apr 16 02:31:15 UnRAID kernel: md: disk3 read error, sector=5920976928 Apr 16 02:31:15 UnRAID kernel: md: disk0 read error, sector=5920976936 Multiple disk errors suggest a controller/power problem, since the controller is Intel I would start with power.

See here first: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=972660

Those are not correct, you can see them on the SMART report: Data Units Written: 114,252,166 [58.4 TB] and Data Units Written: 114,251,764 [58.4 TB]