[solved] Grub error 13 due to PC reboot during Kernel upgrade

San2ban · 2012-03-23 06:06:25

Dear Archers
Though I have UPS, sometimes PC reboots during power failure. Yesterday, upgrade was happening, during which PC rebooted. Now unable to boot either main or fall back. Grub error 13

Using arch live CD, I checked the file systems on sda1 sda2 sda3. Appears OK. (Writing from windows on /dev/sdb)

I do not want to re-install. Next steps?

Last edited by San2ban (2012-03-25 11:03:47)

Cory_j · 2012-03-23 06:54:45

you may try

pacman -Syu linux-headers

loafer · 2012-03-23 06:59:20

I would chroot and then check /var/log/pacman.log. Then reinstall the kernel and any other packages affected.

https://wiki.archlinux.org/index.php/Change_Root

San2ban · 2012-03-23 08:46:21

Cory_j wrote:

you may try
pacman -Syu linux-headers

This cannot be done at the moment. GRUB error 13.

SQUASHFS means what?

loafer · 2012-03-23 12:30:01

Did you try to reinstall the kernel from a chroot?

I do not understand the reference to squashfs at all. There is no context to it.

Gcool · 2012-03-23 12:45:10

Chroot in, double check your grub config and reinstall grub.

San2ban · 2012-03-23 15:33:37

@loafer
NO. I did not
SQUASHFS or bad magic number is displayed when fsck /dev/sda is run

San2ban · 2012-03-24 08:12:00

root@unknown001bb9b49eba /root % efsck -b 8193 /dev/sda
zsh: correct 'efsck' to 'fsck' [nyae]? y
fsck from util-linux 2.19.1
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

Superblock corrupted. 8193 not accepted. Further ?.....

Gcool · 2012-03-24 09:27:43

Make sure you're actually dealing with the correct partitions (try using uuid or id to refer to the partition). More info here.

San2ban · 2012-03-24 10:16:28

# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
tmpfs                   /tmp            tmpfs   nodev,nosuid    0       0

UUID=76a1021f-3ca5-4f7b-a5cd-73a91d9ccf15 /boot ext2 defaults 0 1
UUID=ea8d94b7-6357-4a36-92d8-d9decb211a82 swap swap defaults 0 0
UUID=4f1443e4-6dd6-4f56-8d84-95eecd921856 / ext3 defaults 0 1

I am at the end of my wit. When Chrooted using live CD, all appears OK, when I reboot, grub loads till stage 1.5 and falls at grub prompt grub>

San2ban · 2012-03-25 11:03:25

Finally.......Reinstalled

Arch Linux

#1 2012-03-23 06:06:25

[solved] Grub error 13 due to PC reboot during Kernel upgrade

#2 2012-03-23 06:54:45

Re: [solved] Grub error 13 due to PC reboot during Kernel upgrade

#3 2012-03-23 06:59:20

Re: [solved] Grub error 13 due to PC reboot during Kernel upgrade

#4 2012-03-23 08:46:21

Re: [solved] Grub error 13 due to PC reboot during Kernel upgrade

#5 2012-03-23 12:30:01

Re: [solved] Grub error 13 due to PC reboot during Kernel upgrade

#6 2012-03-23 12:45:10

Re: [solved] Grub error 13 due to PC reboot during Kernel upgrade

#7 2012-03-23 15:33:37

Re: [solved] Grub error 13 due to PC reboot during Kernel upgrade

#8 2012-03-24 08:12:00

Re: [solved] Grub error 13 due to PC reboot during Kernel upgrade

#9 2012-03-24 09:27:43

Re: [solved] Grub error 13 due to PC reboot during Kernel upgrade

#10 2012-03-24 10:16:28

Re: [solved] Grub error 13 due to PC reboot during Kernel upgrade

#11 2012-03-25 11:03:25

Re: [solved] Grub error 13 due to PC reboot during Kernel upgrade

Board footer