I am using OpenSuse 12.3 and KDE
I need to start the system without the graphics mode.
I solved my problem by using a disk “live” and accessed the prompt, but it is very time consuming.>:(
How do I start the system with the mode command prompt?
Thanks in advance
Supposing you always want to start in a terminal
Yast-System-boot loader options add a space 3 to the line Optional kernel command line parameters
This will cause a boot to init level 3 which is a terminal
We need to start in terminal mode only when troubleshooting.
In this way you suggested, the options to enter in the graphical mode, continue to be available in the grub?
If only for trouble shooting press at the grub prompt which puts it in edit mode scroll down to line that start linux press end key put space and a 3 press f10 to continue boot
I think gogalthorpe meant to type:
“press e” when at the grub2 screen (the list of OSes you have installed)
Then find the line that starts with “linux”
press “end”
enter a 3
Then press f10, to boot to a prompt.
Thanks for the tip, but the problem I have now, does not let the system go up to grub
So?
What do you guys do when the system does not come to the grub?
And we want to get to the command prompt without using a live cd ?
Is it possible?
Any idea?
No.
Without a boot loader you cannot boot your system. Period.
You have to boot from a LiveCD/USB (or a different hard disk) and restore the boot loader.
I do not need to boot my system. (for now)
Only there is a problem in the system load, just in my fstab.
This problem in fstab does not let go until the boot grub
But, after this point, the boot loader is working fine. So, i don’t need to fix the boot loader
I need to go into terminal mode when this problem occurs and edit my fstab
Already solved the problem by using a LiveCD, but a solution is time consuming and I believe that this problem may occur more often and would like a faster solution.
If it is as you say, there is no other solution than use a live CD, but, is not there any more feature?
Then you don’t have a problem with the boot loader (grub).
The boot loader has absolutely nothing to do with /etc/fstab. It doesn’t even look at /etc/fstab.
But your question was:
If grub doesn’t load, there’s no other way than to boot from a different disk.
I need to go into terminal mode when this problem occurs and edit my fstab
Already solved the problem by using a LiveCD, but a solution is time consuming and I believe that this problem may occur more often and would like a faster solution.
If it is as you say, there is no other solution than use a live CD, but, is not there any more feature?
That’s a completely different story.
Your boot loader (grub) is working fine.
And you were already told how to add “3” to the kernel boot options to get to runlevel 3.
If you’re using grub (not grub2), just enter that at the boot menu prompt.
If runlevel 3 doesn’t work, you can even try “init=/bin/sh” to get to a minimal text system.
The fstab runs before grub.
If there is any problem in fstba, grub will not be executed. Is this my case.
My fstab have problems generated by NFS shares.
But your question was:
If grub doesn’t load, there’s no other way than to boot from a different disk.
That’s a completely different story.
Your boot loader (grub) is working fine.
And you were already told how to add “3” to the kernel boot options to get to runlevel 3.
If you’re using grub (not grub2), just enter that at the boot menu prompt.
If runlevel 3 doesn’t work, you can even try “init=/bin/sh” to get to a minimal text system.
Sorry, but do not know where to put this option “3”
Also do not know where to put “init = /bin/sh”
Can you explain in more detail?
My system uses grub2
Nonsense.
You mix up grub and systemd (or something else) I guess.
grub just shows the boot menu, then loads the kernel and initrd and hands over.
It doesn’t even know (or care) about an fstab.
Sorry, but do not know where to put this option “3”
Also do not know where to put “init = /bin/sh”
Can you explain in more detail?
My system uses grub2
As I said, already answered in this thread:
If “3” doesn’t work, add “init=/bin/sh” instead.
On 2013-11-10 15:36, sergelli wrote:
>
> wolfi323;2596961 Wrote:
>> Then you don’t have a problem with the boot loader (grub).
>> The boot loader has absolutely nothing to do with /etc/fstab. It
>> doesn’t even look at /etc/fstab.
>>
> The fstab runs before grub.
NEVER.
Please believe us, we likely know more than you about this.
> If there is any problem in fstba, grub will not be executed. Is this my
> case.
FALSE.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
When I started my PC the grub appeared, but the system did not come up.
Then I pressed the ESC key and I see the load was standing in a line that was carrying some NFS service. But do not leave it.
Any pressed keys as f1, f2, f3 … f12, restart the load from a point that I can not remember, but do not restart the grub screen and go back to stop the load.
As the grub did not show up, I thought the contents of fstab is used grub before being rotated.
Certainly, I’m wrong. Sorry about that.
Now, I rebooted and followed his instructions when he appeared the grub.
Only put “3” did not work, but adding “init = /bin/sh”, I got to access the command line.
Thank you, I apologize again.
You were wonderful.
init level 3 still tries to use the fstab file to mount things but init = /bin/sh only mounts root. I think you can also use init level 1 ie put a 1 in the boot line.