You are not logged in.
Pages: 1
Topic closed
Greetings All,
I've got a fresh arch install with some error messages on boot. Never seen anything like this in over 20 arch installs. Scanned the webs but no substantial search results, nothing in the journal. Keeping in mind that the machine in question has only one hdd, these are the error messages:
error: /dev/sdb/: no medium found
error: /dev/sdc/: no medium found
error: /dev/sdd/: no medium found
error: /dev/sde/: no medium found
I don't know if this is a correlation, but in BIOS I can select to turn on up to 6 SATA drives. Other than that, everything works absolutely fine. I guess one option is to disable loglevel messages, but I'd really like to know what's going on. Anywho, I could really use some help on this one. If you guys have any questions feel free to ask, and sorry that I can't provide more information.
Last edited by w201 (2015-06-04 01:01:30)
Offline
Okay, seems like whenever you make a post, two minutes later you find an answer. Turns out this machine has a card reader, four to be exact, so problem solved.
Offline
Start with fstab and then check any automounting setup you're using.
Offline
Start with fstab and then check any automounting setup you're using.
fstab just has /dev/sda1 and /dev/sda2, other than that there's no automounting that I'm aware of. Any ideas how grub is able to detect those drives?
Last edited by w201 (2015-06-04 02:15:02)
Offline
Are you sure it's not boot order or something similar in BIOS?
Offline
Just checked, 1 is USB/DVD 2 is HDD, so it's not the boot sequence.
Offline
you can access to fdisk -l ??
Well, I suppose that this is somekind of signature, no?
Offline
you can access to fdisk -l ??
Disk /dev/sda: 232.9 GiB, 250000000000 bytes, 488281250 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
Disklabel type: gpt
Disk identifier: FA9878FD-3406-48CB-B351-F0268805D20C
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 41947135 41943040 20G Linux filesystem
/dev/sda3 41947136 488281216 446334081 212.8G Linux filesystem
Should have thought of this before, but I unplugged the card reader, a Dell TEAC CA-200 USB Flash Card Reader, and the error messages go away. I also found this thread:
https://bugs.launchpad.net/ubuntu/+sour … ug/1398025
Last edited by w201 (2015-06-05 13:45:58)
Offline
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!
Offline
I really doubt they're looking for more help nearly 6 years later.
Online
Closing this old thread, please pay attention to the dates and don't necrobump old topics.
Offline
Pages: 1
Topic closed