October 7, 201510 yr Hello folks, Got a really strange thing happening here, I upgraded from unraid 6.01 to 6.1.3 and now my TV & Films directory seems to be missing. normally under /mnt/user or /mnt/user0 I'd have TV, Films, PVR, Backup, Timemachine etc. now all I get under /mnt is /user and disks :- drwxr-xr-x 11 root root 220 Oct 7 23:32 ./ drwxr-xr-x 18 root root 380 Sep 21 06:21 ../ drwxrwxrwx 1 nobody users 84 Mar 10 2015 btrfs/ drwxrwxrwx 2 nobody users 6 Oct 7 20:48 cache/ drwxrwxrwx 7 nobody users 111 Oct 7 20:00 disk1/ drwxrwxrwx 7 nobody users 89 May 22 15:40 disk2/ drwxrwxrwx 3 nobody users 15 Oct 23 2014 disk3/ drwxrwxrwx 3 nobody users 15 Oct 23 2014 disk4/ drwxrwxrwx 3 nobody users 15 Oct 23 2014 disk5/ drwxrwxrwx 3 nobody users 15 Nov 2 2014 disk6/ drwxr-xr-x 3 root root 60 Oct 7 23:33 user/ under /mnt/user is TV root@NAS-server:/mnt/user# ls TV/ under there nothing. so I went into the GUI, deleted the TV share so there is nothing there. check on the USB stick :- root@NAS-server:/boot/config/shares# ls -la total 8 drwxrwxrwx 2 root root 4096 Oct 7 23:33 ./ drwxrwxrwx 8 root root 4096 Oct 7 23:30 ../ empty, fine, do a clean reboot... back comes /mnt/user/TV with nothing in it, where is it getting this from ? If I create any shares and reboot they disappear. if I go into the disks how ever I can see all my data is still there. root@NAS-server:/boot/config/shares# cd /mnt/disk1/ root@NAS-server:/mnt/disk1# ls Downloads/ Films/ Macbckup/ TV/ backup/ btrfs@ so question, where is the server getting /mnt/user/TV from when it's clearly not there, why if I create a new share Films do I not see my films ? I'm figuring it's going to be a full clean install at this point but I really don't want to if I can avoid it.. Any help appreciated. Thanks
October 8, 201510 yr Community Expert Sounds as if the USB drive may be mounted read-only for some reason so that changes made in the GUI are not being saved. All top level folders on the disks should automatically become User shares if things are working correctly (assuming User Shares are enabled under Settings). Posting the diagnostics that were requested should help with determining what is going on.
October 8, 201510 yr Author Hi folks, Nope USB stick is writeable ok, I can touch and remove a file from the /boot/config directory no problems. Diagnostics attached if it helps. Thanks nas-server-diagnostics-20151008-0823.zip
October 8, 201510 yr Community Expert Hi folks, Nope USB stick is writeable ok, I can touch and remove a file from the /boot/config directory no problems. Diagnostics attached if it helps. Thanks The diagnostics do not include a share.cfg file which suggests that User Shares have not been enabled under Settings->Global Share Settings. However I thought you said you have been able to use the Shares tab and this does not normally appear if User Shares are not enabled? It might be worth trying to toggle the setting off/on to see if that makes a difference.
October 8, 201510 yr Author Thanks for the assistance so far folks, So I did as you suggested, stopped the array, turned off then on again the global shares, and rebooted. the share.cfg is back and the TV share came back. But I deleted that and created Films again. Everything looks like it worked as expected.. But there are still not Films in my Film Directory :- root@NAS-server:/mnt/user/Films# cd /boot/config/shares root@NAS-server:/boot/config/shares# ls Films.cfg* root@NAS-server:/boot/config/shares# more Films.cfg # Generated settings: shareComment="" shareInclude="" shareExclude="" shareUseCache="yes" shareCOW="auto" shareAllocator="highwater" shareSplitLevel="" shareFloor="0" shareExport="e" shareSecurity="public" shareReadList="" shareWriteList="" shareExportNFS="-" shareExportNFSFsid="0" shareSecurityNFS="public" shareHostListNFS="" shareExportAFP="-" shareSecurityAFP="public" shareReadListAFP="" shareWriteListAFP="" shareVolsizelimitAFP="" shareVoldbpathAFP="" root@NAS-server:/boot/config/shares# cd /mnt root@NAS-server:/mnt# ls btrfs/ cache/ disk1/ disk2/ disk3/ disk4/ disk5/ disk6/ user/ root@NAS-server:/mnt# cd user/ root@NAS-server:/mnt/user# ls Films/ root@NAS-server:/mnt/user# cd Films/ root@NAS-server:/mnt/user/Films# ls root@NAS-server:/mnt/user/Films# cd ../../disk1 root@NAS-server:/mnt/disk1# ls Downloads/ Films/ Macbckup/ TV/ backup/ btrfs@ root@NAS-server:/mnt/disk1# cd Films/ root@NAS-server:/mnt/disk1/Films# ls 12\ Years\ a\ Slave\ (2013)/ Attached new diags incase that helps.] Thanks Steve nas-server-diagnostics-20151008-1018.zip
October 8, 201510 yr Author ok so I am making headway, if I stop the array and then reboot it, then log back in again before starting the array, the strange /mnt/user/TV directory is back. so If I delete it :- cd /mnt/ root@NAS-server:/mnt# ls btrfs/ user/ root@NAS-server:/mnt# cd user/ root@NAS-server:/mnt/user# ls TV/ root@NAS-server:/mnt/user# cd TV/ root@NAS-server:/mnt/user/TV# ls root@NAS-server:/mnt/user/TV# cd .. root@NAS-server:/mnt/user# cd .. root@NAS-server:/mnt# rm -r user then start the array :- root@NAS-server:/mnt# df -k Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 131072 1832 129240 2% /var/log /dev/sda1 1950348 317796 1632552 17% /boot /dev/sdd 390624996 289328592 100183376 75% /mnt/btrfs /dev/loop0 52428800 3268316 47540452 7% /var/lib/docker /dev/md1 2928835740 1513993724 1414842016 52% /mnt/disk1 /dev/md2 2928835740 653928104 2274907636 23% /mnt/disk2 /dev/md3 2928835740 552813848 2376021892 19% /mnt/disk3 /dev/md4 2928835740 553486092 2375349648 19% /mnt/disk4 /dev/md5 2928835740 553751512 2375084228 19% /mnt/disk5 /dev/md6 2928835740 553886704 2374949036 19% /mnt/disk6 /dev/sdb1 499863384 32928 499830456 1% /mnt/cache shfs 17573014440 4381859984 13191154456 25% /mnt/user0 shfs 18072877824 4381892912 13690984912 25% /mnt/user root@NAS-server:/mnt# cd /mnt/ root@NAS-server:/mnt# ls btrfs/ cache/ disk1/ disk2/ disk3/ disk4/ disk5/ disk6/ user/ user0/ root@NAS-server:/mnt# cd user root@NAS-server:/mnt/user# ls Downloads/ Films/ Macbckup/ PVR/ TV/ backup/ btrfs@ root@NAS-server:/mnt/user# all is good with the world again. so where is this /mnt/user/TV directory coming from ?
October 8, 201510 yr Community Expert ...so where is this /mnt/user/TV directory coming from ? One or more of your disks has a top level folder named TV
October 8, 201510 yr Author Do you know what I think I'm just going to do a fresh build on this server, things are getting very odd. Plex has decided to stop working, even though Films and TV are back it refuses to see the directories, I've reinstalled the docker multiple times, removed all the plex data still not playing. Sickrage has stopped working. /mnt seems to be owned by root:root which stops plex from even starting. I am having to fix too many strange little issues I take it as long as I don't touch the data disks and just put a full fresh image on the USB stick my data will stay intact ?
October 21, 201510 yr Some thoughts - * I noticed some things about your system, from the diagnostics of 2015-10-08, that almost certainly affect your chances for successful operation. You are clearly an advanced user, and you know enough to make advanced changes to the way unRAID operates, but I suspect the unRAID design is not yet robust enough for them. * You have significant insertions in the go file. That's OK if you know what you're doing, and you do appear to know more than I do, so I'm going to have to be careful what I say! But some of the changes look to me to be significantly altering the order of unRAID startup. * Early in the go file you issue a "docker stop", but we don't know for sure that docker has been initialized to even process that. It *should* be harmless, but I can't say for sure. Then shortly after, you issue a "docker start", and it appears that definitely is wrong, and it isn't ready for a start. The syslog shows docker setup activity at this time, activity that normally never appears at this point. This docker activity normally only appears AFTER the array is started (and emhttp has long been loaded). I think your docker statements here are probably causing some of your problems. * You have delayed the startup of emhttp for over 80 seconds. Some of the proprietary functionality of unRAID is in emhttp, so not having it available until much later could certainly have affected earlier operation. I'm not privy to what's in it, but from all I know, it's not wise to mess with it, or the normal order of startup. unRAID needs it, for unRAID to run correctly. Plus, it manages starting and stopping various services in the right order. I'm going to suggest reworking your go file to preserve normal startup, then adding all your extra setup afterward, if you can. * A picky point, probably just a technicality - your very first action in your go file is to run "mkdir -p /mnt/btrfs". While I would hope that /mnt has been setup already, if it doesn't exist yet, then your use of the -p option will force it to be created with the current bash session's owner and permissions, which *might* not be correct for unRAID, and could cause problems later. * FUSE is not running! This is huge. Fuse is never initialized in your setup, and it always is in normal unRAID systems. Without Fuse, the User Share system is never setup, and even if enabled, the User Shares cannot work, and the User Share paths /mnt/user and /mnt/user0 are not created. If /mnt/user is appearing, then something of yours is creating it, and it's not the true virtual file system /mnt/user that Fuse creates. I don't know what could cause the lack of Fuse. Do you possibly have a custom kernel, or modified unRAID system? (Or just a borked system) * No where does a TV folder or share appear in the configuration visible in the diagnostics. Since FUSE isn't running, I have to assume you have a configured path for it (/mnt/user/TV) in a script you are using, or a configured path in a plugin or Docker container you are using. You clearly know more than I, so I've tried not to speculate about the impacts of your additions. I hope though that some of the points above (even if they aren't all correct!) will give you the ideas you need to get your system working.
Archived
This topic is now archived and is closed to further replies.