Linux Mate 13 64bit

AM3+ FX 4130 / AM3+ FX 4300
GA-78LMT-SP2 / GA-78LMT-SP2 AM3+
STT DDR 1600 / STT DD3 1600 (2x4) 8GB

I shut down my computer last night and whe I turned it back on this morining, I was greeted by a black screen that said, I needed to mount my hard drive, select S or M. I choose S and my screen sign in password came up and I login into Mint. I'm not dual booting, this is a new custome built computer, new hard drive and the only other Distro that's been on this machine is Linux Mint 15 Mate, until I installed Linux Mint 13. I'm a novice and I read a couple of sites where some people experienced the same thing, but I didn't fully understand. I messed up a HDD last mouth fooling around with partitions. So, I need some assistance, thank you.


Here's the info when I ran sudo fdisk -l

studio1@studio1-GA-78LMT-USB3 ~ $ sudo fdisk -l
[sudo] password for studio1:

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000bc54e

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 969469951 484733952 83 Linux
/dev/sda2 969471998 976771071 3649537 5 Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5 969472000 976771071 3649536 82 Linux swap / Solaris

Post your /etc/fstab file. No other drives internal or external connected to this computer?

studio1@studio1-GA-78LMT-USB3 ~ $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=d1a604fe-f12f-4923-a5ca-b7bf579b58ec / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=ecf765e9-2647-4d25-8fa8-0ab89152bfc6 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0


Nope, I have no other drivers connect to the computer. The on;y thing I have plugged in is USB hub in the back of my computer: with a blue tooth dongle (3.0), my printer, and mouse dongle.

It happened once my computer has booted up as it should; I've learn if something happens that shouldn't... problems may be down the road.

You have a rather unusual layout of partitions.
Please post the output from the following, as root or sudo:
andRichard.

studio1@studio1-GA-78LMT-USB3 ~ $ sudo blkid -o list -c /dev/nul
[sudo] password for studio1:
device fs_type label mount point UUID
-------------------------------------------------------------------------------
/dev/sda1 ext4 / d1a604fe-f12f-4923-a5ca-b7bf579b58ec
/dev/sda5 swap <swap> ecf765e9-2647-4d25-8fa8-0ab89152bfc6
studio1@studio1-GA-78LMT-USB3 ~ $


studio1@studio1-GA-78LMT-USB3 ~ $ df -hl
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 462G 17G 423G 4% /
udev 3.7G 8.0K 3.7G 1% /dev
tmpfs 1.5G 1.1M 1.5G 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 3.7G 2.3M 3.7G 1% /run/shm

That's not particularly unusual. Many installers put swap in a logical partition instead of a primary, and it's standard to use 5 as the swap.

Since your fstab seems correct but the / partition on /dev/sda1 is not mounting at boot, the simplest thing for you to do is copy all important data to another disk, DVD, CD, USB, etc., and then reinstall. Boot a LiveCD in order to save any irreplaceable data.

It appears that something has changed to prevent the partition from mounting.
Could be a permission conflict or something else. Since it is a fresh install it makes more sense to reinstall.

I find that reinstalling 2 or 3 times helps me to understand the installer and the system.
If you are going to mess around with partitions, you may need to get to know the installer.

regards.

Thanks for the advice and that's what I've done, all is well. For now...fingers crossed.