trurl

Disk7 still unmountable. Might be worthwhile to upgrade Unraid since xfs_progs has been updated since your version.

Why do they have multiple partitions?

Yes, but no need to backup docker.img in system, since it is easily restored by reinstalling from Previous Apps.

Cache wouldn't be involved in this anyway since the destination is an array disk. Caching only applies to user shares.

Are you unmounting the Unassigned Devices before powering them down?

How are you getting these screenshots if your server can't be reached on the network?

Post new diagnostics with the array started in normal mode.

Backup to the Unassigned Devices. Docker appdata plus whatever of your other files are important and irreplaceable. Mirror or parity is never a substitute for backups. If the only way you can attach the second 2TB SSD is USB, I wouldn't do it. SATA + USB as mirror doesn't seem like a good idea. An alternative configuration would be 1TB SSD on SATA as ZFS pool, and experiment with 2x2TB ZFS pool on USB. USB not recommended for assigned disks for many reasons, but some are successful with it depending on specific hardware.

Attach Diagnostics ZIP to your NEXT post in this thread.

Are these smaller drives new or just something you already have?

Put the 2TB as a ZFS pool, nvme fine as is. Leave out the others and USB, except perhaps as Unassigned Devices. If you eventually need more capacity you can make a real HDD array on different hardware.

Do it again without -n

Will it boot in SAFE mode?

Go to Docker page, click Container Size button at bottom, post the result.

Lots of security updates since your version, as well as new features. I always recommend latest stable release. But that can wait. Check filesystem on disk7

Your go file appears to be empty, even though it seems to be the correct size. Put the stock go file in your config folder.

Attach Diagnostics ZIP to your NEXT post in this thread.

You have a custom go file which includes things from Unraid v5. Replace with the stock go file

You can have a single drive, but you won't have any redundancy until you have at least 2 drives. Normally, HDDs go in the Unraid array, with one disk as parity. Lots more detailed information in the Unraid Docs linked at the top of the page. Or just ask here if you have some specific questions.

Do this.

Sorry, it was disk9 that was being emulated, and it is mountable.

We usually tell you to use the webUI to check filesystem, and you can do the repair there as well, but I'm not sure how much of the current methods applies to your old Unraid version, so I have been letting you do the command line. And you seemed to be doing it right the first time Have you always specified the md device when you did xfs_repair? Using the sd device will invalidate parity when used on an array disk.

Now emulated disk7 is unmountable again. Probably something with another disk causing emulation problems. Your syslog is extremely cluttered due to the connections to the known bad disks. ST2000DM001_Z560842G-20260626-1531 (sde) ST3000DM001_W1F2GS5R-20260626-1531 (sdb)Shutdown, unplug these disks, reboot, start the array in normal mode, and post new diagnostics.

Restart in normal mode and post new diagnostics

Sorry, I didn't notice that you didn't actually let it repair disks 7 and 8. You have to do it without -n