View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0003047Kali LinuxGeneral Bugpublic2016-02-06 23:572018-01-29 12:32
ReporterLinuxSupahFly Assigned Tog0tmi1k  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionsuspended 
Product Version2016.1 
Summary0003047: linux-boot-prober yields wrong UUID for kernel root parameter
Description

To understand better, first, let me show you my annotated blkid results:

/dev/sda3: UUID="5bb6dc47-4b57-4610-9e4d-6d4e604a171f" TYPE="swap" PARTUUID="fa43222a-03" # <- Common swap partition
/dev/sda1: LABEL="ROOT" UUID="883242e7-e8da-40d2-aab7-40a2f771aa6b" TYPE="ext4" PARTUUID="fa43222a-01" # <- Ubuntu partition
/dev/sda4: LABEL="BOOT" UUID="dcd42ae2-281e-4101-9d64-fb0301c6eb37" TYPE="ext4" PARTUUID="fa43222a-04" # <- Common boot partition
/dev/sdj2: LABEL="KALI" UUID="c5f8b7c2-82b6-4c22-a69e-6b4954ee5d5f" TYPE="ext4" PARTUUID="d60d1859-02" # <- Kali 2 partition

Now, when I installed Ubuntu, it was a clean install I had converted from Windows XP. It ran fine as a Ubuntu/XP Dual-Boot, then eventually, it was just Ubuntu, and back in December 2015, I installed Kali on a new partition. The problem is that when the Kali installer ran update-grub, everything got all messed up and I couldn't boot Ubuntu, but I could chroot in from Kali, and I ran update-grub again, but from the chroot and discovered I wasn't able to boot Kali any longer, but could again chroot into the Kali install from Ubuntu.

After some poking around and some Googling, I discovered that whichever distro runs update-grub, it's UUID is the one used for all options. (See attached file).

Steps To Reproduce

Have multiple physicals drives or create 4 partitions. Two common partitions for both installs - one for /boot/ and one for /SWAP/, then install Kali on one remaining and something else on the other and examine /boot/grub/grub.cfg after each instance of update-grub from both distros.

Additional Information

I was able to fix the problem by manually editing /boot/grub/grub.cfg and cleaning it up a bit by correcting the UUID assignments and removing extra menu entries (as we can't boot Ubuntu with the Kali kernel, and we can't boot Kali with the Ubuntu kernels).

Attached Files
grub.cfg.combined (70,073 bytes)

Activities

g0tmi1k

g0tmi1k

2018-01-29 12:32

administrator   ~0008141

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling 2016.x), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing,and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2016-02-06 23:57 LinuxSupahFly New Issue
2016-02-06 23:57 LinuxSupahFly File Added: grub.cfg.combined
2018-01-29 12:32 g0tmi1k Assigned To => g0tmi1k
2018-01-29 12:32 g0tmi1k Status new => closed
2018-01-29 12:32 g0tmi1k Resolution open => suspended
2018-01-29 12:32 g0tmi1k Note Added: 0008141