update-grub complains about non-existent drives (due to cardreader)

Thank you for your bug report. Is that a new/recent issue?

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

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 the splash screen and it complained about the missing drives while the live image was booting.

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.

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

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
nvme0n1 259:0 0 477G 0 disk
├─nvme0n1p1 259:1 0 512M 0 part /boot/efi
└─nvme0n1p2 259:2 0 476.4G 0 part
  └─vgkubuntu-root 253:0 0 475.5G 0 lvm /

Status changed to 'Confirmed' because the bug affects multiple users.

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 removable disk

# Je suppose donc que c'est le multi-lecteur de carte SD que j'ai ajouté, et, connecté en interne à la machine.

# Si ce lecteur n'est pas utilisé pour des fonctions lvm, l'ajouter au global_filter dans "/etc/lvm/lvm.conf".
sudo nano /etc/lvm/lvm.conf
# Ajouter la ligne suivante permettra de retirer les lignes "/dev/sdb: open failed: No medium found" :
global_filter = ["r|/dev/sdb|"]

# Exemple complémentaire :
# Accepte chaque périphériques de blocs :
# filter = [ "a|.*/|" ]
# Rejeter le lecteur de CD :
# filter = [ "r|/dev/cdrom|" ]

Résolu pour moi, avec ça !
Les messages d'erreur ne sont plus affichés dans mon cas.

Thank you, Zer00Cool, it helps. Here it was without any new device, right after an installation with LVM.

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 `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
Found linux image: /boot/vmlinuz-5.3.0-29-generic
Found initrd image: /boot/initrd.img-5.3.0-29-generic
Found linux image: /boot/vmlinuz-5.3.0-26-generic
Found initrd image: /boot/initrd.img-5.3.0-26-generic
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
```

It goes on, but I'm skipping it.

```
$ lsblk
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 512M 0 part /boot/efi
├─nvme0n1p2 259:2 0 732M 0 part /boot
└─nvme0n1p3 259:3 0 930.3G 0 part
  └─nvme0n1p3_crypt 253:0 0 930.3G 0 crypt
    ├─ubuntu--vg-root 253:1 0 929.3G 0 lvm /
    └─ubuntu--vg-swap_1 253:2 0 976M 0 lvm [SWAP]
```

Above I'm skipping bunch of loop## from output of lsblk.

The Ubuntu "Disks" app identified the /dev/sda as "Generic- SD/MMC". It seems it's a built-in card reader of my ThinkPad. I decided to follow comment #9 above to filter out that device from LVM. And, advice from comment #9 fixed the issue! Thanks a lot Zer00Cool!

What I did exactly is:

1. grep for "global_filter" in lvm.conf - that file is really long...

```
$ grep -Fn "global_filter" /etc/lvm/lvm.conf
142: # Configuration option devices/global_filter.
146: # Use global_filter to hide devices from these LVM system components.
148: # global_filter are not opened by LVM.
150: # global_filter = [ "a|.*/|" ]
```

2. After the commented out "global_filter" setting (line 150 in my case), I added the following:

```
global_filter = [ "r|/dev/sda|" ]
```

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 configuration file ...
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
  /dev/sda: open failed: No medium found
Found linux image: /boot/vmlinuz-5.3.0-46-lowlatency
```

After adding the comment, it seems to be corrected:

```
$ sudo 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.3.0-46-lowlatency
Found initrd image: /boot/initrd.img-5.3.0-46-lowlatency
Found linux image: /boot/vmlinuz-5.3.0-45-lowlatency
Found initrd image: /boot/initrd.img-5.3.0-45-lowlatency
Found linux image: /boot/vmlinuz-5.3.0-42-lowlatency
Found initrd image: /boot/initrd.img-5.3.0-42-lowlatency
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done
```

Wondering if there is any way to detect removable media not connected which was the source of my issue since my internal drives are NVMe and do not use SDx, those were USB keys as I recall.

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.cfg'
Generating grub configuration file ...
Found background: /boot/boot.png
Found background image: /boot/boot.png
Found linux image: /boot/vmlinuz-5.10.15-051015-lowlatency
Found initrd image: /boot/initrd.img-5.10.15-051015-lowlatency
  /dev/sdh: open failed: No medium found
  /dev/sdi: open failed: No medium found
  /dev/sdh: open failed: No medium found
  /dev/sdi: open failed: No medium found
done
```

This comes from lvs in lvm2

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-44-generic
Found initrd image: /boot/initrd.img-5.8.0-44-generic
File descriptor 4 (pipe:[48288]) leaked on lvs invocation. Parent PID 6394: /bin/sh
File descriptor 5 (pipe:[48288]) leaked on lvs invocation. Parent PID 6394: /bin/sh
File descriptor 9 (pipe:[48291]) leaked on lvs invocation. Parent PID 6394: /bin/sh
  /dev/sdd: open failed: No medium found
  /dev/sdd: open failed: No medium found
Adding boot menu entry for UEFI Firmware Settings
done

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 31.1M 1 loop /snap/snapd/11036
loop1 7:1 0 32.3M 1 loop /snap/snapd/11107
sda 8:0 0 1.1T 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
├─sda2 8:2 0 8G 0 part [SWAP]
└─sda3 8:3 0 1.1T 0 part /
sdb 8:16 0 10.9T 0 disk
└─sdb1 8:17 0 10.9T 0 part /var/CommuniGate
sdc 8:32 0 1.1T 0 disk
└─sdc1 8:33 0 1.1T 0 part /var/CommuniGate/SystemLogs

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 root 9 Apr 13 11:06 usb-Generic_USB_CF_Reader_058F312D81B-0:1 -> ../../sdf
lrwxrwxrwx 1 root root 9 Apr 13 11:06 usb-Generic_USB_MS_Reader_058F312D81B-0:3 -> ../../sdh
lrwxrwxrwx 1 root root 9 Apr 13 11:06 usb-Generic_USB_SD_Reader_058F312D81B-0:0 -> ../../sde
lrwxrwxrwx 1 root root 9 Apr 13 11:06 usb-Generic_USB_SM_Reader_058F312D81B-0:2 -> ../../sdg

Since all card reader slot device ids contain the unique 'Reader_058F312D81B', you can use the following global filter in lvm.conf.

"r|/dev/disk/by-id/.*Reader_058F312D81B.*" # filter out card reader slots

Good luck!

Mind the trailing "|" in above comment.

Hence the correct way is :

global_filter = [ "r|/dev/disk/by-id/.*Reader_058F312D81B.*|" ]

In MacBook Pro 2015, the inbuilt SD Card Reader needs to be filtered out. Comment#16 helped me fix the issue.

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 anything we can do to help fix this?

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/{vendor,model,rev}}
 /sys/block/sda/removable:1
 /sys/block/sda/device/vendor:Generic-
 /sys/block/sda/device/model:SD/MMC
 /sys/block/sda/device/rev:1.00

Original:
---

Error messages:

 $ sudo vgs
   /dev/sda: open failed: No medium found
   /dev/sda: open failed: No medium found

 $ echo $?
 0

NOTE syscalls/error codes for /dev/sda:

 $ sudo strace -f -e openat vgs 2>&1 | grep /dev/sda
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1 ENOMEDIUM (No medium found)
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No medium found)
   /dev/sda: open failed: No medium found
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1 ENOMEDIUM (No medium found)
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No medium found)
   /dev/sda: open failed: No medium found

Patched:
---

No messages:

 $ sudo vgs

 $ echo $?
 0

SAME syscalls/error codes for /dev/sda:

 $ sudo strace -f -e openat vgs 2>&1 | grep /dev/sda
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1 ENOMEDIUM (No medium found)
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No medium found)
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1 ENOMEDIUM (No medium found)
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No medium found)

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.

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.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

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
 $ lxc shell lp1834250

Container:
---

 # lsb_release -cs
 focal

focal-updates: error messages

 # dpkg -s lvm2 | grep Version:
 Version: 2.03.07-1ubuntu1

 # vgs
   /dev/sda: open failed: No medium found
   /dev/sda: open failed: No medium found

 # strace -e openat vgs 2>&1 | grep /dev/sda
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1 ENOMEDIUM (No medium found)
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No medium found)
   /dev/sda: open failed: No medium found
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1 ENOMEDIUM (No medium found)
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No medium found)
   /dev/sda: open failed: No medium found
 # vgs
   /dev/sda: open failed: No medium found
   /dev/sda: open failed: No medium found

focal-proposed: no error messages; same syscall behavior

 # echo 'deb http://archive.ubuntu.com/ubuntu focal-proposed main' >>/etc/apt/sources.list
 # apt update
 # apt-cache madison lvm2 | grep focal-proposed
       lvm2 | 2.03.07-1ubuntu1.1 | http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
 # apt install lvm2

 # dpkg -s lvm2 | grep Version:
 Version: 2.03.07-1ubuntu1.1

 # vgs
 #

 # strace -e openat vgs 2>&1 | grep /dev/sda
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1 ENOMEDIUM (No medium found)
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No medium found)
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_DIRECT|O_NOATIME) = -1 ENOMEDIUM (No medium found)
 openat(AT_FDCWD, "/dev/sda", O_RDONLY|O_NOATIME) = -1 ENOMEDIUM (No medium found)

All autopkgtests for the newly accepted lvm2 (2.03.07-1ubuntu1.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

docker.io-app/20.10.25-0ubuntu1~20.04.1 (amd64, ppc64el, s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#lvm2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!