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/dev/sda6:clean; 6574 1/13118464 file, 26970410/104944580 blocks is corrupt ,and you might try running e2fsck with alternate superblock

e2fsck -b 8193 <device> what would i do to this help me

I'll translate:
The file-system is corrupt, in a non recoverable way.

This is so unusual that the program may have made a mistake. Does that partition exist? Does it contain an ext2 file system (ext3 is fine too)? If yes to both questions, then:

... it's definitely corrupt. But the corruption may be limited to the primary superblock.

... so you should try scanning from the backup superblock that ext filesystems keep handy. man e2fsck to understand.

Well, first answer the questions above. If they pan out, then the suggestion is to run:

e2fsck -b 8193 /dev/sda6

You'll probably have to do this as root from a recovery mode or a live session.

(8193 is the location of the backup superblock, if you have the default 1k block sizes.)
Good luck and I hope you made backups.

the first thing that i do is i mount the external drive to mnt/Mandriva then after that i configure the fstab then after that i restart linux box then this problem came up...is there any effect from what i did??

You should have mentioned all of this in your original post.

Start over, describe exactly everything you did prior to this error. I am assuming it booted fine before?

Details are important. Post the fstab file and tell us what changes you made, as well as anything else actually relevant to the issue.

You have obvious created the problem. What boot loader are you using? Post the config file for it.

i connect external harddrive (ntfs format) before cause i want to make a backup for my files so i mounted it "mount dev/sdb1 mnt/Mandriva" then after that i go to fstab "vi etc/fstab" then configure the table

"dev/sdb1 mnt/Mandriva auto defaults 1 2" i put a ext3 in this code but i cant remember where i guess after auto or after defaults dont know exactly.. thats the only thing.. help me pls....

Ok, if it's formatted ntfs why would you tell fstab that it's ext3? I'm assumimg as you said you put ext3 'in this code' but can't remember where.

Ok, here ya go.

1. Disconnect the external drive.

2. Boot your system.

3. Edit fstab remove the line you added.

4. Connect the drive and mount it manually and ensure it mounts and reads correctly.

5. Post your fstab file contents here.

my external hhd already disconnected and i trieed to restart my linux box i always encounter this ...



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/dev/sda6:clean; 6574 1/13118464 file, 26970410/104944580 blocks is corrupt ,and you might try running e2fsck with alternate superblock

I'd still like to see the contents of your fstab. Do you have a LiveCD distro laying around? If so boot that so you can access the affected drive.

Then the answer to the second question in post #2 is "no, it is not a valid ext2 file system". It is ntfs. Mount it as ntfs.

As masonm said, remove the line you added to fstab. Then mount manually with the following:

ntfs-3g /dev/sdb1 /mnt/Mandriva

(If you do not have ntfs-3g installed then "mount -t ntfs" can be substituted)

And I bet that will work. When it does, you can edit /etc/fstab to add a line that says:

/dev/sdb1 /mnt/Mandriva ntfs-3g defaults,noauto 0 0

(If you do not have ntfs-3g installed then "ntfs" can be substituted)

It's checking at all, instead of just failing the mount, because you put the last field in fstab to 2.

You don't really want it to try mounting at boot, you really want it to mount when it is available... otherwise you'll get an error if you try to boot when it is not plugged in.

i can access my fstab but my keyboard function abnormally there's something erased at my fstab could help me pls..



/dev/sda1/ ext3 defaults 1 1
<-------------missing line
/dev/sdb1 mnt/Mandriva ext3 defaults 1 2<----------i already delte this file

/dev/sda5 swap swap defaults 0 0



after this i already reboot it then its ok but i can't login my gui anymore i already type all my username and password but this error show.


"could not start kstartupconfig. check your installation"


is there an effect of missing line in fstab above?? help pls...

help me.

You'll have to show the entire "cat /etc/fstab" output, as well as the output of "fdisk -l" - looks like you deleted more than you intended.

If you do: cat "/etc/fstab > fstab.txt" and "fdisk -l > fdisk.txt" you will be able to copy the files fstab.txt and fdisk.txt to a location where you can access them with another system (maybe you copy them to a floppy, or a windows partition). That will allow you to copy and paste the exact messages so we know there are no typos.

/dev/sda1/ ext3 defaults 1 1
<-------------missing line
/dev/sdb1 mnt/Mandriva ext3 defaults 1 2<----------i already delte this file

mone /mnt/floopy supermount dev=/dev/fd0,fs=ext2:vfat,--,umask=0022,iocharset=utf8,sync 0 0

none /proc proc defaults 0 0
/dev/sda5 swap swap defaults 0 0

note: "this the complete setup of my linux box /etc/fstab"



Device Boot start end Blocks Id System
/dev/sda1 * 1 1019 8185086 83 linux
/dev/sda2 1020 14593 109033155 5 Extended
/dev/sda5 1020 1528 4088511 82 Linux swap/Solaris
/dev/sda6 1529 14593 104944581 83 linux



note: "my fdisk table partition"


1.Is there anything wrong about this ???
2.can't access my desktop anymore "COULD NOT START KSTARTUPCONFIG. check your instalation"
3 could you find whats wrong w/ my fstab table??

tnx so much... god bless!!