Recovery environment in Ghost 14 does not recognize my USB backup drive

Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.

Hello, the recovery disc I'm using is a custom one specifically made for this PC. Boots fine, but USB is not functioning.

 

 

 Regarding drivers: there is no specific USB driver for the hard drive. The USB drive works perfectly when operating under WIn XP.

 

Have you created an “alias” for this USB drive within Norton Ghost? That might also be a factor in accessing the drive in the Recovery Environment. I’d recommend creating one for all your USB drives.

Yes, alias is ‘Backup1’

Is your USB drive an enclosure?

 

Enclosure?  Well, it’d an IDE hard drive in an IDE cabinet connected with USB to my PC. Works perfect for everything except the NG recovery environment.

Hello, I've made a custom recovery CD with Norton Ghost 14. Computer boots fine but NG does not recognize the USB harddrive where my backups are. The same USB harddrive was used when I made my backups.

 

It only identifies my C: and D: harddrives, a duplicate CD-drive with identical content (although I only have one CD inserted), but not my USB drive.

 

What's wrong?

 

P.S. I also have a problem with SymSnapService.exe. In services the path points to "C:\Program Files\Norton Ghost\Shared\Drivers\SymSnapService.exe", whereas my Norton Ghost installation directory is - and has always been - "C:\Program\Norton Ghost\Shared\Drivers\SymSnapService.exe". How could this happen?

 

Currently I have manually created a duplicate of SymSnapService.exe in a sub-directory under "Program Files".

 

All SymSnapService entries in the Registry are pointing correctly to the "Program" folder.

It's possible that a non-standard driver is being used in Windows which is missing in the recovery environment.   Have you run the driver validation wizard within Ghost?  Go into device manager, drives, locate this drive and check the properties.  Click on "Driver Details" and list what drivers, manufacturer, and driver version are being used while in Windows.

 

Also, is there a specific reason why you installed Ghost to a directory under C:\Program and not C:\Program Files?

 

 

 

Message Edited by erik_carlstrom on 06-25-2008 12:31 PM

Yes, I have run the driver validation wizard and created a custom recovery disc.

 

I'm on a Swedish XP installation and NG ends up under "C:\Program" per default. This created the issue with the missing SymSnapService. When I uninstalled the whole thing and reinstalled it under "Program Files" this problem was resolved. It seems that you have an issue also with non-english XP installations.

Did you install the English version of Ghost or the Swedish version? 

 

Swedish.

 

Should this impact USB compatibility within the recovery environment?

It shouldn't.  I was more concerned about the install location.  If you could provide the items around the drivers that might be where the problem resides.

 

I have no clue about what USB-drivers are missing. There is no custom USB driver needed for the USB hard drive. It's just using XP's native drivers.

 

After a short google session it seems that I'm not the only one having this issue.

 

What I did eventually was to move the backup from the USB HDD to a secondary built-in HDD which works fine from the recovery environment. So I was able to recover my backup, but not from the external USB drive.

I’m assuming that the usb drive is powered and connected before you start the recovery environment.  If not, then it won’t be viewable.  A storage device has to be connected and powered before WinPE loads.  Is this a native USB connection (are you using a USB connected to a PCMCIA slot?  etc)?

Yes, it's powered an spinning while booting the recovery environment. I have tried several different USB connections, none is working. Normally it is connected to one of the USB slots on the mother board.

 

However, what is also important is that I have tried connecting a USB stick to all of the USB slots while being in the recovery environment, and the stick is inactive in all of the slots (not flashing, stays unmounted). To me this indicates that all USB connections are dead within the recovery environment.  However, mouse and keyboard works fine - they are both connected through USB.

I've sent you a PM.

 

 

I too have this Usb drive problem.

My backups are on a Freecom 500 directly connected to my PC and not through a hub.

I do not have another drive with sufficient space to transfer the backup files.

I am using the standard XP Home (SP3) drivers to connect to the Freecom. In my system the Freecom is named Backup.

Driver for device is -usbstor.sys-  file version 5.1.2600.5512.

 

I am now stuck with about five backups and not able to restore one of them from the recovery disc.

 

Cairnhill 09/07/2008

 

1 Like

Do you have the USB drive connected and powered before you boot from the recovery disk?  Did you make a customer recovery disk through Ghost? 

 

 

Depending on the make and model of these USB drives, their drivers may not be included on the default Symantec Recovery Disk (SRD). I would recommend creating a Custom Recovery Disk that will include these drivers, and let us know if that resolves the problem for you. Before you create this Custom Recovery Disk, you may also want to ensure that you have the latest drivers installed for these devices. Thanks!