›

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Google

Sign In Register
Our Sites

covecube.com 
community.covecube.com 
blog.covecube.com 
wiki.covecube.com 
bitflock.com 
stablebit.com 

Categories

Poll

No poll attached to this discussion.

In order to better support our growing community we've set up a new more powerful forum.


The new forum is at: http://community.covecube.com


The new forum is running IP.Board and will be our primary forum from now on.


This forum is being retired, but will remain online indefinitely in order to preserve its contents. This forum is now read only.


Thank you,


How Can I Preserve My Drivepool For Motherboard (Different) Replacement

mbc0mbc0
edited November 2012 in DrivePool
Hi,

I need to upgrade my motherboard & have 12 disks in my drivepool.  I am not sure if WHS2011 will allow me to get away with replacing the board or not so I may end up having to reload WHS2011 so need to know if I have to "Dismantle" the pool first?

Many Thanks For Any Advice!
Share on Twitter

Comments

  • saitoh183saitoh183
    Resident Guru
    no you dont, When you reinstall DP it should pick up all your drives. To be on the safe side, keep them unplugged during your WHS2011 installation. Also if the second partition created by WHS is in your pool, i would remove it from the pool since WHS installation wipes system disk and secondary partition
    Share on Twitter
  • mbc0mbc0
    Member
    I am kinda stuffed at the moment as I am unable to remove any drive... I posted this morning about it but no replies yet as I get access denied after hours of migrating files :-(

    Share on Twitter
  • ShaneShane
    edited November 2012 Resident Guru
    Might be a permissions error. Run the "reset permissions" option of the WSS Troubleshoot tool - http://wiki.covecube.com/StableBit_DrivePool_Utilities - and then try to remove the second partition from the pool as Saitoh183 suggests.
    Share on Twitter
  • mbc0mbc0
    Member
    Well.. It turned out to be a dodgy SATA cable! on one drive that was preventing its own removal & removal of others! 

    Replaced cable & voila! drive removed successfully.. would have thought I would have got an I/O error on removal but still... all ok now...

    Thanks for your replies :-)
    Share on Twitter
Sign In or Register to comment.