Arch Linux

quellen

Member

From: Italy

Registered: 2014-05-24

Posts: 312

Re: no medium found errors

Have you tried installing 'lsscsi'?
I had the same problem and did a little research on the issue of SCSI Generic Driver.
Try:
  # pacman -S lsscsi

Related article: http://sg.danny.cz/sg/

Sam-the-6, have you solved?
i have installed lsscsi, and now what should i do?

$ lsscsi|grep Reader
[4:0:0:0]    disk    Generic  USB SD Reader    1.00  /dev/sdc 
[4:0:0:1]    disk    Generic  USB CF Reader    1.01  /dev/sdd 
[4:0:0:2]    disk    Generic  USB SM Reader    1.02  /dev/sde 
[4:0:0:3]    disk    Generic  USB MS Reader    1.03  /dev/sdf 

Last edited by quellen (2015-05-05 17:25:06)

---

sorry for my bad english

Razor X

Member

From: California

Registered: 2012-08-22

Posts: 14

Website

Re: no medium found errors

Have you tried installing 'lsscsi'?
I had the same problem and did a little research on the issue of SCSI Generic Driver.
Try:
  # pacman -S lsscsi

Related article: http://sg.danny.cz/sg/

Sam-the-6, have you solved?
i have installed lsscsi, and now what should i do?

$ lsscsi|grep Reader
[4:0:0:0]    disk    Generic  USB SD Reader    1.00  /dev/sdc 
[4:0:0:1]    disk    Generic  USB CF Reader    1.01  /dev/sdd 
[4:0:0:2]    disk    Generic  USB SM Reader    1.02  /dev/sde 
[4:0:0:3]    disk    Generic  USB MS Reader    1.03  /dev/sdf 

Did you ever solve this? I would also like to get rid of those messages (they pollute my dm-crypt login prompt).

quequotion

Member

From: Oita, Japan

Registered: 2013-07-29

Posts: 814

Website

Re: no medium found errors

I found these kernel options on the Silent boot wiki article.

It's a somewhat extreme solution, just make sure you have a stable boot strategy in place.

loglevel=0 udev.log-priority=0

I want systemd to generally shut up, so I enabled both. I think "udev.log-priority=0" is what does the trick for this annoyance (it should be enough to suppress the "no medium found" messages).
The logs are still written to the journal and dmesg (when available).

I added a few more kernel options:

vga=current vt.handoff=7

Ancient defaults in Ubuntu, these are purported to assist the transition from bootloader--specified as GRUB--through bootsplash--specified as Plymouth--to desktop manager--specified as LightDM. I'm using them with systemd's integrated gummiboot, which is not breaking at least

Plus: /etc/sysctl.d/20-quiet-printk.conf

kernel.printk = 0 0 0 0

Also from the article, but 0 for that extra "..." boot.

As a result I now have a total blackout between the uefi screen and lightdm... which I suppose is fine while plymouth refuses to cooperate, but a little eerie.

Last edited by quequotion (2015-07-20 09:03:40)

---

makepkg-optimize · indicator-powersave · pantheon-{3d,lite} · {pantheon,higan}-qq

4ndreas

Member

Registered: 2021-04-13

Posts: 2

Re: no medium found errors

Little late, but it didn't annoy me enough until now ;-)

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!

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,196

Re: no medium found errors

Closing this old thread, please pay attention to the dates and don't necrobump old topics.