I have two D5-300 enclosures. My first enclosure initialized fine and I was able to create a RAID5 array without issues. When initializing the second enclosure, I get a "disk damage error" for drive 3. Both enclosures are populated with 5 identical 4TB WD Red NAS drives. I returned and replaced what was identified as the bad drive, but the same error occurs. In fact when I swap the drives around, drive 3 always shows an error. There appears to be a fault with the second enclosure. What can I do to remediate?
Disk damage error when initializing
Re: Disk damage error when initializing
You can send an email to support(at)terra-master.com to ask for a replacement.
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: Disk damage error when initializing
I purchased this through Amazon in the US. I just received a replacement unit and get the same error in the same slot!
Re: Disk damage error when initializing
This may not be hardware faulty, two devices defective exactly same issue which is almost impossible. You check your hard drive and replace with another one and try again.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Re: Disk damage error when initializing
@TMROY - I think you're right. The slot number it was indicating may have been a red herring. I tried all drives in all different slots, and I think I was able to determine there was a bad drive in the group.