locked
Quick drive replacement, is it possible? RRS feed

  • Question

  • Hello,

    I have a dodgy SAMSUNG 2TB F4 that I think is failing, but I can still read most of the
    data on it.

    So I bought a WD TB EADS, that I haven't yet added to the pool.

    What if I:

    1. Labeled the WD EADS to DATA
    2. copy the DE folder and the QSM_VolumeID file from the SAMSUNG F4 to the WD EADS drive
    3. shutdown WHS
    4. disconnect the SAMSUNG F4
    5 restart WHS

    would WHS complain?

    Is it even technically possible?
     

    If not, why?

    And I know it is probably not supported.


    thanks in advance all WHS DE gurus.

    Pe

    Thursday, December 1, 2011 3:44 PM

All replies

  • What if you:
     
    1.  Install and add the new drive to the pool
    2.  Remove the Samsung from the pool
    3.  After removal operation is complete, shut down, disconnect and remove Samsung drive.
     
    --
    ______________
     
    BullDawg
    In God We Trust
    ______________

    Hello,

    I have a dodgy SAMSUNG 2TB F4 that I think is failing, but I can still read most of the
    data on it.

    So I bought a WD TB EADS, that I haven't yet added to the pool.

    What if I:

    1. Labeled the WD EADS to DATA
    2. copy the DE folder and the QSM_VolumeID file from the SAMSUNG F4 to the WD EADS drive
    3. shutdown WHS
    4. disconnect the SAMSUNG F4
    5 restart WHS

    would WHS complain?

    Is it even technically possible?
     

    If not, why?

    And I know it is probably not supported.


    thanks in advance all WHS DE gurus.

    Pe


    BullDawg
    Thursday, December 1, 2011 4:12 PM
  • Thanks,

    yes i know about the standard procedure, but I read horror posts

    about removing drives from the pool taking ages.

     

    I thought this would be a quicker way.

     

    regards

     

    Per

    Thursday, December 1, 2011 5:04 PM
  • I would expect Windows Home Server to choke on the operation, to be honest.

    If the drive is failing (and it is failing if there are files that you can't read any more), removing it from server storage can take a long time, or fail completely. The first thing to do is to try running chkdsk /r on the drive, to see if that corrects any issues. If that doesn't help, or if you start getting read errors again, you can:

    • Shut your server down.
    • Physically remove the drive.
    • Boot your server.
    • Remove the missing drive using the console (this will be fast). Accept any warnings about loss of files, etc. 
    • Connect the drive you removed to some other computer on your network.
    • Copy files from <drive>:\DE\Shares back to your shares.
    • Use the backup database repair functionality in the console to repair the database.

    Before you proceed, though, there's a post in the FAQ section concerning what's at risk when a drive fails. You should read it.


    I'm not on the WHS team, I just post a lot. :)
    Friday, December 2, 2011 1:50 AM
    Moderator
  • Ok, thanks,

    I take the safe route then.

     

    Per

    Friday, December 2, 2011 10:55 AM