fredmiranda.com
Login

  

  Previous versions of sjms's message #10207074 « Drobo finds an issue 12/31/2011 »

  

sjms
Offline
Upload & Sell: On
Drobo finds an issue


spooled up my Drobo S this morning and after a little bit the 3rd position HD (1TB Cavier Black) indicator went RED. in addition i had already started a full back it up to a secondary source as i do weekly before it faulted this drive. it started its fault tolerance routine and i simply pulled out the failing drive popped in a replacement and went out for awhile (like 3 hours). came back with 5 GREEN lights lit and the backup still going and finally completed 30 minutes later. put the failed drive into an external slot i use as a optional drive position and performed the WD diagnostics which it failed \"read test element\" of the test. pulled up the WD website and sent for an RMA. will have a new drive by wednesday or thursday as it is still under warranty.
no drama, no excitement. it just worked as designed. and i had full access while all this fun was occuring.



Jan 07, 2012 at 07:52 AM
sjms
Offline
Upload & Sell: On
Drobo finds an issue today


spooled up my Drobo S this morning and after a little bit the 3rd position HD (1TB Cavier Black) indicator went RED. in addition i had already started a full back it up to a secondary source as i do weekly before it faulted this drive. it started its fault tolerance routine and i simply pulled out the failing drive popped in a replacement and went out for awhile (like 3 hours). came back with 5 GREEN lights lit and the backup still going and finally completed 30 minutes later. put the failed drive into an external slot i use as a optional drive position and performed the WD diagnostics which it failed \"read test element\" of the test. pulled up the WD website and sent for an RMA. will have a new drive by wednesday or thursday as it is still under warranty.
no drama, no excitement. it just worked as designed. and i had full access while all this fun was occuring.



Dec 31, 2011 at 07:35 PM





  Previous versions of sjms's message #10207074 « Drobo finds an issue 12/31/2011 »