The officially official Devuan Forum!

Lawson

Member

From: UK

Registered: 2020-11-25

Posts: 5  

[Solved] Boot error messages for non-existant drives

Hi,

Apologies if this is a noob question, but I am happy to learn and get my hands dirty if someone can help, please.

On boot, I am getting the following error(s)

[....] Setting up LVM Volume Groups...  /dev/sdb: open failed: No medium found
   /dev/sdc: open failed: No medium found
   /dev/sdd: open failed: No medium found
   /dev/sde: open failed: No medium found

As far as I know, I am not using LVM and none of these drives are in my /etc/fstab (only one line for my HDD, based on an a UUID identifier + swap and an NFS share).

Normally I would be happy to ignore it - everything boots fine otherwise - but I am using the sensor plugin on XFCE to display my coretemp-0 CPU temperatures and when my desktop starts I get 4 large warning panels telling me that it cannot read sensor information for /dev/sd[b-e], and I don't know it this is related or not.

I installed Devuan only a month or so ago from devuan_beowulf_3.0.0_amd64_desktop-live.iso written to a usb stick that identified itself as /dev/sdf during install (and has since been removed).
My hardware is quite old - a Hewlett Packard mini-tower that doesn't even have a HDMI port.

Please let me know if I can supply any relevant information.  I read the release notes, and have tried a search on these forums for boot AND error and LVM but couldn't find anything I thought was relevant.

advTHANKSance.

Last edited by Lawson (2020-11-26 10:38:30)

Dutch_Master

Member

Registered: 2018-05-31

Posts: 285  

Re: [Solved] Boot error messages for non-existant drives

Go into the BIOS and disable the unused SATA ports.

Lawson

Member

From: UK

Registered: 2020-11-25

Posts: 5  

Re: [Solved] Boot error messages for non-existant drives

Hi Dutch_Master,

Thanks for the reply - I had a look in the BIOS and couldn't seem to find a way.

However, I rebooted/restarted the desktop and the warning message for the Sensor plugin suggested

$ sudo chmod u+s /usr/sbin/hddtemp

to avoid the Permission denied messages.  Once I did this, I could do...

$ hddtemp /dev/sda
/dev/sda: ST3360320AS: 41°C
$ hddtemp /dev/sdb
/dev/sdb: Generic USB SD Reader: S.M.A.R.T. not available
$ hddtemp /dev/sdc
/dev/sdc: Generic USB CF Reader: S.M.A.R.T. not available
$ hddtemp /dev/sdd
/dev/sdd: Generic USB SM Reader: S.M.A.R.T. not available
$ hddtemp /dev/sde
/dev/sde: Generic USB MS Reader: S.M.A.R.T. not available

so it looks like I have some internal card readers that are taking up /dev/sd[b-e]

At least the desktop sensor messages have gone now, & I can live with the boot error messages as they don't interfere with anything - AFAIK.

It gives me something else to search on, too.

rolfie

Member

Registered: 2017-11-25

Posts: 1,172  

Re: [Solved] Boot error messages for non-existant drives

You can ignore the errors due to devices sdb to sde. Depending on the type of reader, there is no way to get rid of these messages (I have such an adapter myself in one of my PCs).

About the LVM: are you sure you haven't got that running? What is lsblk showing? Run this as root.

rolfie

Lawson

Member

From: UK

Registered: 2020-11-25

Posts: 5  

Re: [Solved] Boot error messages for non-existant drives

Hi rolfie,

$ sudo lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 335.4G  0 disk 
├─sda1   8:1    0     2G  0 part [SWAP]
├─sda2   8:2    0 228.3G  0 part /
├─sda3   8:3    0     1K  0 part 
└─sda5   8:5    0 103.3G  0 part 
sr0     11:0    1  1024M  0 rom 

sda5 is an old Ubuntu partition (for my 80yr old dad), but I'm not sure about the 1K sda3 partition, nor sr0

fsmithred

Administrator

Registered: 2016-11-25

Posts: 2,486  

Re: [Solved] Boot error messages for non-existant drives

sr0 = cdrom

If you used lvm previously on this drive, there might still be some metadata hanging around. I think in that case, gparted would show it, but you might also see it with lvdisplay and vgdisplay. You can get rid of that with lvremove and vgremove, but I think that will cause loss of data. So don't do that if you don't want to reinstall.

If you don't need to remove lvm metadata and you don't plan to use lvm, you could uninstall the lvm2 package. While you're at it, you could also uninstall mdadm if you're not using RAID.

rolfie

Member

Registered: 2017-11-25

Posts: 1,172  

Re: [Solved] Boot error messages for non-existant drives

Hi Lawson,

sda uses the traditional msdos partitioning, max of 4 primary partitions supported, or you use the dirty trick of adding an extended partition with logical drives. This is what we see here.

sda1 and sda2 are two primary partitions for swap and Devuan. sda3 is the extended partition for the rest of the drive which holds sda5 as first logical partition. This is normal naming. Everything fine and explainable.

lsblk does not show any indication of an open LVM. If the messages don't disturb you too much leave it as is.

Maybe the LVM is hidden in the Ubuntu stuff?

rolfie

Last edited by rolfie (2020-11-25 17:56:50)

golinux

Administrator

Registered: 2016-11-25

Posts: 3,317  

Re: [Solved] Boot error messages for non-existant drives

@rolfie . . . An "Invisible ink" trick?

---

Get answers - Help Devuan - Report a bug - Search packages

rolfie

Member

Registered: 2017-11-25

Posts: 1,172  

Re: [Solved] Boot error messages for non-existant drives

@rolfie . . . An "Invisible ink" trick?

Impressing, isn't it?

No, you were reading too fast. I just hit TAB in the middle of starting to answer, which posted what I wrote so far. Had to edit the post for a complete answer.

Sorry, easily explainable.

rolfie

Last edited by rolfie (2020-11-25 17:56:12)

Lawson

Member

From: UK

Registered: 2020-11-25

Posts: 5  

Re: [Solved] Boot error messages for non-existant drives

Hi rolfie,

Thanks for the explanation.  I think I'll take your advice to just leave it be.  It doesn't cause any issues, so I will ignore it.

Best,
L.

Lawson

Member

From: UK

Registered: 2020-11-25

Posts: 5  

Re: [Solved] Boot error messages for non-existant drives

Hi fsmithred,
I'll remove lvm2 and mdadm on this old clunker, but I'll leave off the lv/vgremove stuff.
Thanks for the info.

[edit 'cos I can't spell - fingers faster than brain]

Last edited by Lawson (2020-11-25 19:03:48)