[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/609779
** Changed in: grub2 (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/609779
Title:
Stable device name update erroneously claims multiple disks
To manage
If there was only one device in the previous device.map, then I follow
exactly that logic - there's no chance of you having picked the wrong
one.
Removable devices seem likely to be an issue. At this point I'm not
entirely sure of the best handling for these.
--
Stable device name update
Hmm.. I don't have a backup, I don't think. My install history on this
laptop is likely to be... ripe. So if you haven't had any other similar
reports, let's nuke this bug report as a ghost.
However, what are the circumstances where you could end up with only one
line in device.map and still
We do try quite hard to avoid giving this message unnecessarily. I
don't suppose you have a backup that would include the previous contents
of /boot/grub/device.map?
** Package changed: grub (Ubuntu) = grub2 (Ubuntu)
--
Stable device name update erroneously claims multiple disks
In particular, the test is if /boot/grub/device.map was present, did
its previous contents consist of exactly one line, or not?. I made the
assumption that if it contained exactly one line before then it would
contain exactly one line afterwards, and vice versa; apparently that is
not true on
Marking importance high because it's an alarming message and seems like
we could straightforwardly detect cases where there is only a single
drive in the machine (or at least, only a single line in device.map
after regeneration).
** Changed in: grub (Ubuntu)
Importance: Undecided = High
--
