Hi everyone,
I'm not sure what information will be needed, so this will be a question in progress. Here's my situation. I upgraded from Amahi on Fedora 14 to Amahi 7 (clean installation and then installed Greyhole, and added my drives back in). When I ssh into my Amahi Server, I can see the individual files in each directory (/var/hda/files/music for example). However when I mount them via SAMBA on my desktop, all I can see are subdirectories. The files don't appear at all.
The other curious thing is, if I save a file to the mounted share, it appears in any desktop that's connected and on the server. So what I have is this:
files stored on server before upgrade --- not visible to desktops connecting to the server after upgrade.
subdirectories stored on server before upgrade --- visible to desktops connecting after upgrade (but files inside are not visible).
files saved to server from desktop after upgrade --- visible to everyone connected to the network.
If I do a ls -l on the server, it shows the files with their respective locations in the /var/hda/files/drives directory. The permissions on everything inside of the directory is -rwxrwxrwx (or drwxrwxrwx for subdirectories). Nothing should be hidden (except of course the . files).
So my question is how do I get the individual files to appear on my clients? I've rebooted everything at least once since I did the upgrade.
Have a great day.
Patrick.
SOLVED:Can't see files on shares after upgrading to Amahi 7.
-
- Posts: 75
- Joined: Thu Jan 19, 2012 6:52 am
Re: Cannot see files on shares after upgrading to Amahi 7.
Check that the ownership of the files in the shares are set to your first admin user:users.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
-
- Posts: 75
- Joined: Thu Jan 19, 2012 6:52 am
Re: Cannot see files on shares after upgrading to Amahi 7.
A quick update to this. If I try ls -l or cat on a file, I get ls: cannot access Outlook.pst: Permission denied. Obviously the file name will be different for each one. If I ssh into the server as root and do the same command, I actually see the file (or contents in a cat command).
If I ssh into the server as my regular user, I get the same permission denied messages for cat. In the shares, everything is owned by root. However, in one of the shares, I chowned them to patrickdickey:users. I still get the permission denied for cat on those files.
On my desktop, here are the results of dmesg | tail, dmesg | grep cifs and dmesg | grep CIFS
And on the server, here are the results of dmesg | grep cifs and dmesg | grep CIFS
I'll check this thread later to see if anyone has suggestions, or if I need to post anything else. Thanks again, and have a great day.
Patrick.
If I ssh into the server as my regular user, I get the same permission denied messages for cat. In the shares, everything is owned by root. However, in one of the shares, I chowned them to patrickdickey:users. I still get the permission denied for cat on those files.
On my desktop, here are the results of dmesg | tail, dmesg | grep cifs and dmesg | grep CIFS
Code: Select all
patrickdickey@dcky-ubuntu64:~$dmesg | grep cifs
[ 43.088965] FS-Cache: Netfs 'cifs' registered for caching
[ 43.089113] Key type cifs.spnego registered
[ 43.089130] Key type cifs.idmap registered
patrickdickey@dcky-ubuntu64:~$dmesg | tail
[690870.124168] sr 3:0:0:0: [sr0] unaligned transfer
[690870.223020] winecfg.exe: sending ioctl 5305 to a partition!
[692624.602310] rhythmbox: sending ioctl 2285 to a partition!
[692624.602369] rhythmbox: sending ioctl 2285 to a partition!
[692624.602392] rhythmbox: sending ioctl 2285 to a partition!
[692624.602411] rhythmbox: sending ioctl 2285 to a partition!
[693610.017211] CIFS VFS: Unexpected lookup error -512
[695406.629944] CIFS VFS: Unexpected lookup error -512
[696074.547139] CIFS VFS: Unexpected lookup error -512
[819473.172792] CIFS VFS: Unexpected lookup error -512
patrickdickey@dcky-ubuntu64:~$dmesg | grep CIFS
[ 604.339021] CIFS VFS: Autodisabling the use of server inode numbers on \\hda\Docs. This server doesn't seem to support them properly. Hardlinks will not be recognized on this mount. Consider mounting with the "noserverino" option to silence this message.
[693610.017211] CIFS VFS: Unexpected lookup error -512
[695406.629944] CIFS VFS: Unexpected lookup error -512
[696074.547139] CIFS VFS: Unexpected lookup error -512
[819473.172792] CIFS VFS: Unexpected lookup error -512
patrickdickey@dcky-ubuntu64:~$
Code: Select all
-bash-4.2$ dmesg | grep cifs
[ 37.147150] FS-Cache: Netfs 'cifs' registered for caching
[ 37.147465] Key type cifs.spnego registered
[ 37.147511] Key type cifs.idmap registered
-bash-4.2$ dmesg | grep CIFS
-bash-4.2$
Patrick.
-
- Posts: 75
- Joined: Thu Jan 19, 2012 6:52 am
Re: Cannot see files on shares after upgrading to Amahi 7.
I just saw your update after I posted my second reply. One question for you. Should /var/hda/files/sharename and it's subdirectory be owned by the first admin: users, or should /var/hda/files and everything below that (shares and drives etc) be owned by admin:users?Check that the ownership of the files in the shares are set to your first admin user:users.
Thanks for the quick reply.
Patrick.
P.S. Here is the result of ls -l on /var/hda/files
Code: Select all
-bash-4.2$ ls -l
total 152
drwxrwxr-x 3 patrickdickey users 4096 Aug 22 06:05 ashleymiles
drwxrwxr-x 9 patrickdickey users 20480 Aug 18 07:15 books
drwxrwxr-x 5 patrickdickey users 4096 Aug 18 23:45 docs
drwxr-xr-x 8 root root 4096 Aug 18 04:56 drives
drwx------. 2 patrickdickey users 16384 Aug 18 02:56 lost+found
drwxrwxr-x 9 patrickdickey users 12288 Sep 6 08:24 movies
drwxrwxr-x 303 patrickdickey users 45056 Aug 18 08:54 music
drwxrwxr-x 80 patrickdickey users 24576 Sep 14 21:06 patrickdickey
drwxrwxr-x 35 patrickdickey users 4096 Aug 18 07:23 pictures
drwxrwxr-x 2 patrickdickey users 4096 Aug 18 03:58 public
drwxrwxr-x 11 patrickdickey users 4096 Aug 19 08:36 software
drwxrwxr-x 2 patrickdickey users 4096 Aug 18 03:58 videos
-bash-4.2$
Code: Select all
-bash-4.2$ ls -l movies/yoga-high-quality1500.wmv
lrwxrwxrwx 1 root root 64 Aug 18 07:28 movies/yoga-high-quality1500.wmv -> /var/hda/files/drives/drive7/gh/Movies/yoga-high-quality1500.wmv
-bash-4.2$
Re: Cannot see files on shares after upgrading to Amahi 7.
I personally have ownership for /var/hda/files set to my first admin user:users. Also when you mounted the drives, did you add the depends listed in the wiki for adding drives?
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
-
- Posts: 75
- Joined: Thu Jan 19, 2012 6:52 am
Re: Cannot see files on shares after upgrading to Amahi 7.
When I mounted the drives, I used my old /etc/fstab. So, I had whatever was set up in there.I personally have ownership for /var/hda/files set to my first admin user:users. Also when you mounted the drives, did you add the depends listed in the wiki for adding drives?
Here are the results of ls -al on /var/hda
Code: Select all
root@localhost:~#ls -al /var/hda
total 52
drwxr-xr-x. 13 root root 4096 Aug 18 03:44 .
drwxr-xr-x. 22 root root 4096 Aug 18 19:32 ..
drwxr-xr-x. 7 apache apache 4096 Sep 6 19:05 apps
drwxr-xr-x. 5 apache apache 4096 Aug 26 18:03 calendar
drwxr-xr-x. 2 apache apache 4096 Aug 19 02:05 dbs
drwxr-xr-x. 4 root root 4096 Aug 18 03:43 domain-settings
drwxr-xr-x. 2 apache apache 4096 Aug 19 02:05 drives
drwxr-xr-x. 2 apache apache 4096 Aug 19 02:05 elevated
drwxr-xr-x. 14 patrickdickey users 4096 Aug 19 16:51 files
drwxr-xr-x. 4 root root 4096 Aug 18 03:44 platform
drwxr-xr-x. 2 apache apache 4096 Aug 19 02:06 shares
drwxrwxr-x. 3 apache users 4096 Sep 6 19:05 tmp
drwxr-xr-x. 5 apache apache 4096 Sep 6 19:04 web-apps
root@localhost:~#
Code: Select all
root@localhost:~#ls -al /var/hda/files
total 160
drwxr-xr-x. 14 patrickdickey users 4096 Aug 19 16:51 .
drwxr-xr-x. 13 root root 4096 Aug 18 03:44 ..
drwxrwxr-x 3 patrickdickey users 4096 Aug 22 06:05 ashleymiles
drwxrwxr-x 9 patrickdickey users 20480 Aug 18 07:15 books
drwxrwxr-x 5 patrickdickey users 4096 Aug 18 23:45 docs
drwxr-xr-x 8 root root 4096 Aug 18 04:56 drives
drwx------. 2 patrickdickey users 16384 Aug 18 04:46 lost+found
drwxrwxr-x 9 patrickdickey users 12288 Sep 6 08:24 movies
drwxrwxr-x 303 patrickdickey users 45056 Aug 18 08:54 music
drwxrwxr-x 80 patrickdickey users 24576 Sep 15 00:42 patrickdickey
drwxrwxr-x 35 patrickdickey users 4096 Aug 18 07:23 pictures
drwxrwxr-x 2 patrickdickey users 4096 Aug 18 04:46 public
drwxrwxr-x 11 patrickdickey users 4096 Aug 19 08:36 software
drwxrwxr-x 2 patrickdickey users 4096 Aug 18 04:46 videos
root@localhost:~#
Code: Select all
root@localhost:~#cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Sun Aug 18 07:56:33 2013
#
# 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/hda-root / ext4 defaults 1 1
UUID=18fe9e01-d01e-40f9-969b-4a060f5e2b71 /boot ext4 defaults 1 2
/dev/mapper/hda-home /home ext4 defaults 1 2
UUID=a9603d9e-9a60-4d50-a182-dabd1da0217f /var/hda/files ext4 defaults 1 2
/dev/mapper/hda-swap swap swap defaults 0 0
UUID=5daf66e3-61f2-438e-a288-a218c922434e /var/hda/files/drives/drive1 ext4 defaults 1 2
UUID=ee6b982e-4a79-47af-a2e9-d408591c8935 /var/hda/files/drives/drive2 ext4 defaults 1 2
# UUID=7285bf28-e97c-46ec-a7b5-402a5d76f886 /var/hda/files/drives/drive3 ext4 defaults 1 2
UUID=561975f5-db29-4f89-981c-3c110c64cddd /var/hda/files/drives/drive4 ext4 defaults 1 2
UUID=b6557d0e-9433-41cf-be24-cd40eddac1f8 /var/hda/files/drives/drive5 ext4 defaults 1 2
UUID=f30859b4-6f6d-41d2-aa80-a6afea739f65 /var/hda/files/drives/drive6 ext4 defaults 1 2
UUID=666a5cb2-822c-4994-a2ca-081a6fd55fdd /var/hda/files/drives/drive7 ext4 defaults 1 2
root@localhost:~#
Also here are the cat's of lmhosts and smb.conf from /etc/samba (since I'm not sure if maybe that's where the issue lies)
Code: Select all
root@localhost:/etc/samba#cat lmhosts
# This file is automatically generated. Any manual changes MAY BE OVERWRITTEN
# Amahi configuration, generated on 2013-08-19 16:51:19 -0500
127.0.0.1 localhost
192.168.2.99 hda
192.168.2.99 files
192.168.2.99 hda.local.lan
192.168.2.99 files.local.lanroot@localhost:/etc/samba#
root@localhost:/etc/samba#cat smb.conf
# This file is automatically generated for WORKGROUP setup.
# Any manual changes MAY BE OVERWRITTEN
# Amahi configuration, generated on 2013-08-19 16:51:19 -0500
[global]
workgroup = workgroup
server string = local.lan
netbios name = hda
printing = cups
printcap name = cups
load printers = yes
cups options = raw
log file = /var/log/samba/%m.log
log level = 0
max log size = 150
preferred master = yes
os level = 60
time server = yes
unix extensions = no
wide links = yes
security = user
username map script = /usr/share/hda-platform/hda-usermap
large readwrite = yes
encrypt passwords = yes
dos charset = CP850
unix charset = UTF8
guest account = nobody
map to guest = Bad User
wins support = yes
[homes]
comment = Home Directories
valid users = %S
browseable = no
writable = yes
create mask = 0644
directory mask = 0755
[print$]
path = /var/lib/samba/drivers
read only = yes
force group = root
write list = @ntadmin root
force group = root
create mask = 0664
directory mask = 0775
guest ok = yes
[printers]
path = /var/spool/samba
writeable = yes
browseable = yes
printable = yes
public = yes
[ashleymiles]
comment = ashleymiles
path = /var/hda/files/ashleymiles
writeable = no
browseable = yes
valid users = patrickdickey, ashleymiles
write list = patrickdickey, ashleymiles
create mask = 0775
force create mode = 0664
directory mask = 0775
force directory mode = 0775
[Books]
comment = Books
path = /var/hda/files/books
writeable = yes
browseable = yes
create mask = 0775
force create mode = 0664
directory mask = 0775
force directory mode = 0775
[Docs]
comment = Docs
path = /var/hda/files/docs
writeable = yes
browseable = yes
create mask = 0775
force create mode = 0664
directory mask = 0775
force directory mode = 0775
[Movies]
comment = Movies
path = /var/hda/files/movies
writeable = yes
browseable = yes
create mask = 0775
force create mode = 0664
directory mask = 0775
force directory mode = 0775
[Music]
comment = Music
path = /var/hda/files/music
writeable = yes
browseable = yes
create mask = 0775
force create mode = 0664
directory mask = 0775
force directory mode = 0775
[patrickdickey]
comment = patrickdickey
path = /var/hda/files/patrickdickey
writeable = no
browseable = yes
valid users = patrickdickey
write list = patrickdickey
create mask = 0775
force create mode = 0664
directory mask = 0775
force directory mode = 0775
[Pictures]
comment = Pictures
path = /var/hda/files/pictures
writeable = yes
browseable = yes
create mask = 0775
force create mode = 0664
directory mask = 0775
force directory mode = 0775
[Public]
comment = Public
path = /var/hda/files/public
writeable = yes
browseable = yes
create mask = 0775
force create mode = 0664
directory mask = 0775
force directory mode = 0775
[Software]
comment = Software
path = /var/hda/files/software
writeable = yes
browseable = yes
create mask = 0775
force create mode = 0664
directory mask = 0775
force directory mode = 0775
[Videos]
comment = Videos
path = /var/hda/files/videos
writeable = yes
browseable = yes
create mask = 0775
force create mode = 0664
directory mask = 0775
force directory mode = 0775
root@localhost:/etc/samba#
And I guess one other question is, would removing the drives from /etc/fstab, and going through the process of re-adding them (via the wiki) fix this? If I did it, I would do it the manual way (using the hda-diskmount command and manually entering that information into fstab).
A final question (that I thought of after previewing this post) is this: On my smb.conf, I have the file mask and directory mask set to 0775. In my /etc/fstab on my clients, I have both file and directory mode set to 0777. Would that make a difference?
Here's my /etc/fstab from one of the clients, just to show you what I mean:
Code: Select all
patrickdickey@dcky-ubuntu64:~$cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=a448480b-a267-43a4-9053-82112c447089 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=e5cb85ae-f0c0-419e-aefe-ed072fa28c6d none swap sw 0 0
# Adding networked drives 3-18-13
//hda/Music /home/patrickdickey/Music cifs username=patrickdickey,password=xxxx,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
//hda/Movies /home/patrickdickey/Videos cifs username=patrickdickey,password=xxxx,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
//hda/patrickdickey /home/patrickdickey/myhda cifs username=patrickdickey,password=xxxx,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
//hda/Docs /home/patrickdickey/DocsHDA cifs username=patrickdickey,password=xxxx,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
//hda/Books /home/patrickdickey/Books cifs username=patrickdickey,password=xxxxx,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
patrickdickey@dcky-ubuntu64:~$
Patrick.
Re: Cannot see files on shares after upgrading to Amahi 7.
I would change ownership on the /var/hda/files/drives as well to first admin user:users. Ensure when you do the ownership changes you do them recursively or the files in the folder will not change.
See if that fixes your issue. Also recommend you upgrade Greyhole to the latest version. It did fix some bugs in other areas.
See if that fixes your issue. Also recommend you upgrade Greyhole to the latest version. It did fix some bugs in other areas.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
-
- Posts: 75
- Joined: Thu Jan 19, 2012 6:52 am
Re: Cannot see files on shares after upgrading to Amahi 7.
chown -R drives/ did the trick. And I'm already on the latest version of hda-greyhole (at least that I can see). 0.9.34-1.i386 is my version number.I would change ownership on the /var/hda/files/drives as well to first admin user:users. Ensure when you do the ownership changes you do them recursively or the files in the folder will not change.
See if that fixes your issue. Also recommend you upgrade Greyhole to the latest version. It did fix some bugs in other areas.
Thanks, and have a great day.
Patrick.
Re: SOLVED:Can't see files on shares after upgrading to Amah
Awesome! Glad things are working correctly now. Happy to help.
ßîgƒσστ65
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Applications Manager
My HDA: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz on MSI board, 16GB RAM, 1TBx1+2TBx2+4TBx2
Re: SOLVED:Can't see files on shares after upgrading to Amah
i am actually having the same exact problem (seeing shares from all of my network machines, but connections are refused for what I'm assuming is permissions issues), what do you mean when you say " to first admin user:users." are you saying that we should find the first person that appears in the users group? I'm a little confused, if you could clarify with an example chown syntax or a way that I could verify my groups are set up right that would be appreciated
Who is online
Users browsing this forum: No registered users and 43 guests