[SOVLED] Can not boot

thelastblack · 2014-07-28 17:36:04

Hello
I upgraded my arch distro. I really don't know when I did this, because I always sleep my laptop instead of powering it off. And my last uptime was 2 weeks.
So I must have done a `pacman -Syyu` sometime between last night and two weeks ago.
Today I wanted to connect to my workplace with openvpn, it gave errors and by searching I found out that it can be fixed via rebooting.
I rebooted and guess what? I got a "Boot Error". Nothing less nothing more. When I press a key, I go to my boot device selection screen (my bios one, not os-related).

At first I thought it was an issue like this topic: https://bbs.archlinux.org/viewtopic.php?id=184283
But then I found out that I already have 3.15.5-2
Also downgrading kernel gives error about "/lib/modules/3.15.3.1-ARCH/<somefiles> already exist".
I don't think kernel is my problem.

Just found out that grub was somehow removed from my device. I reinstalled grub from a live archbang, and now I have grub menu.

But still no booting.
I dig more and found something intresting. Here is my menu part for grub.cfg

menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-ad4103fa-d940-47ca-8506-301d8071d4$
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='hd0,msdos5'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5  ad4103fa-d940-47ca-8506-301d8071d467
        else
          search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
        fi
        echo    'Loading Linux core repo kernel ...'
        linux   /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 rw  quiet
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initramfs-linux.img
}

But the problem is that there is no disk with uuid ad4103fa-d940-47ca-8506-301d8071d467! And I don't know what uuid should I put there.
Here is my partitioning scheme (blkid output):

/dev/sda1: UUID="fb3382a2-e71c-445f-87c2-d7d871b98314" TYPE="ext4" 
/dev/sda3: UUID="989D4S-fhhw-4Aud-l5fG-Ldww-CLq3-7TOZke" TYPE="LVM2_member" 
/dev/sdb1: UUID="2013-09-01-06-07-52-00" LABEL="ARCHBANG" TYPE="iso9660" PTTYPE="dos" 
/dev/sdb2: SEC_TYPE="msdos" LABEL="ARCHISO_EFI" UUID="9464-DFA7" TYPE="vfat" 
/dev/loop0: TYPE="squashfs" 
/dev/loop1: UUID="caccd8c1-78ee-4a56-a202-109104d2df61" TYPE="ext4" 
/dev/loop2: UUID="caccd8c1-78ee-4a56-a202-109104d2df61" TYPE="ext4" 
/dev/mapper/arch_root-image: UUID="caccd8c1-78ee-4a56-a202-109104d2df61" TYPE="ext4" 
/dev/mapper/fedora_vahid--fedora-root: UUID="27df4af6-419d-48f4-9707-5fc772b4bee5" TYPE="ext4" 
/dev/mapper/fedora_vahid--fedora-home: UUID="5e923eb3-f598-491d-8dbd-505715a7e779" TYPE="ext4" 
/dev/mapper/fedora_vahid--fedora-swap: UUID="1fe30972-abbd-46b8-95ce-c25cf29b0b81" TYPE="swap"

What uuid is needed for grub menu? /dev/sda3 (LVM partition) or my root partition (inside LVM)? Or boot partition?

Does that uuid became invalid because I reinstalled grub? Why grub was removed? A recent update caused that? My laptop's uptime was about two weeks before this happened, so anytime in two weeks ago this could happen.
I am really confused.
I don't want to reinstall my arch. I had tones of softwares installed, many data in local mysql and mongo, their configs, many local websites and their virtual host definitions, ...
Really, please guide me. It is a pain to reinstall arch now :-(

Last edited by thelastblack (2014-07-28 18:42:57)

Trilby · 2014-07-28 17:40:27

Check your pacman logs to see what was updated and when.

For the bootloader, the UUID for "root=..." should be (as the variable name implies) your root partition which sounds like it would be your /dev/sda3.

thelastblack · 2014-07-28 17:46:38

I think by "root" you mean "/dev/mapper/fedora_vahid--fedora-root: UUID="27df4af6-419d-48f4-9707-5fc772b4bee5" TYPE="ext4" ", right?
What about the others?

Trilby · 2014-07-28 17:50:58

I have no idea - it's your system. What is your root partition? That is what should be in the bootloader config as the bootloader config is on the boot partition, so at that point the boot partition has already been found and read.

However, unless you have a very odd naming scheme, I highly doubt something called "fedora-root" is the right one when there is an "arch_root" right next to it. But again, it's your system.

thelastblack · 2014-07-28 17:52:16

I changed all uuids in menu entry to "/dev/mapper/fedora_vahid--fedora-root: UUID="27df4af6-419d-48f4-9707-5fc772b4bee5" TYPE="ext4", no luck :-(
Also I tried changing all uuids to /dev/sda1 (uuid of course, which is my /boot partition), again with no luck :-(

Trilby · 2014-07-28 17:52:56

OK, good luck trying random things.

thelastblack · 2014-07-28 18:16:25

I like to clarify somethings.
arch_root is created by live system, not me
You see *fedora* because this scheme was created by Fedora at first. But then it went on my nerves and I changed it to Arch (and loved it since then :-) )
Yep, that was my story :-)

thelastblack · 2014-07-28 18:17:15

OK, thanks @Trilby :-)

jasonwryan · 2014-07-28 18:19:21

Not a Pacman issue, moving to NC...

Head_on_a_Stick · 2014-07-28 18:30:45

What is the output of:

lsblk -f

I don't use LVM so I may be wrong, but it looks like you should replace the "ad4103fa-d940-47ca-8506-301d8071d467" entries in grub.cfg with either "caccd8c1-78ee-4a56-a202-109104d2df61" (UUID for "arch_root-image") or maybe "989D4S-fhhw-4Aud-l5fG-Ldww-CLq3-7TOZke" (for sda3)...
Why don't you try them and see if they work?

thelastblack · 2014-07-28 18:39:48

I don't know why it didn't come on my mind earlier, but a `grub-mkconfig -o /boot/grub/grub.cfg` solved problem. System booted finally!
Here is the boot entry, modified by above command:

menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-27df4af6-419d-48f4-9707-5fc772b4bee5' {
        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod ext2
        set root='hd0,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  fb3382a2-e71c-445f-87c2-d7d871b98314
        else
          search --no-floppy --fs-uuid --set=root fb3382a2-e71c-445f-87c2-d7d871b98314
        fi
        echo    'Loading Linux linux ...'
        linux   /vmlinuz-linux root=UUID=27df4af6-419d-48f4-9707-5fc772b4bee5 rw
        echo    'Loading initial ramdisk ...'
        initrd  /initramfs-linux.img
}

thelastblack · 2014-07-28 18:45:39

Thread is marked as solved.
But I really have no idea what has happened. Probably an upgrade wiped my grub, somehow. I didn't find any problem like mine on net.
I just give this instructions, maybe someone has my problem too:
Boot with a live linux, chroot into your existing linux, install grub and run grub-mkconfig. It worked for me.

Arch Linux

#1 2014-07-28 17:36:04

[SOVLED] Can not boot

#2 2014-07-28 17:40:27

Re: [SOVLED] Can not boot

#3 2014-07-28 17:46:38

Re: [SOVLED] Can not boot

#4 2014-07-28 17:50:58

Re: [SOVLED] Can not boot

#5 2014-07-28 17:52:16

Re: [SOVLED] Can not boot

#6 2014-07-28 17:52:56

Re: [SOVLED] Can not boot

#7 2014-07-28 18:16:25

Re: [SOVLED] Can not boot

#8 2014-07-28 18:17:15

Re: [SOVLED] Can not boot

#9 2014-07-28 18:19:21

Re: [SOVLED] Can not boot

#10 2014-07-28 18:30:45

Re: [SOVLED] Can not boot

#11 2014-07-28 18:39:48

Re: [SOVLED] Can not boot

#12 2014-07-28 18:45:39

Re: [SOVLED] Can not boot

Board footer