Last time my laptop had weird problem (couldn't boot to GUI until I reinstalled new kernel) after I used Ktorrent's scheduled shutdown.
Yesterday I scheduled a shutdown in console with "shutdown 40" and went to bed. This morning my laptop can't boot at all
error: file '/grub/x64-pc/normal.mod' not found.
This is a tri-boot system as listed in my signature. Opensuse takes control of the grub2, which supports both UEFI and secure boot. But I have secure boot option disabled in BIOS as manjaro does not support it.
The first thing I did is to boot it with my portable opensuse and did a fsck to the 1TB drive which has 3 os installed. Here's the message:
I wonder if I should do as suggested "e2fsck -b 8193 /dev/sda"?
Also, can I do a regular grub rescure as instructed here by caf?
Thanks. Friday evening, grub is broken...:(
Yesterday I scheduled a shutdown in console with "shutdown 40" and went to bed. This morning my laptop can't boot at all
error: file '/grub/x64-pc/normal.mod' not found.
This is a tri-boot system as listed in my signature. Opensuse takes control of the grub2, which supports both UEFI and secure boot. But I have secure boot option disabled in BIOS as manjaro does not support it.
The first thing I did is to boot it with my portable opensuse and did a fsck to the 1TB drive which has 3 os installed. Here's the message:
Code:
# fsck /dev/sda
fsck from util-linux 2.23.2
e2fsck 1.42.8 (20-Jun-2013)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
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>Also, can I do a regular grub rescure as instructed here by caf?
Thanks. Friday evening, grub is broken...:(