fstab question
by pbpersson from LinuxQuestions.org on (#5NWXB)
I first started posting here in 2005 when I knew nothing about Linux at all and I have not posted here for ten years (I have been on the Ubuntu forum). So HELLO AGAIN!
Here is my question, this relates to a Raspberry Pi model 4 running the latest version of Raspbian. When I booted the machine, this is the message I received:
You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" to boot into default mode.
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
Press Enter to continue.
When I would hit enter the screen would blank for a while and then return with two copies of this error message. There was apparently no way to access the command line or recover from this error.
To fix this I changed some options in the /etc/fstab file to change how the system was automatically mounting my 4 external NTFS drives. I have rebooted the machine a few times and I think it is fixed now. :)
My questions are:
1. Is the system supposed to become completely disabled if there is an issue in the fstab file?
2. Is this common for all distros? In other words, is this a feature of the Linux kernel?
3. Is there any graceful way to recover from this error? If this was a "real" desktop I would have booted from a flash drive to fix it but since this was a Raspberry Pi machine I had to pull the SD card and modify the fstab file on another machine.
Thank you! :)
Here is my question, this relates to a Raspberry Pi model 4 running the latest version of Raspbian. When I booted the machine, this is the message I received:
You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or "exit" to boot into default mode.
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
Press Enter to continue.
When I would hit enter the screen would blank for a while and then return with two copies of this error message. There was apparently no way to access the command line or recover from this error.
To fix this I changed some options in the /etc/fstab file to change how the system was automatically mounting my 4 external NTFS drives. I have rebooted the machine a few times and I think it is fixed now. :)
My questions are:
1. Is the system supposed to become completely disabled if there is an issue in the fstab file?
2. Is this common for all distros? In other words, is this a feature of the Linux kernel?
3. Is there any graceful way to recover from this error? If this was a "real" desktop I would have booted from a flash drive to fix it but since this was a Raspberry Pi machine I had to pull the SD card and modify the fstab file on another machine.
Thank you! :)