Hi Philip,
glad to hear that I'm not fully mistaken ;-). It may not be a very frequent use
case having different Linux installs in parallel, but solving this will really
improve things for those users.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I see now. So os-prober detects an install on another partition,
decides to try and boot it with some kernel, but passes the wrong root
argument. That does seem wrong.
** Changed in: os-prober (Ubuntu)
Status: Won't Fix => Triaged
** Description changed:
- Binary package hint: os-probe
I agree with you that os-prober cannot automatically tell, which kernel
files belong to which installation, if several linux installs share the
same /boot.
(1) Still, its behaviour could be easily improved: If os-prober detects
two linux installs with a shared /boot, it could simply ask the user,
os-prober can not support multiple installs with a shared /boot. How is
it supposed to know which files belong to which install? To make this
work you just have to manually configure grub.cfg.
** Changed in: os-prober (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug not
I installed 17.10 on my SSD and have in total 4 Ubuntu partitions (2 on
hard drive and 2 on SSD). With the install, as best I can recall,
everything was fine and I could boot both partitions on the SSD. I then
updated Grub using Grub Customizer. The menu still shows 4 options for
boot, but the t
Marking grub.cfg read only doesn't work - I tried that at first.
I make a backup copy of my grub.cfg before doing kernel updates, run the
updates and update-grub as normal, then compare the changes to the
backup, and manually re-edit where needed to ensure smooth booting -
before I ever boot a new
Thanks, EvilSupahFly. I can now add this:
Rm'ing every grub related file on the other systems, reinstalling grub,
and running update-grub was REALLY BAD IDEA. Now when I try to boot
/dev/sda6 (the system that is an fsarchiver-made clone of my main,
/dev/sda5-based 14.04 system, where grub is suppo
I had to edit by hand, remembering to re-edit after a kernel update as my
changes get wiped out by update-grub.
On Aug 1, 2016 17:16, "My name" wrote:
> Same thing with me in 14.04. This is a pretty basic thing to be broken
> for so long. Suggestions for work-arounds would be nice, since it
> do
BTW, all my linux systems are 1-partition-each, no seperate ~s, or swaps
or boot. Keeping it simple. They are on 2 drives, one external, one
internal. Grub is on /dev/sda with config files on sda5, which is the
one that boots. Some are on primary and some on logical partitions. Sda1
and sda2 are Wi
Same thing with me in 14.04. This is a pretty basic thing to be broken
for so long. Suggestions for work-arounds would be nice, since it
doesn't look fixing it is imminent.
Personally, I've tried a 2 grub rescue utilities, one from within one of
the partitions that will boot, and another from CD.
** Changed in: os-prober (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554307
Title:
linux-boot-prober yields wrong uuid for kernel root parameter
To manag
** Tags added: trusty vivid wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554307
Title:
linux-boot-prober yields wrong uuid for kernel root parameter
To manage notifications about this bug go
I've updated to Ubuntu 15.10 and the bug still exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554307
Title:
linux-boot-prober yields wrong uuid for kernel root parameter
To manage notificati
Yesterday, I installed KALI beside my existing Ubuntu 15.04, and I'm
still seeing this issue. When I ran 'update-grub' from Ubuntu, all menu
options boot Ubuntu but with problems. When I ran 'update-grub' in KALI,
everything changes to KALI but also with problems.
I have one common dedicated boot
** Changed in: os-prober (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554307
Title:
linux-boot-prober yields wrong uuid for kernel root parameter
To
Yes, the bug appears on 14.04 LTS release. The partition in question is
not mounted via /etc/fstab.
To understand what's going on I'd better give you blkid output with some
my comments:
$ blkid /dev/sda*
/dev/sda1: UUID="66ECBF91ECBF5A4F" TYPE="ntfs"
/dev/sda10: UUID="04db7581-6256-408c-969b-278
Are you able to reproduce this on a currently supported release? What
does the /etc/fstab on the partition in question say?
** No longer affects: grub2 (Ubuntu)
** Changed in: os-prober (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a mem
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554307
Title:
linux-boot-prober yields wrong uuid for kernel root parameter
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554307
Title:
linux
Anyone a clue what makes this bug happen?
I just copied my two systems to a new ssd and now I have this problem as
well... but I think it worked well before!
It is easy to see even without comparing the uuids, as my old Mint
installation has kernel 3.0.0-13 still:
nsk@sesta09:~$ sudo linux-boot-
** Changed in: os-prober (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554307
Title:
linux-boot-prober yields wrong uuid for kernel root parameter
To manage
I think this bug is still there with maverick.
I have a fresh lucid and maverick installation sharing a boot partition.
When I do a grub-update in maverick, the script which runs linux-boot-
prober apparently got the uuid wrong for the lucid partition.
--
linux-boot-prober yields wrong uuid for
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42927516/Dependencies.txt
--
linux-boot-prober yields wrong uuid for kernel root parameter
https://bugs.launchpad.net/bugs/554307
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
23 matches
Mail list logo
