trurl

If you want to keep the data. So the files on both of those disks would not fit on just one of them. Some would have to go to free space on other disks. More information might suggest more specific ideas. Attach diagnostics to your NEXT post in this thread.

Disk2 disconnected (as sdh) and reconnected as Unassigned Device (sdr). Syslogs flooded with those errors you posted so can't see much else, including what disk should have been Disk5. Doesn't look like it is showing up at all. Both emulated disks seem mountable, but looks like emulated disk5 may be empty. Did you format? Looks like you are trying to use USB for many of these. USB connections are NOT recommended for assigned disks for many reasons, including the disconnects you are getting. I doubt you will be able to get this many disks as a stable array as long as you are using USB.

Attach Diagnostics to your NEXT post in this thread.

Attach Diagnostics to your NEXT post in this thread

The config folder from your backup is all you need to get going again with your configuration on a new install. If you can reformat the original flash and use it you won't have to do the license transfer to a new flash

What OS?

But you don't want to use that USB disk1 for your purposes. In your diagnostics you had not yet created pools for your nvme and SSD. That is where you want your dockers/VMs. Post new diagnostics

Each of the fields in your screenshots has a label to the left that you have not included in any of your screenshots.

The quote wasn't from my post. So you mean that your comment was about the Media share and the downloads_cache pool? The Media share isn't set to use any pool.

You can't What do you get from command line with this? ls -lah /mnt/user/Personal\ and\ Backups/Backups

What happens if you boot in SAFE mode?

You don't specify what "that" refers to. The text you quoted discusses 4 different shares. Also, your screenshots are very difficult to work with since the don't show any labels.

Still seeing the same in these except FCP hadn't done its scan yet. Check Filesystem on disk1. Post the output.

Looks like you have an FSCK file on flash. That file happens when a file is corrupt. Whatever can be guessed about its contents gets put into FSCK. Was that file also on your backup? Reboot and see if syslog works. If not, maybe something important got corrupted on flash. Your config folder from your backup is all you need to get your configuration on a new install. Maybe you already know since you changed flash drives.

Do you have a current flash backup?

Do you have a current flash backup?

Possibly since it couldn't become disabled, it became corrupted instead.

Already included in diagnostics. Mar 21 15:12:32 Tower kernel: sd 1:0:6:0: [sdg] tag#545 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=0s Mar 21 15:12:32 Tower kernel: sd 1:0:6:0: [sdg] tag#545 Sense Key : 0xb [current] Mar 21 15:12:32 Tower kernel: sd 1:0:6:0: [sdg] tag#545 ASC=0x0 ASCQ=0x0 Mar 21 15:12:32 Tower kernel: sd 1:0:6:0: [sdg] tag#545 CDB: opcode=0x2a 2a 08 3a 38 37 30 00 00 08 00 Mar 21 15:12:32 Tower kernel: I/O error, dev sdg, sector 976762672 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 2 Mar 21 15:12:32 Tower kernel: md: disk1 write error, sector=976762608 Mar 21 15:12:32 Tower kernel: XFS (md1p1): log I/O error -5 Mar 21 15:12:32 Tower kernel: XFS (md1p1): Filesystem has been shut down due to log error (0x2). Mar 21 15:12:32 Tower kernel: XFS (md1p1): Please unmount the filesystem and rectify the problem(s). This would have disabled disk1 if you had parity. Possibly it is unmountable now. Mar 21 15:24:37 Tower root: Fix Common Problems: Error: disk1 (ST1000LM010-9YH146_Z1008ZGE) has read errors ** Ignored Mar 21 15:24:46 Tower root: Failed to write /mnt/disk1/33297349.tmp Mar 21 15:24:46 Tower root: Fix Common Problems: Error: Unable to write to disk1 Seems it is at least readonly. Why would you set FCP to ignore read errors??? Reboot and post new diagnostics.

Most recent diagnostics shows those OK.

If you want to restrict a share so it only goes to a few disks, Include is the right idea. If you want to restrict a share so it doesn't go to a few disks, Exclude is the right idea. Never use Include and Exclude together. Looks like you tried to include a lot of disks you no longer have. Better to Include All instead of specific disks that might not exist.

Is that why you are using docker folder instead of docker.img? You shouldn't need to access anything within docker.img. Try recreating (as 20G image, not folder) and reinstalling https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file But before that, your domains and system shares have files on the array. Ideally, appdata, domains, and system shares would have all files on fast pool such as cache, with nothing on the array, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open. Nothing can move or delete open files, so you will have to disable Docker and VM Manager in Settings before you can work with these. Since you have Dynamix File Manager plugin might be simpler to clean this up yourself instead of trying to reconfigure so Mover will take care of it, and Mover won't replace files anyway so if there are duplicates you will have to decide which to keep.

Attach Diagnostics to your NEXT post in this thread.

yes

Do you have any client computer with a mapped drive to that share?