no medium found errors

lukasm · 2014-11-23 13:45:38

Hi everyone

After a recent upgrade I suddenly get some errors when booting, these are a lot of error similar to

"no medium found at /dev/sdaX"

I have no idea where I find those in a log (they don't show up nor in dmesg nor in journalctl).

In journalctl I found the following entries:

Nov 23 14:34:32 X kernel: sd 6:0:0:3: [sdf] Attached SCSI removable disk
Nov 23 14:34:32 X kernel: sd 6:0:0:1: [sdd] Attached SCSI removable disk
Nov 23 14:34:32 X kernel: sd 6:0:0:0: [sdc] Attached SCSI removable disk
Nov 23 14:34:32 X kernel: sd 6:0:0:4: [sdg] Attached SCSI removable disk
Nov 23 14:34:32 X kernel: sd 6:0:0:2: [sde] Attached SCSI removable disk
Nov 23 14:34:32 X kernel: scsi 6:0:0:4: Direct-Access     Generic  STORAGE DEVICE   0551 PQ: 0 ANSI: 5
Nov 23 14:34:32 X kernel: scsi 6:0:0:3: Direct-Access     Generic  STORAGE DEVICE   0551 PQ: 0 ANSI: 5
Nov 23 14:34:32 X kernel: scsi 6:0:0:2: Direct-Access     Generic  STORAGE DEVICE   0551 PQ: 0 ANSI: 5
Nov 23 14:34:32 X kernel: scsi 6:0:0:1: Direct-Access     Generic  STORAGE DEVICE   0551 PQ: 0 ANSI: 5
Nov 23 14:34:32 X kernel: scsi 6:0:0:0: Direct-Access     Generic  STORAGE DEVICE   0551 PQ: 0 ANSI: 5

I don't know if this has to be like that, because there are no disks attached at sdc to sdg.

I mean basically everything works, but I have no clue where these errors come from. And after one boot suddenly sdb was mounted at sdg, when I reboot, it's at the normal place sdb again.

Today I did the following upgrades according to pacman.log

[2014-11-23 11:31] [PACMAN] starting full system upgrade
[2014-11-23 11:32] [PACMAN] upgraded glibc (2.20-2 -> 2.20-3)
[2014-11-23 11:32] [PACMAN] upgraded libdbus (1.8.8-1 -> 1.8.10-1)
[2014-11-23 11:32] [PACMAN] upgraded dbus (1.8.8-1 -> 1.8.10-1)
[2014-11-23 11:32] [PACMAN] upgraded glib2 (2.42.0-1 -> 2.42.1-1)
[2014-11-23 11:32] [PACMAN] upgraded kmod (18-2 -> 19-1)
[2014-11-23 11:32] [PACMAN] upgraded libsystemd (217-6 -> 217-7)
[2014-11-23 11:32] [PACMAN] upgraded systemd (217-6 -> 217-7)
[2014-11-23 11:32] [PACMAN] upgraded device-mapper (2.02.111-1 -> 2.02.112-1)
[2014-11-23 11:32] [PACMAN] upgraded gvfs (1.22.2-2 -> 1.22.2-3)
[2014-11-23 11:32] [PACMAN] upgraded gvfs-smb (1.22.2-2 -> 1.22.2-3)
[2014-11-23 11:32] [PACMAN] upgraded harfbuzz (0.9.35-2 -> 0.9.36-1)
[2014-11-23 11:32] [PACMAN] upgraded harfbuzz-icu (0.9.35-2 -> 0.9.36-1)
[2014-11-23 11:32] [PACMAN] upgraded lib32-libdbus (1.8.8-1 -> 1.8.10-1)
[2014-11-23 11:32] [PACMAN] upgraded lib32-mesa-dri (10.3.3-1 -> 10.3.4-1)
[2014-11-23 11:32] [PACMAN] upgraded mesa-dri (10.3.3-1 -> 10.3.4-1)
[2014-11-23 11:32] [PACMAN] upgraded mesa (10.3.3-1 -> 10.3.4-1)
[2014-11-23 11:32] [PACMAN] upgraded lib32-mesa (10.3.3-1 -> 10.3.4-1)
[2014-11-23 11:32] [PACMAN] upgraded lib32-mesa-libgl (10.3.3-1 -> 10.3.4-1)
[2014-11-23 11:32] [PACMAN] upgraded lib32-sqlite (3.8.7.1-1 -> 3.8.7.2-1)
[2014-11-23 11:32] [PACMAN] upgraded libimobiledevice (1.1.6-1 -> 1.1.7-1)
[2014-11-23 11:32] [PACMAN] upgraded libwebp (0.4.1-1 -> 0.4.2-1)
[2014-11-23 11:32] [PACMAN] upgraded lvm2 (2.02.111-1 -> 2.02.112-1)
[2014-11-23 11:32] [PACMAN] upgraded phpmyadmin (4.2.11-1 -> 4.2.12-1)
[2014-11-23 11:32] [PACMAN] upgraded systemd-sysvcompat (217-6 -> 217-7)
[2014-11-23 11:32] [PACMAN] upgraded upower (0.99.1-2 -> 0.99.1-3)
[2014-11-23 11:32] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2014-11-23 11:32] [PACMAN] upgraded virtualbox-host-modules (4.3.18-4 -> 4.3.20-1)
[2014-11-23 11:32] [PACMAN] upgraded virtualbox (4.3.18-1 -> 4.3.20-1)
[2014-11-23 11:32] [PACMAN] upgraded virtualbox-guest-iso (4.3.18-1 -> 4.3.20-1)
[2014-11-23 11:32] [PACMAN] upgraded xorg-xkbcomp (1.2.4-2 -> 1.3.0-1)

Thanks for answering!

TheSaint · 2014-11-23 15:00:59

Do you have a card reader in your PC?

lukasm · 2014-11-23 15:08:09

Yes I have a cardreader which seems to work. And it's true that these are the other sdX.

I mean, nothing has changed since yesterday, so do I have to care about these messages? And what could be the reason for them?

TheSaint · 2014-11-23 17:06:12

It's obvious that if any of the slot is empty the kernel will report such message, which is harmless.

lukasm · 2014-11-23 17:49:07

And why do I get this "no media found" messages since today? I mean that suggests that something has changed?

I haven't changed anything except updating a few packages.

TheSaint · 2014-11-24 14:57:59

I was searching an answer. Maybe with more details I'll know the answer.
What we'll se by if is internal

$ lspci -vnn > /to/file/hosting/and/post/the/link

if is USB

$ lsusb > /to/file/hosting/and/post/the/link

Otherwise you might assume that is a simple harmless message.

tzoi516 · 2014-11-24 15:12:33

I get the same thing, along with hwdb.bin doesn't exist

I have lvm2 with encryption, so I assume it's because it can't read anything until after I enter my password. Everything still works normally.

lukasm · 2014-11-24 15:40:45

So I copied both of the outputs to pastebin.

lsusb
http://pastebin.com/gwBGxmGH

lspci
http://pastebin.com/ZCg8pnHd

So the cardreader the devices belong to is this line here:

Bus 004 Device 002: ID 05e3:0732 Genesys Logic, Inc. All-in-One Cardreader

Would be great if you had an answer!

@tzoi516: Do you get it too only for about 3 days or so?

Last edited by lukasm (2014-11-24 15:41:32)

tzoi516 · 2014-11-24 16:13:17

Yes, at least 3 days. I get more lines when I plug in my USB3 drive before I turn my computer on.

Except for those lines at boot that don't show up in journalctl things still run normally. I believe someone is working on a fix.

TheSaint · 2014-11-24 19:20:21

What I found is regarding xhci_hcd module. Another would be g_mass_storage module. But researches are leading nowhere.
If I put the vendorID and productID, some complain lead to ubuntu forum.
The best I got is this. That intuitively gives me to think that some print out is left in that code to note the module functioning.
Maybe USB2.0 port won't issue these messages.

Last edited by TheSaint (2014-11-24 19:21:11)

tzoi516 · 2014-11-25 15:26:07

This started happening to me shortly after I added the Intel microcode line to grub.cfg.

TheSaint · 2014-11-25 15:35:49

OK, assuming that you're correct. What happen if you remove it?
Then we can detect the cause, doesn't it?

ratcheer · 2014-11-25 15:45:46

I have the same problem, occasionally. The most recent time was this morning. It gives me several of the "device not found" messages, then the bootup process just stops - no prompt or anything. With no changes whatsoever, I press the hardware reset button, then the system reboots, normally and completely.

Yes, the devices it complains about are probably multi-card reader devices.

Tim

TheSaint · 2014-11-25 15:59:30

@ ratcheer, do you have one, right?
Does happen if is unplugged, (if external) ?

ratcheer · 2014-11-25 22:02:27

TheSaint wrote:

@ ratcheer, do you have one, right?
Does happen if is unplugged, (if external) ?

Sorry, it is an internally installed card reader. It came in the system when it was new.

And, unplugging it wouldn't really tell us anything, because the problem only occurs occasionally.

Thanks,
Tim

TheSaint · 2014-11-26 08:50:29

Couldn't it maybe is related with fsck?

lukasm · 2014-11-26 08:51:54

Thanks TheSaint for your help. It's true that my cardreader uses USB3, but I can't plug it in at a USB2 port to compare.

As far as I can see the error doesn't show up every time too, but at more than half the time. I today did some comparisons between the journalctl outputs.

First I found the error finally in the logs.

#! journalctl -b-1 | grep "No medium found"
Nov 26 09:14:57 X systemd-udevd[219]: error: /dev/sdc: No medium found
Nov 26 09:14:57 X systemd-udevd[219]: error: /dev/sdd: No medium found
Nov 26 09:14:57 X systemd-udevd[219]: error: /dev/sdb: No medium found
Nov 26 09:14:57 X systemd-udevd[219]: error: /dev/sde: No medium found
Nov 26 09:14:57 X systemd-udevd[219]: error: /dev/sdf: No medium found

Another boot the errors were much longer (i.e. twice the same errors) e.g.

Nov 26 08:50:48 X systemd-udevd[212]: error: /dev/sdc: No medium found
Nov 26 08:50:48 X systemd-udevd[212]: error: /dev/sdd: No medium found
Nov 26 08:50:48 X systemd-udevd[212]: error: /dev/sdf: No medium found
Nov 26 08:50:48 X systemd-udevd[212]: error: /dev/sdg: No medium found
Nov 26 08:50:48 X systemd-udevd[212]: error: /dev/sde: No medium found
Nov 26 08:50:48 X systemd-udevd[212]: error: /dev/sdc: No medium found
Nov 26 08:50:48 X systemd-udevd[212]: error: /dev/sdd: No medium found
Nov 26 08:50:48 X systemd-udevd[212]: error: /dev/sdf: No medium found
Nov 26 08:50:48 X systemd-udevd[212]: error: /dev/sdg: No medium found
Nov 26 08:50:48 X systemd-udevd[212]: error: /dev/sde: No medium found

I'm not yet sure when these errors show up twice and if this is the case when I observe it on screen, but maybe that goes in the right direction.

Another thing that may be related to this, is, that sometimes it attachs my harddisk at sdb and sometimes at sdg.

And a last thing is: Sometimes it seems to recognize my CD-Reader, sometimes not, so these lines are missing sometimes (because I mostly never use my CD-Device, I probably never noticed.

Nov 26 08:50:48 X kernel: ata5.00: ATAPI: TSSTcorp CDDVDW SH-S223C, SB06, max UDMA/100
Nov 26 08:50:48 X kernel: scsi 4:0:0:0: CD-ROM            TSSTcorp CDDVDW SH-S223C  SB06 PQ: 0 ANSI: 5
Nov 26 08:50:48 X kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
Nov 26 08:50:48 X kernel: sr 4:0:0:0: Attached scsi CD-ROM sr0

Probably this helps looking for a solution (or at least a reason).

Regards

TheSaint · 2014-11-27 01:14:48

I got news told me that don't matter USB3.0 or lower version, still same. So we should wait some developer to discover the black magic of this

Last edited by TheSaint (2014-11-27 01:16:21)

mich41 · 2014-11-27 20:48:02

Probably an effect of this systemd and upower update.

You can fix it by stuffing all card reader slots with some cards

quellen · 2014-12-17 18:09:02

same problem, how can I solved? :-(

# journalctl -b|grep -i error
dic 17 19:00:44 linux kernel: ioapic: probe of 0000:00:00.5 failed with error -22
dic 17 19:00:48 linux systemd-udevd[158]: error: /dev/sde: No medium found
dic 17 19:00:48 linux systemd-udevd[158]: error: /dev/sdc: No medium found
dic 17 19:00:48 linux systemd-udevd[158]: error: /dev/sdf: No medium found
dic 17 19:00:48 linux systemd-udevd[158]: error: /dev/sdd: No medium found
dic 17 19:01:25 linux kactivitymanagerd[454]: Couldn't start kded5 from org.kde.kded5.service: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name org.kde.kded5 was not provided by any .service files") , falling back to running kbuildsycoca5
dic 17 19:01:25 linux kbuildsycoca5[460]: Parse error in  "/home/pippo/.config/menus/applications-merged/xdg-desktop-menu-dummy.menu" , line  1 , col  1 :  "unexpected end of file"

ratcheer wrote:

The most recent time was this morning. It gives me several of the "device not found" messages, then the bootup process just stops - no prompt or anything. With no changes whatsoever, I press the hardware reset button, then the system reboots, normally and completely.
Tim

i too.

https://bugs.freedesktop.org/show_bug.cgi?id=86414

Last edited by quellen (2014-12-17 20:18:48)

quequotion · 2015-01-06 03:54:08

quellen wrote:

https://bugs.freedesktop.org/show_bug.cgi?id=86414

Lennart Poettering wrote:

Again, this is really an issue with certain device/driver combinations. Either way this needs to be fixed in the kernel. Please report this as kernel bug, there's nothing to do in the systemd/udev context.

This is why we can't have nice things systemd gets boycotted.

How about suppressing the error? Disabling the card reader until after boot?

TheSaint · 2015-01-06 08:04:26

quequotion wrote:

How about suppressing the error? Disabling the card reader until after boot?

The latter is quite reasonable.

quequotion · 2015-01-26 13:38:37

TheSaint wrote:

quequotion wrote:
How about suppressing the error? Disabling the card reader until after boot?
The latter is quite reasonable.

How would you go about doing it?
I have in mind to find a solution with udev, and I'm curious if this advice on the wiki could be adapted to the purpose.

Here's one of the devices (the CF slot of a multi-card reader):
udevadm info -a -p $(udevadm info -q path -n /dev/sdf)

looking at device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host8/target8:0:0/8:0:0:0/block/sdf':
  KERNEL=="sdf"
  SUBSYSTEM=="block"
  DRIVER==""
  ATTR{ro}=="0"
  ATTR{size}=="0"
  ATTR{stat}=="       0        0        0        0        0        0        0        0        0        0        0"
  ATTR{range}=="16"
  ATTR{discard_alignment}=="0"
  ATTR{events}=="media_change"
  ATTR{ext_range}=="256"
  ATTR{events_poll_msecs}=="-1"
  ATTR{alignment_offset}=="0"
  ATTR{inflight}=="       0        0"
  ATTR{removable}=="1"
  ATTR{capability}=="51"
  ATTR{events_async}==""

looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host8/target8:0:0/8:0:0:0':
  KERNELS=="8:0:0:0"
  SUBSYSTEMS=="scsi"
  DRIVERS=="sd"
  ATTRS{rev}=="0.00"
  ATTRS{type}=="0"
  ATTRS{scsi_level}=="3"
  ATTRS{model}=="Compact Flash   "
  ATTRS{state}=="running"
  ATTRS{queue_type}=="none"
  ATTRS{iodone_cnt}=="0xe78"
  ATTRS{iorequest_cnt}=="0xe78"
  ATTRS{device_busy}=="0"
  ATTRS{evt_capacity_change_reported}=="0"
  ATTRS{timeout}=="30"
  ATTRS{evt_media_change}=="0"
  ATTRS{max_sectors}=="240"
  ATTRS{ioerr_cnt}=="0xe77"
  ATTRS{queue_depth}=="1"
  ATTRS{vendor}=="Generic "
  ATTRS{evt_soft_threshold_reached}=="0"
  ATTRS{device_blocked}=="0"
  ATTRS{evt_mode_parameter_change_reported}=="0"
  ATTRS{evt_lun_change_reported}=="0"
  ATTRS{evt_inquiry_change_reported}=="0"
  ATTRS{iocounterbits}=="32"
  ATTRS{eh_timeout}=="10"

looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host8/target8:0:0':
  KERNELS=="target8:0:0"
  SUBSYSTEMS=="scsi"
  DRIVERS==""

looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/host8':
  KERNELS=="host8"
  SUBSYSTEMS=="scsi"
  DRIVERS==""

looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0':
  KERNELS=="1-1.4:1.0"
  SUBSYSTEMS=="usb"
  DRIVERS=="usb-storage"
  ATTRS{bInterfaceClass}=="08"
  ATTRS{bInterfaceSubClass}=="06"
  ATTRS{bInterfaceProtocol}=="50"
  ATTRS{bNumEndpoints}=="02"
  ATTRS{supports_autosuspend}=="1"
  ATTRS{bAlternateSetting}==" 0"
  ATTRS{bInterfaceNumber}=="00"

looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4':
  KERNELS=="1-1.4"
  SUBSYSTEMS=="usb"
  DRIVERS=="usb"
  ATTRS{bDeviceSubClass}=="00"
  ATTRS{bDeviceProtocol}=="00"
  ATTRS{devpath}=="1.4"
  ATTRS{idVendor}=="048d"
  ATTRS{speed}=="480"
  ATTRS{bNumInterfaces}==" 1"
  ATTRS{bConfigurationValue}=="1"
  ATTRS{bMaxPacketSize0}=="64"
  ATTRS{busnum}=="1"
  ATTRS{devnum}=="3"
  ATTRS{configuration}==""
  ATTRS{bMaxPower}=="500mA"
  ATTRS{authorized}=="1"
  ATTRS{bmAttributes}=="80"
  ATTRS{bNumConfigurations}=="1"
  ATTRS{maxchild}=="0"
  ATTRS{bcdDevice}=="0100"
  ATTRS{avoid_reset_quirk}=="0"
  ATTRS{quirks}=="0x0"
  ATTRS{serial}=="0000000000000006"
  ATTRS{version}==" 2.00"
  ATTRS{urbnum}=="74091"
  ATTRS{ltm_capable}=="no"
  ATTRS{manufacturer}=="Generic "
  ATTRS{removable}=="unknown"
  ATTRS{idProduct}=="1345"
  ATTRS{bDeviceClass}=="00"
  ATTRS{product}=="Mass Storage Device"

looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1/1-1':
  KERNELS=="1-1"
  SUBSYSTEMS=="usb"
  DRIVERS=="usb"
  ATTRS{bDeviceSubClass}=="00"
  ATTRS{bDeviceProtocol}=="01"
  ATTRS{devpath}=="1"
  ATTRS{idVendor}=="8087"
  ATTRS{speed}=="480"
  ATTRS{bNumInterfaces}==" 1"
  ATTRS{bConfigurationValue}=="1"
  ATTRS{bMaxPacketSize0}=="64"
  ATTRS{busnum}=="1"
  ATTRS{devnum}=="2"
  ATTRS{configuration}==""
  ATTRS{bMaxPower}=="0mA"
  ATTRS{authorized}=="1"
  ATTRS{bmAttributes}=="e0"
  ATTRS{bNumConfigurations}=="1"
  ATTRS{maxchild}=="6"
  ATTRS{bcdDevice}=="0000"
  ATTRS{avoid_reset_quirk}=="0"
  ATTRS{quirks}=="0x0"
  ATTRS{version}==" 2.00"
  ATTRS{urbnum}=="34"
  ATTRS{ltm_capable}=="no"
  ATTRS{removable}=="unknown"
  ATTRS{idProduct}=="0024"
  ATTRS{bDeviceClass}=="09"

looking at parent device '/devices/pci0000:00/0000:00:1a.0/usb1':
  KERNELS=="usb1"
  SUBSYSTEMS=="usb"
  DRIVERS=="usb"
  ATTRS{bDeviceSubClass}=="00"
  ATTRS{bDeviceProtocol}=="00"
  ATTRS{devpath}=="0"
  ATTRS{idVendor}=="1d6b"
  ATTRS{speed}=="480"
  ATTRS{bNumInterfaces}==" 1"
  ATTRS{bConfigurationValue}=="1"
  ATTRS{bMaxPacketSize0}=="64"
  ATTRS{authorized_default}=="1"
  ATTRS{busnum}=="1"
  ATTRS{devnum}=="1"
  ATTRS{configuration}==""
  ATTRS{bMaxPower}=="0mA"
  ATTRS{authorized}=="1"
  ATTRS{bmAttributes}=="e0"
  ATTRS{bNumConfigurations}=="1"
  ATTRS{maxchild}=="2"
  ATTRS{bcdDevice}=="0318"
  ATTRS{avoid_reset_quirk}=="0"
  ATTRS{quirks}=="0x0"
  ATTRS{serial}=="0000:00:1a.0"
  ATTRS{version}==" 2.00"
  ATTRS{urbnum}=="24"
  ATTRS{ltm_capable}=="no"
  ATTRS{manufacturer}=="Linux 3.18.1-3-ck ehci_hcd"
  ATTRS{removable}=="unknown"
  ATTRS{idProduct}=="0002"
  ATTRS{bDeviceClass}=="09"
  ATTRS{product}=="EHCI Host Controller"

looking at parent device '/devices/pci0000:00/0000:00:1a.0':
  KERNELS=="0000:00:1a.0"
  SUBSYSTEMS=="pci"
  DRIVERS=="ehci-pci"
  ATTRS{irq}=="16"
  ATTRS{subsystem_vendor}=="0x1849"
  ATTRS{broken_parity_status}=="0"
  ATTRS{class}=="0x0c0320"
  ATTRS{companion}==""
  ATTRS{driver_override}=="(null)"
  ATTRS{consistent_dma_mask_bits}=="32"
  ATTRS{dma_mask_bits}=="32"
  ATTRS{local_cpus}=="ffffffff,ffffffff,ffffffff,ffffffff"
  ATTRS{device}=="0x1c2d"
  ATTRS{uframe_periodic_max}=="100"
  ATTRS{enable}=="1"
  ATTRS{msi_bus}=="1"
  ATTRS{local_cpulist}=="0-127"
  ATTRS{vendor}=="0x8086"
  ATTRS{subsystem_device}=="0x1c2d"
  ATTRS{d3cold_allowed}=="1"

looking at parent device '/devices/pci0000:00':
  KERNELS=="pci0000:00"
  SUBSYSTEMS==""
  DRIVERS==""

There are a number of ATTRS that could be used to identify the device, although I'd most prefer to use idProduct and idVendor (all the slots share 1345:048d, which may stand for "Mass Storage Device":"Generic"). There are also a number of udisk parameters that could be set on it, but I think UDISKS_SYSTEM_INTERNAL="0" as in the wiki is the most likely to resolve the issue.

The slots also share ATTRS{removable}=="unknown", which seems symptomatic of the issue discussed in the wiki, although the wiki mentions neither the "no medium found" errors nor "ATTRS{removable}".

These rules have no effect:

SUBSYSTEMS=="usb", ATTRS{idProduct}=="1345", ATTRS{idVendor}=="048d", ENV{UDISKS_SYSTEM_INTERNAL}="0"

SUBSYSTEMS=="usb", ATTRS{idProduct}=="1345", ATTRS{idVendor}=="048d", ATTRS{removable}="1"

Last edited by quequotion (2015-01-29 18:46:57)

alphaniner · 2015-01-26 14:28:21

You could check other devices:

$ udevadm info -a -p /sys/class/block/sda |grep removable          # SATA HDD
    ATTR{removable}=="0"
$ udevadm info -a -p /sys/class/block/sde |grep removable          # CF card in IDE adapter
    ATTR{removable}=="0"
$ udevadm info -a -p /sys/class/block/sdf |grep removable          # USB thumb drive
    ATTR{removable}=="1"
    ATTRS{removable}=="unknown"
    ATTRS{removable}=="unknown"

Sam-the-6 · 2015-05-05 14:29:38

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

Arch Linux

#1 2014-11-23 13:45:38

no medium found errors

#2 2014-11-23 15:00:59

Re: no medium found errors

#3 2014-11-23 15:08:09

Re: no medium found errors

#4 2014-11-23 17:06:12

Re: no medium found errors

#5 2014-11-23 17:49:07

Re: no medium found errors

#6 2014-11-24 14:57:59

Re: no medium found errors

#7 2014-11-24 15:12:33

Re: no medium found errors

#8 2014-11-24 15:40:45

Re: no medium found errors

#9 2014-11-24 16:13:17

Re: no medium found errors

#10 2014-11-24 19:20:21

Re: no medium found errors

#11 2014-11-25 15:26:07

Re: no medium found errors

#12 2014-11-25 15:35:49

Re: no medium found errors

#13 2014-11-25 15:45:46

Re: no medium found errors

#14 2014-11-25 15:59:30

Re: no medium found errors

#15 2014-11-25 22:02:27

Re: no medium found errors

#16 2014-11-26 08:50:29

Re: no medium found errors

#17 2014-11-26 08:51:54

Re: no medium found errors

#18 2014-11-27 01:14:48

Re: no medium found errors

#19 2014-11-27 20:48:02

Re: no medium found errors

#20 2014-12-17 18:09:02

Re: no medium found errors

#21 2015-01-06 03:54:08

Re: no medium found errors

#22 2015-01-06 08:04:26

Re: no medium found errors

#23 2015-01-26 13:38:37

Re: no medium found errors

#24 2015-01-26 14:28:21

Re: no medium found errors

#25 2015-05-05 14:29:38

Re: no medium found errors

Board footer