[Mageia-discuss] System won't boot after hardware upgrade
ctrl.alt.sup at free.fr
Fri Sep 23 01:03:55 CEST 2011
JA Magallon a écrit :
> On Thu, 22 Sep 2011 15:21:19 +0530
> xi<ctrl.alt.sup at free.fr> wrote:
>> I have changed my motherboard and Mageia now refuses to boot (kernel
>> panic after trying to mount /dev/sda1 : "waiting for device sda1 to
>> appear (timeout 1 min), ...").
>> I think I know the reason of my problem : the initrd does not load the
>> correct driver for my "new" IDE controller, so it can't mount my disk
>> (driver for old motherboard is pata_amd and new driver is pata_via).
> Can you post your mobo model ?
The mobo on which I initially installed Mageia is a Tyan Tiger MPX (dual
athlon MP). The IDE controller is from AMD (kernel module pata_amd)
The "new" mobo is a Tyan Tiger 200T (dual PIII). The IDE controller is
from Via (kernel module pata_via). When trying to boot on it, the init
script loads pata_amd module then fails in kernel panic after 1 minute.
>> I tried to play with mageia rescue CD, but I am unable to regenerate the
>> initrd with the correct IDE driver (in fact, the rescue CD doesn't even
>> contain the mkinitrd command).
>> My question is : how can I solve my problem, given that I have only one
>> rescue CD and my HD containing mageia that don't boot anymore ?
>> A long time ago in the perfect world of Mandrake (:P), all IDE
>> controller were included _inside_ the kernel and _not_ compiled as
>> modules*, so this problem never occured because all IDE drivers were
>> always "loaded" (thus allowing my system to be booted on any computer).
>> Now that the ide/sata drivers as compiled as modules, why don't the
>> initrd try to load all the ATA drivers if mounting of "/" fails ?
>> (from my point of view, it is a much better solution than failing with a
>> kernel panic ...)
>> Thanks for your help,
>> *this is _my_ interpretation, I may be wrong.
More information about the Mageia-discuss