JorgeB

Cache filesystem is corrupt and needs to be re-done, you also need to check filesystem on disk4, but these are likely a consequence of all the crashing, not the reason for it, after it's fixed you can enable the syslog server/mirror feature to see if it catches something, but if the problem is hardware related it likely won't.

SMART report is incomplete due to a likely bug with smatmoontools, not sure if the new beta uses a newer version, you could try that.

Not on the syslog, there might be if you post the complete diagnostics instead.

Logs are after rebooting so not much help, you can try this but if it's a hardware issue there might not be anything logged when it crashes.

Did it also crash with the old hardware?

Macvlan call traces are usually caused by having dockers with a custom IP address:

Best bet for that is to start a new thread on the KVM forum, don't forget to include the diagnostics.

Again this is a general support issue, but looking at the diags you have something crashing Samba: Jun 23 13:24:07 KNORRHANE kernel: traps: smbd[19654] general protection ip:149efb96af94 sp:7fff9501b5e0 error:0 in ld-2.30.so[149efb95f000+20000] Jun 23 13:24:07 KNORRHANE root: /etc/rc.d/rc.samba: line 12: 19654 Segmentation fault /usr/sbin/smbd -D Start by booting in safe mode, and if you need more help please start a thread in the general support forum.

Again this is a general support issue, but looking at the diags you have something crashing Samba: Jun 23 13:24:07 KNORRHANE kernel: traps: smbd[19654] general protection ip:149efb96af94 sp:7fff9501b5e0 error:0 in ld-2.30.so[149efb95f000+20000] Jun 23 13:24:07 KNORRHANE root: /etc/rc.d/rc.samba: line 12: 19654 Segmentation fault /usr/sbin/smbd -D Start by booting in safe mode, and if you need more help please start a thread in the general support forum.

Changed Status to Closed Changed Priority to Other

This is a general support issue, please start by looking at this thread, there is no one-size-fits-all solution but there are several thing you can try:

This is a general support issue, please start by looking at this thread, there is no one-size-fits-all solution but there are several thing you can try:

👍

It's saved on the SMART report, I didn't look for it, disk is fine for now, I would keep using it, but any more read errors in the near future consider replacing.

Try booting in safe mode and if it still crashes setup the syslog server/mirror and post that after a crash.

NVMe devices can easily get to 70C or close to that during heavy writes, but you should really avoid preclearing flash based devices.

You can post on the beta release thread mentioning that your NIC isn't working, don't forget to add the diags.

Both the docker and VM service appear to be starting correctly. Do you really mean the VM settings or the VM page?

Except for the VM config the rest should be plug'n'play

Though part of the SMART report is missing it appears to be a Seagate, so those large values for error rate are normal. The reported uncorretable errors while never a good sign can be intermittent, you should run an extended SMART test.

Boot using the GUI mode.

Done, but it could be useful to others if you post how you solved it.

This means there was a read error, you can try ddrescue as it will skip them while trying to get as much data as possible, still if there are errors there could always be some corruption on the rebuilt disk, unless by luck the problem sector(s) correspond to empty space there.

Well, it appears I was wrong, it does look like a driver issue, you might need to wait for an upcoming release to use that NIC, best bet for now would be an ad-don NIC.

This will only work if the copy was completed. This assumes you're running a recent version of Unraid, it might not work on very old releases, it works on any release newer than v6.2, it also assumes you have single parity, if you have dual parity the command is different (remove the 29) -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, make sure new parity is assigned to the parity slot and old parity assigned to the disk to be rebuilt -Important - After checking the assignments leave the browser on that page, the "Main" page. -Open an SSH session/use the console and type (don't copy/paste directly from the forum, as sometimes it can insert extra characters): mdcmd set invalidslot # 29 Replace # with the disk number you want to rebuild, i.e. to rebuild disk3 it would be: mdcmd set invalidslot 3 29 -Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box (GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the invalid slot command, but they won't be as long as the procedure was correctly done), disk# will start rebuilding, disk should mount immediately but if it's unmountable don't format, wait for the rebuild to finish and then run a filesystem check