I can browse the HOME folder, but cant browse other shares

[kikkegek]

hi guys,

I have strange problem.

I left for a short holiday. everything was fine.

Returned and my wife tells me she can not access the shares anymore.

I have checked all kinds of stuff, but cant figure out what has happened? was there an update of some kind causing this?

I already rebooted the HDA and my laptops. Even the routers, but nothing helps. I can only access the HOME folders, but cant access the shares for movies and pictures etc.

I can connect through putty.exe and vncviewer, no problem. I can also right to all shares when I am logged in as a user through VNC. but I just cant access the shares over the network.

also when browsing from my windows machines, I can access //hda and see the folders. but then I can only access the home folder. all other folder give me this error:

Code: Select all

no access to \\HDA\Pictures errorcode: 0x80070035 can not find networkpath

What am I missing?

here is some info:

Code: Select all

[root@amahi jochen]# mount /dev/mapper/vg_amahi-lv_root on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext4 (rw) /dev/mapper/vg_amahi-lv_home on /home type ext4 (rw) /dev/sda3 on /var/hda/files type ext4 (rw) /dev/sdb1 on /var/hda/files/drives/drive1 type ext4 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) fusectl on /sys/fs/fuse/connections type fusectl (rw) gvfs-fuse-daemon on /home/jochen/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=jochen)

Code: Select all

# # /etc/fstab # Created by anaconda on Sun Jul 31 16:09:11 2011 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # /dev/mapper/vg_amahi-lv_root / ext4 defaults 1 1 UUID=2f6fc156-23d4-4d4c-884e-2c21c7e71aed /boot ext4 defaults 1 2 /dev/mapper/vg_amahi-lv_home /home ext4 defaults 1 2 UUID=485db5c1-4dce-4b5d-b270-60b05a87659d /var/hda/files ext4 defaults 1 2 /dev/mapper/vg_amahi-lv_swap swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 UUID=667bd417-70f4-4524-ab03-501113edf499 /var/hda/files/drives/drive1 ext4 defaults 1 2

Code: Select all

[root@amahi home]# ls -al total 36 drwxr-xr-x. 6 root root 4096 Sep 5 21:35 . dr-xr-xr-x. 25 root root 4096 Jan 29 11:27 .. drwx------ 5 brenda users 4096 Jul 31 18:09 brenda drwx------. 40 jochen users 4096 Jan 29 12:26 jochen drwx------. 2 root root 16384 Jul 31 16:06 lost+found drwx------ 6 vmail vmail 4096 Sep 5 21:37 vmail

Code: Select all

[root@amahi files]# ls -al total 72 drwxr-xr-x. 15 jochen users 4096 Nov 22 19:10 . drwxr-xr-x. 12 root root 4096 Jul 31 16:33 .. drwxrwxr-x. 2 jochen users 4096 Jul 31 16:33 books drwxrwxr-x. 14 jochen users 4096 Sep 17 12:06 docs drwxrwxr-x 6 jochen users 4096 Jan 29 07:54 Downloads drwxr-xr-x 4 root root 4096 Sep 11 20:04 drives drwxr-xr-x 11 root root 4096 Jan 29 08:48 gh drwxrwxr-x. 2 jochen users 16384 Jul 31 16:06 lost+found drwxrwxrwx. 6 jochen users 4096 Jan 29 12:52 movies drwxrwxr-x. 10 jochen users 4096 Jan 20 19:28 music drwxrwxr-x. 24 jochen users 4096 Jan 17 20:26 pictures drwxrwxr-x 112 jochen users 4096 Dec 5 19:56 Software drwxrwxrwx 4 jochen users 4096 Nov 22 19:16 Torrentflux-b4rt drwxrwxrwx 36 jochen users 4096 Jan 19 09:32 torrents drwx------ 5 jochen users 4096 Aug 1 11:05 .Trash-500

I have used the HDA last night. without any problems. even added some NZB downloads, browsed the folders and viewed some videos from my HDA. So it happened over night.

[bigfoot65]

Recommend you try the shares troubleshooter in the wiki.

http://wiki.amahi.org/index.php/Shares_troubleshooting

If you are using Windows 7 as the client, there are some who have to use the domain name to access shares.

[kikkegek]

Recommend you try the shares troubleshooter in the wiki.

http://wiki.amahi.org/index.php/Shares_troubleshooting

If you are using Windows 7 as the client, there are some who have to use the domain name to access shares.

I am using Windows 7 on my laptop and some of my desktops. But untill last night everything was fine.

what log file should I check to see what happened over night?

it even finished the NZB downloads and then shutdown.

I'll check the troubleshooter, but I dont think it will give new insights, because I didnt change anything myself.

[kikkegek]

hi Bigfoot65,

I ran through the whole wiki, but nothing helped. result is still I can not access my shares. only my home folder.

tested from W7 and Vista machines.

I have set the debug level for SAMBA to 5 and uploaded the samba log file for my laptop here.

I run a BATCH file to mount a couple of shares on my W7 laptop.

this is the result/output:

samba.log

(71.2 KiB) Downloaded 198 times

[bigfoot65]

Are you using your HDA for DHCP/DNS server? Have you released/renewed the DHCP lease for your clients?

Did you try the \\hda.home.com\share or whatever domain you are using? Also check that all your shares are owned by the first admin user and permissions are set to 775.

[kikkegek]

I think I know what is going on.

I think Greyhole was updated. Because when I check, the symlinks are not there anymore.

I checked the greyhole version and it reported:

Code: Select all

[root@amahi jochen]# ls -l /usr/lib*/samba/vfs/greyhole.so ls: cannot access /usr/lib*/samba/vfs/greyhole.so: No such file or directory

so I manually reinstalled greyhole:

Code: Select all

[root@amahi jochen]# rpm -q hda-greyhole hda-greyhole-0.9.20-1.i386 [root@amahi jochen]# rpm -Uvh --force http://www.greyhole.net/releases/rpm/`uname -i`/`rpm -qa hda-greyhole`.rpm Retrieving http://www.greyhole.net/releases/rpm/i386/hda-greyhole-0.9.20-1.i386.rpm Preparing... ########################################### [100%] 1:hda-greyhole ########################################### [100%] Executing post-install script... Found LIB_DIR = /usr/lib Detected Samba 3.5; creating symlink pointing to greyhole-samba35.so Post-install script completed. =========================================================================== See /usr/share/greyhole/USAGE to learn how to configure and start Greyhole. ===========================================================================

and checked again:

Code: Select all

[root@amahi jochen]# ls -l /usr/lib*/samba/vfs/greyhole.so lrwxrwxrwx 1 root root 37 Jan 29 22:50 /usr/lib/samba/vfs/greyhole.so -> /usr/lib/greyhole/greyhole-samba35.so [root@amahi jochen]#

and all shares are back again.

I think I have found a bug didn't I?

I am just happy I fixed it and my shares are up again....thanks for the great wiki's....in the end they helped me solve it...

AMAHI ROCKS!

[bigfoot65]

Glad ya sorted it out.

Greyhole has not been updated on F14. hda-greyhole-0.9.2 is what mine reports, so not sure how it broke.

[rhubarb]

I have the same problem. On Friday (27th) the shares were working. I go away for the weekend and come back Sunday eveneing (29th) to find the Samba shares are not accessible. (Except the share that is on the same disk as the rootfs for some reason)

I have started trawling through /var/log/messages and find near the top

Jan 29 07:03:25 fedora-arm yum: Updated: hda-greyhole-0.9.20-1.armv5tel

I remember that I did some manual (from the command line) YUM (or whatever it is) to get some greyhole when I first installed since it didnt seem to work initially. so this could be part of the problem

Later down the log file I start getting lot of:-

Jan 29 22:00:48 fedora-arm smbd[21057]: [2012/01/29 22:00:48, 0] smbd/vfs.c:175(vfs_init_custom)
Jan 29 22:00:48 fedora-arm smbd[21057]: Can't find a vfs module [greyhole]
Jan 29 22:00:48 fedora-arm smbd[21057]: [2012/01/29 22:00:48, 0] smbd/vfs.c:322(smbd_vfs_init)
Jan 29 22:00:48 fedora-arm smbd[21057]: smbd_vfs_init: vfs_init_custom failed for greyhole
Jan 29 22:00:48 fedora-arm smbd[21057]: [2012/01/29 22:00:48, 0] smbd/service.c:846(make_connection_snum)
Jan 29 22:00:48 fedora-arm smbd[21057]: vfs_init failed for service dev

The last word "dev" is the name of one of my now inaccessible shares

I will try reinstalling greyhole as mentioned above.

Peter

[rhubarb]

the reason why one of my shares is still available is cos it is not under greyhole. Ie it does not have something like

dfree command = /usr/bin/greyhole-dfree
vfs objects = greyhole

in /etc/samba/smb.conf

I also have the symlink problem

[root@fedora-arm samba]# ls -l /usr/lib*/samba/vfs/greyhole.so ls: cannot access /usr/lib*/samba/vfs/greyhole.so: No such file or directory

I searched the entire machine for greyhole.so
find . | grep greyhole.so
but found nothing.

I have looked at the http://wiki.amahi.org/index.php/Greyhol ... repository
but it has not helped

I have a feeling that I (once upon a time) manually downgraded Greyhole to find somehting that worked. On sunday it was automatically upgraded (by Amahi?) to the latest version which for some reason does not work on my ARM dreamplug

so where am I going to find a greyhole.so?

Peter

[rhubarb]

I did the following and my shares are back (eg3.4)

smbstatus to get samba version
cd /usr/lib/samba/vfs
ln -is /usr/lib/greyhole/greyhole-samba34.so greyhole.so
sudo service smb restart

Peter