Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I was able to recover by booting from a usb, mounting sda1, and editing fstab. When I used nano it did not open full screen and I managed to truncate the permissions off somehow. I think I have the wrong UUID for my swap file. I think it changed in all my rebooting. The blkid command probably gave me the correct UUID.
r@r:~$ sudo fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c84b5
Device Boot Start End Blocks Id System
/dev/sda1 2048 40962047 20480000 83 Linux
/dev/sda2 40962048 296962047 128000000 83 Linux
/dev/sda3 600565760 625141759 12288000 82 Linux swap / Solaris
Does it maintain swap from reboot?
sda3 in fstab is wrong format, You only needed to replace UUID in fstab not the whole line I marked the UUID in red. That has change though, so put it back in original format & change to new UUID.
My /var/log file is taking up 15 Gb. 6 Gb of that is my syslog file. Here is a sample of the messages:
Feb 11 20:41:28 r kernel: [556124.707960] mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
Feb 11 20:41:28 r kernel: [556124.707963] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Feb 11 20:41:28 r kernel: [556124.707983] mei_me 0000:00:16.0: reset: wrong host start response
Feb 11 20:41:28 r kernel: [556124.707986] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Feb 11 20:41:28 r kernel: [556124.708008] mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
Feb 11 20:41:28 r kernel: [556124.708011] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Feb 11 20:41:28 r kernel: [556124.708031] mei_me 0000:00:16.0: reset: wrong host start response
Feb 11 20:41:28 r kernel: [556124.708034] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
From Googling it I think it is a bug and I am either suppose to blacklist the module mei_me of stop it in the bios.
I will see if I can find out how to blacklist it. I also noticed that the log goes back to the 11th.