Thread: My ext4 partition is having some problems

i'm sorry ambiguous title, couldn't figure out how else describe situation.

around 2 days ago, playing around live session of meego. impressed, decided install it. on installation dialog, shrank part of /home partition (for ubuntu) make way around 8gb meego. when process completed, resulted in error, (stupidly ) ignored. installation aborted point, , did not try again.

booted ubuntu (11.04). ran fsck since plugged in. while doing so, encountered error on /dev/sda7 partition (i'll try take picture of if manage to; don't want log out of live session of ubuntu 10.10 i'm running now).
had options fix, skip or ignore; pressed "f" tell attempt fix it. did not work. booted display manager, once try log in, said unable update .iceauthority, or something. when realized /home partition (on /dev/sda7) did not mount.

desperate, booted ubuntu 10.10 live session (as 1 had) fix it. read threads , posts in forums, , evetually ran these:

code:

sudo fsck.ext4 /dev/sda7  sudo mke2fs -n /dev/sda7  sudo e2fsck -b 20480000 /dev/sda7

i restarted, same error messages popped on plymouth, , /dev/sda7 not mounted again.

search more, , ran:

code:

sudo mke2fs -s /dev/sda7  sudo fsck /dev/sda7

it prompted if wanted continue/fix, and, out of desperation, pressed "y". continued give me prompts. held "y" half hour, before fell sleepy , decided put small stone on "y" key.

when woke up, still prompting. decided ctrl+c (yes, of idiot), , decided mount partition using nautilus, , resulted in "error mounting: mount: stale nfs file handle". have no idea why ubuntu thought /home ntfs partition (since formatted ext4).

now, need recover partition whole, don't know do. have backup of data, need ubuntu functional, since i'm 8% away downloading 35gib torrent i've been downloading past 2 weeks (i have crippled internet connection).

oh, , output fdisk:

code:

255 heads, 63 sectors/track, 30401 cylinders  units = cylinders of 16065 * 512 = 8225280 bytes  sector size (logical/physical): 512 bytes / 512 bytes  i/o size (minimum/optimal): 512 bytes / 512 bytes  disk identifier: 0xb8ba0d59       device boot      start         end      blocks   id  system  /dev/sda1   *           1        1824    14647296   83  linux  /dev/sda4            1824       30401   229546689+   f  w95 ext'd (lba)  /dev/sda5           22068       30152    64942383    7  hpfs/ntfs  /dev/sda6           30153       30401     2000061   82  linux swap / solaris  /dev/sda7            1824       20947   153600000   83  linux    partition table entries not in disk order    disk /dev/sdb: 1017 mb, 1017117696 bytes  32 heads, 61 sectors/track, 1017 cylinders  units = cylinders of 1952 * 512 = 999424 bytes  sector size (logical/physical): 512 bytes / 512 bytes  i/o size (minimum/optimal): 512 bytes / 512 bytes  disk identifier: 0x000c2a0e       device boot      start         end      blocks   id  system  /dev/sdb1   *           1        1017      992561+   c  w95 fat32 (lba)    disk /dev/sdc: 320.1 gb, 320072932864 bytes  255 heads, 63 sectors/track, 38913 cylinders  units = cylinders of 16065 * 512 = 8225280 bytes  sector size (logical/physical): 512 bytes / 512 bytes  i/o size (minimum/optimal): 512 bytes / 512 bytes  disk identifier: 0xa4b57300       device boot      start         end      blocks   id  system  /dev/sdc1               1       38913   312568641    7  hpfs/ntfs

any appreciated.

sorry long post, thought needed describe how got mess. excuse stupidity, too, beginner , asking stupid questions apparent obvious answers.
let me know if there's info missing.

in advance.

posted adeklipse

then search more, , ran:

code:

sudo mke2fs -s /dev/sda7

my feeling step far. mke2fs manual:

code:

-s    write superblock , group descriptors only.  useful  if         of superblock , backup superblocks corrupted, ,        last-ditch recovery method desired.   causes  mke2fs         reinitialize   superblock  ,  group descriptors, while not        touching inode table , block , inode  bitmaps.          e2fsck  program  should  run after option        used, , there no guarantee data   salvage‐        able.   it  critical specify correct filesystem block‐        size when using option, or there no chance of recovery.

emphasis added me. think saying should used absolute last ditch effort, because there's no recovery if not work.

unless come forward magic bullet, might have face fact partition scrambled.

why recommend partition(s) backed before resize/move operations done on it. if goes wrong during process not trivial figure out , change back.

chris.

Forum The Ubuntu Forum Community Ubuntu Official Flavours Support New to Ubuntu [ubuntu] My ext4 partition is having some problems

Ubuntu