Jump to content

Christopher (Drashna)

Administrators
  • Posts

    11573
  • Joined

  • Last visited

  • Days Won

    366

Posts posted by Christopher (Drashna)

  1. I only do the "file placement limiter" for removing the drives. And.. for drives that I know may be in less than perfect health, I leave the "duplicated" option checked, and uncheck the unduplicated option, that way if the drive *does* fail, I only lose duplicates, and not any "unique" content.

     

    But I do leave the "balance immediate" options enabled. Though, I do have the "not more often than" enabled, as everything has "settled" properly and this helps prevent unnecessary activity.

  2. Well, you can't pass on SMART data on Hyper V (well, unless alex wants to figure out how to hack the pass through drivers to do so....), but you can install a second licensed copy (at a discount at least) on the HyperV host. If it's 2012 Core, this should work as well too (as it has the right version of .NET framework).

     

    But I've put up and pinned the instructions. :)

  3. Tomba, did it say "scanning" or "waiting to scan"? Because normally, if there is disk activity, Scanner will delay the scan, as to not interfere with normal file operations.

     

    That, or, have you messed with that setting?  Or, it was possibly low enough activity where it didn't trigger this delay in Scanner.

  4. That's entirely up to you. If it's working fine right now, you can just leave it.

     

    But I would recommend reformatting it as GPT. (but some have called me a glutton for punishment.... and maybe rightly)

    You can use the "File Placement Limiter" balancer to clear out the drive, so the pool is still accessible while it's migrating the data off of the disk. Once that's done, just remove it (should be very quick as there would be no data on the drive), then use disk management. There.... make sure you absolutely have the correct disk. Then delete the partitions (all of them) that are on the disk in question. Once that's done, right click on the box where it says the drive #, and select "Convert to GPT", and then you're set.  Create a partition at this point if you want (or just let drive Pool do that)

  5. Hmm, Would you mind posting those logs? Ideally, uploading them to a cloud solution, and post a link via http://stablebit.com/Contact

     

    As for migrating the files yourself... Check the balancers. Use the "File Placement Limiter" and uncheck both boxes for the drive in question.  Also make sure it is set to immediately balance.

     

     

    That or you *can* copy the contents of the folder (not the folder itself) to the contents of a different "PoolPart" folder on a different drive.

  6. I'm just as guilty of the "not duplicating everything". I'd like to, but ....

     

    Also, you could use the "File Placement Limiter" balancer to force migration off the disk in question. That way, you don't have to sit waiting for the drive to remove. You can clear the data off and then quickly remove the disk. :)

  7. Nimbu,  head to "http://stablebit.com/Contact" and we'll reset the activation for you.

    In the meanwhile, you could activate the trial period. 

     

    And very nice grab on the ex495.  Though, as for the BIOS, there really isn't much in there to change. :(  I had one of those units, and yeah, a lot of hte options are basically stripped out. Though, IIRC, most of the default settings are basically ideal.

     

     

    And yeah, the HP MicroServer's are a nice system too. Are you planning on using the BIOS mod for it?

     

    Also, I'd recommend a small disk for the operating system. And basically just backing up that drive. 

  8. Sorry, I think I skimmed a lot of the post (I apologize for that, but a nasty case of the stomach flu really does a number on you)

     

    And for the shared parts, you're absolutely correct.  

    Again, sorry.

     

    Though, if the OS SKU (version) includes it, "lusrmgr.msc" is a good way to verify that the user account names are identical.

  9. Yup. :)

     

    DrivePool will recognize the pooled drives, rebuild the pool, and it should even notice if you are missing disks. :)

    However, after that, I would recommend using the "WSS Troubleshooter" to "Reset NTFS permissions on the pool" (to wipe them clean), and then "Rebuild DrivePool Shares", as this will configure WHS2011 to use the pooled drive for the shared folders, so you don't have to manually configure them yourself.

    http://wiki.covecube.com/StableBit_DrivePool_Utilities

     

    Almost like that tool was built for reinstalls. :):P

     

     

     

    Also, if you don't mind me asking, did you have Server Backup set up? And if not, why not? It would have made restoring a half hour procedure, and you'd be back up and running just as it was.

     

    And .... (sorry for the completely shameless self promotion here, but) Did you have StableBit Scanner installed? If not, I would recommend at least checking it out, as it may have warned you about that failed hard drive before it went (depending on how it failed).  

×
×
  • Create New...