Hello
I wonder if during the boot it is possible to to discard the graphics mode and go straight to the prompt.
How I do it?
Thanks in advance.
And what exactly do you mean with that?
If you want to boot straight to text mode, choose “multiuser-mode” as default target in YaST->System->Services Manager, or run “systemctl set-default multi-user.target”.
You could also add ‘3’ to the boot options, permanently in YaST->System->Boot Loader or /etc/default/grub. For a one-time action, press ‘e’ at the boot menu and append ‘3’ to the line starting with “linux” or “linuxefi”, then press ‘F10’ to boot.
If you want to get rid of the graphical boot splash screen, add “plymouth.enable=0” to the boot options (see above), or uninstall plymouth completely.
My machine will not turn on the opensuse.
The boot is not coming to the graphics mode.
So, I have no way do these configurações.que you’re suggesting.
The reason is because the machine can not mount a external device contained in a fstab line
The boot is trying to set up this line of fstab, but not out of it.
Thus, I wish to interrupt the boot, log and edit the fstab
I know I can do this with a live disc, but I’m using a netbook, it does not have cdrom
Nothing of what I suggested needs graphics mode. You can even run YaST in text mode.
But apparently you don’t even get to a text mode login?
Well, that’s the problem when people only ask a specific question without telling what the actual problem is…
If the boot is stuck at the graphical boot screen, just press ESC or Ctrl+Alt+F1 and you should be able to login. Actually in your case you’ll probably be in “emergency mode” then and would have to enter the root password. You should be able to “fix” your fstab then.
The reason is because the machine can not mount a external device contained in a fstab line
The boot is trying to set up this line of fstab, but not out of it.
Thus, I wish to interrupt the boot, log and edit the fstab
Try single user mode then, i.e. append ‘1’ or ‘S’ to the kernel boot options like I mentioned before.
Or if not even this works, try “init=/bin/sh”. You should get to a basic text mode system then, without any system services started.
I know I can do this with a live disc, but I’m using a netbook, it does not have cdrom
You can put a Live ISO onto an USB stick/drive as well and boot from it.
If you dual boot with Windows 8 or above be sure that you turn off FAST boot in Windows. It leaves the Windows partitions dirty and unmountable in Linux.
I did not explain right.
I can not open the OpenSuse on my NetBook
The boot does not progress when the boot try to mount the shares that are in the fstab.
So I do not have the yeast and can not configure anything
I need to stop the boot and enter a screen with command prompt
It is possible, without a Live ISO?
I only use the OpenSuse.
Wolfie gave instructions on how to boot to text. If that does not work then show the error you get
Ok.
I’m wondering how do I get out of the boot, which has not yet opened the OpenSuse (and can not open it) and have a prompt to log in as root and edit the fstab.
But if to help me, you need to see the messages that appear at boot time, so I’ll make a photo from my netbook screen and post here in this forum. But as few can do it here a few hours because I’m away from my netBook.
But I can guarantee that the boot is still trying to mount shares from other PCs and the boot can’t open the OpenSuse.
Have you actually read my replies? :\
Again: try to press the ESC key on your keyboard, or Ctrl+Alt+F1.
If that doesn’t help, press ‘e’ at the boot menu and append ‘1’ or ‘S’ to the line starting with “linux” or “linuxefi” and press ‘F10’ to boot.
You should get to a text mode login then.
In the worst case (if all of the above doesn’t help), press ‘e’ at the boot menu, append “init=/bin/sh” to the line starting with “linux” or “linuxefi” and press ‘F10’ to boot.
wolfi has already explained this to you. You must read and follow the instructions he gave you.
This will bring you a command prompt where you will be able to do what you need to do to get your system working properly.
To the OP,
You need to be exact in describing what you see in your boot process.
The first milestone (after BIOS) is the Grub menu, do you see a graphical menu with selections for your kernel and “Advanced” ? If you are unable to see this, then your disk is not read correctly.
If you can see the Grub menu, then you should select “Advanced” and on the next screen select the second entry (not the top entry) which should be your Recovery/Emergency boot.
That should hopefully allow you to boot into a working OS with a working network connection but without running the full, advanced capabilities of a full OS.
If the above doesn’t work, reply with what you tried and at what point you weren’t successful.
TSU
Please excuse me for this failure.
I really do not know why I did not see your instructions before.
Just like you teach, before and during starting the boot, I keep typing “e” key and in the screen that appeared I put “1” at the end of the line that begins with the word “linux”. So I went straight to the command prompt and I could come in as root.
After that, I edited my fstab adding “noauto” in all lines that mounted external shares. and restarted the machine.
Now the machine is ok
It would be great that OpenSuse administrators undo the update that causing this problem because before I did not have to use “noauto” in my shares called by fstab.
Thanks for your time
With the auto option, the device will be mounted automatically at bootup or when the mount -a command is issued. auto is the default option. If you do not want the device to be mounted automatically, use the noauto option in /etc/fstab. With noauto, the device can be only mounted explicitly.
nofail is better in many cases since it only fails if the partition is not found or unmountable for some reason
What partition are failing? You may want to check them
If the partitions can not mount then the proper action happened and perhaps the updates simply fixed something that was broken.
Yes. Your guidance is correct, but I reaffirm that OpenSuse administrators should prevent the boot locking in case of failure one EXTERNAL assembly.
Before this never happened.
???
If you add an entry to the fstab, it is mounted automatically by default and considered as required for the system (unless you specify noauto and/or nofail).
See also “man mount” and “man systemd.mount”.
If a required service cannot be started, the system drops to emergency mode. That’s intended behavior and not even new with systemd.
The only issue I can see from your description is that apparently the boot splash wasn’t removed correctly.
Or did the system hang?
AFAIK there was such a problem with emergency mode not working in 13.1 (if rsyslog is installed IIRC), but that should be fixed meanwhile.
Before this never happened.
That behavior is the same since years.