JorgeB

👍

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

Connections on disk5, shutdown the server, check connections even if it's just removing and re-connecting the cables, power back on and post new diags, disk is still offline on the diags posted.

Unraid has the driver, though IIRC it's not working correctly on v6.8, it should work on v6.9-beta22, please post diags from the beta.

Parity swap procedure needs to be done from start to finish, any other step/interruption will make it stat over, if you're absolutely sure the parity copy completed you could use the invalid slot command, but I would advise just starting over, also 30+ hours is a lot, unless the parity is very large.

Shutting should be perfectly safe. No point, server has two invalid disks that can't be emulated by the single parity.

You're welcome, like mentioned not all SSDs (in fact most of them) are able to sustain 500MB/s writes, 800MB/s means you now have an NVMe device, which is generally considerably faster, though like all devices some models are faster than others.

If it's not that it's likely a problem with the disk.

Thanks for write up, and if you don't mind going to mark this as solved.

You have a lot of stuff (everything?) in the nerdapck plugin installed, make sure you only install what is needed, and of those and IIRC atop is known to fill the log.

Reboot.

All errors appear to have been correct by the scrub, still good to run a second one to confirm, if no more errors filesystem is good now. Correct.

Couple of unrelated observations: -trim is running every hour, that overkill IMHO, once a day is usually what we recommend -CPU is overheating and throttling down, check cooling Jun 20 20:09:11 TazServer kernel: CPU14: Package temperature above threshold, cpu clock throttled (total events = 1) Jun 20 20:09:11 TazServer kernel: CPU15: Package temperature above threshold, cpu clock throttled (total events = 1) Jun 20 20:09:11 TazServer kernel: CPU7: Package temperature above threshold, cpu clock throttled (total events = 1) Jun 20 20:09:11 TazServer kernel: CPU4: Package temperature above threshold, cpu clock throttled (total events = 1) The device error is cause by an unassigned NTFS disk that possibly isn't even no longer connected: Jun 20 20:30:42 TazServer ntfs-3g[12382]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Jun 20 20:30:42 TazServer ntfs-3g[12382]: Failed to read index block: Input/output error Jun 20 20:30:42 TazServer kernel: Buffer I/O error on dev sdh2, logical block 9852661, async page read Run chkdsk on that disk before using it again.