yesterday i made shutdown to my pc.When I again booted then surprisingly mi got the grub error 17.so as usual I took my ubuntu live cd and tried to boot from it so that I could be able to fix grub(if there is some error)
but live cd failed to boot into os and gave some errors like that:Buffer [355.005069]I/O error on sda 8 logical block 0
[355.005069]ata3.00:exception emask 0*0 sact 0*0 serr 0*0 action..
and to it there were also some unusual lines

Also my xp is working fine.
I dont know what to do now??

thanx in advance

Could you explain more!

http://www.spreadfirefox.com/?q=affi...211983&t=1

see whats the problem is that i am not able to boot into my linux....
grub was showing error 17...live cd was not working as it was showing error which i mentioned.........
one more thing...what i did was that i installed extifs in xp and tried to open my linux drive...but to my surprise even xp didnt worked happily afterwards!!!forget that partiion I was not able to open my c: also!!

no help from anyone??

Have you tried booting it up with any other livecds and tried running fsck?

sudo fsck /dev/sda8
fsck 1.40-WIP (14-Nov-2006)
e2fsck 1.40-WIP (14-Nov-2006)
fsck.ext2: No such file or directory while trying to open /dev/sda8

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

ubuntu@ubuntu:~$ sudo e2fsck -b 8193 /dev/sda8
e2fsck 1.40-WIP (14-Nov-2006)
e2fsck: No such file or directory while trying to open /dev/sda8

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

ubuntu@ubuntu:~$ sudo e2fsck -b 8193 /dev/sda8
e2fsck 1.40-WIP (14-Nov-2006)
e2fsck: No such file or directory while trying to open /dev/sda8

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>


also
ubuntu@ubuntu:~$ sudo fdisk -l

sk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 1305 10482381 c W95 FAT32 (LBA)
/dev/sda2 1306 19456 145797907+ f W95 Ext'd (LBA)
/dev/sda5 1306 6404 40957686 7 HPFS/NTFS
/dev/sda6 6405 11503 40957686 7 HPFS/NTFS
/dev/sda7 11504 12721 9783553+ 7 HPFS/NTFS
/dev/sda8 * 12722 13994 10225341 83 Linux
/dev/sda9 13995 14053 473886 82 Linux swap / Solaris
/dev/sda10 14054 16602 20474811 7 HPFS/NTFS
/dev/sda11 16603 19456 22924723+ 7 HPFS/NTFS
ubuntu@ubuntu:~$

me going mad with trying hundreds of solution...

Lets take a page from our resident multi-boot expert on this one...

http://justlinux.com/forum/showpost....80&postcount=6

maybe something in this post will help steer you in the right direction..

Installing extifs in XP has proerly corrupted your linux installation.
A couple more things, are you sure you used ext2 and not ext3 ?
sudo fsck.ext2 /dev/sda8

may help, only if youre sure you used ext3.
Your partition table, a lot of wasted windows ntfs partitions! Why so many? You would be better consolidating your ntfs partitions into a single partition and leaving more space for multiple linux distros.

Ubuntu now uses libata and the libata driver only recognises the first 15 partitions, another reason to consolidate the ntfs if you plan to try out alternate OS.
If you plan to reinstall any linux, I would conside at least a / and a
/home partition (as well as /swap). Carrying all your eggs in one basket
has proberbly corrupted your data, if you had a /home partition, this would have been safe.
Instead of using extifs on windows, why not create a small fat32 partition? As winxp and linux can read fat32 this avoids the need of
complications like extifs.
Hope that helps.

Linux can also read NTFS pretty good

sudo fsck.ext3 /dev/sda8
e2fsck 1.40-WIP (14-Nov-2006)
fsck.ext2: No such file or directory while trying to open /dev/sda8

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

let me make u clear that extifs has not corrupted any partition...after i wasnt able to boot into linux then i installed extifs so no point that it has damaged that partition.....
and 70% sure that i made ext3 partition and if u have methods on ext3 partition then u can tell me...
atleast i should be able to know the problem that what happened......and how??

and this link http://justlinux.com/forum/showpost....80&postcount=6 is not of any use to me as I m getting this error
sudo mount /dev/sda8 /all
mount: special device /dev/sda8 does not exist

I have just written a thread on how one can put Grub on a floppy, pen drive, internal/external hard disk and CD/DVD. The idea is to get a Grub prompt to boot the system manually.

I explained how one can use a Grub prompt to boot a Linux without using its boot loader in here.

With a Grub prompt, which you can get from selected Live CD listed here, and based on your "fdisk -l" output
The sda1, already marked active by the "*", should fire up by commands in a Grub prompt
I would expect the Linux in sda8 to answer these commands in a Grub prompt
A Ubuntu Live CD can't boot up another Linux because Ubuntu would have been fired up and prevent itself from destruction. Only a Grub prompt, which is Grub in a state before an operating system is booted, can boot a system.

A boot up screen can easily get corrupted and all it needs may be just a restoration of the boot loader in the MBR. I believe this is getting more common with high speed and high density hard disks that a wrong recording of a few byte can lead to an erroneous loading of the boot loader. It happens to Lilo and Windows systems too.

It is possible that a well used hard disk can get corrupted and eventually dies. The early stage is an area will be impossible to read and the affected area is spreading with time. In an early stage the files should be accessible and salvageable while other operating systems should be still bootable individually.

-----------------------------------------------------------------------

Lastly Grub and Linux are two separate systems. A partition having a problem in Linux may not be reported in Grub and vice versa. If your "fdisk -l" shows up all the partitions, including sda8, that the Ubuntu Live CD must have it as a detected device. It is possible that you may not piece all the information together accurately to show us the current situation, like make Ubuntu Live CD booting another Linux.

Your last resort is to boot up the Linux in sda8 manually without using its installer boot loader( fire up the kernel and initrd statements yourself!).

I/O error is usually coming from lower level in the system, suggesting that your HD can't be read properly. This would imply a hardware issue, probably a bad block.

Can you access sda9, sda10, and sda11?

Have you tried testdisk (run it from a live CD) on sda8?

Do this. From a Linux Live CD. run the dd command to try to copy off partition sda8. If you want, just copy it to /dev/null; the point of this exercise is to see if dd will read the HD without reporting any I/O errors.

Use this command:

dd if=/dev/sda8 of=/dev/null bs=512

and see what happens.

If that fails with an I/O error, you have a solid indication of a hardware problem.

You could also run manufacturers diagnostics on your HD, or you could give smartctl a try.

The best thing, I think, would be for you to run SpinRite on the drive. However this costs money unless you have a friend that has a copy.

@jiml8
it is sure now that my hard disk is not damaged as one awesome software http://easylinux.info/uploads/explore2fs-1.07.zip accessed ,copied the data with so much ease(even the much recommended software extifs failed!!!!)so no need to check it by dd command
and also I m easily able to read my sda9,10,11...through windows.
now nothing happened but my confusion has increased......