[How to delay Drivepool service after reboot]

I ran "services.msc", find the "StableBit DrivePool Service", right click on it, and select "Properties", Open the "Dependencies" tab. It does list the Virtual Disk service.

 

Then I set startup type to "Automatic (delayed)"

 

I reboot the system. No missing disks this time!

 

Thanks.

[How to delay Drivepool service after reboot]

I have 64 disks. Every time after system reboot, some of disks were not ready yet before DrivePool would complain and re-measure. And that take a long time to re-scan the full thing.

 

My questions is:

 

1. Is there a way to disable the automatic "re-measure"? I don't use duplicate, no need for auto-placement and balancer. I just want a simple file pool.

 

2. If disable not possible, can I delay it for minutes?

[Can I unmount a pool?]

Christopher (Drashna), on 16 Sept 2014 - 02:45 AM, said:

Ah, okay. So removing/disconnecting/turning off the external pool is causing the internal pool to be remeasured?

.....

select disk 5
offline disk
select disk 6
offline disk
select disk 7
offline disk

Setting them online would be a matter of using "online" instead of "offline"

And you can load up diskpart and run "list disk" to determine what numbers the disks are.

 

Also, be aware, that you may need to test this out, as the disks may change number between reboots, etc. Especially as when the pool is recreated, it may change the disk order number.

 

1. I have 3 drivepool with 7 disks each. All of them are USB disks. Anytime when any of these 21 disks missing, all three pools will be remeasured.

 

2. Dont use disk #, use

 

                   disk <disk path>

 

    Where

<disk path>

Specifies the location of the disk to receive focus, for example, PCIROOT(0)#PCI(0F02)#ATA(C00T00L00). To view the location path of a disk, select it and then type detail disk.

 

 

    Ref: http://technet.microsoft.com/en-us/library/cc731355.aspx

 

    But make sure to use the same physical port ( USB or SATA )

[Replacing a bad disk under a Drivepool/Snapraid setup]

Wargazm, on 26 May 2014 - 9:01 PM, said:

 

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

 

there is alternate way, and i like this much better.

 

7. rename "PoolPart.xxx" to something else like "PoolPart.xxx.del"

 

8. rename "PoolPart.yyy" to "PoolPart.xxx"

 

9. in Disk Manager make your new drive "offline"

    ignore that DrivePool complain about disk disconnected...

 

10.  in Disk Manager make your new drive "online"

 

11. in drivepool, there will be two item for the new drive, one is normal, yet another one says "missing" 

      remove the missing one

 

12. Done

 

13. Optional step. delete the empty folder "PoolPart.xxx.del"

      make sure it is empty before deletion, if not sure, leave it there won't hurt

 

I did not fully test this, if someone have sucess on this or have modified procedure, please share.

in my post yesterday, snapraid files were touched. five minutes.

today's procedure, ADS files are put back under the original poolpart folder name. one minute

 

thanks

[Replacing a bad disk under a Drivepool/Snapraid setup]

Wargazm, on 26 May 2014 - 9:01 PM, said:

 

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

 

Yesterday, I ran into the same situation like you. Did all that, step 1 to 6 and some more:

 

7. snapraid --test-force-content-text test-rewrite (to convert the content file to text )

 

8. uedit d0\SnapRAID.content (where d0 is the first disk of snapraid array)

    the content file is big, several G, so you better edit it without temporary file

 

9. in ultraedit replace all "PoolPart.xxx" with "PoolPart.yyy" and exit

 

10. snapraid test-rewrite (convert back to binary)

 

11. snapraid diff (to check parity)

 

12. if no complain from snapraid, yes, you are DONE.

 

next time, better not, hope this will save u hours