trurl

If you disable Docker in Settings can you start the array?

Each parity disk must be at least as large as any single data disk. So, you can't have a 4TB parity disk with a 16TB data disk.

Personally, I don't think you have enough disks to warrant dual parity.

Delete the .cfg file for that share, then configure it again from the webUI.

Linux is case sensitive, so make sure you don't have a docker or something else configured to reference it with the wrong case.

You either rebuild the disabled disk, or New Config and rebuild parity. Those are the only ways to get the array in sync again.

The disk was disabled because a write to it failed. That write, and any subsequent writes to the emulated disk, can be recovered by rebuilding the disk. If instead, you rebuild parity, those writes would be lost.

So, rebuilding the disabled disk is preferred over rebuilding parity.

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-819173

Your df screenshot seems to indicate you don't have any mounted storage.

Attach Diagnostics ZIP to your NEXT post in this thread.

I don't have anything to add that I haven't already said above.

Yes, apcupsd is shutting the system down after power loss.

You are using your UPS incorrectly though.

The purpose of UPS isn't to allow you to run on battery. The purpose of UPS is to allow clean shutdown when power is lost.

UPS should allow system to keep running during very brief loss of power, but shutdown if power loss is not very brief.

You should set "Time on battery before shutdown". 120 seconds or even less.

You mentioned the number of bays but not the number of drives. With 16 drives you should consider dual parity.

Unraid keeps track of disk assignments by drive serial number, assuming the controller passes that information. RAID controllers or USB may not.

If you want to reassign a data disk as a parity disk you will have to copy the data from it.

Then New Config will let you assign any drives as you wish and build parity on any drives assigned to parity slots.

Looks like you decided to deviate from the "standard" way to setup docker.
DOCKER_IMAGE_FILE="/mnt/dockerapps/docker.img" DOCKER_APP_CONFIG_PATH="/mnt/dockerapps/"This means your docker.img is not actually in any user share since it is at the top level of the pool. And it means that if you don't specify "appdata" or some other user share, the appdata path for a new container may default to the top level of that pool also, which might mean a new container would create a new user share for its appdata.

That is not sufficient. You must disable Docker in Settings before you try to work with these files.

The warnings are about moving/copying between array (or pool ) and user shares. This is because Linux doesn't know that user shares are just another view of the disks and pools, and so it might try to overwrite what it is trying to read.

MC or Krusader could let you make this mistake. The built-in file manager won't let you make this mistake.

Also, Unassigned Devices are not part of the array, pools, or user shares, so not affected by this at all.

The initial burst of speed is due to ram buffering. The slower speed you experienced is typical of array writes, since parity is updated at the same time. Turbo mode might help. See here for more about how array writes are done:
https://docs.unraid.net/unraid-os/manual/storage-management/#array-write-modes

Default for pool is btrfs raid1, which is a mirror with total size equal to the smallest drive. If you want to use the total combined size of the drives you must switch the pool to single mode.

Parity doesn't mount since it has no filesystem. If it shows as an option to assign and stays assigned that is what you want.

/dev, like all Unraid OS folders, is in RAM, and so doesn't persist.

You can use the User Scripts plugin to run a script to reapply this change after boot.

Default is mirror so that looks OK if that is what you want. Mirror size is displayed on the first line of the pool.

Normal.

Filesystem overhead.

If you start in maintenance mode, no disks are mounted, so no shares or anything else is accessible.

Start in normal (not maintenance) mode and post new diagnostics.

All disks are involved in parity sync. Possibly a power problem?

Be sure you don't run New Permissions on appdata.



Edit settings.json in your transmission appdata and set the umask to 000

correct

Test again without Mover Tuning plugin.
 
You can go directly to the correct support page for any of your plugins by clicking its Support link on the Plugins page of your Unraid webUI.

Assuming you haven't done anything including rebooting since those diagnostics:
 
Original BAD disk1 is the source disk, sdg
New destination disk is sdc
 
So the command is
ddrescue -f /dev/sdg /dev/sdc /boot/ddrescue.log  
 

delete or rename config/network.cfg and it will use default (DHCP)