Originally Posted by Vareg
I will add the line
mount -a -f -v # to check fstab
to fstab but should i do that in single user mod or in rescue mode?
This are lines to be run from command line and not added to your fstab.
chroot stands for change root and in somekind of way is what rescue modes do but not to the full attend. The process would be to mount your normal filesystem somewhere inside the rescue mode filesystem. I just took /mnt for this as this is normaly the way to go. As it seems the rescue system already does this to some kind of degree.
Lets clear things up even more.
1.) Boot into rescue mode
2.) Start a shell
3.) run mount
to see what filesystems are mounted already.
Okay now we have to see if anything of your normal filesystem is mounted. And if is you have to be sure that really every part of it is mounted. Depends on how you partitioned your disk. Check the output of mount
if it contains something like sda which should be your first harddisk.
For the next step you have to make sure that you have mounted you normal filesystem completly to /mnt.
We now are going to include some other needed pseudo filesystems.
mount -t proc chproc /mnt/proc
mount -t sysfs chsys /mnt/sys
mount -t devtmpfs chdev /mnt/dev
mount -t devpts cdpts /mnt/dev/pts
See my first post here for possible errors.
We now have your normal system mounted and ready to be run as though you have booted from it. Next step is to change into this so only this part is seen for all programs and the kernel. We need to change root
chroot /mnt /bin/bash
We now are inside your normal system and see if the fstab is all good.
This makes sure that fstab is correct.
What you definetly should be on the lookout inside your fstab are filesystem that are remote. Like nfs.
For the dmesg output you might need to wade through all of it. Or see what is the output off:
dmesg | grep -i error
dmesg | grep -i firmware
dmesg | grep -i failure
While the rescue mode is up. Try to get the original fstab of your system and put it here.