Hah.
Sorry for panic. False alarm.
The magic commands that solve everything are
sudo mount -v --bind /mnt/@/ /mnt
sudo mount -v --bind /mnt/home/@home /mnt/home # optional
So, I've been little confused with btrfs subvolumes. Actually the above message
is a bug in
kubuntu installer.
**
The bug is still present.
# update-grub -v
grub-mkconfig (GRUB) 2.02~beta2-36ubuntu3.2
After chroot
# update-grub
/usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
Ubuntu: kubuntu-16.04.1-desktop-amd64
Filesystem:
/dev/sda <- grub installed here
/dev/sda5 <- /boot
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: 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/591454
Title:
grub-probe:
Since this very old bug was about upgrading from hardy to lucid, and
hardy is long since end of life, I'm going to close this now.
** Project changed: update-manager = ubuntu
** No longer affects: ubuntu
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Invalid
--
You received this
Hi All,
In my case the issue was caused due to the fact that i have used a btrfs
filesystem for my root partition and as Nils mentioned if you just mount
the /dev/sdx to mnt and then mount --bind all the nedeed parts, chroot
and try to update grub or grub-install the comands will both fail as you
worked when mounting the default @ subvolume, as opposed to mounting
sdxy and chrooting into /mnt/@/ maybe the problem is having @ in the
path?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/591454
I have the same problem in 14.04 when accessing through chroot to repair
a uefi bootloader.
Installed is 14.04, bootloader was overwritten by Win 8 bios update utility.
Ubuntu 14.04 LiveCD is used to boot, and installed root and boot partitions are
mounted to chroot into them to reinstall
Thank you Carlos! I had no idea how to fix this problem with Lucid, but
your answer in #4 worked perfectly. Thanks again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/591454
Title:
grub-probe:
** Attachment removed: VarLogDistupgradeSystemstatetargz.gz
https://bugs.launchpad.net/bugs/591454/+attachment/1420857/+files/VarLogDistupgradeSystemstatetargz.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Carlos, I had the same problem as you. I think it works like this (in
my case, anyway):
1. Upgrading from Hardy to Lucid doesn't install LVM support--the lvm2 package
is not even installed by update-manager.
2. After upgrading ALL packages, resolving many conflicts by hand, getting the
new
This was specifically encountered by update-manager not installing lvm2
when upgrading from Hardy to Lucid on a system using LVM for several
partitions, including root.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[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/591454
Carlos, the version of GRUB 2 in Maverick should deal with symlinks in
/dev/mapper/. For that matter, the LVM configuration in Ubuntu does not
yet create symlinks in /dev/mapper/ as far as I know, so I'm not sure
how you ran across this problem in Ubuntu ...
--
grub-probe: cannot find a device
In fact, all entries in /dev/mapper are not symlinks in Ubuntu. Somehow
my grub2 could not find the disk and I had to boot using a rescue cd and
it created the symlinks I saw after chrooting in Ubuntu.
--
grub-probe: cannot find a device for /boot/grub
https://bugs.launchpad.net/bugs/591454
You
I had this problem yesterday because I'm using an LVM boot partition and
/dev/mapper/VolumeGroup-LogicalVolume was a symlink to /dev/dm-X. After
removing the symlink and running cp -R /dev/dm-X /dev/mapper
/VolumeGroup-LogicalVolume, I could run grub-install successfully.
--
grub-probe: cannot
15 matches
Mail list logo
