I'm experiencing new "glitch". When I try to run scripts via keyboard shortcut in Cinnamon (Linux Mint 21) there is a window with error:
scriptname failure to remap file to open file descriptor (no such file or directory).
Interestingly web search had not found exact error, so I post the question in hope of learning more about Linux system I'm using. Then I was able to run scriptname
from bash terminal which I had opened before "glitch" running my chroot
script.
Also most GUI apps do not start. Making new tab in terminal results in tab with:
failed to open PTY no such file or directory.
That pointed me to discover that many of files in /dev
are gone. I've been doing script with chroot
and that script was run many times before with slight changes, it unmounted and deleted files in chrooted temp working folder, why files in root /dev
got deleted? I still have not understood.
I'd like to know how to restore full functionality w/out reboot. Looks like quick restore of /dev
is not available, from this answer
"With devtmpfs, the only automated method might be a reboot.
What files do you advise me to make manually in /dev
?
Also, any ideas for "failure to remap file" error? TIA
P.S. Ah, one more thing. After I've discovered the glitches above I've tried to start new console via Ctrl+Alt+Fx (with PTY errors, wasn't it foolish?), got blinking prompt, switched back and now my keyboard/trackpad do not work. I've got idea to connect externals via USB and they work. Ideas how to restart laptop's keyboard?
/dev
with a fresh install. "failure to remap file to open file descriptor" might be an error message for a failedfreopen
. Unfortunately it doesn't tell you the file name that does not exist. (Maybe you should not run commands asroot
unless absolutely necessary. Maybe insufficient error handling or preconditions checking in your script.)_make_custom_liveusb.sh
), apart from changes which I had not thought important for mount(s). I have a suspicion addedrsync -a /folderX /folderY
of a location of a mount (mount ... /folderX
) might somehow messed things up.root
) even if a previous command failed which may lead to unexpected results. You don't know what all went wrong and what all got deleted or overwritten. I suggest to back up your data and reinstall and be more cautious when running scripts that execute commands asroot
.