[SOLVED] a warning "/dev/sde no medium found" everywhere

[Lycoris]

I met a problem, a warning "/dev/sde open failed: no medium found" was appeared in results of many commands, such as pvs/vgs.


root@pve:/etc/pve/qemu-server# vgs
/dev/sde: open failed: No medium found
VG #PV #LV #SN Attr VSize VFree
disk2 1 1 0 wz--n- 238.47g 88.47g
pve 1 5 0 wz--n- <476.44g <16.00g

root@pve:/etc/pve/qemu-server# pvs
/dev/sde: open failed: No medium found
PV VG Fmt Attr PSize PFree
/dev/nvme0n1 disk2 lvm2 a-- 238.47g 88.47g
/dev/nvme1n1p3 pve lvm2 a-- <476.44g <16.00g


But I didn't have this drive at all.

root@pve:/etc/pve/qemu-server# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 3.7T 0 disk
├─sda1 8:1 0 2G 0 part
└─sda2 8:2 0 3.7T 0 part
sdb 8:16 0 3.7T 0 disk
├─sdb1 8:17 0 2G 0 part
└─sdb2 8:18 0 3.7T 0 part
sdc 8:32 0 3.7T 0 disk
├─sdc1 8:33 0 2G 0 part
└─sdc2 8:34 0 3.7T 0 part
sdd 8:48 0 931.5G 0 disk
└─sdd1 8:49 0 931.5G 0 part
nvme0n1 259:0 0 238.5G 0 disk
└─disk2-vm--103--disk--0 253:8 0 150G 0 lvm
nvme1n1 259:1 0 477G 0 disk
├─nvme1n1p1 259:2 0 1007K 0 part
├─nvme1n1p2 259:3 0 512M 0 part
└─nvme1n1p3 259:4 0 476.4G 0 part
├─pve-swap 253:0 0 8G 0 lvm [SWAP]
├─pve-root 253:1 0 100G 0 lvm /
├─pve-data_tmeta 253:2 0 3.5G 0 lvm
│ └─pve-data-tpool 253:4 0 345.4G 0 lvm
│ ├─pve-data 253:5 0 345.4G 0 lvm
│ ├─pve-vm--101--disk--0 253:6 0 40G 0 lvm
│ └─pve-vm--102--disk--0 253:7 0 32G 0 lvm
└─pve-data_tdata 253:3 0 345.4G 0 lvm
└─pve-data-tpool 253:4 0 345.4G 0 lvm
├─pve-data 253:5 0 345.4G 0 lvm
├─pve-vm--101--disk--0 253:6 0 40G 0 lvm
└─pve-vm--102--disk--0 253:7 0 32G 0 lvm

So, how can I solve this problem?

 

[Stoiko Ivanov]

hmm - do you have a '/dev/sde' device node?:
* `ls -la /dev/sde`
* `dmesg |grep sde`

some other users noticed that they get this message for a card-reader in their system: https://bbs.archlinux.org/viewtopic.php?id=198226

if you don't have a '/dev/sde' in your system - does it show up in the lvm-configs:
`grep -r sde /etc/lvm`

I hope this helps!

 

[Republicus]

I am having the very same issue on latest proxmox. Fresh install of proxmox and only one ssd attached.

This appears to be an issue (for me) with usb devices.
In my case I have an IP KVM interface/dongle that is now trying to be mounted as /dev/sda or /dev/sdb
The second one was a bad ISO mounted on my motherboard via ICMP. Unmounting the ISO resolved one failing device.
But, naturally I need my KVM device attached so I don't know what to do concerning it.

root@pvesan:~# fdisk -l
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Disk model: LITEON CV8-8E128
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: EA05F665-2D6E-4559-9DDB-9917B9278BB4

Device       Start       End   Sectors   Size Type
/dev/sda1       34      2047      2014  1007K BIOS boot
/dev/sda2     2048   1050623   1048576   512M EFI System
/dev/sda3  1050624 250069646 249019023 118.8G Linux LVM


Disk /dev/mapper/pve-swap: 16 GiB, 17179869184 bytes, 33554432 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-root: 29.5 GiB, 31675383808 bytes, 61865984 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

root@pvesan:~# update-grub
Generating grub configuration file ...
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
Found linux image: /boot/vmlinuz-5.0.15-1-pve
Found initrd image: /boot/initrd.img-5.0.15-1-pve
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
  /dev/sdb: open failed: No medium found
  /dev/sdc: open failed: No medium found
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
done

 

[Stoiko Ivanov]

either you attach a dummy image to the KVM-drive - or (not sure if this helps with the `update-grub` calls) you can consider adding the device to the 'global_filter' in '/etc/lvm/lvm.conf' (the comments in the file explain what format the global_filter needs to be)

I hope this helps!

 

[Lycoris]

hmm - do you have a '/dev/sde' device node?:
* `ls -la /dev/sde`
* `dmesg |grep sde`

some other users noticed that they get this message for a card-reader in their system: https://bbs.archlinux.org/viewtopic.php?id=198226

if you don't have a '/dev/sde' in your system - does it show up in the lvm-configs:
`grep -r sde /etc/lvm`

I hope this helps!

Thanks, I really found this device by "ls /dev/sde", and "dmesg | grep sde" shows"[ 2.820666] sd 7:0:0:0: [sde] Attached SCSI removable disk".

So I guess it is a card reader on my chassis' front board.

 

[Stoiko Ivanov]

Glad you found out where the message is originating!
Please mark the thread as solved - so that others know what to expect
Thanks!

 

[Republicus]

This really isn't the behavior we have expected or should expect. It's not a proxmox originating issue; so where best should this be reported? Is this udev causing the issues?

 

[tommyc]

I ran into this myself. If you are not going to use that drive for any lvm functions you can add it to the
global_filter in /etc/lvm.conf

global_filter = [ "r|/dev/sde|, r|/dev/zd.*|", "r|/dev/mapper/pve-.*|" "r|/dev/mapper/.*-(vm|base)--[0-9]+--disk--[0-9]+|"]

# Example
# Accept every block device:
# filter = [ "a|.*/|" ]
# Reject the cdrom drive:
# filter = [ "r|/dev/cdrom|" ]

 

[Yuneldeltoro]

I have same problem:
root@pve123: /# vgs
/dev/sdf: open failed: No medium found
/dev/sdg: open failed: No medium found
/dev/sdh: open failed: No medium found
/dev/sdi: open failed: No medium found
/dev/sdj: open failed: No medium found
VG #PV #LV #SN Attr VSize VFree
pve 1 2 0 wz--n- ******** *****

My Solution.
Add in global_filter "r|/dev/sd[f-j]|",

global_filter = [ "r|/dev/sd[f-j]|", ...

from shell:
# sed -i -e "s/global_filter = \[/global_filter = [\ \"r\|\/dev\/sd\[f-j\]\|\",/" /etc/lvm/lvm.conf