Permissions Error (solved)

Beta Community DVR Beta
#1

I’m using a dedicated USB drive on my iMac. Today I started getting permissions errors:
2017/04/30 21:00:00 [DVR] Starting job 1493600400-10 Madam Secretary on ch=[9.1]
2017/04/30 21:00:00 [DVR] Starting job 1493600400-7 Chicago Justice on ch=[4.1]
2017/04/30 21:00:00 [DVR] Waiting 1h59m59.846734961s until next job 1493607600-1 News4 at 11
2017/04/30 21:00:00 [TNR] Opened connection to 1048F66D for ch9.1
2017/04/30 21:00:00 [TNR] Opened connection to 1048F66D for ch4.1
2017/04/30 21:00:00 [TNR] Closed connection to 1048F66D for ch9.1
2017/04/30 21:00:00 [DVR] Error running job 1493600400-10 Madam Secretary: mkdir /Volumes/DVR 1: permission denied
2017/04/30 21:00:00 [TNR] Closed connection to 1048F66D for ch4.1
2017/04/30 21:00:00 [DVR] Error running job 1493600400-7 Chicago Justice: mkdir /Volumes/DVR 1: permission denied

I don’t have any issue opening the drive and reading it. I unchecked ‘enable DVR’ and now I get the following error when trying to check it:
Error: unable to create dvr directory: mkdir /Volumes/DVR 1: permission denied

#2

Solved. I had created a share on my NAS named DVR (never used), and the USB drive is named DVR. Reboot cause confusion between the two, unmounting the ‘DVR’ hare on the NAS fixed everything.

1 Like
#3

Having the same issue with the Synology NAS. It is connected to Mac using admin account.

NAS has shared folder called DVR and admin has read / write.
I am logged into Mac with user account that is not 'admin'.
I try to set up storage in Channels Settings using /Volumes/NASName/DVR and get the " Error: unable to create dvr directory: mkdir /Volumes/NASName: permission denied".

Can you see what is incorrect in this setup?

Thank you.

#4

Recently, I had a few of my TV Show folders switch to root ownership and therefore I wasn't getting any new recordings due to permissions problems. There were no permissions issues on the help diagnostics screen.

I thought maybe my Ubuntu installation got messed up by something. I set the folders back to my ownership with read/write and they have been fine since.

Perhaps this is actually a bug?