New user : No write access to USB drive

[nick4]

(5th Jan, 2014 09:44 PM)xraxor Wrote:  hi nick4, im not sure what to do as that all I done when I ran into writing problems. I did tho setup the download packages and the packages didn't have write access to media so had to run this command chmod -R 777 /media/USB_HDD_NAME

not sure why this is happening. can yu setup NFS instead?

I tried running the above command, but my drive has a space in it's name. I thought usually it got repalce with an underscore, but that didn't work. Drive name is "Seagate Drive" so I tried to run the command with "Seagate_Drive" but that didn't work. Is there another way to run that line?

Also, do you mean setup Xbian to run as an NFS server? I haven't tried that, and I am not sure where to start. I googled around and found a ton of info about XBMC being a NFS client but not a server.

I formerly had the usb drive plugged into my Mac and running a NFS Server from there. But I could no longer add new shares, XBMC could see them, but not access them. After a lot of googling, I found that I am not the only one that had that problem. Seems the Mavericks upgrade broke a few things. So i decided to plug the drive into the pi itself and moved to XBian at the same time. Running videos with the drive plugged into the Pi is much smoother, so I would like to keep it that way.

Anyway, theres my story, and thanks for your help.

Edit: As a side note, I am able to write to the other files on the Pi, I was able to place and delete a few dummy files in the "Xbian" folder, for example.

---

Edit again:


Ok, sorry for all the posting, it occurred to me that the easiest thing to do here is change the drive name in order to run the command. So, I did that.

Here;s an example of what returned for every file on the drive (i was running as root in ssh, btw):

Code:

chmod: changing permissions of `/media/Seagate/Movies/example/example.fanart.jpg': Read-only file system