[Expired for grub2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/499483
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Because I'm about 5 times more likely to replace the primary hard drive
and copy all files over than add hard drives in a manner that changes
the detection order.
--
/etc/default/grub cannot disable use of UUID
https://bugs.launchpad.net/bugs/499483
You received this bug notification because you
I've hit this before on a system where UUIDs were unstable but /dev/sdxy
identities and bios identities weren't.
Annoying.
--
/etc/default/grub cannot disable use of UUID
https://bugs.launchpad.net/bugs/499483
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Blink. Why were your UUIDs unstable? They're meant to be set in
filesystem superblocks.
--
/etc/default/grub cannot disable use of UUID
https://bugs.launchpad.net/bugs/499483
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
But GRUB is not intrinsically limited to using the BIOS for this. If we
got to the point of being able to use ata.mod across the board, or even
just detected the problem and used ata.mod when necessary, it wouldn't
matter what the BIOS supported.
--
/etc/default/grub cannot disable use of UUID
Colin, isn't this the cause of this bug? the issue found with the UUID is
because of the bioses not being able to support booting off a device 137GB
the whole discussion was that if by disabling the UUID altogether by setting a
variable in the grub defaults file this could be circumvented
We really need to fix such bugs instead of working around them.
Hardcoding device names is responsible for literally hundreds of other
open bug reports, and the only way to fix this is to use a more dynamic
approach throughout. Sergei, I hope there's a separate bug report filed
for the problem
I would also be in favor of adding this feature
DISABLE_GRUB_SEARCH_ALTOGETHER=true
(or whatever name you choose), as described and suggested in the very
first message of this thread by Eskild.
Rationale: if your BIOS does not support large (137GB ;) disks then Grub gets
stuck unable to search
Am Montag, den 18.01.2010, 02:43 + schrieb Leppie:
GRUB can't know how the later booted kernel and udev names the /dev/
files for your disks.
It can only use UUIDs LABEL and a file on the filesystem which the
search command already supports.
then why does the search still use the
Am Montag, den 11.01.2010, 09:47 + schrieb Eskild Jacobsen:
Hello Felix
I think you might have read this bug report a bit fast... This is
actually for the kernel root= parameter.
Well according to your bug submission you mean clearly the search
--fs-uuid --set command and not the Linux
On some systems removing the search statement altogether makes the boot process
much slower.
Is it possible to use it with the conventional /dev/sXX references at all, or
can it only search using uuid?
--
/etc/default/grub cannot disable use of UUID
https://bugs.launchpad.net/bugs/499483
You
Am Sonntag, den 17.01.2010, 16:26 + schrieb Leppie:
On some systems removing the search statement altogether makes the boot
process much slower.
Is it possible to use it with the conventional /dev/sXX references at all, or
can it only search using uuid?
GRUB can't know how the later
GRUB can't know how the later booted kernel and udev names the /dev/
files for your disks.
It can only use UUIDs LABEL and a file on the filesystem which the
search command already supports.
then why does the search still use the --fs-uuid option even though
GRUB_DISABLE_LINUX_UUID is set to true
Hello Felix
I think you might have read this bug report a bit fast... This is
actually for the kernel root= parameter. What I'm trying to point out,
is that in order to use grub2 without UUID on file systems, the proposed
solution will work great. File system UUID is a sure way to get into
** Attachment added: grub-mkconfig_lib.patch
http://launchpadlibrarian.net/37089454/grub-mkconfig_lib.patch
--
/etc/default/grub cannot disable use of UUID
https://bugs.launchpad.net/bugs/499483
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
this affects netbased installs
** Changed in: grub2 (Ubuntu)
Status: New = Confirmed
--
/etc/default/grub cannot disable use of UUID
https://bugs.launchpad.net/bugs/499483
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
17 matches
Mail list logo
