LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 11-10-2019, 02:00 PM   #1
linustalman
Senior Member
 
Registered: Mar 2010
Location: Ireland
Distribution: Debian 10 (Buster) x64
Posts: 4,504

Rep: Reputation: 445Reputation: 445Reputation: 445Reputation: 445Reputation: 445
Question Error messages on bootup: "open failed: No medium found".


Hi.

I use LUKS and my drive is dev/sda1. My PC boots fine.

However, on bootup, I get these messages:

Code:
/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
/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
Why am I getting these messages and can it be remedied?

Thanks.
 
Old 11-10-2019, 10:26 PM   #2
RandomTroll
Senior Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 1,559

Rep: Reputation: 248Reputation: 248Reputation: 248
Because you have entries for all those devices in /etc/fstab but they don't exist. I get the same for entries for removable drives that aren't installed at boot: that's not a problem. If you actually have hardware attached to all those devices then there's a problem with them.
 
1 members found this post helpful.
Old 11-12-2019, 06:41 AM   #3
linustalman
Senior Member
 
Registered: Mar 2010
Location: Ireland
Distribution: Debian 10 (Buster) x64
Posts: 4,504

Original Poster
Rep: Reputation: 445Reputation: 445Reputation: 445Reputation: 445Reputation: 445
Post

Quote:
Originally Posted by RandomTroll View Post
Because you have entries for all those devices in /etc/fstab but they don't exist. I get the same for entries for removable drives that aren't installed at boot: that's not a problem. If you actually have hardware attached to all those devices then there's a problem with them.
Hi RT.

The only sda entry in my fstab file is this comment line:
Code:
# /boot was on /dev/sda1 during installation
 
Old 11-12-2019, 06:48 AM   #4
jsbjsb001
Senior Member
 
Registered: Mar 2009
Location: Earth, unfortunately...
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,835

Rep: Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034
Where are you seeing these messages? Your system logs? Because without knowing exactly where they are coming from, it's hard to say much else beyond what was said above.

It would be helpful to know what program is causing these messages.

If they are in your system logs, then you would need to post the relevant part of the log - as in the whole line of each message. As this might tell you what is actually causing them.
 
Old 11-12-2019, 06:53 AM   #5
linustalman
Senior Member
 
Registered: Mar 2010
Location: Ireland
Distribution: Debian 10 (Buster) x64
Posts: 4,504

Original Poster
Rep: Reputation: 445Reputation: 445Reputation: 445Reputation: 445Reputation: 445
Post

Quote:
Originally Posted by jsbjsb001 View Post
Where are you seeing these messages? Your system logs? Because without knowing exactly where they are coming from, it's hard to say much else beyond what was said above.

It would be helpful to know what program is causing these messages.

If they are in your system logs, then you would need to post the relevant part of the log - as in the whole line of each message. As this might tell you what is actually causing them.
Hi jsbjsb001.

I replaced my PC name with 'XXXXX'. BTW, I use LUKS full disk encryption.

I ran this to get them:

Code:
sudo cat /var/log/boot.log
Code:
  Volume group "XXXXXX-vg" not found
  Cannot process volume group XXXXX-vg
  Volume group "XXXXXX-vg" not found
  Cannot process volume group XXXXX-vg
/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
  /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
/dev/mapper/XXXXX--vg-root: clean, 882426/121028608 files, 153652035/484100096 blocks
 
Old 11-12-2019, 07:00 AM   #6
jsbjsb001
Senior Member
 
Registered: Mar 2009
Location: Earth, unfortunately...
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,835

Rep: Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034
It looks like it's coming from LVM based on your output of boot.log above.

But while I have done some reading about LVM, and get at least the basic idea of it; I don't use it myself. So I'm not an "expert" on it. So all I can suggest is to read up about it, and find out how you configure it so it isn't looking for something that doesn't appear to be there.

Then again, if your system still boots and there's no actual problem(s), you could just ignore it...
 
Old 11-12-2019, 05:54 PM   #7
RandomTroll
Senior Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 1,559

Rep: Reputation: 248Reputation: 248Reputation: 248
Quote:
Originally Posted by linustalman View Post
Hi RT.

The only sda entry in my fstab file is this comment line:
Code:
# /boot was on /dev/sda1 during installation
The error messages are about /dev/sd[b-g], not /dev/sda. That's a comment in your fstab. Perhaps these other devices are aliased?

Do they exist physically?
 
Old 11-12-2019, 06:40 PM   #8
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 5,298

Rep: Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021
post your grub.cfg
 
Old 11-13-2019, 04:37 AM   #9
linustalman
Senior Member
 
Registered: Mar 2010
Location: Ireland
Distribution: Debian 10 (Buster) x64
Posts: 4,504

Original Poster
Rep: Reputation: 445Reputation: 445Reputation: 445Reputation: 445Reputation: 445
Question

Quote:
Originally Posted by colorpurple21859 View Post
post your grub.cfg
Hi colorpurple21859. Do you refer to '/etc/default/grub'?
 
Old 11-13-2019, 04:37 AM   #10
linustalman
Senior Member
 
Registered: Mar 2010
Location: Ireland
Distribution: Debian 10 (Buster) x64
Posts: 4,504

Original Poster
Rep: Reputation: 445Reputation: 445Reputation: 445Reputation: 445Reputation: 445
Quote:
Originally Posted by RandomTroll View Post
The error messages are about /dev/sd[b-g], not /dev/sda. That's a comment in your fstab. Perhaps these other devices are aliased?

Do they exist physically?
I just noticed these items in GNOME Disk Utility [see 4 attached images]. I've no idea what they are. Maybe just placeholders?.
Attached Thumbnails
Click image for larger version

Name:	1.png
Views:	71
Size:	67.4 KB
ID:	31831   Click image for larger version

Name:	2.png
Views:	34
Size:	69.3 KB
ID:	31832   Click image for larger version

Name:	3.png
Views:	21
Size:	69.0 KB
ID:	31833   Click image for larger version

Name:	4.png
Views:	21
Size:	67.8 KB
ID:	31834  

Last edited by linustalman; 11-13-2019 at 04:38 AM.
 
Old 11-13-2019, 04:58 AM   #11
jsbjsb001
Senior Member
 
Registered: Mar 2009
Location: Earth, unfortunately...
Distribution: Currently: OpenMandriva. Previously: openSUSE, PCLinuxOS, CentOS, among others over the years.
Posts: 3,835

Rep: Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034Reputation: 2034
The drives you've highlighted in your screenshots are from a card reader - ie. a SD/CF/SM/MS card reader.

So yes, they basically are like "placeholders", but not sure why something is trying to open them on bootup though.
 
Old 11-13-2019, 05:14 AM   #12
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 5,298

Rep: Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021
/boot/grub/grub.cfg (assuming this is debian)
also the output of
Code:
lvm dumpconfig

Last edited by colorpurple21859; 11-13-2019 at 05:15 AM.
 
Old 11-13-2019, 06:10 AM   #13
linustalman
Senior Member
 
Registered: Mar 2010
Location: Ireland
Distribution: Debian 10 (Buster) x64
Posts: 4,504

Original Poster
Rep: Reputation: 445Reputation: 445Reputation: 445Reputation: 445Reputation: 445
Quote:
Originally Posted by colorpurple21859 View Post
/boot/grub/grub.cfg (assuming this is debian)
also the output of
Code:
lvm dumpconfig
I see. BTE, is there any sensitive data in that file that I should redact? I will post it soon.
 
Old 11-24-2019, 03:05 AM   #14
linustalman
Senior Member
 
Registered: Mar 2010
Location: Ireland
Distribution: Debian 10 (Buster) x64
Posts: 4,504

Original Poster
Rep: Reputation: 445Reputation: 445Reputation: 445Reputation: 445Reputation: 445
Well, colorpurple21859?
 
Old 11-24-2019, 08:07 AM   #15
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora,Xubuntu, others
Posts: 5,298

Rep: Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021Reputation: 1021
Well what? as far as the command, run it and see what is says, is there something there that stands out as might be the problem? If not then it's something else.
Did you look at your /boot/grub/grub.cfg and see if anything stands out there as the problem. It could be something in your initramfs causing the problem.
 
  


Reply

Tags
boot errors, no medium found


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] No package 'x11' found No package 'xext' found No package 'xdamage' found No package 'xfixes' found No package 'x11-xcb' found Jigsaw Linux From Scratch 14 02-23-2021 08:35 PM
Centos Server Failed @ Bootup: Missing "/sbin/blkid" & "fsck" command not found beagle7 Linux - Newbie 4 08-24-2012 01:33 AM
Adding a directory returns "no medium found" error JcN Linux - Newbie 7 02-01-2006 08:40 PM
"Adding a Medium" in Medium Manager???? kymystic Mandriva 1 03-07-2005 03:16 AM
CD ROM mount error: "no medium found"????? RonRussell Linux - Hardware 8 07-01-2002 12:34 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian

All times are GMT -5. The time now is 09:33 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration