Error on bootup "the disk drive for /dev/mapper/... Is not ready yet or not present
 

When I went to boot up my Linux mint laptop today I got the error message "the disk drive for /dev/mapper/mint--vg-swap_1 is not ready or not present."

I searched and couldn't find any answers hat fit my situation and were clear/simple enough for me to try on my own. I did find out that it might have to do with UUIDs and etc/fstab.

I am traveling and have limited troubleshooting resources. I do have a live CD and an android phone. Could anyone help me tro bleshoot my problem? I'm kind of desperate as I have a couple thousand pics on the HD from m the last few months of travel.

From other similar posts it seems like providing /etc/fstab and the output of blkid helped troubleshooters so I will post that in just minute once I copy it over to my phone.

Thanks in advance.

/etc/fstab
BLKID
Let me know if there is any other info needed

Thanks

just curious, how did you get the blkid and fstab if the system would not boot?

if you got that info from the LiveCD, does the liveCD have the ability to mount the "missing" drive that grub is not seeing? if so then you might want to verify that the disk is still stable.

this is a laptop, with the power off and the battery removed, unplug and plug the HDD back into the laptop. in other words reseat the drive to see if it just wiggled lose while being moved.

from the liveCD try some of these:

http://blog.shadypixel.com/monitorin...smartmontools/

http://www.cyberciti.biz/faq/find-ha...pecs-on-linux/

Yes I got that info through booting from the livecd. And yes I can mount the missing drive. Any advice on how to tell if the drive is stable.

I will disconnect the drive when I get a chance and look into the links. Thank you.

Backups for for just this situation - yes, even (especially) when travelling.

If you can mount the mint--lv-root and see your photos you're probably ok. If the filesystem was broken you'd usually be told. Do you really use two swap extents - and is (ony) one of them actually encrypted ?.
Was this aptop hibernated prior to the inital failed (re-)boot ?.

Yeah, I know I should backup but I only have a single 90 GB ssd and no external. Also I upload new photos pretty regularly and would have to backup quite frequently.

As for being able to mount mint--lv-root I can view the filesystem but I can't view my photos or anything else in /home/username probably because /home is encrypted.

As for swap. I have no idea why there would be two swap partitions if that's what your saying. Or why only one would be encrypted. I followed a tutorial on how to setup encrypted lvm on Linux mint and may have done something wrong, but I recall setting up only one swap partition.

I shutdown the computer prior to the failure but it was really low on battery so could've automatically gone to hibernation as I shut it down.

I'm not real comfortable with Linux yet so I'm sorry I can't provide more definitive answers.

Ugh - I don't do crypto, so I'll try not to get in the way. Let's see if we can get some basic info - let's see the output of these from the liveCD

Here is the output of: SUDO PARTED -L
And of: SUDO PVS (just pvs returned a open failed: permission denied error)
And of: SUDO VGS
And of: SUDO LVS

can anyone advise how i might go about fixing my problem based on the information provided?

Let's see what this has in itAnd provide a link to the tutorial you mentioned above.

Unfortunately I can't recall the tutorial I used. I did some searching and couldn't find a tutorial that looked familiar. I may have just used the Linux Mint 16 step-by-step installer.

Here is the output of "sudo cat /etc/crypttab"

And "sudo cat /media/mint/a43b5701-3304-486d-9c7e-f0439fa2b131/etc/crypttab"

Also through another process I was able to decrypt my /home folder and get the pictures and documents I needed from the "lost" drive. So it is much less crucial for me to fix the problem though I would really like to if possible. But if worse comes to worst I can always reinstall Linux Mint without losing any important data.