Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Ghosted drive hides partition every boot

Created: 20 Aug 2012 | 8 comments

I have a drive that was created and imaged using Acronis Trueimage. I am trying to now make a ghost image of it and am having limited success. To create my image I'm using the following command.

ghost32.exe -ib -batch -z6 -split=1024 -clone,mode=create,src=2,dst=driveimage.gho

The drive contains a mix of ext3/ntfs/fat32 partitions with one fat32 partition being more than 32GB in size. After I restore from my created ghost image, the drive looks ok. All the partitions are mounted and assigned drive letters(at least the ones I would expect windows to mount). However, when I try to boot into the windows 7 partition on the drive, the 60GB FAT32 partition is hidden. So I shut it down, plug it into a different machine and use gdisk32.exe to unhide the partition. At that point everything looks good again. But if I put it back in my other machine and try to boot to windows 7, same issue, the 60GB FAT32 partition is hidden again. I do not have any problems with the partition if I just restore using the Acronis image. It's only when I use the image created with ghost that I have this issue. Any Ideas? Here is my partition scheme as listed by gdisk32.exe.

Partition  Status   Type     Volume Label   Mbytes   System      Usage
 O:  1        A    PRIMARY    DOS-EFI       2055.2    FAT32          1%
 N:  2              PRIMARY                       25598.0  NTFS/HPFS  17%
     3         H    PRIMARY                       25600.0  NTFS/HPFS  17%
     4               EXTENDED                     99373.0                      65%
     5               LOGICAL                          5120.0  LINUX             3%
     6               LOGICAL                          5120.0  UNKNOWN     3%
 M:  7             LOGICAL    LOGS             2048.0   FAT32            1%
 L:  8              LOGICAL    RELEASE1      4096.0  FAT32            3%
 K:  9              LOGICAL    RELEASE2      4096.0  FAT32           3%
 J: 10              LOGICAL    RELEASE3      4096.0  FAT32           3%
 I: 11              LOGICAL    RELEASE4       4096.0  FAT32           3%
 H: 12             LOGICAL    RELEASE5      4096.0  FAT32           3%
 G: 13             LOGICAL    RELEASE6      4096.0  FAT32           3%
 F: 14             LOGICAL    DATA             62499.0  FAT32          41%
 

Comments 8 CommentsJump to latest comment

EdT's picture

Is there a boot manager partition as well?  Also, where is the Win 7 system partition? This is around 100-200 Mb and needed for Win 7 to start.  If this hidden partition is on the system as well, you are outside the four primary partition limit and therefore it is not surprising you are having issues.

You have not mentioned which version of Ghost you are using or whether you are booting to DOS or WinPE, so if you post again, please fill in the missing information.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Ian Holm's picture

The partition labeled DOS-EFI contains a grub bootloader and files necessary for booting to DOS, Windows 7 and Windows 8. This is the entire partition table listed by gdisk32. If there was any hidden partition it would have an 'H' listed next to it like partition 3. I am using ghost 11.5.2 build 2266. For whatever reason, the disk manager in windows xp displays the 3 primary partitions + the extended but windows 7 displays them as 5 primary partitions + extended. I'm not sure why xp shows it correctly and not windows 7.

Ian Holm's picture

Anybody have any ideas on this? I tried creating a new image with the -ID flag and now when I go to restore from the image, it says my destination drive is too small. But it's the same drive I created the image from! How can it be too small?

EdT's picture

What sort of drive is it? Could it be an Advanced Format drive? You may need to set partition boundaries in that case.

Have you run CHKDSK on all your drive partitions as any errors could result in crosslinked files and incorrect sizing.

If Acronis Trueimage works, any reason for not sticking with it?  It is no secret that Ghost development ceased some years ago apart from the odd patch being released for specific problems that have arisen. Although a new version is expected early next year, there is no definitive release date and meanwhile support for some of the new features released in Windows 7 and 8 is not going to be fully supported, including the ability to support more than four primary partitions.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Ian Holm's picture

It is a 160GB SSD. I have run CHKDSK, no change and no errors found.

EdT's picture

Why have you not mentioned that you are using an SSD before now?

Try searching on SSD and see what other postings have to say....

eg:

https://www-secure.symantec.com/connect/forums/using-ghost-console-ghost-ssd

and

https://www-secure.symantec.com/connect/forums/deploying-images-ssd-solid-state-disk

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Ian Holm's picture

So I read those articles and tried using -NTC- as well as -FDSP and -FEMAX. None of these had any effect. I have however determined that after imaging with ghost, the Data partition is visible, only after booting into DOS do the partitions get marked as hidden. Does DOS have some issue with FAT32 partitions over 32GB? It is also interesting to note that the 60GB FAT32 partition isn't the only one getting marked as hidden. Both of the NTFS partitions for Win7/Win8 are also getting marked as hidden, however, when booting from those partitions it doesn't seem to cause any problems. I'm still looking for ideas as to what about DOS could be causing this problem.

EdT's picture

DOS has so many limitations that it is difficult to know where to start.

It does not support SATA devices

It uses CHS addressing and consequently is unable to address more that around 132 Gb of storage as this is the address limit for a 32 bit addressing scheme. Modern systems use LBA addressing and provide 64 bit of addressing. Thus the issue is not so much to do with the size of the partition, but it's position on the drive which takes it outside the addressable range of DOS.

This is why WinPE is now the de facto standard boot environment for modern hardware.

I also believe that Win 7 can technically support more primary partitions than previous operating systems but I cannot recall if this is tied on somehow with EFI bios extensions or not.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.