JorgeB

You should contact @SpencerJ

Procedure appears to have been correctly done but don't see a valid filesystem on disk4, this likely means parity wasn't valid, at least not 100% valid, still try running xfs_repair on the disk, maybe it will find a backup superblock.

I would repair the fs first since that should be quick and make data on that disk available now, then rebuild, but either way you do it shouldn't be more or less risky.

Yes, they should work now.

Tested also at work with different computers and it does appear to be fixed, but it was recent, v6.9-beta1 still has the issue, you get an i/o error about once every 10 times but just retry and it happily continues to copy the corrupt file. Also, have some doubts if this was really fixed or is just pure luck that it works correctly currently, I can't find any reference to this bug, when I google the only result I get is my original report here in the forum, but maybe I'm using the wrong keywords, not even sure this was a btrfs issue or Samba, I would assume Samba.

Yes, I was referring to the docker image path, though it can also be easily recreated.

All expect the disk assignments, everything else will use the defaults. You also need to copy the templates from the flash drive and configure the docker paths to be the same as they were, if not using default ones.

It's not that healthy, in fact it appears to be failing, you can confirm by running an extended SMART test. You can do that now. Any LSI with a SAS2008/2308/3008/3408 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, 9400-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed.

Try booting in safe mode, if that doesn't help you recretae the flash drive and restore only super.dat (disk assignments) and you key, if that helps then re-add the other config files a few at a time or just reconfigure the server.

You added the old disk as a new disk, the easiest way now would be to get another disk to replace the disable drive.

Try setting the DNS servers manually, or reset lan config by deleting/renaming network.cfg and network-rules.cfg (if it exists) both on the config folder of your flash.

A few sync errors are normal, even expected after an unclean shutdown, just correct them.

Please use the existing support thread:

Default ISO storage path is invalid, go to Settings -> VM Manager and set a valid path.

Disk7 looks healthy, but don't do a parity check and attempt to move data at the same time, do one or the other first.

I can only see that they are logged as "medium errors", aka bad sectors, but these can sometimes be intermittent.

Give it another chance but anymore errors recommend replacing.

No.

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

Please post the diagnostics: Tools -> Diagnostics

Cache floor is still too high, it's at 8.5TB.

It changes the power saving mode, on desktops hard drives usually there's not much difference, laptop drives will usually park heads sooner, or even go to sleep.

Should be OK, type "mover stop" on the console.

This will only work if parity is still valid, follow the instructions below carefully and ask if there's any doubt. -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, including old disk4 -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 4 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), disk4 will start rebuilding, disk should mount immediately but if it's unmountable don't format, wait for the rebuild to finish (or cancel it) and then run a filesystem check.

Cache floor is set to 9TB, also make sure shares you want to move have the correct settings: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=537383