• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Linux pre-boot request for key response (mounting issue?)

davoid

Android Expert
Aug 3, 2011
1,801
712
London
Hey guys, seems like my foray into Linux has started in earnest. :)

When I boot my computer, I get the following message:

keys:Continue to wait, or Press S to skip mounting or M for manual recovery

When I press S, it boots up fine, but I would rather not have to do this, and I would like to get to the bottom of it.

A bit of background:

I booted from a live DVD of Linux Mint and used gparted to partition my new drive with an OS partition, a swap partition, and a data partition.

Then I went to install linux and it said I needed a drive mounted as root. I couldn't find a way to set a mount point so I chose the option to install linux with a wiped disk.

The resultant drive had a huge OS partition and a small swap partition right at the end in an extended volume (or whatever it's called.)

I then resized the OS partition, deleted the swap partition (along with the logical extension), created a new swap partition next to the OS partition, and created a data partition upto the end of the drive.

It looks like this:

Screenshotgparted_zpsd2e49fc6.png


I then received the stated request for key input upon reboot.

I searched online and several sources suggested that I needed to change my /etc/fstab file to match the UUID of the new swap partition, which I have now done.

But it still asks for key input upon boot. Is the problem something else?

Here are screenshots of blkid and fstab, for comparison:

Screenshotdiskids_zps0c39781b.png



Screenshotupdatedfstab_zps1aefaa1f.png



As you can see, the swap UUIDs are the same, (whereas they weren't previously) so is it possibly the "dev/disk..." line that is causing the problem?
 
Welcome to Linux - that's how you know it's working ;)

Try adding the option "nobootwait" to the /etc/fstab line for the disk that is causing the hesitation at boot. That "Press S to skip mounting or M for manual recovery" *should* be preceded by a message about which drive is not ready.

Thanks for the welcome :)

I think it did flash a message for a microsecond... no idea what it said though.

I could try "nobootwait" with each partition in turn and see what happens.

However, I would like to know WHY it is waiting - as part of my ongoing education.
 
Upvote 0
However, I would like to know WHY it is waiting - as part of my ongoing education.

It's looking for a device that's either not ready or not there. Comment out that line in your fstab "/dev/disk/by-uuid/......" and I'll bet you're all set.

EDIT: It's pointing to a symbolic link to a device rather than the device itself. Sometimes it's an empty CD or flash media that gets added to the fstab file. If you ask me how or why that happens, i'll have to kill a chicken and consult a crystal ball. ;)
 
  • Like
Reactions: davoid
Upvote 0
It's looking for a device that's either not ready or not there. Comment out that line in your fstab "/dev/disk/by-uuid/......" and I'll bet you're all set.

EDIT: It's pointing to a symbolic link to a device rather than the device itself. Sometimes it's an empty CD or flash media that gets added to the fstab file. If you ask me how or why that happens, i'll have to kill a chicken and consult a crystal ball. ;)

How or why does that happen?



(also, pics or it didn't happen)



((also also, I think you're on the right track. The boot-time pause is probably related to that fstab entry that isn't matched by an active partition (that we've seen, at least))).
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones