Ubuntu won't load anymore.

[BBWin3]

Good Day,

Here are the results of:
sudo mke2fs -n /dev/sda1
-BBWin3

ubuntu@ubuntu:~$ sudo mke2fs -n /dev/sda1
mke2fs 1.41.9 (22-Aug-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
4816896 inodes, 19253894 blocks
962694 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
588 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424

[Rubi1200]

Thanks for the output. Before we continue, are you able to see and access any of your files from the LiveCD?

If yes, I would suggest you try and save them to an external media such as a USB drive or the like.

There is always a chance that the command I will give you now may not work or even mean that you could lose data.

If you are willing to continue, then run this command from the LiveCD:

sudo e2fsck -f -b 32768 /dev/sda1

Basically, what we are trying to do is replace the bad superblock that was originally detected in the script.

If this command works, in other words it does not report any errors, then you should be able to boot into the system again.

If there are errors, do not continue, post back here and we will try another option.

[HLSolbjorg]

This worked like a charm for me! Thanks a lot!

[BBWin3]

Hello Again,

I ran the e2fsck, then I said yes to abort, then I ran it again with no abort
here are the results. I also tried 2 other superblock locations with same results:

1st run............


ubuntu@ubuntu:~$ sudo e2fsck -f -b 32768 /dev/sda1


e2fsck 1.41.9 (22-Aug-2009)
Journal version not supported by this e2fsck.
Abort<y>? yes


ubuntu@ubuntu:~$




2nd run............


ubuntu@ubuntu:~$ sudo e2fsck -f -b 32768 /dev/sda1


e2fsck 1.41.9 (22-Aug-2009)
Journal version not supported by this e2fsck.
Abort<y>? no
Journal superblock is corrupt.
Fix<y>? no
e2fsck: The ext2 superblock is corrupt while checking ext3 journal for /dev/sda1


ubuntu@ubuntu:~$

[Rubi1200]

What does the output of this command tell you?

dumpe2fs /dev/sda1 | grep -i superblock

Just to rewind a little bit, how did you end up in this situation in the first place?

These kinds of errors are usually caused by:
user error
buggy device drivers or utilities
power outages
kernel bugs

Also, which version of Ubuntu was installed on the computer?

Thanks.

[BBWin3]

Good Day again,

Firstly some history: I had skipped over file checking twice... my bad.
I believe the hard drive was going bad.
And I turned off the computer during one of those-dumb blond- OKAY
I then ran the suggested file fixes from herman@... sudo e2fsck -C0 -p -f -v /dev/sda2.
Due to error founds on the disk, I ran: sudo e2fsck -y -f -v /dev/sda2
NOTE: I am not sure if I ran the above two commands using /SDA2 or SDA1.

So today, I then tried your suggestion. sudo dumpe2fs /dev/sda1 |grep -i superblock

Output shown below.

After that I tried sudo e2fsck -f -b 162340 /dev/sda1 again.

THIS HAD directoriy and inode count errors.
.... I allowed the program to perform the fixes.

AFTER MANY MANY OF THE ABOVE FIXES....>>> SUCCESS!! <<< REBOOTING now NORMAL.

A greatfull thank you for all of your help.

Now it is time to backup everything and replace the hard drive.

Output of above follows:

 
buntu@ubuntu:~$ sudo dumpe2fs /dev/sda1 | grep -i superblock


dumpe2fs 1.41.9 (22-Aug-2009)
Primary superblock at 0, Group descriptors at 1-5
Backup superblock at 32768, Group descriptors at 32769-32773
Backup superblock at 98304, Group descriptors at 98305-98309
Backup superblock at 163840, Group descriptors at 163841-163845
Backup superblock at 229376, Group descriptors at 229377-229381
Backup superblock at 294912, Group descriptors at 294913-294917
Backup superblock at 819200, Group descriptors at 819201-819205
Backup superblock at 884736, Group descriptors at 884737-884741
Backup superblock at 1605632, Group descriptors at 1605633-1605637
Backup superblock at 2654208, Group descriptors at 2654209-2654213
Backup superblock at 4096000, Group descriptors at 4096001-4096005
Backup superblock at 7962624, Group descriptors at 7962625-7962629
Backup superblock at 11239424, Group descriptors at 11239425-11239429
ubuntu@ubuntu:~$


Then I tried sudo e2fsck -f -b 163840 /dev/sda1 on the 3rd superblock as follows:


Directories count wrong for group #316 (0, counted=44).
Fix<y>? yes
Free inodes count wrong for group #317 (8192, counted=8161).
Fix<y>? yes
Directories count wrong for group #317 (0, counted=1).
Fix<y>? yes
Free inodes count wrong for group #322 (8192, counted=8093).
Fix<y>? yes
Directories count wrong for group #322 (0, counted=8).
Fix<y>? yes


/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 366842/4816896 files (1.6% non-contiguous), 5617412/19253894 blocks
ubuntu@ubuntu:~$

[Rubi1200]

Excellent! I am really glad you sorted it out!

I was actually going to suggest you run the e2fsck again with the -y switch (which would have recursively answered yes to the questions you answered manually).

In any event, take your own advice and save whatever data you can before investing in a new drive.

If you need any additional help, feel free to ask.

And don't forget to drop by the forums now and again, even if you don't have a specific question/problem.

You can learn an enormous amount just by reading posts in the various forum sections.