You are not logged in.

#1 2010-01-09 22:26:07

Raws
Member
From: Campo Grande - Brazil
Registered: 2009-08-19
Posts: 47

canot boot past grub after last kernel upgrade (2.6.32.3-1)

Hello all.

I use 3 computers with arch.

I've made the usual "Syu" upgrade this afternoon in two of then, read pacmans messages and found nothing unusual.

As the kernel packages had been upgraded, I chose to reboot the machine.

Since then, I cant pass grub screen in one of my computers (C2D E7500, intel graphics, 500GB).

After grub I receive one of this two messages: "error 16: inconsistent filesystem structure Press any key to continue", or "error 18: Selected cylinder exceeds maximum supported by BIOS".

It doesn't seem to be a hardware issue. I can boot live discs and access the HDs.

I've searched the foruns, tried to use UUIDs in place of "sda" and to use the kernel fallback... Didnt work.

I dont know what to do next... Any ideas?

Thanks in advance for any help.

Raws

Edit: partitions configuration

sda1 15GB ubuntu (boot is here)
sda2 4GB swap
sda5 15GB arch
sda6 466GB data

Last edited by Raws (2010-01-09 22:29:06)

Offline

#2 2010-01-10 04:23:05

hungerfish
Member
Registered: 2009-09-13
Posts: 254

Re: canot boot past grub after last kernel upgrade (2.6.32.3-1)

What is the content of your /boot/grub/menu.lst file? Do you use such things as 'savedefault' ? if so try commenting that part out, and try to boot your arch-linux with just the 'root' 'kernel' 'initrd' lines present.


Beetles and bacteria are vastly more successful than humans in terms of survival.

Offline

#3 2010-01-10 14:16:10

Raws
Member
From: Campo Grande - Brazil
Registered: 2009-08-19
Posts: 47

Re: canot boot past grub after last kernel upgrade (2.6.32.3-1)

There is just the basic options on menu.lst

root (hd0,4)
kernel /boot/vmlinuz26 rppt=/dev/sda5 resume=/dev/sda2 ro vga=773
initrd /boot/kernel26.img
quiet

I've already tried to use the UUID description of the partition. Didnt work.

Also, removing the vga=773 made no difference.

I've booted on a opensuse liveCD and run fsck on all partitions. On sda1 (ubuntu, unused for months) it found an "unexpected inconsistency", so I've run "e2fsck -f -c -y /dev/sda1", as indicated here: http://en.opensuse.org/SDB:Fsck:_Unexpe … onsistency

After the reboot... the problem continues the same.

Other ideas?

Thanks in advance for any help

Offline

#4 2010-01-10 14:19:04

Raws
Member
From: Campo Grande - Brazil
Registered: 2009-08-19
Posts: 47

Re: canot boot past grub after last kernel upgrade (2.6.32.3-1)

Also.

All partitions are ext4.

About two or three weeks ago a blackout turned the machine off, but after that i've been using it withou problems since then.

The exact moment when everything stoped working was when I rebooted after the last update.

Offline

#5 2010-01-11 01:04:31

hungerfish
Member
Registered: 2009-09-13
Posts: 254

Re: canot boot past grub after last kernel upgrade (2.6.32.3-1)

hmm, my grub lines are:

root   (hd0,4)
kernel /vmlinuz26 root=/dev/disk/by-uuid/... ro
initrd /kernel26.img

This is using a seperate partition for /boot which is ext2.
Maybe the recent kernel-update messed up ext4 support, although I'm not sure if it is actually supported by grub for booting from. I know that it can work, but I'm pretty sure that there are or were some issues with it at somepoint, hence I have that very small extra partition as ext2.


Beetles and bacteria are vastly more successful than humans in terms of survival.

Offline

#6 2010-01-11 01:12:00

graysky
Wiki Maintainer
From: :wq
Registered: 2008-12-01
Posts: 10,595
Website

Re: canot boot past grub after last kernel upgrade (2.6.32.3-1)

Ext4 support is fine; my /boot is ext4 and works.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Online

#7 2010-01-11 01:40:57

sand_man
Member
From: Australia
Registered: 2008-06-10
Posts: 2,164

Re: canot boot past grub after last kernel upgrade (2.6.32.3-1)

Raws wrote:

Also.

All partitions are ext4.

About two or three weeks ago a blackout turned the machine off, but after that i've been using it withou problems since then.

The exact moment when everything stoped working was when I rebooted after the last update.

You might need to use a boot disk and find out what the uuid of the root partition is and use that in the grub config instead of sda*


neutral

Offline

#8 2010-01-12 00:49:44

Raws
Member
From: Campo Grande - Brazil
Registered: 2009-08-19
Posts: 47

Re: canot boot past grub after last kernel upgrade (2.6.32.3-1)

I already tried to use the boot and use the UUID in the place of the sda*.

Didnt work.

Next step, probably, will be to reinstall GRUB/boot on the weekend. And, if that doesnt work, full reinstall of arch.

Any other ideas before that would be wellcome.

Thanks for the help until now.

Offline

Board footer

Powered by FluxBB