Verification done on focal-proposed; all good.
Host:
---
$ sudo dd if=/dev/sda of=/dev/null
dd: failed to open '/dev/sda': No medium found
$ lxc launch ubuntu:focal lp1834250
$ lxc config device add lp1834250 host-sda unix-block source=/dev/sda
path=/dev/sda
Hello Scott, or anyone else affected,
Accepted lvm2 into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lvm2/2.03.07-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.
** Patch added: "lp1834250_lvm2_focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1834250/+attachment/5593897/+files/lp1834250_lvm2_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Uploaded to Focal, and tagged block-proposed-focal.
Attaching slightly modified debdiff (local build version),
for users who want to build lvm2 before a SRU is released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Description changed:
[Impact]
* `update-grub` (actually `vgs`) complains about
'No medium found' on systems with card readers
that have no card in.
* This may confuse users who aren't sure whether
it means problems occurred with the bootloader,
and concern thei
Setup:
--
Add '/dev/sda' from the host to a Focal LXD container:
$ lxc launch ubuntu:focal 'focal-container'
$ lxc config device add 'focal-container' 'lxc-dev-sda' unix-block
source='/dev/sda' path='/dev/sda'
Device:
---
$ grep ^ /sys/block/sda/{removable,device/{vend
** Also affects: lvm2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: lvm2 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: lvm2 (Ubuntu)
Importance: Low => Undecided
** Changed in: lvm2 (Ubuntu Focal)
Status: New => In Progress
** Changed in:
I also ran into this on 20.04. Comment#16 (albeit with different device
filters, also for SD card readers) worked for me as a workaround.
Opaque errors from GRUB always make me uneasy, since I always worry my
machine may not come back after the next reboot. I'm sure I'm not alone.
Is there anythin
In MacBook Pro 2015, the inbuilt SD Card Reader needs to be filtered
out. Comment#16 helped me fix the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834250
Title:
update-grub complains abou
Mind the trailing "|" in above comment.
Hence the correct way is :
global_filter = [ "r|/dev/disk/by-id/.*Reader_058F312D81B.*|" ]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834250
Title:
upda
You can prevent lvm2 from scanning the card reader by using the global filter.
Instead of using drive letters for the filter, like 'sde' which is liable to
change, use the id of the device(s).
E.g.:
# ls -l /dev/disk/by-id/ | grep sd[e-h]
lrwxrwxrwx 1 root root9 Apr 13 11:06
usb-Generic
ubuntu 20.04.1
# update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.8.0-45-generic
Found initrd image: /boot/initrd.img-5.8.0-45-generic
Found linux image: /boot/vmlinuz-5.8.0-4
This comes from lvs in lvm2
** Package changed: grub2 (Ubuntu) => lvm2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834250
Title:
update-grub complains about non-existent drives (due to
It's now 2021, and this issue is still present, even after upgrading to
Linux Mint 20.1 (likely due to Mint being a Ubuntu derivative):
```
[~] $ sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/50_linuxmint.cfg'
Sourcing file `/etc/default/grub.d/init-select.c
Confirmed from comment #11 by mbdev
Adding a global_filter to line 151 just after the default section
corrected the problem.
Before adding the filter to /etc/lvm/lvm.conf I was getting this:
```
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub
I'm running 19.10 x64 (up to date as of today), LVM setup. Originally
installed 19.04 and upgraded. This affects me too. Or, affected rather,
because after following advice from comment #9 above it seems fixed.
Details follow.
```
$ sudo update-grub2
Sourcing file `/etc/default/grub'
Sourcing file
Thank you, Zer00Cool, it helps. Here it was without any new device,
right after an installation with LVM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834250
Title:
update-grub complains about non
For me, but, sorry, in french !
# L'errreur affichée sur Debian lors de la mise à jour du Grub avec update-grub
:
/dev/sdb: open failed: No medium found
# La commande lsblk ne montre aucune partition sdb.
# La commande "sudo dmesg |grep sdb" affiche :
[3.48717] sd 6:0:0:0 [sdb] Attached SCSI re
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/1834250
Title:
upda
I am seeing the same behaviour. The system was installed with the 19.10
beta on LVM and kept up to date.
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1259:00 477G 0 disk
├─nvme0n1p1259:10 512M 0 part /boot/efi
└─nvme0n1p2259:2
Hi,
Same problem here. I want to skip the GRUP so I modify the grub file,
but once I run the command sudo update-grub the terminal show me the
same issue.
Thanks and if I can do anything tell me.
Alex
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
** Summary changed:
- update-grub complains about non-existent drives
+ update-grub complains about non-existent drives (due to cardreader)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834250
Title
** Changed in: grub2 (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834250
Title:
update-grub complains about non-existent drives
To manage notifications ab
I figured out what was causing this issue. I recently installed a multi-
card reader in a 5.25 bay that my system sees as separate drives and "no
medium found" errors are from no media being in the readers. I've since
unplugged all the wires for this device and the errors went away.
--
You receiv
UPDATE: I've installed Kubuntu 19.10 on a separate drive in the same
system and I've found that this bug still persists irregardless of
options. It doesn't matter if I choose encryption or not, nor lvm or
not. Out of curiosity, I booted a thumb drive with the latest live build
on UEFI and escaping
Hi Sebastien,
It's new for me with 19.10. I didn't have this issue with 19.04 either
while it was in development nor after release. I usually use lvm, but
this is the first time trying encryption.
I can reproduce it 100% of the time.
Thanks,
Scott
--
You received this bug notification because
Thank you for your bug report. Is that a new/recent issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834250
Title:
update-grub complains about non-existent drives
To manage notifications about
27 matches
Mail list logo
