Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Cannont Remove Drive due to File Conflict RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I have a drive which I suspect is failing so I decided to be proactive and remove it.    I removed the drive and it moved all of the data off save for 1 file.    The removal process then fails with a file conflict error.

    "The Request Couldn't Be Performed because of an IO Error"

    When I select to see what files couldnt be moved there is only one file listed:
    Data.4096.29.dat

    The Path to this file is D:\Folders\{number string} and when I navigate to this path this file exists and is 4GB.

    I understand this file is part of my backup database.     How Do I get around this problem?

    UPDATE:
    1. I ran a Backup DB Repair and this came back clean.
    2. I ran a Cleanup Now, and this failed stating there is an error in the Backup Service.

    I see the following in the Home Server Event Log:

    Error - Backup - 268370192:
    Unexpected error 0x45d from ReadFile on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\Data.4096.29.dat: The request could not be performed because of an I/O device error.

    Error - Backup - 268370187:
    Client Backup server failed at d:\wssg_src\whs_pp2\qhs\src\backup\util\diskfile.cpp(449)


    Wednesday, April 29, 2009 2:27 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    This did the trick.     The chkdsk /r completed and this allowed a graceful removal of the drive through the home server console.

    Thanks.
    Wednesday, April 29, 2009 10:15 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    If you are unable to remove the hard drive using the Server Storage tab, try the following:

    1. Disconnect the hard drive from your home server.
    2. Remove the hard drive using the Console Server Storage tab. The disconnected hard drive has a Missing status

    Since the file is part of the client backup database you will probably also run into problems there. If you also managed to copy this file from the suspect disk to another location you can try and copy it back to the folder D:\folders\{number string}

    The "file"  you currently see in that location is probably not the real file but a so-called tombstone which points to the actual storage location of the file (probably on the suspect disk)

    Just for the record, did you physically remove the drive, then MOVED all data to another location, then connected it again and try to remove trough the WHS console? Please detail your steps.

    Normally you should remove the disk using the WHS console, Storage tab. This should move all files to another location on your WHS, provided there is sufficient space. If you get errors when trying to remove the disk you could try running chkdsk on the failing disk

    Wednesday, April 29, 2009 3:05 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    The drive is still connected to the WHS box and it status is healthy.   It had about 230GB worth of Data on it.    I have only drive removing it through the WHS Storage Console.   During this process is successfully copied all the data off of this drive to other drives within the pool.    

    When I look at disk management add-in for this drive it reports as having only 4GB space being used.   This paired with WHS reporting there is a file conflict for only the 1 4GB file pretty much validates there is 1 4GB file on this drive preventing proper removal.

    Thoughts?


    Wednesday, April 29, 2009 3:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The drive is still connected to the WHS box and it status is healthy.   It had about 230GB worth of Data on it.    I have only drive removing it through the WHS Storage Console.   During this process is successfully copied all the data off of this drive to other drives within the pool.    

    When I look at disk management add-in for this drive it reports as having only 4GB space being used.   This paired with WHS reporting there is a file conflict for only the 1 4GB file pretty much validates there is 1 4GB file on this drive preventing proper removal.

    Thoughts?



    Hi,

    This file is more than likely part of the backup database. If you wish to copy the database and then delete it and try to remove the drive, please see the steps for copying and deleting the backup database in the Technical Brief for Home Computer Backup and Restore.

    Saving a Copy of the Backup Database

    The Windows Home Server backup database is not duplicated by Windows Home Server Drive Extender. So if you lose a single hard drive on your home server, you could possibly lose all of the backups of your home computers.

     

    You may want to periodically copy the entire backup database from your home server to an external hard disk that you attach to your home server. The external hard disk should not be added to the Server Storage on your Windows Home Server.

     

    Important

    The cluster data files stored in backup database can grow to 4 GB, so it is important that the external hard disk is formatted as NTFS to support copying these large files. Some file systems, such as FAT-32 allow a maximum file size of 2 GB.

     

    The backup database is stored entirely in the folder D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}.

     

    *        To copy the backup database from your Windows Home Server

    (In this example, assume that the external hard drive is given a drive letter of E:)

     

    1.     Run mstsc.exe to start a Remote Desktop Connection session to your home server.

    Caution

    Be careful when using a Remote Desktop Connection to your home server. You can damage Windows Home Server functionality if you use it incorrectly.

     

    2.     Plug in an external hard drive to your home server (do not add it to the Server Storage through the Windows Home Server Console).

    3.     Open a Command Prompt, Click Start, Run and type CMD

    4.     Type net stop PDL.

    5.     Type net stop WHSBackup to stop the Windows Home Server Backup service.

    6.     Copy the contents of D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4} to the external hard drive E:.

    7.     Type net start WHSBackup to restart the Windows Home Server Backup service.

    8.     Type net start PDL.

    The only relevant settings that Windows Home Server backup stores in the registry on the home server are Backup Time and Automatic Backup Management.

    Deleting the Backup Database

    You may want to delete the entire backup database from your home server to reclaim the disk space. The backup database is stored entirely in the folder D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}.

     

    *        To delete the backup database on your Windows Home Server

     

    1.     Run mstsc.exe to start a Remote Desktop Connection session to your home server.

     

    2.     Open a Command Prompt, Click Start, Run and type CMD

    3.     Type net stop PDL.

    4.     Type net stop WHSBackup to stop the Windows Home Server Backup service.

    5.     Delete the contents of D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}.  Do not delete the folder.

    6.     Type net start WHSBackup to restart the Windows Home Server Backup service.

    7.     Type net start PDL.

     

    Important

    After deleting the backup database, you need to reinstall the Windows Home Server Connector software or run the Discovery.Exe program on each of your home computers to re-establish a relationship between your home computers and your home server so new backups will occur.

    Restoring a Backup Database

    You may want to restore an entire backup database, which you previously saved on an external hard drive, to your home server. Prior to restoring a backup database, you need to delete the existing backup database from the home server. Currently, there is not an option to merge backup databases into a single database.  

     

    *        To restore the backup database to your Windows Home Server

    (In this example, assume that the external hard drive is given a drive letter of E:, and it has a copy of a home server backup database that was previously saved as described in the Saving a Copy of the Backup Database section earlier in this document.)

    1.     Run mstsc.exe to start a Remote Desktop Connection session to your home server.

     

    2.     Plug in an external hard drive to your home server (do not add it to the Server Storage through the Windows Home Server Console).

    3.     Open a Command Prompt, Click Start, Run and type CMD.

    4.     Type net stop PDL.

    5.     Type net stop WHSBackup to stop the Windows Home Server Backup service.

    6.     Delete the contents of D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}.  Do not delete the folder.

    7.     Copy the contents from the external hard drive E:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4} to D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}.

    8.     Type net start WHSBackup to restart the Windows Home Server Backup service.

    9.     Type net start PDL.

     

    Lara Jones [MSFT] | Program Manager
    Community Support and Beta | Windows Home Server Team
    Windows Home Server Team Blog
    Connect Windows Home Server
    Windows Home Server
    Wednesday, April 29, 2009 3:37 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks, I will look into this.    I rebooted the SATA enclosure and now this drive is throwing Eventid 7 errors that it has a bad block.

    I am runnning a chkdsk /r on it now in hopes it repairs the errors so I can remove this drive gracefully for an RMA.
    Wednesday, April 29, 2009 3:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I am runnning a chkdsk /r on it now in hopes it repairs the errors so I can remove this drive gracefully for an RMA.

    That's the proper thing to do at this point. Most times this will (temporarily) fix the problem and hopefully allow you to remove the disk without losing the database. If not, your backup database is probably lost. Trying to copy or delete the backup DB before running chkdsk will almost certainly fail anyway.
    Wednesday, April 29, 2009 6:20 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    This did the trick.     The chkdsk /r completed and this allowed a graceful removal of the drive through the home server console.

    Thanks.
    Wednesday, April 29, 2009 10:15 PM