- This topic has 20 replies, 3 voices, and was last updated 3 years, 4 months ago by
.
-
I checked the sdcard – it is not currupted.
Of course burning new image would be an option but as I dedicated lots of time to set it up I would like to avoid doing this again.
for troubleshooting steps you might consider:
1. I deleted the mountpoints in /etc/fstab
2 I added one of them with m2p gui – success
3. I checked /etc/fstab modification date after adding -08:51
4. I pressed delete on the newly added mountpoint in m2p gui at 08:53, for several seconds icon of turning gear apears – then it refreshed – feedbacj no message if removing was succesfull or not – just a refresh where the mountpoint is still present
5. INTERESETING – there were no changes in /etc/fstab but modification time of /etc/fstab changed to 08:53 so the time when I pressed „delete“ in guiSo to me there is no corruption but a bug in the file parsing /etc/fstab
I had a similar issue a month ago. I could not add nor delete mount points.
I’m guessing the problem might be with a kernel upgrade.It looks like a permissions issue somewhere.
I changed the permissions on /etc/fstab (owned by root) from 644 to 666 and was then successful updating the mount points. I’ll see if I can isolate where the edit is performed to see how max2play modifies the file.Maybe the modification is not elevating privileges properly?
Edit: The change I mentioned above is not a proper fix due to security concerns.
Edit2: I checked and this page runs under user www-data and does not appear to request a privilege elevation.
You must be logged in to reply to this topic.