1. Download our Official Android App: Forums for Android!

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

Discussion in 'Computers' started by davoid, Jan 29, 2014.

  1. davoid

    davoid Android Expert
    Thread Starter
    Rank:
    None
    Points:
    223
    Posts:
    1,801
    Joined:
    Aug 3, 2011

    Aug 3, 2011
    1,801
    710
    223
    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:

    [​IMG]

    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:

    [​IMG]


    [​IMG]


    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?
     

    Advertisement

  2. codesplice

    codesplice Elite Recognized Moderator
    Moderator
    Rank:
     #13
    Points:
    1,563
    Posts:
    8,716
    Joined:
    Oct 29, 2013

    Oct 29, 2013
    8,716
    10,100
    1,563
    Male
    SysAdmin
    Huntsville, AL
    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.
     
    davoid likes this.
  3. lunatic59

    lunatic59 Moderati ergo sum
    Moderator
    Rank:
     #2
    Points:
    4,238
    Posts:
    36,618
    Joined:
    Jun 12, 2010

    Jun 12, 2010
    36,618
    34,678
    4,238
    Male
    IT
    Pennsylvania
    You've got 4 entries in your fstab but only three partitions. What's the line beginning with /dev/disk pointing to?
     
    davoid likes this.
  4. davoid

    davoid Android Expert
    Thread Starter
    Rank:
    None
    Points:
    223
    Posts:
    1,801
    Joined:
    Aug 3, 2011

    Aug 3, 2011
    1,801
    710
    223
    London
    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.
     
  5. davoid

    davoid Android Expert
    Thread Starter
    Rank:
    None
    Points:
    223
    Posts:
    1,801
    Joined:
    Aug 3, 2011

    Aug 3, 2011
    1,801
    710
    223
    London

    Hah. You're asking the wrong person I'm afraid. I have not a clue.

    I was hoping someone could explain that to me, lol. :p
     
  6. lunatic59

    lunatic59 Moderati ergo sum
    Moderator
    Rank:
     #2
    Points:
    4,238
    Posts:
    36,618
    Joined:
    Jun 12, 2010

    Jun 12, 2010
    36,618
    34,678
    4,238
    Male
    IT
    Pennsylvania
    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. ;)
     
    davoid likes this.
  7. codesplice

    codesplice Elite Recognized Moderator
    Moderator
    Rank:
     #13
    Points:
    1,563
    Posts:
    8,716
    Joined:
    Oct 29, 2013

    Oct 29, 2013
    8,716
    10,100
    1,563
    Male
    SysAdmin
    Huntsville, AL
    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))).
     
  8. lunatic59

    lunatic59 Moderati ergo sum
    Moderator
    Rank:
     #2
    Points:
    4,238
    Posts:
    36,618
    Joined:
    Jun 12, 2010

    Jun 12, 2010
    36,618
    34,678
    4,238
    Male
    IT
    Pennsylvania
    [​IMG]

    :p

    (check out the signature ;))
     
  9. davoid

    davoid Android Expert
    Thread Starter
    Rank:
    None
    Points:
    223
    Posts:
    1,801
    Joined:
    Aug 3, 2011

    Aug 3, 2011
    1,801
    710
    223
    London
    It worked!

    I can live in ignorance if it means the chickens can breathe easily.
     
  10. lunatic59

    lunatic59 Moderati ergo sum
    Moderator
    Rank:
     #2
    Points:
    4,238
    Posts:
    36,618
    Joined:
    Jun 12, 2010

    Jun 12, 2010
    36,618
    34,678
    4,238
    Male
    IT
    Pennsylvania
    As long as it works, you can leave the voodoo to the witch doctor. :D

    Sorry about the chickens. :( ;)
     
    argedion likes this.
  11. codesplice

    codesplice Elite Recognized Moderator
    Moderator
    Rank:
     #13
    Points:
    1,563
    Posts:
    8,716
    Joined:
    Oct 29, 2013

    Oct 29, 2013
    8,716
    10,100
    1,563
    Male
    SysAdmin
    Huntsville, AL
    I'm going to guess that the /dev/disk/by-uuid/... line may have been automatically generated to point to the removable installation medium?
     
  12. lunatic59

    lunatic59 Moderati ergo sum
    Moderator
    Rank:
     #2
    Points:
    4,238
    Posts:
    36,618
    Joined:
    Jun 12, 2010

    Jun 12, 2010
    36,618
    34,678
    4,238
    Male
    IT
    Pennsylvania
    Or the original swap partition that he deleted. :dontknow:
     

Share This Page

Loading...