LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Debian (https://www.linuxquestions.org/questions/debian-26/)
-   -   Error messages on bootup: "open failed: No medium found". (https://www.linuxquestions.org/questions/debian-26/error-messages-on-bootup-open-failed-no-medium-found-4175664017/)

linustalman 11-10-2019 02:00 PM

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.

RandomTroll 11-10-2019 10:26 PM

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.

linustalman 11-12-2019 06:41 AM

Quote:

Originally Posted by RandomTroll (Post 6056306)
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

jsbjsb001 11-12-2019 06:48 AM

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.

linustalman 11-12-2019 06:53 AM

Quote:

Originally Posted by jsbjsb001 (Post 6056744)
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


jsbjsb001 11-12-2019 07:00 AM

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...

RandomTroll 11-12-2019 05:54 PM

Quote:

Originally Posted by linustalman (Post 6056739)
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?

colorpurple21859 11-12-2019 06:40 PM

post your grub.cfg

linustalman 11-13-2019 04:37 AM

Quote:

Originally Posted by colorpurple21859 (Post 6056990)
post your grub.cfg

Hi colorpurple21859. Do you refer to '/etc/default/grub'?

linustalman 11-13-2019 04:37 AM

4 Attachment(s)
Quote:

Originally Posted by RandomTroll (Post 6056975)
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?.

jsbjsb001 11-13-2019 04:58 AM

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.

colorpurple21859 11-13-2019 05:14 AM

/boot/grub/grub.cfg (assuming this is debian)
also the output of
Code:

lvm dumpconfig

linustalman 11-13-2019 06:10 AM

Quote:

Originally Posted by colorpurple21859 (Post 6057144)
/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.

linustalman 11-24-2019 03:05 AM

Well, colorpurple21859?

colorpurple21859 11-24-2019 08:07 AM

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.


All times are GMT -5. The time now is 02:10 AM.