gparted does not see partitions - but WinXP does (Page 1 of 2)

Hello scholz,
could you please post the print-out of Linux command fdisk -lu , where "l" is a lower-case "L", and parted print ? Both programs are contained in "GParted Live".

Regards
cmdr

I believe that the command that cmdr intended is:

parted /path-to-your-device print

Where /path-to-your-device is probably something like /dev/sda.

Hello scholz,
sorry for my false command; gedakc was right.
fdisk print-out indicates,  that a third primary partition (sda3) is located within the extended partition sda2 (overlapping). This probably breaks the whole extended partition chain. The easiest solution would be to delete sda3 and rebuild it as logical volume within the extended partition ( ->sda 8). Perhaps only the partition table in Master Boot Record is incorrect. It seems, that "sda3" can be  integrated into the extended Partition Boot Record (XBR) chain as well. I would first delete the third partition table in MBR and see, what happens ( with a backup of MBR, of course, to get a second chance). You can do it with "MC_HxEd" (use fluxbox menu; right click on "GParted" desktop). By clicking on sda within the program, you get access to edit the MBR. The third partition table starts at address 0x1DE and ends at 0x1ED. Just overwrite these 16 Bytes with 0x00 and save the result.
Be cautious not to overwrite anything else. Refresh "GParted" and see, what happens. It's not just easy, but possible to give "sda8"/sda3 a suitable XBR, since the distance between sda7 and "sda8"/sda3 is exactly as needed, if it doesn't emerge automatically. But it's not sure, that Linux will cope with these changes.

It's an unnecessary risk to not use the latest version, especially if NTFS is involved.

Regards
cmdr

Hello scholz,

XBR is a Boot Record within the extended partition, that only holds two partition table entries (first and second) in a table similar to the partition table in MBR. The first entry gives the relative address of the appropriate logical volume and its size, whereas the second points to the next XBR, thus forming a chain. The last XBR has only a first entry in its partition table. Distance between XBR and Volume Boot Record is always 63 sectors (one disk track), i.e. you need at minimum 63 sectors between the upper border of a logical volume and the lower border of the next to integrate the needed XBR.

In your case : 311,596,803(first sector of sda3/new sda8) - 311,596,739 (last sector of sda7) - 1 = 63 sectors

"MC_HxEd" has a "mounting wizard". Just plug your stick in on request. It doesn't let you change any Boot Records without a previous backup on your stick. To preserve the Record, copy it to another folder (standard is "BootRec"). It might get overwritten, if you use "MC_HxEd" again and accidentally answer "yes", if you get asked, whether you want to store the (altered) record permanently.

Regards
cmdr

Hello Ulrich,

/dev/sda2         83971755    312576704     114302475  5     Extended

I just came across this line. The filesystem ID is 5 (last number preceeding "Extended"). This is an old MS-DOS 3.3 extended filesystem ID, which doesn't support big present harddisks. I think, that this is part of the problem ... and easy to correct with "MC_HxEd". The value should be 0x0F for the LBA Extended version. Just overwrite Byte 0x1D2 (=05) with 0F in Master Boot Record (sda) and see, what happens.

Regards
cmdr

PS.: We will "reanimate" sda3 as extended sda8, if "GParted" shows partitioning now.

Hello Ulrich,
I googled to find out, what "parted" means by "Partition table: loop". It seems, that the Master Boot Record may contain traces of a Volume Boot  Record. I think, we should have the MBR as a file (use "HxD" with Windows and copy sector 0 (512 Bytes) of your HDD to a file). Upload it to a file sharing site, so that we can have a look at it.

What partition was omitted ?

Please do NOT resize or delete any physical or logical structures on your HDD at the moment, so that it's possible to get "sda8", where it belongs to at last.

Regards
cmdr

Hi cmdr,

sorry for me nagging but you asked me to not alter my HDD.  Is there still hope that I can recover my partitions? Otherwise, I have to re-format and re-install.  I need to work with it in some days.

Thanks, Ulrich

Thanks cmdr! I'll probably try the repartitioning on the weekend.  If you have some more ideas until then, please tell.  Cross your fingers that I can re-install my saved Linux partition (partimage). Ulrich

Hello Ulrich,

I stick at the word "re-formatting" .  Of course you can format any other partition without loosing a working Windows on its own separate partition ( well, unless it's bootmanager does NOT reside elsewhere !) .  But I guess, you mean "re-partitioning".  If XP is located on first primary partition AND starts at sector 63 AND doesn't fill the whole drive , you can do anything you want with the unallocated space above without any interference to first primary. The only thing, that I would avoid, is to create new partitions other than in disk order ( higher number should always be located past lower number).

Regards
cmdr

Hello Ulrich,

No, let's have a look at sda1 Partition/Volume Boot Record at sector 63 and the next 100 sectors. first.

Enter in a console /Terminal window ( NO TYPOS !) :

 dd  if=/dev/sda  of=/root/sda1.pbr  bs=512  skip=63  count=100

It's NO typo to use "sda" here, since we work on the physical drive. Upload the file "sda1.pbr" to a file sharing site and give us the link.

Regards
cmdr

Hello Ulrich,

I analyzed your XP PBR : it fits exactly to the values in MBR and is in no way unusual.
Your problem must have an other cause. I think XP would NOT boot, if there were faults in MBR or PBR (code, addresses or sizes).

Regards
cmdr

Hello Ulrich,

I think, I was right. Could you please give us a last "fdisk" print-out of your present partitioning scheme to finish this thread ?

Regards
cmdr