You are not logged in.
Hi,
I just updated my machine with latest Arch packages. My previous version was a bit old (6 month - 1 year ago). Since I did the upgrade, it does not boot anymore, it stop to the "ramfs" prompt after loading the kernel. Error is saying that it can't find the disks. The kernel is loaded, but it does not find the root partition.
My configuration has an IDE drive as first, and a SATA as second. Both boot and root are on the IDE drive. In grub, the boot line (not changed since the update) says "sda4". I have not changed anything to that since I upgraded.
Does someone had a similar problem ? Has there been any change with kernel ability to boot on IDE disks, or IDE disks naming since few month ?
Any hint ?
Thanks
Offline
try mounting by UUID in fstab instead of /dev/sdxx
Offline
thanks for the hint.
What is strange is that under "ramfs#", a "cd dev" followed by "echo *" does not give anything about sd* or disk* or hd*.
It looks that no disk at all is seen.
Offline
Could it be an error in mkinitcpio.conf? Can you use the fallback kernel to edit mkinitcpio.conf?
Offline
Thanks Zenlod,
but the fallback has the same behavior than the normal, and I get the "ramfs" prompt from which I can't do more.
Offline
Did you delete some modules in the fallback config? My first guess would be that the kernel misses a module to find your /boot - maybe 'filesystems' or 'pata'. A while back (i think it is more than 1 year ago), the linux kernel switched from /dev/hdx to /dev/sdx - and maybe you don't have the right modules in your old mkinitcpio.
I think you'll have to chroot into your pc and load the old kernel to troubleshoot what went wrong (starting with mkinitcpio config)
Offline
zenlord,
Yes, it is fairly possible that I did not update since long time, after the kernel switch from /dev/hdx to /dev/sdx. And it sounds to be a good explanation given the symptom. But how to run a mkinitcpio when you can't even boot the machine ?
As it was urgent (this is my wife's PC....), I just reinstall Arch again with all applications.
Honestly, I would have prefer to be able to boot on my old kernel image, to have a simple way to fix this. Currently this is no possible you have no choice, either the new update work, or you are dead. Only if you are fortunate, you have a CD reader and can run a live CD.
Thanks for your help,
Olivier
Offline