Has anyone been able to configure a ghost boot disk that can be used with PXE, that will support Jumbo Frames?  I need to set the MTU size to 9000. 

I am hoping that Jumbo frames will help to improve the ghost casting process.  I have a cisco 3750 switch and have set the IGMP and MTU size.  I have also set the MTU of the ghost server to 9000.  Just need to see how to change the MTU on the boot images.

I am open to use any OS as the boot disk, DOS, WinPE or Linux.

Hi

i am having issues with ghost32.exe 11.5.1 not seeing large sata hdd using usb to sata adapter

ghost crashing when opened.

Anyone any ideas?

Hello comunity,

I have a problem where my client PCs(Win 7) are not showing up in the Ghost console which runs on Windows Server 2003(XP).

Before this problem happened, my client PCs were running on Windows XP, and they were showing up in the ghost console and theres weren't any problems.  I bought new PCs which run on Windows 7, and after this change I have not been able to find the client PCs.

The PCs are supposed to show up in Machine Groups, however there are not being shown there.  They are also not shown in the subnet folder.

Here are the troubleshooting steps I have taken:

- I have been able to install the ghost configuration client from the ghost console.

- firewalls are off.  Opened port on McAfee

- remote registry (in services) is set to automatically start (checked that it is started)

- unchecked "using shared wizard" in folder options

Are there any other steps I can take?

Or does anyone know the reason to why my Win 7 client PCs are not showing up in the ghost console?

Thank you,

Tomo

A few years back, we used Acronis as our imaging software solution.  Right from the get-go, it worked terrible.  It never worked right.  I'd image a whole lab of 40 PCs and half way through the image, something would hiccup and most of the PCs would reboot and all the PCs that rebooted would be defective and I'd have to image them again.  Sometimes it took me 3-5 times of an image before it was successful.  Acronis' tech support was terrible and unhelpful.  After years of getting no where with what was causing the issue, I gave up on the software and started using Clonezilla with a usb stick and a usb hard drive to reload PCs.

But before with Acronis, there were two things I look at that I wonder if it was what was causing the issues...

The acronis server ran on a virtual machine that shared the phsyical machine and NIC with 3 other VMs.

The images were stored on a USB drive and/or a NAS.

I'm implementing a new Ghost "server" that's actually running on a Windows 7 stand-alone box.  This new PC has a gig NIC and it's plugged directly into a gig switchport on the backbone of the MDF.  Lately I've been trying to make our network as simple as possible to make it less error prone.  I've been trying to keep as many servers off the domain as possible if it's not needed they are on the domain.  Is it required the Ghost server is on the domain?  If it's not on the domain, will it still be able to add the imaged PCs to the domain after it's done imaging?  I don't know if it's necessary, but a few new servers that it isn't necessary I've left off the domain and so far they seem to be less error prone.  Trying to use the KISS (Keep it simple stupid) philosophy to my network now.

Hi

I need to create a windows 7 32 bit image, my GHOST CAST version is 8.0.0.984. i have created windows xp images before but windows 7 looks a little different

thank you

Hi

I have a system where I use Ghost solutions to restore an XP Embedded image to a SATA SSD. When the SSD is 'new' out of the packet, this fails so when I reboot onto the newly imaged disk, it sits with a flashing cursor and refuses to boot.... However, if I try again on this disk and re-image a second time (with same image off same USB stick), the restore succeeds and I can boot up.

I've tried wiping all partition information off a 'used' SSD and I can't replicate this behaviour other than opening a fresh SSD from the manufacturer.

Any ideas what is causing this problem? Hope someone can help!

Andy

Hello and thank you in advance for any insight into my issue.

i am running ghost solution suite 2.5.1

i have a hp 8200 running this software

ip address (static) 192.168.1.1

subnet 255.255.254.0

default gateway 192.168.1.1

i have the server hooked to a dlink 8 port switch (dgs-2208)

and the client computer is also hooked to this switch (simple network)

i have created a boot usb with the ghost boot wizard in both win pe inviroment and pre dos os

winPE : in winpe i have a connection issue witht he server error 10030

i have opened all udp ports in windows fire wall(1345,1346,1347,6666,7777)

and i still cannot establish a connection with the server

i have followed many guides on this site and nothing has worked

predos os :

ghoscast is greyed out

network boot and pxe settings in bios is enabled

thanks

brandon

As part of automating deployment acrosss the enterprise, we are trying to create scripts that can create Tasks\Image items inside the Ghost Console without manual intervention.

Does anyone know how to CREATE Task items inside the SYMANTECGHOST.DB database file ?

Using SymantechGhost Console v11.5.1.2266

We installed Ghost Solution Suite 2.5.1 onto Windows Server 2008 R2 Standard server.  We can create and restore windows xp prof using ghostcast and ghost boot disk for Lenovo PC ok but when we tried to created a Ghost Boot Disk via USB key using PC-DOS to create Windows 7 it only pickup one partition to create image.  When we restored it back we got a blank screen. 

I tried to create a ghost boot disk for USB key using windows PE and when I boots up this ghost boot disk it goes to X: prompt and won't see the Ghostcast server via the network.

I need help create a Windows Server 2008 R2 standard image from IBM HS23 blade server inside IBM Bladecener H.  I created a USB ghost boot disk using PC-Dos and the system just boot directly into Windows.  It bypass reading the USB key.  Any help is greatly appreicated.

Richard

Hi

I am having a rather annoying problem getting our Toshiba Tecra M9 laptops to network boot using a USB boot disk.  It seems to be the same issue as described on the following discussion.

https://www-secure.symantec.com/connect/forums/ghost-11-boot-disk-issues-toshiba-tecra-m9-intel-82566mc-network-card-fine-75
 

I am using Ghost Solutions Suite 2.5 (version 11.5.1.2266).

When using ghost 7.5 to create the floppy boot disk it seems to work fine using the same dos driver.  However the latest version of our image has been created using Ghost 11 and as a colleague has wiped the only boot disk we had I need to create a new boot disk using Ghost 11.

When booting from the USB boot disk it hangs on the gray screen with symantec ghost written on the top and the fan kicks in and goes no further.  I am using the same drivers (the E1000$ for the Intel 82566MC) and the switches -nousb -fni

I would be very grateful for any assistance as this is driving us mad!

Ian

Hello,

recently i learned to use the following command to convert our .gho's to .vmdk's:

ghost32 -clone,mode=restore,src=my.gho,dst=myimage.vmdk -batch –sure

The problem I'm running into is that alot of our .gho files are password protected and when i run this command i get the message:

ABORT : 30003, Password not provided for protected file.

I know the passwords to all of them but do not know where i should enter it in the above command line and in what format.

any help that can be provided would be great.

thanks!

hi guys

i need your help anyone of you there, i have server windows7 ultimate 64bit, C\:drive-500GIG, D:\Drive-500GIG(Archive), S:\Drive-4T(Storage), I take image for back up using Norton ghost 11.0 is no problem. now I re-image the server there have problem in the hard drive, the D:\Drive become S:\Drive, and the S:\Drive become D:\Drive is twisted by itself, i have 3 times to re-image is the same result. why is twisted by itself? i need your helf guys.thnz

Imaging an EFI system with Windows 8 and Symantec Ghost.
 

Requirements:

• 16/32 GB USB flash drive
• Ghost version 11.5 (tested), possibly other versions also.
• Windows 8 ADK/Windows 8 Installation Media
• Time & Patience
   

First let me preface this post by saying the information I have gathered is specific to my experience and may provide a means for one to accomplish Imaging an EFI system natively with versions of Ghost that are currently “unaware” or incompatible with EFI/UEFI.  This guide explains how to Image a system with Windows 8 in native EFI/UEFI mode using ghost.

A system running in EFI mode REQUIRES a GPT Partition Table.  Natively the EFI system is not compatible with a legacy MBR partition table.  When performing a clean installation of Windows 8 on an EFI system it creates a total of 4 partitions.  I felt this many partitions was ridiculous and unnecessary so I removed the additional partitions and found that the minimum requirement is only 2 partitions.

The first partition is a 100 MB FAT32 EFI system partition which is where the boot files will reside.  The rest of the drive will be formatted as an NTFS partition and will contain the Windows installation.

Ghost version 11/12 is unable to interpret the 100MB FAT32 EFI partition so if an Image of an entire GPT Windows disk is captured and then applied to another system, it will not be bootable regardless of the ghost switches specified.

The advantage to using ghost to capture and apply the images is because it can split the files as it creates them.  This is especially useful in this case because in order to boot an EFI system to a bootable USB drive, the drive MUST be formatted as FAT32.  As you may know FAT32 suffers from a single file size limitation of 4GB so if your image is larger than 4GB a separate drive formatted as NTFS would have to be used to store the image.  The result of following this guide is to have the ability to image an EFI system natively using ghost from a single USB drive.

Since ghost is unable to handle the EFI partition, we leverage DiskPart for the creation of a fresh EFI partition along with a fresh NTFS partition.  Once the GPT partition table has been created on the target system, we can use ghost to apply ONLY the Windows partition to the target system.  The last and most important step is to copy the boot files from the Windows partition to the EFI system partition and viola the system now boots into Windows correctly.

EFI Systems intended to run Windows 8 require WinPE 4.0 which can be extracted from the Windows 8 ADK.

1.       Create a bootable Windows 8 Installation/WinPE 4.0 flash drive. (FAT32 set as active)

2.       Install Windows as GPT creating only 2 partitions - the 100MB EFI System Partition and NTFS Windows.

3.       Capture the entire drive using Ghost splitting the image into < 4GB sections (I used a 2GB split).

          Example: Entire Disk Capture (Disk 1 Partitions 1 & 2)

%PEBootRamdiskSourceDrive%\ghost32.exe -clone,mode=create,src=1,DST=%PEBootRamdiskSourceDrive%\images\entiredisk.gho -split=2000 -z2 –sure

4.       Using DiskPart, partition the target system as GTP with 100MB EFI Partition and the rest as NTFS Windows.

          Example: DiskPart Scripted Commands

diskpart /s %PEBootRamdiskSourceDrive%\createpartitions.txt

          Example: Contents of createpartitions.txt:
 

rem Create GPT Disk Structure...


select disk 0

clean

convert gpt


rem Prepare System Partition...


create partition efi size=100

format quick fs=fat32 label="System"

assign letter=S


rem Prepare Windows Partition...


create partition primary

format quick fs=ntfs label="Windows"

assign letter=W

list volume


exit

5.       Using ghost with partition switch (prestore), apply ONLY the second partition (NTFS Windows) of the captured disk Image to the second partition (NTFS) of the target disk (Think Disk 1 Partition 2, to Disk 2 Partition 2).

          Example: Single Partition Restore (Disk Image containing 2 Partitions, Applying Partition 2 Only)

%PEBootRamdiskSourceDrive%\ghost32.exe - clone,mode=prestore,src=%PEBootRamdiskSourceDrive%\images\entiredisk.gho:2,dst=1:2 -sure

6.       Using BCDBoot, Copy Boot files to 100MB system partition.

          Example: BCD Boot Command

W:\Windows\System32\bcdboot W:\Windows /s S:

I know the W: and S: drive letters look weird but don’t worry, The Windows partition assigned as W: in the PE will be assigned C: upon booting into the operating system and the System partition will not receive a drive letter once the system has booted into windows.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------
 

The following information is an attempt to account for different configurations that may exist in the wild.

7.       If for whatever reason you wish to retain the additional partitions or capture an image of a system in its current state containing more than 2 partitions, you may do so but make sure you specify the correct target partition when applying it.

          Example: Entire Disk Capture (Disk 1 containing 4 Partitions)

%PEBootRamdiskSourceDrive%\ghost32.exe -clone,mode=create,src=1,DST=%PEBootRamdiskSourceDrive%\images\entiredisk.gho -split=2000 -z2 –sure

          Example: Single Partition Restore (Restore only the 4th Partition)

%PEBootRamdiskSourceDrive%\ghost32.exe - clone,mode=prestore,src=%PEBootRamdiskSourceDrive%\images\entiredisk.gho:4,dst=1:4 -sure

8.       As an alternative if you wish to simply capture a single partition this can be accomplished by the following:

          Example: Single Partition Capture (Drive 1 Partition 2)

%PEBootRamdiskSourceDrive%\ghost32.exe -clone,mode=pcreate,src=1:2,DST=%PEBootRamdiskSourceDrive%\images\partition2.gho -split=2000 -z2 –sure

  Example: Single Partition Restore (Specify the captured Image consisting of only 1 partition, and apply it to the 4th partition of the target disk)

%PEBootRamdiskSourceDrive%\ghost32.exe - clone,mode=prestore,src=%PEBootRamdiskSourceDrive%\images\partition2.gho:1,dst=1:4 -sure

9.       Please understand this is an outline and your actual drive/partition numbers may be different depending on the number of disks and partitions present on those disks at the time of capturing/applying the images.

10.     Additionaly, the capture and application of entire disk images or single partitions appears to be fully functional from the ghost interface as well.

I hope this all makes sense, enjoy! 

Hi,

Having a brain fart so just want to confirm one thing. If I create a image do I want to use the following command to split and auto name the files

Ghost.exe -SPLIT=2048 -AUTO

The file would be saved on a Buffalo NAS drive or perhaps even a USB thumb drive

Thanks Guys.

Bonjour,

Je vous contact car je souhaite deployer 40Pc's en Windows 7 avec Symantec ghost Suite.

j'utilise un serveur 2008r2 avec le role DHCP actif.

J'ai créé une clef usb d'amorcage avec l'assistant d'amorcage ghost.

Mais je rencontre une erreur 10030 lorsque je boot sur la clef usb.

Mon Pc "client" ne peut pas communiquer avec mon serveur DHCP.

J'ai ajouté les pilotes Vista (.INF et .CAB) sur ma clef USB, sans resultat.

J'ai chargé les pilotes W8, meme probleme.

Sous l'environnement Windows, mes pc's recuperent bien une adresse Ip du DHCP, pas sous dos.

Avez vous des pistes à m'apporter?

Cordialement

Laurent Sornin

im have trouble imaging a drive that has an Acronis secure zone partition 0xbb. what happens is after imaging the drive acronis will not see the secure zone partition.

Hi,

I am getting the above error.

I went on and got the output on a file however I don't have a clue as to what causes the error.

Error output file below: 

*********************************
Date   : Wed Apr 24 00:07:18 2013
Error Number: (28017)
Message: Failed to find parent directory to add NTFS file/directory to.
Version: 11.0.0.1502 (Dec  4 2006, Build=1502)
OS Version: Professional  (Build 7600)
Command line arguments: -afile=e:\errorfile.txt
Active Switches :
       AutoName
PathName            : 62566 $$_system32_wbem_06656d9fdf2f8577.cdf-ms
DumpFile            : 3.2:\Images\MCTP.gho
DumpPos             : -1409033158
Last LFO Buffersize : 0
Last LFO Path       :
  Full Path         : 3.2:\Images\MCTP.gho
  Disk:Partition    : 3:2
  Drive Letter      : F:\
Last LFO Filesystem : Native
FlagImplode         : 0
FlagExplode         : 2

Operation Details :
  Total size.........11876
  MB copied..........11168
  MB remaining.......708
  Percent complete...94%
  Speed..............828 MB/min
  Time elapsed.......13:29  
  Time remaining.....0:51  

Program Call Stack
AbortLog
Generic_Abort
performPostCopyNTFSPartitionOperations
performPostCopyDiskOperations
CopyFileToDisk
CopyMainline
AttemptOperation
sub_main
main

Call Stack
Address            Frame              Logical Addr              Module
0x00000000773764f4 0x000000000012ce00 0x0001:0x00000000000454f4 X:\windows\SYSTEM32\ntdll.dll
0x000000000012d104 0x000000000012ce04 0x0000:0x0000000000000000
0x000000000043acd9 0x000000000012d104 0x0001:0x0000000000039cd9 X:\Ghost\ghost32.exe
0x000000000052e999 0x000000000012d470 0x0001:0x000000000012d999 X:\Ghost\ghost32.exe
0x000000000052e1ab 0x000000000012e53c 0x0001:0x000000000012d1ab X:\Ghost\ghost32.exe
0x000000000052d7d9 0x000000000012ec5c 0x0001:0x000000000012c7d9 X:\Ghost\ghost32.exe
0x000000000052f385 0x000000000012ee78 0x0001:0x000000000012e385 X:\Ghost\ghost32.exe
0x00000000005f68b9 0x000000000012f070 0x0001:0x00000000001f58b9 X:\Ghost\ghost32.exe
0x00000000005f60df 0x000000000012f280 0x0001:0x00000000001f50df X:\Ghost\ghost32.exe
0x000000000054df89 0x000000000012f2d8 0x0001:0x000000000014cf89 X:\Ghost\ghost32.exe
0x0000000000554e3e 0x000000000012f314 0x0001:0x0000000000153e3e X:\Ghost\ghost32.exe
0x0000000000552d82 0x000000000012f508 0x0001:0x0000000000151d82 X:\Ghost\ghost32.exe
0x0000000000401e49 0x000000000012f594 0x0001:0x0000000000000e49 X:\Ghost\ghost32.exe
0x0000000000401c3f 0x000000000012f5b0 0x0001:0x0000000000000c3f X:\Ghost\ghost32.exe
0x00000000004043d0 0x000000000012f840 0x0001:0x00000000000033d0 X:\Ghost\ghost32.exe
0x000000000040383d 0x000000000012ff38 0x0001:0x000000000000283d X:\Ghost\ghost32.exe
0x0000000000410e63 0x000000000012ff88 0x0001:0x000000000000fe63 X:\Ghost\ghost32.exe
0x00000000772a1174 0x000000000012ff94 0x0001:0x0000000000050174 X:\windows\system32\kernel32.dll
0x000000007738b3f5 0x000000000012ffd4 0x0001:0x000000000005a3f5 X:\windows\SYSTEM32\ntdll.dll
0x000000007738b3c8 0x000000000012ffec 0x0001:0x000000000005a3c8 X:\windows\SYSTEM32\ntdll.dll
End Call Stack

Start heap available: 1642459136
Cur   heap available: 1636458496
Total Memory:         2135216128

Allocated
  33500 ..\ghost.cpp:1394
Free

Fat details:

NTFS details:
----------------

NTFS Global Flags:
----------------
  contiguousWrite=1 forceDiskClusterMapping=0
  inhibitCHKDSK=1 ignoreBadLog=0 ignoreCHKDSKBit=0
  enable_cache=0 xfrbuflen=0
  last_attr_type = 0
  loadExact = 0
----------------
 =======================================================
 NTFS volume 0:
 ----------------
 initialised..............1
 read cached..............N
 Selective caching........N
 flags....................Volume OK
 drive....................0x00
 part order...............1
 version..................0x0400
 volsize..................124461055
 blocksize................512
 clusterfactor............8
 clustersize..............4096
 mftrecordsize............1024
 indexrecordsize..........4096
 indexclustperrecord......1
 bootSectorCopyOffset.....124461055
 pagefileSys..............-1
 bootIni..................-1
 volumeLabel..............[]
 sectorsInUse.............22823448
 totalNonCopiedBytes......0
 bytesToCopy..............0
 bitmapClusters...........475
 bitmapUsedBytes..........1944704
 estimatedClusters........475
 estimatedUsedBytes.......1944704
 clustersizeShift.........12
 blocksizeShift...........9
 mftrecordsizeShift.......10
 indexrecordsizeShift.....12
 totalRootMftRecs.........0
 clustermap failover......N
 Boot sector details
  name....................[NTFS    ]
  blocksize...............512
  clusterfactor...........8
  reservedSectorsUnused...0
  mediaType...............0xf8
  secPerTrack.............63
  numHeads................255
  hiddenSectors...........581632
  volsize.................124461055
  mftcluster..............786432
  mftmirrorcluster........16
  clustersPerMFTRecord....246
  clustersPerIndexBuffer..1

  ---------------------------------------------------
  Cluster Allocation Map
  ---------------------------------------------------
  Start: 15557631 Length: 0 Next: 15557631

 =======================================================
 =======================================================
 NTFS volume 1:
 ----------------
 initialised..............1
 read cached..............N
 Selective caching........N
 flags....................Volume OK
 drive....................0x00
 part order...............0
 version..................0x0400
 volsize..................579583
 blocksize................512
 clusterfactor............8
 clustersize..............4096
 mftrecordsize............1024
 indexrecordsize..........4096
 indexclustperrecord......1
 bootSectorCopyOffset.....579583
 pagefileSys..............-1
 bootIni..................-1
 volumeLabel..............[System Res]
 sectorsInUse.............49424
 totalNonCopiedBytes......0
 bytesToCopy..............0
 bitmapClusters...........3
 bitmapUsedBytes..........9056
 estimatedClusters........3
 estimatedUsedBytes.......9056
 clustersizeShift.........12
 blocksizeShift...........9
 mftrecordsizeShift.......10
 indexrecordsizeShift.....12
 totalRootMftRecs.........0
 clustermap failover......N
 Boot sector details
  name....................[NTFS    ]
  blocksize...............512
  clusterfactor...........8
  reservedSectorsUnused...0
  mediaType...............0xf8
  secPerTrack.............63
  numHeads................255
  hiddenSectors...........2048
  volsize.................579583
  mftcluster..............24149
  mftmirrorcluster........16
  clustersPerMFTRecord....246
  clustersPerIndexBuffer..1

  ---------------------------------------------------
  Cluster Allocation Map
  ---------------------------------------------------
  Start: 72447 Length: 0 Next: 72447

 =======================================================

Disk Info :
  remote.............0
  drive..............0
  sectorsUsedCount.......121133056
  estimatedUsedCount.....24322174
  numPartitions..............2
  Version............1151

 # Ord Boot Id Ext     First        Num       Last       Used NTFS
 0  0    1   7 No       2048     204800     206848      49408 Yes
 1  1    0   7 No     206848  120928256  121135104   24272765 Yes

Disk Info :
  remote.............0
  drive..............0
  sectorsUsedCount.......125042688
  estimatedUsedCount.....0
  numPartitions..............2
  Version............0

 # Ord Boot Id Ext     First        Num       Last       Used NTFS
 0  0    1   7 No       2048     579584     581632      49408 Yes
 1  1    0   7 No     581632  124461056  125042688   24272765 Yes

Fixed Drives

Drive 0 SanDisk SSD U100 64G 10.5 217455030077
ASPI
Total Sectors            125045424
Bytes per Sector         512
MB                       61057
Successful IO Count      0

WinNT (Active)
Total Sectors            125045424
Bytes per Sector         512
MB                       61057
Cylinders                7783
Heads                    255
Sectors per Track        63
Successful IO Count      388645

Drive 1 SanDisk Cruzer Blade 1.20 2004452761078C024EA5
ASPI
Total Sectors            62530624
Bytes per Sector         512
MB                       30532
Successful IO Count      0

WinNT (Active)
Total Sectors            62530624
Bytes per Sector         512
MB                       30532
Cylinders                3892
Heads                    255
Sectors per Track        63
Successful IO Count      8

Drive 2 ST1000LM 024 HN-M101M 2AR1
ASPI
Total Sectors            1953525164
Bytes per Sector         512
MB                       953869
Successful IO Count      0

WinNT (Active)
Total Sectors            1953525164
Bytes per Sector         512
MB                       953869
Cylinders                121601
Heads                    255
Sectors per Track        63
Successful IO Count      10

Remote Drives
AsyncIo : 0
Image Devices

Key[1]   1.1:
Key[2]   1:1
Path     1.1:
Desc     1.1: [System Reserved]
Type     NTFS
Disk     0
Offset   2048

Key[1]   1.2:
Key[2]   1:2
Path     1.2:
Desc     1.2: []
Type     NTFS
Disk     0
Offset   581632

Key[1]   2.1:
Key[2]   2:1
Key[3]   E:
Path     E:
Desc     E: 2.1: [SupperBoot]
Type     NTFS
Disk     1
Offset   2048

Key[1]   3.1:
Key[2]   3:1
Key[3]   H:
Path     H:
Desc     H: 3.1: [DATABKUP]
Type     NTFS
Disk     2
Offset   2048

Key[1]   3.2:
Key[2]   3:2
Key[3]   F:
Path     F:
Desc     F: 3.2: [DATABKUP]
Type     NTFS
Disk     2
Offset   6383616

Key[1]   3.3:
Key[2]   3:3
Key[3]   G:
Path     G:
Desc     G: 3.3: [ETC]
Type     NTFS
Disk     2
Offset   1543921664

Key[1]   C:
Path     C:
Desc     C:
Type     Disk

Key[1]   D:
Path     D:
Desc     D:
Type     Disk

Key[1]   X:
Path     X:
Desc     X: [Boot]
Type     Disk

DiskManager diagnostic...
=========================

Fixed Drives

Drive 0 SanDisk SSD U100 64G 10.5 217455030077
ASPI
Total Sectors            125045424
Bytes per Sector         512
MB                       61057
Successful IO Count      0

WinNT (Active)
Total Sectors            125045424
Bytes per Sector         512
MB                       61057
Cylinders                7783
Heads                    255
Sectors per Track        63
Successful IO Count      388661

Drive 1 SanDisk Cruzer Blade 1.20 2004452761078C024EA5
ASPI
Total Sectors            62530624
Bytes per Sector         512
MB                       30532
Successful IO Count      0

WinNT (Active)
Total Sectors            62530624
Bytes per Sector         512
MB                       30532
Cylinders                3892
Heads                    255
Sectors per Track        63
Successful IO Count      8

Drive 2 ST1000LM 024 HN-M101M 2AR1
ASPI
Total Sectors            1953525164
Bytes per Sector         512
MB                       953869
Successful IO Count      0

WinNT (Active)
Total Sectors            1953525164
Bytes per Sector         512
MB                       953869
Cylinders                121601
Heads                    255
Sectors per Track        63
Successful IO Count      10

FilesystemManager diagnostic...
===============================

Volume 1
VolumePos: 2.1:
DriveLetter: E:
Description:   29.82GB Primary Disk 1 Offset       1MB   29.82GB SanDisk Cruzer Blade 1.20 2004452761078C024EA5
Type:        fsfNtfsWindowsXP
Name:        SupperBoot

Volume 2
VolumePos: 3.1:
DriveLetter: H:
Description:    3.04GB Primary Disk 2 Offset       1MB    3.04GB ST1000LM 024 HN-M101M 2AR1
Type:        fsfNtfsWindowsXP
Name:        DATABKUP

Volume 3
VolumePos: 3.2:
DriveLetter: F:
Description:  733.15GB Primary Disk 2 Offset    3.04GB  733.15GB ST1000LM 024 HN-M101M 2AR1
Type:        fsfNtfsWindowsXP
Name:        DATABKUP

Volume 4
VolumePos: 3.3:
DriveLetter: G:
Description:  195.31GB Primary Disk 2 Offset  736.20GB  195.31GB ST1000LM 024 HN-M101M 2AR1
Type:        fsfNtfsWindowsXP
Name:        ETC

Volume 5
VolumePos: 1.2:
DriveLetter:
Description:   59.35GB Primary Disk 0 Offset     284MB   59.35GB SanDisk SSD U100 64G 10.5 217455030077
Type:        fsfNtfsWindowsXP
Name:       

Volume 6
VolumePos: 1.1:
DriveLetter:
Description:     283MB Primary Disk 0 Offset       1MB     283MB SanDisk SSD U100 64G 10.5 217455030077
Type:        fsfNtfsWindowsXP
Name:        System Reserved

FilesystemMounter diagnostic...
===============================

LfoFilesystemManager diagnostic...
==================================

Filesystem Index: 0
Filesystem Descriptor:
  ID's:
    ID Type: 2
    ID: E:
    ID Type: 1
    ID: 2.1:
    ID Type: 4
    ID: SUPPERBOOT:
  DriveType: 2
  FilesystemInfo:
    formatType: 8
    volumeName: SupperBoot

Filesystem Index: 1
Filesystem Descriptor:
  ID's:
    ID Type: 2
    ID: F:
    ID Type: 1
    ID: 3.2:
    ID Type: 4
    ID: DATABKUP:
  DriveType: 4
  FilesystemInfo:
    formatType: 8
    volumeName: DATABKUP

Filesystem Index: 2
Filesystem Descriptor:
  ID's:
    ID Type: 2
    ID: G:
    ID Type: 1
    ID: 3.3:
    ID Type: 4
    ID: ETC:
  DriveType: 4
  FilesystemInfo:
    formatType: 8
    volumeName: ETC

Filesystem Index: 3
Filesystem Descriptor:
  ID's:
    ID Type: 2
    ID: H:
    ID Type: 1
    ID: 3.1:
    ID Type: 4
    ID: DATABKUP:
  DriveType: 4
  FilesystemInfo:
    formatType: 8
    volumeName: DATABKUP

Filesystem Index: 4
Filesystem Descriptor:
  ID's:
    ID Type: 2
    ID: X:
  DriveType: 4
  No FilesystemInfo structure.
  Filesystem has no VolumePtr

Filesystem Index: 5
Filesystem Descriptor:
  ID's:
    ID Type: 1
    ID: 1.1:
    ID Type: 4
    ID: SYSTEM RESERVED:
  DriveType: 4
  FilesystemInfo:
    formatType: 8
    volumeName: System Reserved

Filesystem Index: 6
Filesystem Descriptor:
  ID's:
    ID Type: 1
    ID: 1.2:
  DriveType: 4
  FilesystemInfo:
    formatType: 8
    volumeName:

*********************************

Thanks in advance.

Asher