I search everywhere if I will lose data in recovery mode so will I? I looked everywhere even in ask ubuntu and found nothing helpful.
When I tried to run fsck on Ubuntu 18.04 recovery-mode I got the following message. Can anyone tell me why?
/lib/recocery-mode/recovery-menu: line 80: /etc/default/rcS: No such file or directory
fsck from util-linux 2.31.1
/dev/sda4 is mounted
e2fsck: Cannot continue, aborting.
I kinda screwed up the /etc directory by running:
sudo chmod 417 /etc
Leaving me unable to use sudo:
sudo: can't open /etc/sudoers: permission denied.
sudo: no valid sudoers sources foundm quitting
Ive been trying to fix it via recovery mode but i'm not sure to what mode I should set it. (I know sudoers is 0440, but this doesnt fix it because /etc is still messed up.)
Oh and for the future, how do i add lines to files in etc without screwing up the permissions of etc?
Thanks in advance, Joeri.
P.S. Im running in Virtual box if that makes a difference.
Edit: Booting in recovery and running:
root@joeri-VirtualBox:/# chmod 755 etc
chmod: changing permissions of 'etc' : read-only file system
root@joeri-VirtualBox:/# cd etc
root@joeri-VirtualBox:/etc# ls -ld
drw-rw-rwx 139 root root 12288 2012-04-19 16:29
Doesnt change the permissions of etc. Doing the same on a self created folder on the desktop does, so chmod is working, just not on etc.
Okay, so I had a dual boot of Tango Studio (based on Ubuntu 10.04) and Windows XP.
Yesterday I downloaded the .iso for Ubuntu 11.10 and attempted to install from a USB (my BIOS won't normally boot from USB but I had PLOP boot manager on a CD). I booted up Ubuntu from the USB and then from there formatted the partition with Tango on and installed Ubuntu 11.10. On booting up I came into Grub rescue mode. So I booted up from the USB again and used boot-repair to reinstall Grub.
After this I would see the normal Grub menu, but on choosing Ubuntu I would come to a black screen. On choosing recovery mode it would begin starting normally with no obvious errors but instead of coming to a cli I would just get a blank screen with a flashing cursor on the top left, not accepting any input.
I have since reformatted and reinstalled from a CD rather than USB and had the exact same problem. I used boot-repair again and the result is the same. Output of the most recent boot-repair is at http://paste.ubuntu.com/869805/
I have also tried editing the ubuntu grub entry and replacing quiet with text nomodeset as I saw in an answer to another question. This got me a bit further - I saw the purple ubuntu loading screen but still came to a blank screen after that. Anyway, in most of the other questions in which that is brought up the user is still able to boot into recovery, while I am not.
Can anyone help? Thanks in advance, let me know if there's any more info I need to provide!
EDIT FOR MORE INFO:
I read something saying it's quiet splash that should be replaced with nomodeset. Earlier I had left splash in the line. So i tried it this way and it froze after displaying the following text:
fsck from util-linux 2.19.1
mountall: Plymouth command failed
mountall: Disconnected from Plymouth
/dev/sda5:clean, 139359/1741488 files, 745830/6961125 blocks
From a bit of googling it doesn't look like plymouth is essential, but I've checked and I do have the most current versions of mountall and plymouth installed so I don't know why there's a problem
EDIT FOR MORE INFO AGAIN:
I used dkpg --reconfigure plymouth cause I saw it mentioned in another forum and it still says plymouth command failed on boot
FOLLOW UP - JULY
Unfortunately I was not able to get this working. I needed it working and switched distribution before anyone commented or answered this question, so am unable to try out any suggestions posted here
I'm thinking of giving this another go sometime soon, if I do then I'll report back.
Can't seem to boot into root shell in recovery mode from GRUB. I try booting into recovery mode from the GRUB menu and don't ever get a shell, just log messages from the kernel bootup. Ctrl+Alt+F1-F12 don't really give me anything important either.