Mageia forum

Computer running Mageia 9 that I'm accessing remotely went down, and did not boot, showing filesystem errors on one mirror raid.
The booting process stopped asking for root password or Control-D options, but it was showing typed password and pressing enter did not enter the console, Control-D also did not worked (nothing happened).
Choosing failsafe from GRUB menu directly was no difference. On "tty 12 " I have seen messages about skipping failsafe console, I do not remember the message but it sounded like there was not enough reasons to start maintenance. Booting with rd.break was working.
I actually used live Mageia to skip mounting this file system, then booted original system without any additional problem and check and fixed corrupted file system.
So everything is working I'm just curious if anyone encountered same behavior that I thing shouldn't exist the system should go to maintenance mode if this is the option chosen from GRUB menu.

rychok wrote:The booting process stopped asking for root password or Control-D options, but it was showing typed password and pressing enter did not enter the console, Control-D also did not worked (nothing happened).

Ctrl-D will usually not help at all if you cannot boot normally (in emergency mode).
Are you sure that you actually entered the correct root password ? What error message did you get there ?

rd.break (which is basically the same as using something like init=/bin/sh which doesn't work for many newer distros who use sulogin in their pam configuration) works around the login requirement as the kernel basically starts a shell directly.

I have entered correct password, and like I said the typing was visible, usually it is hidden.
Control-D did not work in sense that pressing this combination did not go any forward same like entering root password.
Base on messages from "Ctrl-Alt-F12" the maintenance service was skipped the shell did not start.
I can not reproduce this, the strange thing is that the corrupted file system is only some storage nothing related to system boot, but it was required to be mounted in fstab.

Well, I cannot reproduce either. Using failsafe (it's actually called Recovery Mode here) login as root works just fine.
If you cannot reproduce please mark this thread as [DONE].

I know, at that time I have tried same thing on my laptop and it was fine, it must have been some specific situation that cause that.