MowMdown

You can install a handful at a time, say do 5 plugins, and wait, if anything happens start removing them 1 by one, if nothing happens install another 5 and repeat.

Disk2 is having read errors, if the screenshot is disk2, you should consider replacing it. It does appear you have a parity disk so as long as it's in sync, you wont lose any data unless a 2nd disk has issues.

The sign to watch for is if those numbers for reallocated and uncorrectable continue to increase, if they do, the disk is going to die soon. If the numbers stabilize where they are, you can continue to get more life out of it BUT i would suggest having another disk ready to replace it. It could last a few days, weeks, months or just die later today.

To answer your question, no, unraid licenses cannot be transferred.

click on "disk2" and pause the scrub, you ideally do not want to run a zfs pool scrub at the same time as a parity check/sync

From what I can gather amazon does not offer a public API to manually retrieve the photos which might be why you cant seem to find anything on it.

They want you to be locked in which IMO is a terrible thing for the consumer due to having your photos being held hostage like what you described.

Any reason you don't just select "Container" as the network type and select the container you are networking too?

Add new disks to the system, mount them with the Unassigned Devices plugin.
Format disks and copy (not move) all data from array disks to the unassigned devices plugin. I would suggest using another plugin for this called "Unbalanced"
Remove all disks from array, run a new config, and assign new disks (that contain the copied data) to the disk slots.
Build parity if you are going to have parity.
I think this way might be a good approach because your old array disks will still contain data in the even you need to add them back in in-case of a new disk failure before the new parity is finished syncing.

you will need to delete the folder /mnt/cache_two and then reformat. unraid is weird and will not finish the format if the folder exists prior to the format.
(or use a different name other than "cache_two")

May 18 13:23:20 Tower emhttpd: shcmd (4096): /usr/sbin/zpool create -f -o ashift=12 -O dnodesize=auto -O acltype=posixacl -O xattr=sa -O utf8only=on -m /mnt/cache_two cache_two /dev/nvme0n1p4 May 18 13:23:20 Tower root: mountpoint '/mnt/cache_two' exists and is not empty May 18 13:23:20 Tower root: use '-m' option to provide a different default May 18 13:23:20 Tower emhttpd: shcmd (4096): exit status: 1

Yes as long as you only have Parity1 and no Parity2 (parity2 the disk order matters)

1. Stop the array.
2. Tools > New Config (perverse all slots)
3. On the MAIN page, move disk6 slot assignment to the disk3 slot
4. Check "parity is valid" and start the array.

Unless you are manually running parity checks, that setting doesn't affect scheduled parity checks. As to why it's not persistent, couldn't' tell you.

This was actually a plex issue and they very recently pushed a fix that may not yet be available to download as of this message.

If you are running a linuxserver plex container you can add the following variables to pull the specific version.



VERSION: 1.43.2.10623-07eb705bc PLEX_DOWNLOAD: https://downloads.plex.tv/plex-media-server-builds
Source: https://forums.plex.tv/t/hardware-gpu-quicksync-transcoding-broken-on-beta-1-43-1-10540/937145/118

Well the risk is losing a single drive means total loss of the pool and most people, including myself, prefer our systems remain running and functioning in the event of a drive loss.

256GB is what I consider on the low end but I dont see why it wont be usable. I ran unraid for years with only a 250GB single drive pool before switching to a RAID10 setup where I now run mirrored pairs for my pool.

As long as you have a good backup strategy, which you should have regardless of your pool configuration, and are prepared to deal with it shall a failure occur, it's your system to do as you wish with.

use lsof /mnt/disk# to see if anything is keeping it awake.

you 100% have a docker container or a plugin reading from a disk.

Yeah this thing is going to struggle with immich. Pinning to a core or two might help but If I were you I would disable all of the machine learning and video conversion settings. The CPU has an iGPU which can handle some of the tasks pretty efficently but not all of immich's tasks can utilize the iGPU and will rely on the CPU which you have very little of.

Also you need to configure immich to use the iGPU manually if you have not done so already.

mv Trial.key Trial.old Just note that the command is case-sensititve so it might be mv trial.key trial.old

So the data that is on the disk you want to remove will remain on the removed disk?

If that's the case, with the array stopped, click on TOOLS > New Config > preserve all slots and confirm you want to do this.

Back on the MAIN page, set the slots of the disk(s) you want to remove to "unassigned", start the array in maintenance mode to make it permanent and then shut the system down to remove the disks.

The data on those disks will remain.

Once you reboot you will need to re-sync parity

Jan 19 11:42:21 UNR1 kernel: XFS (md9p1): Corruption detected! Free inode 0x8a not marked free! (mode 0x41ff) Jan 19 11:42:21 UNR1 kernel: XFS (md9p1): Internal error xfs_trans_cancel at line 978 of file fs/xfs/xfs_trans.c. Caller xfs_create+0x28e/0x310 Jan 19 11:42:21 UNR1 kernel: CPU: 5 UID: 99 PID: 459364 Comm: KIO::WorkerThre Tainted: P O 6.12.54-Unraid #1 Jan 19 11:42:21 UNR1 kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE Jan 19 11:42:21 UNR1 kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D43/PRO B660M-A WIFI DDR4 (MS-7D43), BIOS 1.N1 05/13/2025 . . . . Jan 19 11:42:21 UNR1 kernel: XFS (md9p1): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0xd1/0x110 (fs/xfs/xfs_trans.c:979). Shutting down filesystem. Jan 19 11:42:21 UNR1 kernel: XFS (md9p1): Please unmount the filesystem and rectify the problem(s)Disk 9 seems to have corruption. Stop the array, put it in maintenance mode, click Disk 9 and run the xfs repair tool. Post the results.

In addition to not having a "minimum free space" configured you also have the mover tuning plugin which depending on which version you have could be broken and/or you did not disable the dry-run setting which comes enabled by default.

My suggestion is to remove this plugin altogether.

10 is 10 bytes, if you want 10GB you need to type in 10 GB

To easily roll back, there should be a "previous" folder on your USB, just copy those files from that folder back to the root of the USB and overwrite the existing ones. This will boot you back into 7.1.4.

As always, make a backup of your USB before doing anything.

The solution is to move the data over, new files should be wrote to the new storage location. Existing files being modified wont be moved regardless of what storage pool you selected in the share settings.

Stop/Disable docker service in the unraid settings. Set cache_data as the secondary storage for your system share and then set the mover action so that the arrow points to cache_system from cache_data so that it looks like cache_data -> cache_system and run mover.

Always make a backup of your appdata.
It can be extremely risky changing the docker branch and rolling back my not always be possible due to technical reasons like one way data migrations. This is why a backup of your appdata is critical.
To make the change you simply edit the docker container template, expand to advanced view, and edit (or add) the docker branch tag to the end of the repository:

In the example below the tag is the whole part after "plex" :latest so in this case latest is the tag. You will need to figure out what tag was used and append it.
You may or may not have a tag, if you don't you will need to add the semi-colon+tag. (then click update)

If the action is unsucessful or the docker run says failed, your container will be orphaned, you will need to click on the "add container" button, click on the corresponding template, and fix it and run it again.



Here is another example with a custom tag specific for this container:

You didn't enable "Host access to Custom Networks" in the unraid docker settings page.

Honestly with how strict you're trying to micromanage your share and subfolders, you're better off choosing the "Manual: Do not split directories" and then creating the directories exactly where you want them.

Otherwise with a Top level split that you have selected, you're going to end up with a Movie share on each disk and then also potentially having one of each subcategory on each disk if the fill allocation changes as you hit the highwater mark on each disk. Basically by the time highwater has cycled through each disk (lets say each disk is 50%) the 2nd round of highwater could leave you with the "Movie" share on each disk and having all of these sub folders on every disk as well: (this is kind of an extreme example but this is what it could look like at the end)

Movie (disk1,2,3,4):
720p Horror (disk1,2)
movie1 (disk1)
movie2 (disk1)
movie3 (disk2)
movie4 (disk2)
720p SciFi (disk2,3)
movie4 (disk2)
movie5 (disk2)
movie6 (disk2)
movie7 (disk3)
1080p SciFi (disk3,4)
movie8 (disk3)
movie9 (disk3)
movie10 (disk3)
movie11 (disk4)
1080p Other (disk1,2,3)
movie12 (disk1)
movie13 (disk1)
movie14 (disk2)
movie15 (disk3)
2160p Comedy (disk3,4)
movie16 (disk3)
movie17 (disk3)
movie18 (disk4)
movie19 (disk4)
2160p Action (disk1,2,3,4)
movie20 (disk1)
movie21 (disk2)
movie22 (disk3)
movie23 (disk4)

That's an outdated practice using direct disk paths now. Instead what you should do is go into the global share settings and set "Permit Exclusive Shares: Yes" this will achieve the samething but allow you to use /mnt/user/... instead of /mnt/pool_name/... while keeping the performance of the direct disk operation.

You’re not going to have bitrot protection if you don’t use a proper zfs zpool using unraids pools.

Zfs disks in the main unraid array will not provide you any of zfs’s benefits you seek.

But yes the unraid array can use a mix of filesystems as they are independent disks from one another.

Most people use XFS in their unraid array as btrfs is (in my opinion) not great and zfs has no purpose as a single disk zpool which is your only option when used in the unraid array.