Problem with boot mageia

[norberto]

Hola : Despues de unos problemas con Mageia 2 beta 1, decidi reinstalar el sistema para solucionar el problema que tenia.
Instale Mageia de 64 bits,escritorio kde y gnome, y al final de la instalacion me preguntaba si queria actualizar los paquetes y acepte.

Luego de la actualizacion , al reiniciar, daba tres errores en pantalla, lo cual creo, es lo que no me deja iniciar la cesion de linux :

Hello : I was problem with mageia 2 beta 1, and reinstall the system for solution the problem.
I was intall mageia 2 beta 1 with desktop kde and gnome, and update the system in the installation.

Next, in the boot, of the system, i find 3 errors :



Failed to load start kernel moudles............................................................failed

Failed to load legacy module configuration..................................................failed

started initialize storage subsystem(Raid,LVM,etc.).......................................ok

Dependency failed. Aborted start of /media/win_g

Dependency failed. Aborted start of Relabel all failsystems, if necesary

Dependency failed. Aborted start of Mark the need to relabel after reboot

Dependency failed. Aborted start of setup link in /boot for running kernel

Welcome to emergency mode. Use "systemctl default" or ^D to activate default mode.

Give root password for maintence
( or type Control-D to continue):

Si tipeo Control-D vuele a lo mismo :

Welcome to emergency mode. Use "systemctl default" or ^D to activate default mode.

Give root password for maintence
( or type Control-D to continue):




Muchas Gracias

Thanks.

PD: Estos errores ya me los generaba antes de reinstalar el sistema, luego de una actualizacion.

[linuxero]

I suggest you enter the root password, try fsck your disks, then try again

(intenta controlar los discos con fsck como root y reinicia a ver..)

Code: Select all

# fsck.extx -cfv /dev/sdxx


[norberto]

I install mageia 2 beta 2 and i can run linux with desktop kde. I install Kde only.
(Instale mageia 2 beta2 con escritorio Kde y pude ingresar , pero sigo teniendo dos errores)

But two errors no disappears :

Failed to load start kernel moudles............................................................failed

Failed to load legacy module configuration..................................................failed

Gracias

[doktor5000]

But two errors no disappears :

Code: Select all

Failed to load start kernel moudles............................................................failed

Failed to load legacy module configuration..................................................failed


Those two errors are no real problems, you can ignore them.

I suggest you enter the root password, try fsck your disks, then try again

Code: Select all

# fsck.extx -cfv /dev/sdxx


If those disks are not ext, this will fail, if you propose commands, use the most common ones. In this case just

Code: Select all

fsck -v /dev/sdxx

Also you should explain the commands if it's not obvious, your example will also run a badblocks test and it will
force that even if the filesystem is marked clean, depending on the size of the partition to check, this check will
take hours!

On the other hand, that check would be useless in this case, there's no sign that the filesystems are damaged,
it's only that systemd didn't boot to multi-user or graphical.target, but to emergency shell. This is rather common for current
cauldron, especially after upgrades from previous installation. Your help is appreciated, but you also have to do it properly

[linuxero]

Sure, however I deduced from the explanation that the system was installed using default values, so EXT4 I must say..I might have been sleepy then.

As for put it properly you're right..as a matter of fact I should have mentioned that he should do that using the rescue system option when booting the installation medium

Great to learn with you guys

[doktor5000]

Sure, however I deduced from the explanation that the system was installed using default values, so EXT4 I must say..I might have been sleepy then.

Well, no real need to, fsck will figure out itself what particular fsck it needs to run. But the other way round it will not work

[mrigs]

Hi all,

I ran into the same problem and going thru the thread I tried -

fsck -v

It ran fsck on /dev/sda5 and /dev/sda6 and then when I rebooted, I land in the same emergency shell. Any other pointers?

-regards,

[linuxero]

... It ran fsck on /dev/sda5 and /dev/sda6 and then when I rebooted, I land in the same emergency shell. Any other pointers?

Actually it is a per case issue, one should at least try to trace the cause. If it is an installation, for instance, it may be off great help mentioning the steps followed, if it is an already functioning installation that appeared to develop this problem, maybe remembering the last few things done before rebooting can help!

When I had this problem, I had a system hang so I rebooted brutally. When I dropped into the emergency shell I could only assume a failure in the disks so this fixed it for me.

So please, try some details as the mods suggest all the time

@doktor5000 guess you're right dok! that's why I am here..to learn

[mrigs]

Thanks much linuxero.

if it is an already functioning installation that appeared to develop this problem, maybe remembering the last few things done before rebooting can help!

I was able to get the issue resolved for myself by remembering that prior I developed this problem when I had formatted and mounted a flash drive under /mnt/windows and had then shut down the system (there were some Mageia updates too). I was at least able to log in to the system when I plugged in the flash drive during the system reboot.

I have since unmounted the flash drive.

-regards,

[linuxero]

So is it ok now?

[mrigs]

OK, this issue is fixed, at least for me. However I can see another issue - missing window title bars. But that is a different issue altogether, I believe. Need to search the forum for the same.

[isadora]

OK, this issue is fixed, at least for me. However I can see another issue - missing window title bars. But that is a different issue altogether, I believe. Need to search the forum for the same.

Exactly, and otherwise open another topic, but first try to find out if there were others before you.