Gamelist Locations

hansolo77

How can I fix it then?

chipsnblip

i'd first start by verifying the permissions/ownership of your home directory:

$ ls -la / | egrep home

drwxr-xr-x 3 root root 4096 Mar 13 14:55 home

then keep digging:

$ ls -la /home | egrep pi

drwxr-xr-x 12 pi pi 4096 Jul 8 02:43 pi

$ ls -la /home/pi | egrep RetroPie

drwxr-xr-x 6 pi pi 4096 Apr 14 10:27 RetroPie
drwxr-xr-x 9 pi pi 4096 Jul 3 03:11 RetroPie-Setup

hansolo77

@chipsnblip here are my results:

ls -la / | egrep home

drwxr-xr-x 3 root root 4096 Mar 13 17:55 home

ls -la /home | egrep pi

drwxr-xr-x 13 pi pi 4096 Jul 10 12:48 pi

ls -la /home/pi | egrep RetroPie

drwxrwxrwx 1 root root 4096 Jul 1 00:32 RetroPie
drwxr-xr-x 9 pi pi 4096 Jun 30 23:50 RetroPie-Setup

Sano

Just to be sure : is your RetroPie folder on the SD, or do you have some manual mount on USB key, NAS, ... ?

hansolo77

The RetroPi folder is mounted on a usb hard drive..

Sano

Was sort of obvious when you said chown was not working.
You have to add uid=1000,gid=1000 in the options part of your fstab line, then.
And of course umount/remount the FS.

hansolo77

Where? Currently my /etc/fstab line has this:

UUID=80B89CC9B89CBF5A /home/pi/RetroPie ntfs nofail,user,umask=0000 0 2

Sano

UUID=80B89CC9B89CBF5A /home/pi/RetroPie ntfs nofail,user,uid=1000,gid=1000,umask=0000 0 0

hansolo77

No 2 on the end then? Sorry I don't know much about this part of the build, copied from somebody else found through Google. :)

Sano

@hansolo77
Last field is for fsck pass number when rebooting.
AFAIK fsck (so last digit of fstab lines) is only for unix filesystems.
You may repair ntfs on linux with ntfsfix, but it has limitations, and you should use a windows computer instead.

hansolo77

I do use Windows. I think there are 2 things I did wrong here. Firstly was with the fstab, and secondly was my backup process. When I built my system, I backed up the RetroPie folder to my server, so I would have easy access to the BIOS and ROMS folders so I could just easily copy them back over if the drive fails. Rather than remove the drive and connect it to the computer, I downloaded all the files to the server with SFTP. When I started building my brother's system, I just re-used those same files, and SFTP'd them back over (again, without connecting the drive directly). I think it wrote the files over with the wrong permissions. I should have just connected the drive and copied them over that way. Would have been faster too. Live and learn I guess.

Sano

@hansolo77
So is your problem solved ?

hansolo77

Looks like it could be. I'm about to leave for work so I will test more tomorrow. But quick glances show it now has that whole path set up as pi:pi.