Jump to content
Covecube Inc.


  • Content Count

  • Joined

  • Last visited

Posts posted by Wargazm

  1. I had a drive go bad, so I pulled it and replaced it.  I removed the bad drive and added the new drive back to drive pool so it would create a .PoolPart folder, then used SnapRaid to recover the data on that drive.


    It all worked fine.  No data loss.


    But now, all the used space on the newly-replaced drive is marked as "other" data is DrivePool.  Everything on the old drives is still marked a Unduplicated (I don't enable any data duplication).


    Is this a problem or should I just ignore it?  



  2. Hello all,
    I have Snapraid configured with Drivepool like many of you. I have a drive that needs replacing, so before doing that I did some googling to make sure I had the procedure correct. I found a very helpful guid for drive replacement here: https://sourceforge.net/p/snapraid/discussion/1677233/thread/a223522f/?page=1


    I had a question about my snapraid conf file. In reading through that thread, I see that the recommendation for the "disk" lines in the conf file is as follows:


    disk d1 c:\mount\disk1\PoolPart.xxxxxx

    disk d2 c:\mount\disk2\PoolPart.yyyyyy

    (etc through d5 in my case)


    This varies from how I set mine up. What I did:


    disk d1 W:\

    disk d2 V:\

    (etc through d5 in my case)


    So after reading this post:




    by Quaraxkad I see that the way I set it up, while not technically wrong, is cumbersome.


    What I'm wondering is how I can re-configure snapraid to use the recommended method. Do I have to unmount all my disks from their drive letters and remount them under the C: drive? Would that cause snapraid to have to rebuild parity from scratch? What's the least dangerous way to proceed here?


    Thanks in advance for any assistance.

  3. I see.  Just a few more questions:


    1. What is ADS?

    2. Would this procedure work?

    1. Drive dies, or is about to die.  
    2. Disconnect the drive
    3. Click remove in Drivepool
    4. Reconnect new drive, use Snapraid to recover the data, which will be in a PoolPart.xxx directory.
    5. Add new drive to pool.  Drivepool creates a new, empty PoolPart.yyy on the drive
    6. Move data directly from PoolPart.xxx to PoolPart.yyy. (this is the step I'm unsure about, can I mainpulate data in those directories directly and have DrivePool work?)
    7. Done

  4. I ended up removing the disk, copying the files to the pool until the disk was empty, then adding the newly emptied disk back into the pool.  This had the unfortunate side-effect of requiring me to re-sync all of my snapraid parity data, however.  Not a big deal, but I'd like to avoid that in the future.


    What's the correct way to replace a disk, for future reference?  If one of my drives blows up tomorrow, I should be able to recover my data with snapraid.  But then I have to tell Drivepool to pick up that new disk as a drop-in replacement for the one that blew up.  I don't know how to do that.

  5. I am using Drivepool and Snapraid concurrently.  Here is the way I have my disks set up:


    one 300GB disk - OS boot disk

    five disks of various sizes - Content for pool, protected by Snapraid

    two 4TB disks - Snapraid parity


    One of the five content disks was a 2TB WD drive that went bad, so I replaced it with a 3TB WD dive and used snapraid to recover the drivepool data that had been written to the disk.  the recovery went well, but now Drivepool isn't adding the drive back into the pool silently as I had thought it would.  


    So I am not sure how to proceed.  The data is all on the new drive, I just want Drivepool to pick up the drive and continue on using the new drive as if everything was normal.


    Any help would be much appreciated!  Thanks in advance.

  6. IN the last few days I've moved my storage spaces-based pool over to a DrivePool/SnapRaid solution, and I like it quite a bit.


    I also installed Scanner, which has alerted me to some SMART warnings.  No imminent failure yet, but still not good.  


    The thing is that I'm not seeing anything in the GUI that shows me DrivePool is aware of the SMART issues that Scanner found.  I thought that there was an option to have DrivePool evacuate a disk when it got a SMART warning from Scanner, but I'm not seeing anything like that in the options...not sure even where to look.


    What sort of integration between the two products should I be expecting?  

    arg, figures I find it right after I post the topic.  It's under the Balancers section.  Never mind!  :-)

  • Create New...