Full of Problem, need a help please...

[Husse]

If it was not for

root partition is in read-only mode

I would say you've ended up in UUID hell
http://www.linuxmint.com/wiki/index.php ... _a_problem
root partition is in read-only mode rings a bell, I think I've done something in that area but can't find it

[newW2]

It is something that can be fixed. You could use Supergrub disk; and if you get the machine to boot you'll need to make sure that fstab and grub menu list are correct afterward. Or you can do this with the Live Cd and a few easy cli commands in terminal.

So as Husse and the wiki tell you, boot using the live cd. Also as Husse has written in the wiki, the disks should be mounted and if not you can do so using Gparted.

Once you have booted, and verified that the drives are mounted, open a terminal and do the following:

Code: Select all

sudo vol_id /dev/sdbx -u

Where x is the location of the offending partition. This cli entry will display the UUID you need to change (note it's a good idea to run the command (sudo_vol_id /dev/partition-you-want-the-vol-id-of -u) for all the disk numbers to have them handy because you need to change those that are listed wrong in fstab (see following for ftab).

Once you have all the UUID's written down, enter the following in the terminal:

Code: Select all

sudo gedit /etc/fstab

This will list the fstab file and you'll find, at the very least, that your root "/" mount point uuid in fstab is different than the one listed by the vol_id command. Replace the UUID for the offending partition or partitions with the uuid's you got from vol_id command.
Looks like fun? Actually, you'll see that many people (including me) tell you to use device names for the partitions and forget the uuid. Device names don't care about uuid volume ids. So once you get booted into your installed Linux Mint DE, you'll want to edit the grub menu list file and the fstab file as suggested in the wiki. That is unless you like trying to correctly enter those uuid values. Just get rid of them.
Here's an example fstab using the uuid. It is followed with an edit to remove the uuid for each device (partition) name. The device names are already there in the fstab file, they are commented out with the # symbol. Remove the # symbol in front of the device name, and delete the uuid; leaving the mount point and the rest of the line. Repeat for the rest of the partitions.

Example using UUID volume identifier in fstab:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1
UUID=e8e008a4-8c6b-4db0-8729-b337eb747078 / ext3 defaults,errors=remount-ro 0 1
# /dev/sda2
UUID=96493987-17df-478e-9611-05c54204502c /home ext3 defaults 0 2
# /dev/sdb1
UUID=74a5c397-c764-426e-8498-f43c8df06c1d none swap sw 0 0
/dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
/dev/hdb /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0

What the above fstab looks like after deleting the UUID volume identifier for the partition:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/sda1 / ext3 defaults,errors=remount-ro 0 1
/dev/sda2 /home ext3 defaults 0 2
/dev/sdb1 none swap sw 0 0
/dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
/dev/hdb /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0

Have fun.

[Husse]

via liveCD I can not mount my root partition,

Sure about that?
Open gparted from the menu - that will mount the partitions
On the other hand
do you manage to boot and this happens when you restart X?
Then the problem is something else (or not)

[AlexSlocker]

Is the computer hard drive recent? I mean, I've had this similar problem. On the place I used to work we use GNU/Linux as well. One day a sudden electric shutdown made the file system corruptes. From that day it happened something similar two more times and we always thought it was about the electric shutdown. Finally we get to the conclusion that it must be the hard drive, because we notice always the problem in the same sectors, and we try different distros as well (Fedora, Ubuntu and Linux Mint). Also when doing certain task the hard drive sounds like 'scratching', I know all the hard drives scratch in some moments, but this one does almost every time you open a folder.

My idea, based on that experience, is that your hard drive might be broken, perhaps in the first sectors, included MBR and some others. And the problem when you hit Ctrl + Alt + Backspace might be that the system cannot read xorg.conf properly. I know these generate weirder questions like, ok, but if the hard drive is broken, why it boots for the very first time? I have no answer, but this is the most logical solution I can figure.

As an advice, try other distros or operative systems and see if the problem is there as well. Do not test Ubuntu, because, as long as Linux Mint is based on it, the errors LM might have, may be in Ubuntu also.

I hope you'll find the problem.

[newW2]

Force mount of all drives in fstab:
sudo mount -a force

Of course Super Grub Disk (SGD). I did see that you had tried SGD:
http://sgd.benjamin-butschko.de/?section=download

RESTORE GRUB IN 3 STEPS