Unable to install binary for splashscreen?

[pjft]

Hi all, hope you're doing great.

I decided to run a full update of my RetroPie setup, from 4.0.x to the latest one (4.1.x?).

Anyway, I updated the setup script, then all installed packages. However, I got an error on updating the splashscreen binary. Here's the log:

chown: changing ownership of ‘/home/pi/RetroPie/splashscreens’: Operation not permitted
chown: changing ownership of ‘/home/pi/RetroPie/splashscreens/README.txt’: Operation not permitted
Unable to install binary for splashscreen

Log ended at: Thu 9 Feb 06:51:27 GMT 2017
Total running time: 0 hours, 0 mins, 1 secs

I know that the chown errors are related to me having a USB drive mounted on the RetroPie folder - so far so good - but I didn't expect this to prevent the binary (whatever it is?) to be installed.

I confirm that the README file has been touched at least - its date is from today - but I see nothing in the folder other than the retropie-extra folder.

I wonder if there should be anything else there, or if it's just an overreaction to not being able to change ownership by the setup script.

This is by no means a blocker for me, just surfacing and wondering if it's working as intended or if I'm missing something.

Thanks, and have a great day.

[meleu]

@pjft Where exactly is your USB drive mounted? Maybe it's mounted as read-only...

I think the chown commands are executed in the install_bin_splashscreen() function and is failing because of the USB drive.

The "Unable to install binary" seems to be the error message when something goes wrong in a scriptmodule's install_bin_* function (as we can see here).

[pjft]

Thanks Meleu - and good to hear from you.

You may be right in regards to the message reason - it might just be a regular exception handling message, as I see it here.

I looked into whether it's read-only or not, but in fact it doesn't seem to be the case. I believe the chown errors are caused by the drive being FAT32, which has no support for the chown Linux permission setting.

Still, not a bother - splash screen still shows, no concerns. Just curious if anything was missing. :)

Thanks!

[herb_fargus]

@pjft
Didn't realise fat32 didn't chown learn something new every day.

Wonder if formatting it as ext4 would at least resolve the errors. Anyways glad it still works. Automounting is still a bit of a preliminary support. It will likely be improved a bit in the future

[pjft]

@herb_fargus Thanks for the reply.

Yeah, coming from a MS DOS/MS Windows background I'm certainly not a linux expert so I'm constantly being surprised at the small nuances here and there. I suspect formatting as EXT2/3/4 would help, but that would defeat my purpose of then having it easily readable/accessible on my desktop (which is non-Linux). :)

I did hack away with OSX Fuse this morning to read a EXT4 partition from a previous backup of mine on a Macbook (it seems the retroarch update must have either removed the previous shader folders I had, or changed their locations, so I'm going to copy them back).

I had mounted this manually from back in 3.6/3.7, and it has always worked perfectly asides from these chown errors which I take are par for the course using FAT32 in the current set up :)

No big deal anyway, it's always fun. Thanks everyone!