GParted prob

[carverj]

HI everyone
Gparted was working fine last time but now it shows both my hard drives as unallocated, whereas a few days ago it would show all partitions.
It is the same when I try to use the Breezy install CD. Oh, and by the way my fstab file hasn't been altered since GParted was working allright.
Could someone please try to help as I am soooo busy and don't have the time to reinstall my current dual boot setup from scratch.
Ta in advance

_________________
My original post regarding this attmpted partition resize
http://www.ubuntuforums.org/showthread.php?t=233448

[mlind]

Does qtparted or parted show the same information? Is your system working otherwise normally except gparted problems?

[carverj]

Yes, It seems fine otherwise.... I could even see the different mounts when browsing whilst running the live cd (which I didn't think you could do)
which leads me to query whether there is a problem with the hard drive or even the MBR !?
How may I check this?

[mlind]

I reckon the problem is with gparted (or parted) instead of corrupted partition table. For me, parted dies with "floating point exception" (which is a known bug).

While using livecd, you can check filesystems using e2fsck:

sudo e2fsck -f /dev/xxx

Where /dev/xxx is the filesystem, like /dev/hda1

I dunno how to verify partition table, except using cfdisk/fdisk..
btw. Did you try out qtparted?

[carverj]

Ok, so gave qtparted a try and it found the 2 drives but when I to click on them instead of showing me partitions it gives me the following error message

Critical error during ped_disk_new!

Could some one point me in the right direction to find the problem with my disk?

Running e2fsch only gave me the following error:

ubuntu@ubuntu:~$ sudo e2fsck -f /dev/hda1
e2fsck 1.38 (30-Jun-2005)
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/hda1

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>

Would this be because XP is on the first partition (and therefore is of the wrong filetype to check) or am I in need of a new pair of hard drives?

[mlind]

Originally Posted by carverj Running e2fsch only gave me the following error: ubuntu@ubuntu:~$ sudo e2fsck -f /dev/hda1 e2fsck 1.38 (30-Jun-2005) Couldn't find ext2 superblock, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/hda1 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> Would this be because XP is on the first partition (and therefore is of the wrong filetype to check) or am I in need of a new pair of hard drives?

e2fsck is for ext2/ext3 like its manual page says.. Don't use it with other filesystems.

[carverj]

No worries, managed to wipe the Ubuntu partitions totally with the help of
the PCLinux OS Live CD. Am trying to use an XP CD to fdisk or is it FDISK
/MBR or whatever (so I can boot into the XP partition at the start of the
disk in order to make it larger with Partition Magic).
It seems the Administrator password is not accepted. I assumed the
administrator password in XP would be my password !?
Does anyone know how I can bypass this obstacle?
Cheers all

[mlind]

You can boot into xp's recovery console using xp's cd (then execute fixboot or fixmbr). You can also download win98 bootdisk image from bootdisk.com, boot using it and execute fdisk /mbr.

[carverj]

[quote] You can boot into xp's recovery console using xp's cd (then execute fixboot or fixmbr). QUOTE]
Yeah, have tried but it asks for Administration password and my password is not working. I didn't think to look into the Administration password as I assumed my account would be sufficient for administration. lol learn the hard way huh?

You can also download win98 bootdisk image from bootdisk.com, boot using it and execute fdisk /mbr.

Could try this but won't I have the same problem as above or is there a way for me to fix the MBR without entering the windows Administration password?
Thanks for the reply b;y the way

[mlind]

Originally Posted by carverj Could try this but won't I have the same problem as above or is there a way for me to fix the MBR without entering the windows Administration password? Thanks for the reply b;y the way

recovery console boots up from the cd to command-line interface and doesn't require login.
win98 bootdisk doesn't require login either, it boots to "dos". (bootdisk contains the fdisk utility)