fixing partition after resizing (pref w/o reformatting)
 

I have a dual boot system set up for a friend, win and Ubuntu,

I resized the ubuntu partition from 45 GB to 35 GB to give some space for both OSs to share
using puppy 4.2.1 Gparted to resize (its ext3)

now when trying to boot ubuntu, error occurs relating to partition, it asks me to hit ctrl-D to continue (which loops back to same error), or enter root password to fix,

when i log in root i try fsck
it continually gives me
"Error writing block 9240597 (invalid argument) while getting next inode from scan. Ignore error?"
it asks this twice, then
"Force rewrite?"
ive held down Yes for at least a minute or so while it scrolls up block number and continues same pattern.

I decided to go back to puppy and "check" the partition,
in GParted There is ! next to the partition, when I tell it to "check",
it instantly gives me an error and doesn't continue to check/repair.

One other thing i noticed
I booted with Knoppix to and noticed the label of partition "hda5 35 GB"
but, when i open it on the window it says "36 GB free out of 45 GB", (45 being the original size before i resized it to 35)

the new ~10 GB fat32 partition is working, windows can use it, and puppy can use it.

I would rather not have to reformat the partition, as i dont want to worry the owner and redo settings.

also in Gparted(w/puppy boot), it says Unable to read contents of this filesystem!, because of this some operations may be unavailable.

although I can mount the partition and see files inside just fine.

well now I got this yes loop going for about 10 mins now, anyway to automate this?
the -y wont work, cause the first option is a no.

well i can access everything on the "corrupted" partition. so I'm guessing the superblock is wrong, since looking at partition sizes from live cds shows the old and new size of the partition.

Hi,

Just boot with the install media or a livecd. Then perform the fsck on the filesystem. You don't perform maintenance on a live or mounted partition.

Edited: nevermind me... ><

I rand fsck with a backup superblock, and got it working