locked
WHS Backup crashes client (Event ID 1003 Error Code 00000019) RRS feed

  • Question

  • WHS Backup crashes client computer and computer restarts.  Only happens when backup is enabled.

     

    Anybody run into this problem?

     

    Product: Windows Operating System
    ID: 1003
    Source: System Error
    Version: 5.2
    Symbolic Name: ER_KRNLCRASH_LOG

    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Description:
    Error code 00000019, parameter1 00000020, parameter2 ebebaa30, parameter3 ebebaa50, parameter4 0c040201.
       
    Computer Info:

     

    Computer is ASUS Maximus Formula Motherboard X38 Chipset with 512GB Seagate drive

    Latest drivers installed

     

    OS Name Microsoft Windows XP Professional
    Version 5.1.2600 Service Pack 2 Build 2600
    OS Manufacturer Microsoft Corporation
    System Manufacturer ASUS

    System Model Maximus Formula
    System Type X86-based PC
    Processor x86 Family 6 Model 15 Stepping 11 GenuineIntel ~3005 Mhz
    Processor x86 Family 6 Model 15 Stepping 11 GenuineIntel ~3005 Mhz
    BIOS Version/Date American Megatrends Inc. 0505, 10/12/07
    SMBIOS Version 2.4
    Windows Directory C:\WINDOWS
    System Directory C:\WINDOWS\system32
    Boot Device \Device\HarddiskVolume1
    Hardware Abstraction Layer Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)"
    Total Physical Memory 4,096.00 MB
    Available Physical Memory 2.58 GB
    Total Virtual Memory 2.00 GB
    Available Virtual Memory 1.96 GB
    Page File Space 6.34 GB
    Page File C:\pagefile.sys

    Debug Info:

     

    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 00000020, a pool block header size is corrupt.
    Arg2: ebebaa30, The pool entry we were looking for within the page.
    Arg3: ebebaa50, The next pool entry.
    Arg4: 0c040201, (reserved)

    Debugging Details:
    ------------------

    ***                                                                   ***
    ***    Type referenced: mssmbios!_SMBIOS_DATA_OBJECT                  ***
    GetUlongFromAddress: unable to read from 8055b6f0
    BUGCHECK_STR:  0x19_20
    POOL_ADDRESS:  ebebaa30
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  DRIVER_FAULT
    LOCK_ADDRESS:  80551160 -- (!locks 80551160)
    Resource @ nt!PiEngineLock (0x80551160)    Available
    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
    1 total locks
    PNP_TRIAGE:
     Lock address  : 0x80551160
     Thread Count  : 0
     Thread address: 0x00000000
     Thread wait   : 0x0
    LAST_CONTROL_TRANSFER:  from 8054a583 to 804f9deb
    STACK_TEXT: 
    ba507928 8054a583 00000019 00000020 ebebaa30 nt!KeI386GetLid+0x1d
    ba507978 8058e975 ebebaa38 00000000 00000000 nt!g_rgAttributeTags+0x38b
    ba5079d8 8059038d 86e91620 e603c188 ba507a44 nt!PiProcessTargetDeviceEvent+0x69
    ba507acc 80590f9b 885a0638 89794848 8a461e40 nt!PpHotSwapInitRemovalPolicy+0x2d
    ba507d20 8059148a 8a461e40 00000001 00000000 nt!IopInitializeDeviceInstanceKey+0x531
    ba507d54 804f6853 00000003 8055a5c0 8056375c nt!IopPnPDispatch+0x250
    ba507d7c 805379bd 00000000 00000000 8af23da8 nt!KdSetOwedBreakpoints+0xb7
    ba507dac 805ce84c 00000000 00000000 00000000 nt!_ValidateEH3RN+0x15
    ba507ddc 8054532e 805378ce 00000001 00000000 nt!RtlUpcaseUnicodeToMultiByteN+0x7fc
    00000000 00000000 00000000 00000000 00000000 nt!KdPitchDebugger+0x232
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    nt!KeI386GetLid+1d
    804f9deb ??              ???
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  nt!KeI386GetLid+1d
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlpa.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  45e53f9d
    FAILURE_BUCKET_ID:  0x19_20_nt!KeI386GetLid+1d
    BUCKET_ID:  0x19_20_nt!KeI386GetLid+1d

    Wednesday, March 5, 2008 3:40 PM

Answers

  • I managed to find the a solution to the problem elsewhere:

    http://forums.seagate.com/stx/board/message?board.id=Discwizard&thread.id=46
    http://www.techspot.com/vb/topic94820-5.html

    In short, the problem seems to be rooted in MBR corruption caused by certain hard disk cloning software (including Seagate's DiscWizard, and Acronis True Image, which DiscWizard is based on).  The problem effects all backup software that makes use of Windows' Volume Shadow Copy, and thus is not limited to WHS.

    To fixed the problem, simply follow these steps:

    1. Go to windows Device Manager
    2. Click "view" and select "show hidden devices"
    3. Scroll down to "storage volumes"
    4. Click on the plus to expand.
    5. Click on each one listed and right click and uninstall. (you will get a message on some staying to reboot before it takes effect. Select no until you do them all.)
    6. Reboot.
    7. Wait till windows automatically reinstalls devices. Will prompt to reboot again.
    8 Reboot.

    Saturday, April 12, 2008 10:19 PM

All replies

  • What happens when you click on the Tray Icon and select Backup Now?

     

    Saturday, March 8, 2008 12:43 AM
  • Hi,

    i have the same Problem on 1 Client.

    The client crashes at manual backup too.

     

     

    Sunday, March 9, 2008 11:15 AM
  • What is the client OS?

    How many hard drives on client?  ARe they all NTFS?

    Has it ever backed up?

    Have you uninstalled the Connector and reinstalled it?

     

    What version of WIndows Home Server are you running? (Console - Settings - Resources - do find it)

    Sunday, March 9, 2008 11:41 PM
  • Basically same thing when I do a "backup now"

     

    BSOD - BAD_POOL_HEADER, System takes a dump, restarts.

     

    I have updated all my drivers and BIOS to the latest versions.  Windows Update is caught completely up.

     

    I have two other clients that back up okay.  Just one computer has the problem.  The computer is otherwise stable, and runs for days.  No serious messages in the event log.

     

    I have removed the client from WHS, and removed and reinstalled the client connector.

     

    I will test out my memory later to make sure I don't have bad RAM.

     

    Here is more detailed Debug info:

     

    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 00000020, a pool block header size is corrupt.
    Arg2: e65d6a98, The pool entry we were looking for within the page.
    Arg3: e65d6ab8, The next pool entry.
    Arg4: 0c040801, (reserved)

    Debugging Details:
    ------------------

    GetUlongFromAddress: unable to read from 80564c50

     

    BUGCHECK_STR:  0x19_20

    POOL_ADDRESS:  e65d6a98

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

    LOCK_ADDRESS:  8055a4e0 -- (!locks 8055a4e0)

    Resource @ nt!PiEngineLock (0x8055a4e0)    Available

    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

    1 total locks

    PNP_TRIAGE:
     Lock address  : 0x8055a4e0
     Thread Count  : 0
     Thread address: 0x00000000
     Thread wait   : 0x0

    LAST_CONTROL_TRANSFER:  from 8054a583 to 804f9deb

    STACK_TEXT: 
    ba507928 8054a583 00000019 00000020 e65d6a98 nt!KeBugCheckEx+0x1b
    ba507978 8058e975 e65d6aa0 00000000 00000000 nt!ExFreePoolWithTag+0x2a3
    ba5079d8 8059038d 88ed0030 e5dfdd78 ba507a44 nt!PipMakeGloballyUniqueId+0x3a9
    ba507acc 80590f9b 89889228 88f55588 8ae67a30 nt!PipProcessNewDeviceNode+0x185
    ba507d20 8059148a 8ae67a30 00000001 00000000 nt!PipProcessDevNodeTree+0x16b
    ba507d54 804f6853 00000003 8055a5c0 8056375c nt!PiProcessReenumeration+0x60
    ba507d7c 805379bd 00000000 00000000 8af33da8 nt!PipDeviceActionWorker+0x14b
    ba507dac 805ce84c 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
    ba507ddc 8054532e 805378ce 00000001 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!ExFreePoolWithTag+2a3
    8054a583 8b45f8          mov     eax,dword ptr [ebp-8]

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!ExFreePoolWithTag+2a3

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  45e53f9d

    FAILURE_BUCKET_ID:  0x19_20_nt!ExFreePoolWithTag+2a3

    BUCKET_ID:  0x19_20_nt!ExFreePoolWithTag+2a3

    Followup: MachineOwner
    ---------

     

     

     

     

     

    Monday, March 10, 2008 5:16 AM
  •  

    Windows Home Server Konsole: 6.0.1500.0
    Windows Home Server Sichern und Wiederherstellen: 6.0.1500.8
    Windows Home Server Laufwerkextender: 6.0.1500.0
    Windows Home Server Remotezugriff: 6.0.1500.0
    Windows Home Server Speicher-Manager: 6.0.1500.8

     

    Client OS: Win XP Pro.

    HD: 1x 300 GB P-ATA NTFS

     

    I think the problem happened first time after a full restore with Acronis True Image,

    but I´m not sure.

     

     

    Stephan

     

     

     

     

     

    Monday, March 10, 2008 7:41 AM
  • I wonder if WHS is keeping information about a computer even if a computer is removed from the backup list?

     

    I say this because I had a disk partition that no longer exists, but still shows up when I remove and add a computer to the computer backup list.

     

    This error started happening after I changed out my motherboard and then hard drive on the client computer with the backup problems.  I did these in two distinct steps days apart.

     

    Here are the steps I took:

     

    Changed motherboard (ASUS Maximus Formula)

    1. Set IDE drivers to Microsoft generic IDE drivers
    2. Performed WinXP repair install
    3. Removed any software pertaining to old motherboard
    4. Removed client from WHS
    5. Updated all drivers
    6. Updated BIOS
    7. Waited a few days
    8. Changed hard drive from 120MB WD ATA to 500MB Seagate SATA
    9. Waited a few days
    10. Added client to WHS backup
    11. Client crashed on WHS backup
    12. Removed client from WHS backup, uninstalled connector software
    13. Reinstalled connector software, added client to WHS backup
    14. Client crashed on WHS backup either scheduled or backup now

    Before the motherboard and HD change, the backup worked fine.

     

    The client computer has a clean events system and application log.

     

     

    Now, the client

    Monday, March 10, 2008 6:17 PM
  • Have you tried to select the home computer via the Windows Home Server Console - Computers & Backup tab and then clicked on the "Configure Backup" button?

     

    What happens?

     

     

     

    Monday, March 10, 2008 6:44 PM
  • > Have you tried to select the home computer via the Windows Home Server Console - Computers & Backup tab and then clicked on the "Configure Backup" button?

    >

    >What happens?

     

    Nothing unusual, except for a dialog showing a non-existant drive.

     

    Otherwise, the dialogs show nothing unusual.

     

    On the "choose volumes to backup" dialog:

     

    Name Capacity Used Space Location Status  
    C: (Local Disk) 465.76 GB 68.01 GB Internal
    D: (New Volume) 19.93GB 17.59 GB Unknown Not Connected  

     

    The D: drive does not exist, so it shouldn't be showing up.  That partition was removed two months long ago.

    Tuesday, March 11, 2008 2:28 PM
  • Hi Dan, could you please contact me at whsforum@microsoft.com - we'd like to investigate.

    Friday, March 14, 2008 7:12 PM
  • I have exactly the same problem - BSOD with the Bad Pool Header message when I attempt a Backup from the Client side or the WHS side.  I am using a newly installed HP MediaSmart WHS.  I have the connector installed on two desktop XP Pro PC's and one XP Pro laptop.  The backup works without a problem on the two desktop PCs.  The BSOD crash occurs when trying to backup my HP nc6400 laptop.  The laptop has never successfully backed up.  The client shows 0% backed up and the WHS shows 0% backed up - about 30 seconds later the crash and reboot occurs on the laptop.  Windows and HP drivers/patches are up to date.

     

    Tuesday, March 18, 2008 5:13 AM
  • I've encountered the same problem on another client computer.

     

    This should help narrow the problem down a bit:

     

    Backups on this client computer were working fine until I upgraded the hard drive.

     

    I upgraded the hard drive:

     

    ATA WD Caviar 120MB using motherboard (Gateway El Paso) IDE controller --> SATA Seagate 465MB using a StarTech SATA PCI controller.

     

     

    The other client computer which I originally posted about also was upgraded from an ATA 120MB to a SATA 465MB but using motherboard controllers.

     

    Both clients were upgraded to the following hard drive:

     

    Model ST3500320AS Seagate Barracuda 7200.11 SATA 3Gb/s 500-GB Hard Drive Firmware SD15
    Size 465.76 GB (500,105,249,280 bytes)

    Saturday, March 29, 2008 3:43 PM
  • Had a Dell laptop backing up properly until I upgraded to a larger hard drive with Apricorn, a software product apparently made by Acronis and now I am having the same problem, BSOD with Bad Header Pool.

    Anybody have a solution short of rebuilding the os on the client drive?

    Warren
    Saturday, April 5, 2008 12:37 AM
  •  wpruitt wrote:
    Had a Dell laptop backing up properly until I upgraded to a larger hard drive with Apricorn, a software product apparently made by Acronis and now I am having the same problem, BSOD with Bad Header Pool.

    Anybody have a solution short of rebuilding the os on the client drive?

    Warren

     

    Very Interesting!  The only computer (my laptop) that I am have the Backup BSOD problem on happens to be one that I used Acronis to clone the drive to a larger one.  I wonder if there is any connection between Acronis and this problem.

     

    Saturday, April 5, 2008 3:06 AM
  •  johnef wrote:

     

     

    Very Interesting!  The only computer (my laptop) that I am have the Backup BSOD problem on happens to be one that I used Acronis to clone the drive to a larger one.  I wonder if there is any connection between Acronis and this problem.

     

     

    I also have just one of 6 machines which regularly crashes when WHS initiates a backup.  It doesn't seem to happen if I have the WHS console open on the machine which crashes.

    This machine has also been "reconstituted" with Acronis, but unfortuntaely for this theory so have 2 of the machines which have no problems.

     

    My Crash message is as follows:

     

    Driver_IRQL_NOT_LESS_OR_EQUAL

    STOP 0X000000D1 (0X0000002C,0X00000002,0X823A33C4)

    NVSTOR.SYS ADRESS 823A33C4 BASE AT 8239F000, DATESTAMP 458D543D

     

    Any advice appreciated

     

    PS Vista Business, SP1, all updates to all programs and drivers.  AMD 4600+, 2GB RAM, plenty of HDD space.

    Saturday, April 5, 2008 8:58 AM
  • Rach3,

    You have a different problem!

    Yours is very likely caused by the NVidia drivers. You need to ensure they are updated to the latest versions, as nvstor.sys had a bug. This thread has more info.

     

    HTH,

     

    Colin

     

    Saturday, April 5, 2008 9:34 AM
  • I used Seagate Disk Wizard to upgrade my hard drives from WD ATA 120GB Seagate 500GB SATA drives.

     

    The Seagate Disk Wizard uses its own version of Acronis.

    After I read about the Acronis possibility, I:

    • Removed all of the Seagate Disk Wizard and Acronis software
    • Performed a full Disk Check (SCANDISK)
    • Tried performing a manual backup.

    I still got the BSOD with Bad Header Pool.

     

    Dang!  I was hoping we were on to something...

    Monday, April 7, 2008 3:28 AM
  •  ColinWH wrote:

    Rach3,

    You have a different problem!

    Yours is very likely caused by the NVidia drivers. You need to ensure they are updated to the latest versions, as nvstor.sys had a bug. This thread has more info.

     

    HTH,

     

    Colin

     

     

    Thanks Colin,

    Actually the thread you directed me to was originally mine and I thought I had solved it with upgrade of the nVidia drivers.  However the problem has returned and despite upgrading the nVidia drivers with every release, the problem remains.

    I am considering replacing the (rather old) graphics card with a new one and if the problem persists I think I will upgrade the computer completely.

    Monday, April 7, 2008 11:04 AM
  • On the laptop where I had the problem, backups worked fine until I updated the hard drive and reinstalled the server. I tried deleting and re-establishing the cache file, chkdsk, defrag and re-install connector software on the client all to no avail. There had been no other changes to the machine prior to the disk update. The server had been off for a couple of weeks as my trial version had expired and was waiting on my purchased oem copy to arrive. The problem occured after the server reinstall. The other clients did not show this problem and since I had updated this drive on the laptop I would assume that is where the problem was introduced. But maybe not.

    If I had known of a potential problem I would have stepped thru my process differently to help narrow the cause. No matter as I rebuilt the hard drive on the laptop this weekend and all works fine now.

    Warren
    Monday, April 7, 2008 4:56 PM
  • I wonder if this problem is happening to anybody with Windows XP SP3 installed?

     

    XP SP3 should be out before July.

     

    Tuesday, April 8, 2008 3:56 AM
  • 1. Cloned a new 250G Seagate from an 80G WD.

    2. Removed PC from HP WHS EX470

    3. Tried to back up and got bad_pool_header.

    4. Reinstalled orig 80G drive....no problem

    5. Put 250G back in and tried to back up using XP Backup same problem

    Tuesday, April 8, 2008 6:39 PM
  • I also experienced what appears to be the identical problem on my laptop, a Dell Inspiron XPS Gen 2.  (Bluescreen reporting BAD_POOL_HEADER after initiating a manual WHS backup - the backup progress bar is still at 0% when crash occurs)
    The problem began after I upgraded to a larger hard drive, using Seagate's DiscWizard to clone the old hard drive to the new, larger drive.
    Aside from the WHS backup problems, the laptop (and the new hard drive) works fine - I have not encountered any other issues.
    For now I have simply turned backup off for this laptop, but clearly this is not a long term solution!! Any hint as to the cause of the problem (or, better yet, resolution of the problem) would be greatly appreciated.

    The exact bluescreen msg is:

    *** STOP: 0x00000019 (0x00000020,0xE44DF1E8,0xE44DF208,0x0C040201)

    Friday, April 11, 2008 5:54 AM
  • I managed to find the a solution to the problem elsewhere:

    http://forums.seagate.com/stx/board/message?board.id=Discwizard&thread.id=46
    http://www.techspot.com/vb/topic94820-5.html

    In short, the problem seems to be rooted in MBR corruption caused by certain hard disk cloning software (including Seagate's DiscWizard, and Acronis True Image, which DiscWizard is based on).  The problem effects all backup software that makes use of Windows' Volume Shadow Copy, and thus is not limited to WHS.

    To fixed the problem, simply follow these steps:

    1. Go to windows Device Manager
    2. Click "view" and select "show hidden devices"
    3. Scroll down to "storage volumes"
    4. Click on the plus to expand.
    5. Click on each one listed and right click and uninstall. (you will get a message on some staying to reboot before it takes effect. Select no until you do them all.)
    6. Reboot.
    7. Wait till windows automatically reinstalls devices. Will prompt to reboot again.
    8 Reboot.

    Saturday, April 12, 2008 10:19 PM
  •  SytS wrote:
    I managed to find the a solution to the problem elsewhere:

    http://forums.seagate.com/stx/board/message?board.id=Discwizard&thread.id=46
    http://www.techspot.com/vb/topic94820-5.html

    In short, the problem seems to be rooted in MBR corruption caused by certain hard disk cloning software (including Seagate's DiscWizard, and Acronis True Image, which DiscWizard is based on).  The problem effects all backup software that makes use of Windows' Volume Shadow Copy, and thus is not limited to WHS.


     

    Wow...Thanks SytS!!!

     

    That worked great.  I can now backup my laptop without the Blue Screen.

    Sunday, April 13, 2008 4:24 AM
  •  SytS wrote:
    I managed to find the a solution to the problem elsewhere:

    http://forums.seagate.com/stx/board/message?board.id=Discwizard&thread.id=46
    http://www.techspot.com/vb/topic94820-5.html

     

    This solves the problem for me.

     

    Big thanks for coming thru for us!!

    Great sleuthing!

     

    Dan

     

    Monday, April 14, 2008 4:09 AM
  •  SytS wrote:
    I managed to find the a solution to the problem elsewhere:

    http://forums.seagate.com/stx/board/message?board.id=Discwizard&thread.id=46
    http://www.techspot.com/vb/topic94820-5.html

    In short, the problem seems to be rooted in MBR corruption caused by certain hard disk cloning software (including Seagate's DiscWizard, and Acronis True Image, which DiscWizard is based on).  The problem effects all backup software that makes use of Windows' Volume Shadow Copy, and thus is not limited to WHS.

    To fixed the problem, simply follow these steps:

    1. Go to windows Device Manager
    2. Click "view" and select "show hidden devices"
    3. Scroll down to "storage volumes"
    4. Click on the plus to expand.
    5. Click on each one listed and right click and uninstall. (you will get a message on some staying to reboot before it takes effect. Select no until you do them all.)
    6. Reboot.
    7. Wait till windows automatically reinstalls devices. Will prompt to reboot again.
    8 Reboot.



    thank goodness for this response.  I was about ready to put my old hard drive back into my laptop and forget the added space when I came across this post.  it worked perfectly after following your advice.  thanks for the time savings.
    Friday, May 30, 2008 11:59 PM
  • I'm troubleshooting an XP Pro system that was cloned with Acronis and beleive that perhaps the crash is related to Acronis???

    Saturday, August 23, 2008 2:48 AM
  •  Anonymous26354554 wrote:

    I'm troubleshooting an XP Pro system that was cloned with Acronis and beleive that perhaps the crash is related to Acronis???

     

    Very likely.  My problem laptop (that experienced the same problem) was also cloned with Acronis.  Thanks to the earlier poster, this problem is completely resolved for me.

    Saturday, August 23, 2008 4:02 AM
  • I recently et up WHS and everything was fine except the BSOD when I back up the single computer (of 5) that had its disk copied with Acronis. I see references elsewhere to the problem.

     

    Richard

     

    Sunday, August 31, 2008 2:49 PM
  • I have the exact same problem.  I used Acronis to copy my harddrive to a larger drive and ever since it crashes during the backup.
    Sunday, November 30, 2008 11:11 PM
  • I had the same issue with a my #2 computer, I just completed cloning the hard drive using Acronis TrueImage. 

    No more issues after following the steps from SytS.

    Thanks for the post in resolving this problem, I spent a few hours researching this issue.

    Again THANKS! 
    Friday, December 5, 2008 6:39 PM
  • Thank you SysT for your posted solution - I had same problem - system crashes with Code 19 when doing a WHS backup of a newly Acronis-restored HD. Now works OK.

    Many thanks...Mark
    Thursday, March 19, 2009 4:01 PM
  • Thank you very much. It solved my problem with one of the client pc's rebooting during backup. I followed the steps and found one of the storage volumes contained 3 square symbols next to it..i did the steps and it works fine now. Thanks for the post.
    Sunday, May 31, 2009 11:41 PM
  • Yes. I did an acronis backup of my xp pro partition so that i could install xp media center 05. Well seeing that xp media center was running sluggish, i decided to restore xp pro with the acronis image and thats when the trouble started. idk why or how, but following the steps provided above solved the inconvenience.
    Sunday, May 31, 2009 11:44 PM