Boot only in recovery mode

lucaspeed · 2023-01-29 10:44:48

Hi, I have Beryllium installed on a Mac Mini since mid-January.
I use it on a daily basis for light tasks, yesterday I powered it off like every day but today boots only in recovery mode. Screen remain black even booting in TTY login.

I tried the usual journalctl -xb in recovery but, to my knowledge, I can't see anything in logs that could stop the boot process.
It's useful to know that it is a vanilla installation, I made only Bunsen updates.
Anyone has something to suggest?

Thank you.

EDIT: Strange thing is, removing "quiet" from the default GRUB entry makes the entry bootable.

Last edited by lucaspeed (2023-01-29 13:57:44)

rbh · 2023-01-29 14:01:31

lucaspeed wrote:

I tried the usual journalctl -xb in recovery but, to my knowledge, I can't see anything in logs that could stop the boot process.

From "man journalctl":
-b [...] Show messages from a specific boot. This will add a match for "_BOOT_ID=".
The argument may be empty, in which case logs for the current boot will be shown.

The boot into recovery mode, is not halted... But, the interesting thing to know, is why the system boots to recovery mode. Often you get a screen message why.
It's curious you can boot to rescue mode but not to tty.
You can not boot to runlevel 3? Edit grub parameter, add "3", as boot parameter.

If you after unsuccessful boot to tty, reboot to rescuemode, can't you get vital info in the logg from previous boot? ("journalctl -xb 1").

This laptop can't boot to graphical target. For some months ago, it just hang with dark screen. Boot to runlevel 3, was ok. After logging int, command "startx" was successfull. Some weeks ago, X loads directly after logging in... Has not bothered to debug the system...

Most often when system boots to rescue mode, it's because of drive problems. Corrupt file system, missing partition (swap) or differenc between fstab and reality.

Have you run fsck on the drive(s) and compared fstab with reality?

lucaspeed · 2023-01-29 14:17:15

I checked the drive with fsck booting from a live USB, and it was ok.
As you can see in my updated post, the difference in normal and recovery entries are "quiet" in place of "single", so I tried removing "quiet" in the GRUB entry and that solved the problem.
I don't know why, I'd really like to know!

Last edited by lucaspeed (2023-01-29 14:18:32)

rbh · 2023-01-29 22:10:55

lucaspeed wrote:

so I tried removing "quiet" in the GRUB entry and that solved the problem.
I don't know why, I'd really like to know!

But that is impossible. You must have done some more changes.

The boot parameter "quiet", is to suppress boot messages. That is the only thing it does. If you can boot correct now, your system should still boot ok if you ad back "quiet".

Did you change directly in /boot/grub/grub.cfg? It is recommended to edit /etc/default/grub and run "sudo update-grub". If you did that, the update might have fixed your boot problems.

Btw, default BL install, has boot parameters "quiet splash". I allways change to " nosplash", as I want to see boot messages.

lucaspeed · 2023-01-29 22:41:35

Yes, I obviously used update-grub. In my installation I had only quiet and I see boot messages.
Tomorrow I will try to add "quiet" again just to see what happens.
Thank you

lucaspeed · 2023-01-31 04:26:37

Strange enough, adding "quiet" again makes the system unbootable. Never saw anything like that!

#1 2023-01-29 10:44:48

Boot only in recovery mode

#2 2023-01-29 14:01:31

Re: Boot only in recovery mode

#3 2023-01-29 14:17:15

Re: Boot only in recovery mode

#4 2023-01-29 22:10:55

Re: Boot only in recovery mode

#5 2023-01-29 22:41:35

Re: Boot only in recovery mode

#6 2023-01-31 04:26:37

Re: Boot only in recovery mode

Board footer