[arch-general] kernel26 2.6.32.10-1 Boot Failure at initrd/initramfs
Guys, I just attempted an update which installed kernel26 2.6.32.10-1 on my x86_64 box. After the update, the box failed to boot and the boot process stopped at the initrd/initramfs. (I have the slash because I can't remember the exact init----) But it was very early in the boot process. I have checked logs and nothing for this boot attempt was written to the logs. I suspect it was too early in the boot process for logging to be enabled. I have never tried to recover from a failed arch boot before. What's the proper way. Boot with the install cd and chroot your install and either downgrade to the last kernel or try mkinitcpio again? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On 03/18/2010 12:47 PM, David C. Rankin wrote:
Guys,
I just attempted an update which installed kernel26 2.6.32.10-1 on my x86_64 box. After the update, the box failed to boot and the boot process stopped at the initrd/initramfs. (I have the slash because I can't remember the exact init----) But it was very early in the boot process. I have checked logs and nothing for this boot attempt was written to the logs. I suspect it was too early in the boot process for logging to be enabled.
I have never tried to recover from a failed arch boot before. What's the proper way. Boot with the install cd and chroot your install and either downgrade to the last kernel or try mkinitcpio again?
I think initrd and initramfs barely mean the same thing. initrd stands for Initial RAM Disk and initramfs for Initial RAM Filesystem. If you could give the exact error message, we could get some idea about it. You can try mkinitcpio. Then if it doesn't work downgrade. -- Nilesh Govindarajan Site & Server Adminstrator www.itech7.com
On 03/18/2010 03:31 AM, Nilesh Govindarajan wrote:
On 03/18/2010 12:47 PM, David C. Rankin wrote:
Guys,
I just attempted an update which installed kernel26 2.6.32.10-1 on my x86_64 box. After the update, the box failed to boot and the boot process stopped at the initrd/initramfs. (I have the slash because I can't remember the exact init----) But it was very early in the boot process. I have checked logs and nothing for this boot attempt was written to the logs. I suspect it was too early in the boot process for logging to be enabled.
I have never tried to recover from a failed arch boot before. What's the proper way. Boot with the install cd and chroot your install and either downgrade to the last kernel or try mkinitcpio again?
I think initrd and initramfs barely mean the same thing. initrd stands for Initial RAM Disk and initramfs for Initial RAM Filesystem.
If you could give the exact error message, we could get some idea about it.
You can try mkinitcpio. Then if it doesn't work downgrade.
Ok, I tried loading it again and it is "Initrd". As soon as you get the Initrd message, it just sits there and 30 secnds later or so, it reboots. I also have the LTS kernel installed and it is just fine. That's what I'm running on currently. With that clarification, what say the gurus? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On 03/18/2010 05:08 PM, David C. Rankin wrote:
On 03/18/2010 03:31 AM, Nilesh Govindarajan wrote:
On 03/18/2010 12:47 PM, David C. Rankin wrote:
Guys,
I just attempted an update which installed kernel26 2.6.32.10-1 on my x86_64 box. After the update, the box failed to boot and the boot process stopped at the initrd/initramfs. (I have the slash because I can't remember the exact init----) But it was very early in the boot process. I have checked logs and nothing for this boot attempt was written to the logs. I suspect it was too early in the boot process for logging to be enabled.
I have never tried to recover from a failed arch boot before. What's the proper way. Boot with the install cd and chroot your install and either downgrade to the last kernel or try mkinitcpio again?
I think initrd and initramfs barely mean the same thing. initrd stands for Initial RAM Disk and initramfs for Initial RAM Filesystem.
If you could give the exact error message, we could get some idea about it.
You can try mkinitcpio. Then if it doesn't work downgrade.
Ok,
I tried loading it again and it is "Initrd". As soon as you get the Initrd message, it just sits there and 30 secnds later or so, it reboots.
I also have the LTS kernel installed and it is just fine. That's what I'm running on currently. With that clarification, what say the gurus?
I think your kernel has got corrupt. Try reinstalling it. -- Nilesh Govindarajan Site & Server Adminstrator www.itech7.com
On 03/18/2010 06:59 AM, Nilesh Govindarajan wrote:
I think your kernel has got corrupt. Try reinstalling it.
I think your right. I updated again and it pulled in 2.6.33-1 and then it booted. Gremlins -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Thu, Mar 18, 2010 at 2:17 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
I just attempted an update which installed kernel26 2.6.32.10-1 on my x86_64 box. After the update, the box failed to boot and the boot process stopped at the initrd/initramfs.
did you try the fallback image ?
On 03/18/2010 04:01 AM, Emmanuel Benisty wrote:
On Thu, Mar 18, 2010 at 2:17 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
I just attempted an update which installed kernel26 2.6.32.10-1 on my x86_64 box. After the update, the box failed to boot and the boot process stopped at the initrd/initramfs.
did you try the fallback image ?
Nope, I just switched to the LTS kernel. I can give it a try in a bit. (backup is busy right now) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On 03/18/10 at 02:17am, David C. Rankin wrote:
Guys,
I just attempted an update which installed kernel26 2.6.32.10-1 on my x86_64 box. After the update, the box failed to boot and the boot process stopped at the initrd/initramfs. (I have the slash because I can't remember the exact init----) But it was very early in the boot process. I have checked logs and nothing for this boot attempt was written to the logs. I suspect it was too early in the boot process for logging to be enabled.
I have never tried to recover from a failed arch boot before. What's the proper way. Boot with the install cd and chroot your install and either downgrade to the last kernel or try mkinitcpio again?
You should be able to boot from the fallback image. I had this issue once, and the error message was "can't find root filesystem in 30 seconds"; what I did for recovering was: reboot from fallback image add to /etc/mkinitcpio.conf MODULES="ext4" mkinitcpio -c /etc/mkinitcpio.conf -g /boot/kernel26.img reboot from the new image since I heard that new kernel had worse performance for ext4 than the previous one, and my / was ext4. You should also read the mkinitcpio wiki page for more info.
On 03/18/2010 04:05 AM, lolilolicon wrote:
On 03/18/10 at 02:17am, David C. Rankin wrote:
Guys,
I just attempted an update which installed kernel26 2.6.32.10-1 on my x86_64 box. After the update, the box failed to boot and the boot process stopped at the initrd/initramfs. (I have the slash because I can't remember the exact init----) But it was very early in the boot process. I have checked logs and nothing for this boot attempt was written to the logs. I suspect it was too early in the boot process for logging to be enabled.
I have never tried to recover from a failed arch boot before. What's the proper way. Boot with the install cd and chroot your install and either downgrade to the last kernel or try mkinitcpio again?
You should be able to boot from the fallback image.
I had this issue once, and the error message was "can't find root filesystem in 30 seconds"; what I did for recovering was: reboot from fallback image add to /etc/mkinitcpio.conf MODULES="ext4" mkinitcpio -c /etc/mkinitcpio.conf -g /boot/kernel26.img reboot from the new image since I heard that new kernel had worse performance for ext4 than the previous one, and my / was ext4.
You should also read the mkinitcpio wiki page for more info.
Hmm /boot and / are ext3 and the data drives are ext4. I'll give it a try. Currently I'm not loading the ext4 module in the mkinitcpio.conf MODULES line. Can't hurt....... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
participants (4)
-
David C. Rankin
-
Emmanuel Benisty
-
lolilolicon
-
Nilesh Govindarajan