August 15, 201312 yr I just upgraded to 5.0rc16c from 4.7. The upgrade went smoothly, and I ran the permissions script as instructed following the first boot into v5. After the script finished, I could access some of my shares but others pop up a message in Windows saying the share is not accessible. There are 4 shares including my Flash share that I cannot access. I tried re-running the script again and then rebooting the server but it didn't help. I found this thread which describes the exact problem I am having: http://lime-technology.com/forum/index.php?topic=22677.0 The shares I cannot access are "Documents", "flash", "Pictures" and "Videos". I had (and still have) unmenu installed prior to the upgrade with the following packages installed, running and set to re-install after a reboot: apcupsd - A daemon for controlling APC UPS devices "C" compiler & development tools mail and ssmtp - Configure unRAID to be able to send e-mail notifications via the "mail" command. unRAID Status Alert sent hourly by e-mail Monthly Parity Check pci utils (pci utilities) unRAID Power-Down on disk overtemp Clean Powerdown Here is the output of the two commands that Joe. L. asked for in that other thread: root@Tower:~# ls -al /boot total 36176 drwxrwxrwx 6 root root 4096 Dec 31 1969 ./ drwxr-xr-x 16 root root 0 Aug 14 21:26 ../ -rwxrwxrwx 1 root root 2732624 Jul 5 15:42 bzimage* -rwxrwxrwx 1 root root 33987604 Jul 5 15:43 bzroot* drwxrwxrwx 3 root root 4096 Aug 14 21:25 config/ -r-xr-xr-x 1 root root 13639 Nov 9 2012 ldlinux.sys* -rwxrwxrwx 1 root root 5162 Nov 8 2012 license.txt* drwxrwxrwx 2 root root 4096 Aug 14 21:23 logs/ -rwxrwxrwx 1 root root 830 Nov 8 2012 make_bootable.bat* -rwxrwxrwx 1 root root 165080 Nov 8 2012 memtest* -rwxrwxrwx 1 root root 33404 Nov 8 2012 menu.c32* drwxrwxrwx 3 root root 16384 Aug 14 21:26 packages/ -rwxrwxrwx 1 root root 6247 Nov 8 2012 readme.txt* -rwxrwxrwx 1 root root 183 Nov 8 2012 syslinux.cfg* -rwxrwxrwx 1 root root 27136 Nov 8 2012 syslinux.exe* drwxrwxrwx 4 root root 16384 Apr 26 10:24 unmenu/ root@Tower:~# root@Tower:~# testparm -s Load smb config files from /etc/samba/smb.conf WARNING: The "null passwords" option is deprecated Can't find include file /boot/config/smb-extra.conf Processing section "" Processing section "[Archive]" Processing section "[backups]" Processing section "[Documents]" Processing section "[Movies]" Processing section "[Music]" Processing section "[Pictures]" Processing section "[Videos]" Processing section "[z - technical]" Loaded services file OK. WARNING: You have some share names that are longer than 12 characters. These may not be accessible to some older clients. (Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.) Server role: ROLE_STANDALONE [global] server string = Media server map to guest = Bad User null passwords = Yes passdb backend = smbpasswd syslog = 0 syslog only = Yes max protocol = SMB2 unix extensions = No load printers = No printcap name = /dev/null disable spoolss = Yes show add printer wizard = No local master = No idmap config * : backend = tdb invalid users = root create mask = 0777 directory mask = 0777 use sendfile = Yes map archive = No wide links = Yes comment = Flash share path = /boot read only = No guest ok = Yes [Archive] path = /mnt/user/Archive read only = No guest ok = Yes [backups] path = /mnt/user/Backups read only = No guest ok = Yes [Documents] path = /mnt/user/Documents read only = No guest ok = Yes [Movies] path = /mnt/user/Movies read only = No guest ok = Yes [Music] path = /mnt/user/Music read only = No guest ok = Yes [Pictures] path = /mnt/user/Pictures read only = No guest ok = Yes [Videos] path = /mnt/user/Videos read only = No guest ok = Yes [z - technical] path = /mnt/user/z - technical read only = No guest ok = Yes browseable = No root@Tower:~# Could someone please let me know what I can do to fix this problem? I am hoping I don't need to install unmenu and have to re-do all of those configs!
August 15, 201312 yr Author Well, I don't know what to say, but I woke up this morning and thought I'd try to access those shares again... and all of a sudden they are now working!?! I didn't touch anything...they just seemed to have fixed themselves overnight! Does anyone have any explanation for this or should we just leave it alone now that everything is working? :-)
Archived
This topic is now archived and is closed to further replies.