Fsck Died with Exit Status 8 - Jaunty

In fact, I don't have anything on my disk... said Gparted...
/dev/sda1 - ext3 - boot, /dev/sda2 - linux swap , then "/dev/sda3 - unknown" :(((

Log of fsck -C3 -R -A -a
Sun Dec 27 23:47:30 2009

fsck 1.41.4 (27-Jan-2009)
fsck.ext3: Unable to resolve 'UUID=20fb5021-6a0a-466b-bef9-8ad42c3ea522'

fsck died with exit status 8

Sun Dec 27 23:47:38 2009
----------------

That's what happens when I boot without cd...

it suggests to start a shell.. but it fail too !

# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' 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 defaults 0 0
# / was on /dev/sda1 during installation
UUID=1e7f0163-9eb0-459c-b620-9872621c2b17 / ext3 relatime,errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=20fb5021-6a0a-466b-bef9-8ad42c3ea522 /home ext3 relatime 0 2
# swap was on /dev/sda2 during installation
UUID=d93b2a77-303f-4f4d-b28c-39e75f6c3844 none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

Please, does nobody can help ?

Did you change anything, partitioning, moving, resizing partition, new label or anything else.

Options:
Compare uuid's with:
sudo blkid

What happens when you mount /home manually:
mount /dev/sda3 /home

If the uuid of /home was correct, use as a workaround static entry in fstab:
# /home was on /dev/sda3 during installation
/dev/sda3 /home ext3 relatime 0 2

Actually we have some issues with Karmic 'forgets' uuid.
https://bugs.launchpad.net/ubuntu/+bug/428318
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/464411
https://bugs.launchpad.net/ubuntu/+bug/479590

https://help.ubuntu.com/community/SystemAdministration/Fsck
https://help.ubuntu.com/community/Fstab

haven't changed anything, I was just watching a movie while it froze...
and not on Karmic.. i've got it but moved back to Jaunty cause of the sound bug. (2 months ago)

ubuntu@ubuntu:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: UUID="1e7f0163-9eb0-459c-b620-9872621c2b17" TYPE="ext3"
/dev/sda2: TYPE="swap" UUID="d93b2a77-303f-4f4d-b28c-39e75f6c3844"

No sda3 found.

ubuntu@ubuntu:~$ mount /dev/sda3 /home
mount: only root can do that
ubuntu@ubuntu:~$ sudo mount /dev/sda3 /home
mount: you must specify the filesystem type

(I'm running on the live-cd)

I've been told that the 'nail' may be out of track on the HD... Could that be possible ? a technical error and not an informatic one ? If the HD is down, how could it bootup and even find sda1 and sda2...?

will go look on the links now :)

ubuntu@ubuntu:~$ sudo mount -t ext3 /dev/sda3 /home
mount: wrong fs type, bad option, bad superblock on /dev/sda3,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

Any hints in dmesg and syslog?
Output of:
sudo fdisk -l

Take a look at manpage:
man fsck.ext3

sudo umount /dev/sda3
sudo fsck.ext3 -v -f /dev/sda3

If there are to many questions to answer you can stop with ctrl+C
and restart again with:
sudo fsck.ext3 -y /dev/sda3

ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb409b409

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 1216 9767488+ 83 Linux
/dev/sda2 1217 1520 2441880 82 Linux swap / Solaris
/dev/sda3 1521 30515 232902337+ 83 Linux
ubuntu@ubuntu:~$ sudo umount /dev/sda3
umount: /dev/sda3: not mounted
ubuntu@ubuntu:~$ sudo fsck.ext3 -v -f /dev/sda3
e2fsck 1.41.4 (27-Jan-2009)
fsck.ext3: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda3
Could this be a zero-length partition?
ubuntu@ubuntu:~$ sudo fsck.ext3 -y /dev/sda3
e2fsck 1.41.4 (27-Jan-2009)
fsck.ext3: Attempt to read block from filesystem resulted in short read while trying to open /dev/sda3
Could this be a zero-length partition?
ubuntu@ubuntu:~$

> mount: wrong fs type, bad option, bad superblock on /dev/sda3
> open /dev/sda3 Could this be a zero-length partition?

Doesn't sound trivial, but can eventually be fixed.
After any action e.g. sudo mount ... (as mentioned above) you should check dmesg to get some details what's wrong:
dmesg | tail

Sorry, no idea what's this:
/dev/loop0: TYPE="squashfs"

> bad superblock

You can try to find out superblock backups
Please read
man mke2fs
##about the -n option
-n Causes mke2fs to not actually create a filesystem, but display what it would
              do if it were to create a filesystem. This can be used to determine the loca‐
              tion of the backup superblocks for a particular filesystem, so long as the
              mke2fs parameters that were passed when the filesystem was originally created
              are used again. (With the -n option added, of course!)

e.g.
http://ubuntuforums.org/showthread.php?s=760e8d8cce2197d180ceb229b19361e3&t=440216&page=2
https://answers.launchpad.net/ubuntu/+question/36925
http://www.linuxforums.org/forum/misc/35926-cannot-boot-up-linux-unable-read-superblock.html
http://ubuntuforums.org/showthread.php?t=1041283

Install testdisk to eventually recover partition in order to backup important data.
https://help.ubuntu.com/community/DataRecovery
http://www.cgsecurity.org/wiki/TestDisk

fly@flyineste-desktop:~$ dmesg | tail
[ 225.682583] [drm] Initialized via 2.11.1 20070202 on minor 0
[ 225.707181] agpgart-via 0000:00:00.0: AGP 3.5 bridge
[ 225.707217] agpgart-via 0000:00:00.0: putting AGP V3 device into 8x mode
[ 225.707335] pci 0000:01:00.0: putting AGP V3 device into 8x mode
[ 229.299852] r8169: eth0: link up
[ 232.474603] mtrr: no MTRR for f0000000,4000000 found
[ 233.785447] agpgart-via 0000:00:00.0: AGP 3.5 bridge
[ 233.785484] agpgart-via 0000:00:00.0: putting AGP V3 device into 8x mode
[ 233.785601] pci 0000:01:00.0: putting AGP V3 device into 8x mode
[ 239.764014] eth0: no IPv6 routers present
fly@flyineste-desktop:~$

>Sorry, no idea what's this:
>/dev/loop0: TYPE="squashfs"

can it be from the live-cd ?
I'm running now on a new user account created yesterday to try to reach the /dev/sda3. But new user has been created on /dev/sda1...
That new user doesn't have sudoers right, so I'm still going through the live-cd to make any changes...

Going to try mke2fs and the TestDisk now (need to switch on live-cd...

ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb409b409

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 1216 9767488+ 83 Linux
/dev/sda2 1217 1520 2441880 82 Linux swap / Solaris
/dev/sda3 1521 30515 232902337+ 83 Linux
ubuntu@ubuntu:~$ sudo mke2fs -n /dev/sda3
mke2fs 1.41.4 (27-Jan-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
14557184 inodes, 58225584 blocks
2911279 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
1777 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, 20480000, 23887872

ubuntu@ubuntu:~$ sudo e2fsck -b 32768 /dev/sda3
e2fsck 1.41.4 (27-Jan-2009)
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
/dev/sda3: recovering journal
e2fsck: Attempt to read block from filesystem resulted in short read while trying to re-open /dev/sda3
e2fsck: io manager magic bad!
ubuntu@ubuntu:~$
----------------------------------------------------------------

Now I have trouble also on the /dev/sda1 ....
No more HD at all on Gparted....

----------------------------------------------------------------
ubuntu@ubuntu:~$ dmesg | tail
[ 1140.301347] Buffer I/O error on device sda, logical block 0
[ 1140.301423] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[ 1140.301429] end_request: I/O error, dev sda, sector 490234744
[ 1140.301433] Buffer I/O error on device sda, logical block 61279343
[ 1140.301455] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[ 1140.301461] end_request: I/O error, dev sda, sector 490234744
[ 1140.301464] Buffer I/O error on device sda, logical block 61279343
[ 1140.301512] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[ 1140.301518] end_request: I/O error, dev sda, sector 0
[ 1140.301521] Buffer I/O error on device sda, logical block 0
ubuntu@ubuntu:~$ blkid
/dev/loop0: TYPE="squashfs"
/dev/sda2: TYPE="swap" UUID="d93b2a77-303f-4f4d-b28c-39e75f6c3844"
ubuntu@ubuntu:~$ sudo fdisk -l
ubuntu@ubuntu:~$
---------------------------------------------------

And can't install testdisk :(

don't have my HD anymore....
Nothing's left...

ubuntu@ubuntu:~$ sudo fdisk -l
ubuntu@ubuntu:~$ blkid
/dev/loop0: TYPE="squashfs"

not sure I thank you for your advices....

Hi again !

I just tried again the e2fsck on the partition and this time it worked !!
Don't ask me how I could do it as I didn't have any partition on any disk anymore a few hours ago. When I bootup again (on live-cd) to read my mails, I found my disk again....
I recover all my data (I think) but I'll buy a new HD and make a new install, just to throw away the f***** disk...

Here are the Konsole moves ::
(the -c -y option didn't work so I hit "y" hundreds times..... )
-----------------------------------------------------------------------

>>>>> sudo e2fsck -b 32768 /dev/sda3

[....]

Free inodes count wrong (14557173, counted=14532598).
Fix<y>? yes

/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda3: 24586/14557184 files (8.2% non-contiguous), 28180517/58225584 blocks

ubuntu@ubuntu:~$ dmesg | tail
[ 1731.265324] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
[ 1731.265333] end_request: I/O error, dev sda, sector 24418804
[ 1731.265361] ata1: EH complete
[ 1731.265466] sd 0:0:0:0: [sda] Write Protect is off
[ 1731.265470] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1731.291598] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1731.293424] sd 0:0:0:0: [sda] 490234752 512-byte hardware sectors: (251 GB/233 GiB)
[ 1731.294391] sd 0:0:0:0: [sda] Write Protect is off
[ 1731.294395] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1731.318292] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 251.0 GB, 251000193024 bytes
255 heads, 63 sectors/track, 30515 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb409b409

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 1216 9767488+ 83 Linux
/dev/sda2 1217 1520 2441880 82 Linux swap / Solaris
/dev/sda3 1521 30515 232902337+ 83 Linux
ubuntu@ubuntu:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: UUID="1e7f0163-9eb0-459c-b620-9872621c2b17" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda2: TYPE="swap" UUID="d93b2a77-303f-4f4d-b28c-39e75f6c3844"
/dev/sda3: UUID="20fb5021-6a0a-466b-bef9-8ad42c3ea522" SEC_TYPE="ext2" TYPE="ext3"

ubuntu@ubuntu:~$ sudo fsck.ext3 -y /dev/sda3
e2fsck 1.41.4 (27-Jan-2009)
/dev/sda3: clean, 24586/14557184 files, 28180517/58225584 blocks

ubuntu@ubuntu:~$ sudo umount /dev/sda3
ubuntu@ubuntu:~$ sudo mount -t ext3 /dev/sda3 /home
ubuntu@ubuntu:~$ dmesg | tail
[ 1731.293424] sd 0:0:0:0: [sda] 490234752 512-byte hardware sectors: (251 GB/233 GiB)
[ 1731.294391] sd 0:0:0:0: [sda] Write Protect is off
[ 1731.294395] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1731.318292] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3402.619068] kjournald starting. Commit interval 5 seconds
[ 3402.619356] EXT3 FS on sda3, internal journal
[ 3402.619364] EXT3-fs: mounted filesystem with ordered data mode.
[ 3690.401621] kjournald starting. Commit interval 5 seconds
[ 3690.401927] EXT3 FS on sda3, internal journal
[ 3690.401936] EXT3-fs: mounted filesystem with ordered data mode.
ubuntu@ubuntu:~$

Thanks a lot Sam !! (sorry to have been so unthankfull on previous post ;)
Hope I won't have other troubles (and hope it stays this way until I install a new HD!)

Thanks for ur help, couldn't have done it without you !

Thanks Sam, that solved my question.

> the -c -y option didn't work so I hit "y" hundreds times.....

Sorry I didn't describe it very well, I meant of course each option separate.

I'm happy it worked out for you; kind of positive proof of concept of a *nix based system.
I agree on making yourself a new year present in buying a new hd.

Enjoy Ubuntu.