ldasilva Posted May 28, 2016 Share Posted May 28, 2016 hi guys im a bit lost on what to do i been searching the forum and seen a few people with the same problem but the fixs they did doesnt seem to work i am missing files under user share but browsing to disk(x) shows files it all started when the drive got maxed out so i moved a few gbs off it to another drive for some free space i then added another 2tb drive into the mix i checked the log file i didnt see any errors i am using version 5.0 anyone point me to the right spot to fix this i was checking the wiki Thanks unraid-log-file-5-28-16.txt Link to comment
RobJ Posted May 29, 2016 Share Posted May 29, 2016 Factors that can affect the visibility of files in a share (that I can think of) * global share settings, drive includes and excludes - have to make sure the right drives are included, not excluded (can't remember if v5.0 even has this setting!) * share settings for each share, drive includes and excludes - have to make sure the right drives are included, not excluded * case sensitivity in share names - a movie that's in /movies won't be found in a share called Movies * if something happens and the User Share file system gets a little messed up, just stop the array, then start it again; the User Share file system is built brand new each time the array starts; if after that a file does not appear in the share you think it should, then it's not configured to appear there, so check the share settings, etc Please consider Upgrading to UnRAID v6! Link to comment
ldasilva Posted May 29, 2016 Author Share Posted May 29, 2016 thanks rob i think my problem was the excludes i added that after i ran out of space thinking it wouldnt use that drive any more for new files more files showed up but now i have a new problem i upgraded to v6 ill post in v6 thread but problem is below . . . . May 29 14:03:54 Tower logger: /usr/sbin/rpc.mountd May 29 14:03:54 Tower emhttp: shcmd (74): /etc/rc.d/rc.atalk status May 29 14:03:54 Tower rpc.mountd[3138]: Version 1.2.8 starting May 29 14:03:54 Tower emhttp: Starting Docker... May 29 14:03:54 Tower logger: /usr/bin/docker not enabled May 29 14:03:55 Tower avahi-daemon[2106]: Service "Tower" (/services/smb.service) successfully established. May 29 14:04:34 Tower shfs/user: shfs_readdir: fstatat: jcg-other-stuff (13) Permission denied May 29 14:04:34 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk2/backup/old-vhs-movies-tapes/hi8-tapes (13) Permission denied May 29 14:04:34 Tower shfs/user: shfs_readdir: fstatat: jcg-other-stuff (13) Permission denied May 29 14:04:34 Tower shfs/user: shfs_readdir: readdir_r: /mnt/disk2/backup/old-vhs-movies-tapes/hi8-tapes (13) Permission denied May 29 14:06:00 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/newperms /mnt/disk2 May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118104 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118109 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118110 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118108 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:14 Tower kernel: REISERFS warning (device md2): vs-13075 reiserfs_read_locked_inode: dead inode read from disk [118103 118105 0x0 SD]. This is likely to be race with knfsd. Ignore May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 May 29 14:06:37 Tower kernel: REISERFS (device md2): Remounting filesystem read-only May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 May 29 14:06:37 Tower kernel: REISERFS error (device md2): vs-7000 search_by_entry_key: search_by_key returned item position == 0 Link to comment
RobJ Posted May 29, 2016 Share Posted May 29, 2016 New post in General Support for v6 is a good idea. And Check Disk File systems is what you need for Disk 2. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.