Thanks for all the replies! If I was home, this would have been a few minutes to check/verify. However I'm out of town, and have a Microsoft Surface Windows machine from work, and a Chromebook (and today I was babysitting my 1 yo toddler granddaughter so progress has been excruciatingly slow). I'm trying to create a bootable USB drive on Windows now, but now that's throwing an error when it gets 20% in. Fun times.
I don't ever remember setting up any ACL's for that directory... Whenever I looked at them in the past I thought they'd be a headache and abandoned the idea. It is a /home/user/ directory that I backed up, have chmod commands in the script, had verified working months ago, but foolishly assumed everything would still be working now... Once I can get to it as root, I can verify perms an chown --recursive too. Ugh! I hadn't seen ChromeOS decided to deprecate ext4 support. *sigh* Hopefully I'll have positive news soon... Of course I'm going back home this weekend. I can just access the files directly from the server once I'm back ---Paul. On Wed, Jul 24, 2024 at 11:40 PM Dan Bacus <[email protected]> wrote: > Hi Paul, > > I hate to even ask because they are the bane of my existence, but have > you checked ACLs just in case they are denying access somehow? Especially > at a directory level? (Lord, but I hate those sneaky little buggers...) > > Has a user been defined to match the UID of the file owner from the > source system? If not, maybe "chown -R 0:0 /mount/point" to get everything > owned by root, and a group of root, at least? I claim to know absolutely > nothing about Chrome OS, so I have no idea how it deals with file access > when ownership of a file can't be traced back to a valid user name. > > Less likely to be an issue, but have you done a "ls -ld /mount/point" > to see permissions on the mounted filesystem's mount point? Back when I > taught the troubleshooting class for Sun Microsystems, one of the problems > we gave students was doing "chmod 0000 /", resulting in only the root user > being able to log in. No other non-root users could log into the system. > Troubleshooting as root, students would check perms on /etc, /home, /usr, > /etc/passwd, /etc/shadow, and the like; but only rarely would someone think > to do "ls -ld /" to look at permissions there without a little nudge from > the old instructor. If you can't read / - well then you can't read > anything anywhere below it either... > > I'm sorry that I could not be of any more help. Best of luck to you! > > Dan > > On Tue, Jul 23, 2024 at 11:35 PM Paul Boniol <[email protected]> > wrote: > >> So... I've got an external drive I used to copy files from my Linux >> computer. The partition is ext4. >> >> Some directories I can access on the Chromebook, but others I can't. >> >> I tried changing all the directory permissions to 0777 and all the file >> permissions to 0666 on the problematic directories/files, but I am still >> getting "Your file couldn’t be accessedIt may have been moved, edited, or >> deleted. >> ERR_FILE_NOT_FOUND" >> >> Everything I've found online points to not being able to mount the whole >> partition. But it is mounting, and other directories (which were close if >> not identical permissions) I can read just fine. >> >> I know Chrome OS is a bit out of scope, but hoping someone has some idea >> what else may be wrong. >> >> ---Paul. >> >> -- >> -- >> You received this message because you are subscribed to the Google Groups >> "NLUG" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/nlug-talk?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "NLUG" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/nlug-talk/CAL9PgS0ESWtqEe4CVqowEAVzgn-2UEwfpVLfXXbtjNXcAmCXaQ%40mail.gmail.com >> <https://groups.google.com/d/msgid/nlug-talk/CAL9PgS0ESWtqEe4CVqowEAVzgn-2UEwfpVLfXXbtjNXcAmCXaQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > -- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/nlug-talk/CAEH-QC9XAq5aCvi_XZu%2BZ9yRuB43AE02ygMzdydOP-6wtcUNYQ%40mail.gmail.com > <https://groups.google.com/d/msgid/nlug-talk/CAEH-QC9XAq5aCvi_XZu%2BZ9yRuB43AE02ygMzdydOP-6wtcUNYQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nlug-talk/CAL9PgS1oQgcJ-NRwMEsWSwcfi%2BB7K_SYn4LBkhM2Ws8BQkg1Xg%40mail.gmail.com.
