Losing Permissions on Share

[phreaq]

I am copying files from one server (WHS) to a new Amahi 7 server.

I have copied about 2 TB so far, and an error has now popped up, and I no longer have permission to write to the amahi share.

I rebooted the amahi, and I was able to write to the drive again, but then I loose permissions again, within 5 to minutes.

When this occurs, I can write to other shares without issue. A reboot does resolve the problem.

So far, it's happened on two different shares/drives, even though 2TB has transferred so far.

Any ideas why is this happening?

[bigfoot65]

Recommend you check the permissions and ownership of the shares you are having issues with. They all should be owned by the 1st admin:users recursively.

[phreaq]

I ran 'sudo chmod -R 777 /var/hda/files/drives/drive5' and .../drive6 previously, but ran it again.

I just lost permissions again, after copying files for 15 minutes or so.

Now when I runn the 'sudo chmod', it says many lines that say:

chmod: changing permissions of â/var/hda/files/drives/drive6/Public/xbmc files/sabnzbd - appdata - local/logs/sabnzbd.log.1â: Read-only file system


During a reboot, it does take about a half hour to do, with a lot of hard drive activity. Perhaps I should run fsck?

[bigfoot65]

Sounds like maybe the drive is not mounted properly. Ensure it's mounted for read and write. The wiki has guidance for mounting the drives and the proper /etc/fstab entries.

[phreaq]

I followed the wiki, and have this in my fstab

#
UUID=019b8a7c-9720-4945-8fec-4f46f90ec54b / ext4 defaults 1 1
UUID=fed3b8b7-cfe7-4d0b-b574-25b56756e558 /boot ext4 defaults 1 2
#
#
#PB-1 HDD1 (top)
UUID=4280317b-e59d-46af-bc56-ab5423815da8 /var/hda/files/drives/drive5 ext4 defaults 1 2
#PB-1 HDD2
UUID=ba1def0b-d473-47b4-91d3-56499ae62066 /var/hda/files/drives/drive6 ext4 defaults 1 2

[phreaq]

I am also receiving a '502 Proxy Error' when running post-processing in SickBeard. Could that be related to the permissions issue?

[phreaq]

It appears I do have drive issues.

I connected a monitor to my headless server and saw the errors.





I'll see what fsck finds

*this forum wasn't letting me add a file, hence the link

[bigfoot65]

Ok, hope you sort it out. Please let us know if we can be of further assistance.