Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Drobo FS refusing brand new hard drives
02-02-2017, 02:09 AM
Post: #1
Drobo FS refusing brand new hard drives
Hi,

I've tried to replace one of the 5 hard drives in my Drobo 3 times now and each time it says it's faulty. These are brand new, different batch Toshiba 3TB P300 drives, and I'm already using two of them in other slots.

I have used Hard Disk Sentinel on these and it shows "perfect", ie. no SMART errors etc - which makes sense since it has never been used.

Is there a way to force Drobo to unmark a drive as faulty and then get it to read it again? I know that once it marks a drive as faulty you can't put it back in because it will recognise it as faulty immediately. Is there a way to remove that marker - perhaps some formatting program etc - that will at least get the Drobo to try again?

I've RMA'd all the drives with Amazon, but they're getting understandably annoyed that I keep sending back perfectly good hard drives!

Thanks,

Jeremy

PS Running latest firmware, dual disk redundancy, and a mixture of 3TB and 2TB drives.
Find all posts by this user
Quote this message in a reply
02-03-2017, 04:35 PM (This post was last modified: 02-03-2017 04:40 PM by Paul.)
Post: #2
RE: Drobo FS refusing brand new hard drives
hi jeremy, can i check if the sentinel tool you used, seemed to run quite quickly (like about 15minutes) to scan each drive? or did it take several hours?

if it was a quicker test, it might be worth making a note of the current smart values, and then to run a full sector test as well, and then to compare smart values again, just to see.

one good tool you can also use (on new / empty drives) is a tool by western digital called data life guard which is free.

at first i was thinking that it could be just the fact that the fs is old, and maybe the drives you are using are special in some way, requiring a new firmware (which may not exist), though when you mentioned you already have 2 of them with the same identical model then it probably isnt that.

i would try some more tests if you can, just in case there actually are some sectors being reallocated too often for their own good, (which might help with the rma process too), but another theoretical test could also be the below, in 2 parts:

(please note, before you try this, if you do not have a backup of your data, you may want to take a backup, or at least of the most important data to play safe)

part 1:
you could try powering all Off, and unplugging all cables from drobo
and remember the order of your diskpack for future, to swap 1 of the working models, with the drive that is in the slot of the drive you were trying to replace.....and then to connect up and power up the drobo.

this way, your drobo should still be booting up with its diskpack drives inside,
but the toshiba drive (which was known to be working) would be in the slot where the replacement toshiba did not work and was rejected.

when the computer and dashboard boot up, and after say 10minutes of general usage, you could see if that (known to be working) toshiba you swapped bays with, gets rejected.... if it does, then it could just be something about that model in that bay.

if the originally working toshiba, still works in its new bay, then there probably is something about the new toshiba that was sent to you, (especially if it is the same model and identical drive firmware etc) - also, dashboard may be able to show you more info and serial/firmware info about each drive, depending on version of dashboard.

the 2nd part of the test, (which will probably be best after letting your drobo run smoothlyfor a few days) would be to then try replacing (while powered on) the new, previously-rejected (and currently outside of the drobo) toshiba drive, by swapping it with the non-toshiba drive that you already swapped bays with in part 1).... if it accepts it here in this bay, then it could have just been a bay issue.... but if it is still rejected, maybe there is something wrong with the drive.


btw for the part about wiping a drive, i think deleting the partition using a standalone connection with the drive to the computer, (without any drobo), to format it in windows, and then delete the partition, followed by using a tool like dariks boot and nuke has been able to wipe any flag, (but im not sure if some models of drobo firmware maintain a copy of the drives serial number)

if you do use dariks tool, it is best to run it on a computer that does not have any other drives or devices attached to it etc, apart from the drive you want to erase, just in case...


by the way, can i check how you have been trying to replace the drives so far?
is the drobo and dashboard on when you do this, or have you possibly been replacing while powered off, and then powering up and seeing it get rejected?

(btw i have XP home SP2, a Drobo v1 with 2x 1TB/2x 1.5TB WD greens, & a bkp Drobo v2 with the same + a DroboShare: unused)
& a DroboS v2 with 3xWD15EADS &2x1TB in DDR mode on win7, & a drobo5D (all usb)
  • btw i did a sustained (write) operation for about 6 hours, and got 13.2MB / sec ...objection? "sustained" :)
    (16.7MB/s on a v2 & 47-96MB/s drobo-s)
Find all posts by this user
Quote this message in a reply
02-05-2017, 07:09 AM
Post: #3
RE: Drobo FS refusing brand new hard drives
That's a brilliant reply, thank you! I will try all of this at some point: in the meantime, I stuck a WD Red in there which is working just fine so at some point one of the P300's will fail and I will see if jiggling things around like you've suggested sorts out the mess.

Thank you so much.
Find all posts by this user
Quote this message in a reply
02-06-2017, 02:55 PM
Post: #4
RE: Drobo FS refusing brand new hard drives
ah thanks for that Smile
also if the wd red has been accepted (and is now "green" in terms of solid green bay light) then that is a good indication that the particular bay seems ok, and also at least for now, the wd drive too)

sure please let us know how things progress.

(btw i have XP home SP2, a Drobo v1 with 2x 1TB/2x 1.5TB WD greens, & a bkp Drobo v2 with the same + a DroboShare: unused)
& a DroboS v2 with 3xWD15EADS &2x1TB in DDR mode on win7, & a drobo5D (all usb)
  • btw i did a sustained (write) operation for about 6 hours, and got 13.2MB / sec ...objection? "sustained" :)
    (16.7MB/s on a v2 & 47-96MB/s drobo-s)
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump: