Can someone help me fix this? Pretend I'm a basic, new user with very few IT skills (actually, you don't have to pretend).

cache is a reserved name for unraid. you named a pool ir maybe a share 'cache' and its causing problems. Find what you named 'cache' and change it to another name. might involve recreating it.

For the appdata thing... at some point it was writing to the array. You will need to move the files manually. This means you need to shut off docker and vm under settings and locate the files in the array disk directory and move them to your cache drive designated drive. After that, turn back on the docker and vm setting.

Edited Sunday at 07:26 PM2 days by Veah

fairly easy to explain:

• you have a disk pool named "cache" (the defaut name for the first ssd you have setup in UNRAID)

• you also have a folder named "cache" in one of of the toplevel directories of one of your disks (or in the array)

Because UNRAID has a filesystem driver that automatically combines equally named folders into a single share, this leads to trouble because you are mixing apples and peas.

Find that folder, rename it to something else and you are done.

(The pool "cache" could also be renamed but that would lead to more problems, so go for the folder)

16 hours ago, MAM59 said:

fairly easy to explain:

• you have a disk pool named "cache" (the defaut name for the first ssd you have setup in UNRAID)

• you also have a folder named "cache" in one of of the toplevel directories of one of your disks (or in the array)

Because UNRAID has a filesystem driver that automatically combines equally named folders into a single share, this leads to trouble because you are mixing apples and peas.

Find that folder, rename it to something else and you are done.

(The pool "cache" could also be renamed but that would lead to more problems, so go for the folder)

Ah, this is helpful. I have a share named "cache." Perhaps changing its name? My device pool also has a cache drive.

Edited 22 hours ago22 hr by Bill_Hickman

3 hours ago, Bill_Hickman said:

Ah, this is helpful. I have a share named "cache." Perhaps changing its name?

Absolutely, this is the first thing that I would do. (Understand that there are 'reserved' words that should never be used for file names, directory/folder names or variables at the OS level for EVERY OS in existence. For examples, Google reserved words for Windows)

38 minutes ago, Frank1940 said:

Understand that there are 'reserved' words that should never be used for file names, directory/folder names or variables at the OS level for EVERY OS in existence. For examples, Google reserved words for Windows

I Googled "Reserved words for Unraid" and all I got was "User".

Is there a list somewhere of reserved words for Unraid?

TIA

actually "cache" is not really "reservered".

It is just that the first pool you create automatically is named "cache".

You CAN change the name later on, but it is common to leave it alone because system folders are also automatically created there and files for dockers and VMs are stored there.

If you rename the "cache"-pool you also have to edit those system folders which can become quite complicated.

Therefor it is adviced to rename the single folder named "cache" that you have created yourself and you know what this share is good for and where it is accessed.

Less trouble.

(BTW: UNRAID takes every toplevel Folder in any disk as a "share" automatically. So if you rename the folder, the share will be deleted and a new one will be created automatically with the new name. Check Share settings afterwards, they will be created with default values again!)

Edited 16 hours ago16 hr by MAM59

13 hours ago, MAM59 said:

actually "cache" is not really "reservered".

It is just that the first pool you create automatically is named "cache".

You CAN change the name later on, but it is common to leave it alone because system folders are also automatically created there and files for dockers and VMs are stored there.

If you rename the "cache"-pool you also have to edit those system folders which can become quite complicated.

Therefor it is adviced to rename the single folder named "cache" that you have created yourself and you know what this share is good for and where it is accessed.

Less trouble.

(BTW: UNRAID takes every toplevel Folder in any disk as a "share" automatically. So if you rename the folder, the share will be deleted and a new one will be created automatically with the new name. Check Share settings afterwards, they will be created with default values again!)

/mnt/user/cache and /mnt/cache/cache should not conflict. It's probably FCP being FCP (outdated warnings)

Edit:

As a test I created a user share named backup but also have a pool named backup.

Actually it looks like unraid automatically symlinked it to my backup pool rather than keeping it a folder on my cache pool where I originally created it... how strange.

Edit2: My mistake, it created it correctly on /mnt/cache (not /mnt/backup) that's my bad, all worked out fine.

Edited 3 hours ago3 hr by MowMdown

7 minutes ago, MowMdown said:

/mnt/user/cache and /mnt/cache/cache should not conflict. It's probably FCP being FCP (outdated warnings)

Don't these two point to the same directory on the cache drive????????? Yes one is a share but the other is top level directory on a disk which could be a part of the share depending on the share setting. You can write to a share by using the /mnt/user/share_name or mnt/disk#/share_name. disk# can be cache if the share_name's primary storage location is cache.

See here for a way to use this situation:

https://forums.unraid.net/topic/58374-secure-writing-strategy-for-unraid-server-using-write-once-read-many-mode

3 minutes ago, Frank1940 said:

Don't these two point to the same directory on the cache drive????????? Yes one is a share but the other is top level directory on a disk which could be a part of the share depending on the share setting. You can write to a share by using the /mnt/user/share_name or mnt/disk#/share_name. disk# can be cache if the share_name's primary storage location is cache.

See here for a way to use this situation:

https://forums.unraid.net/topic/58374-secure-writing-strategy-for-unraid-server-using-write-once-read-many-mode

I confused myself but ultimately unraid did the correct thing (which is what I originally suspected would happen). I have two pools /mnt/cache and /mnt/backup and then created a user-share through cli usingmkdir /mnt/user/backup which it correctly put on the cache pool so there was no conflict with my pool named backup.

You are correct though, accessing the folder at /mnt/cache/cache and /mnt/user/cache (if settings are correct) would access the same files. FCP just complains about it I guess (I removed FCP long ago)

Edited 3 hours ago3 hr by MowMdown