Hi,

 

I ran an extended test with the Fix Common Problems Plugin and ran into the following problem:

 

The following files exist within the same folder on more than one disk.  This duplicated file means that only the version on the lowest numbered disk will be readable, and the others are only going to confuse unRaid and take up excess space:

/mnt/user/appdata/binhex-sabnzbd/admin/history1.db   disk3 cache
/mnt/user/appdata/binhex-sabnzbd/admin/postproc2.sab   disk3 cache
/mnt/user/appdata/binhex-sabnzbd/admin/queue10.sab   disk3 cache
/mnt/user/appdata/binhex-sabnzbd/admin/rss_data.sab   disk3 cache
/mnt/user/appdata/binhex-sabnzbd/admin/server.cert   disk3 cache
/mnt/user/appdata/binhex-sabnzbd/admin/server.key   disk3 cache
/mnt/user/appdata/binhex-sabnzbd/admin/totals10.sab   disk3 cache
/mnt/user/appdata/binhex-sabnzbd/admin/watched_data2.sab   disk3 cache
/mnt/user/appdata/binhex-sabnzbd/logs/sabnzbd.log   disk3 cache
/mnt/user/appdata/binhex-sabnzbd/perms.txt   disk3 cache
/mnt/user/appdata/binhex-sabnzbd/sabnzbd.ini   disk3 cache
/mnt/user/appdata/binhex-sabnzbd/sabnzbd.ini.bak   disk3 cache
/mnt/user/appdata/binhex-sabnzbd/supervisord.log   disk3 cache
/mnt/user/appdata/binhex-sonarr/config.xml   disk3 cache
/mnt/user/appdata/binhex-sonarr/logs/sonarr.txt   disk3 cache
/mnt/user/appdata/binhex-sonarr/logs.db   disk3 cache
/mnt/user/appdata/binhex-sonarr/logs.db-shm   disk3 cache
/mnt/user/appdata/binhex-sonarr/logs.db-wal   disk3 cache
/mnt/user/appdata/binhex-sonarr/nzbdrone.db   disk3 cache
/mnt/user/appdata/binhex-sonarr/nzbdrone.db-shm   disk3 cache
/mnt/user/appdata/binhex-sonarr/nzbdrone.db-wal   disk3 cache
/mnt/user/appdata/binhex-sonarr/nzbdrone.pid   disk3 cache
/mnt/user/appdata/binhex-sonarr/perms.txt   disk3 cache
/mnt/user/appdata/binhex-sonarr/supervisord.log   disk3 cache
/mnt/user/appdata/binhex-sonarr/xdg/.mono/keypairs/[1][xxxjhkjhxxx][-1].xml   disk3 cache
/mnt/user/system/docker/docker.img   disk3 cache


Directories Scanned: 2315  Files Scanned: 27226

 

It probably happened because my cache-drive ran out of space, the docker.container crashed and I had to delete and recreate the docker-image.

 

Everything works just fine on the outside, but I wanted to gather some torrents for seeding on the (ssd)-cache-drive with unBalance. unbalance kindly reminded my that there might some permission-problems and said problem emerged...

 

Any idea how to fix it?

Should I just delete the files from disk3? What's the best way to do it?

 

Thanks in advance!

 

Edited December 31, 20196 yr by Evin

Same here - is there any solution ?

 

12 minutes ago, Schulmeister said:

Same here - is there any solution ?

 

You have to decide which copy you want to keep, and then delete the other one.

 

If the same file exists on multiple drives, then Unraid shows any copy on cache first, and then on array disks in ascending order.