Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[samendolaro]

While using Firmware 1.5  with 2 drives both drives will fail . I am not sure when this is happening.

I ran V1.5 with no apparent issues  while using a single drive.  When I added a second drive (non raid)  both drives will eventually get the failed amber light at the same time. This is usually within hours. It looks like it is happening while the drives are in standby.

I downgraded to V1.4 and everything works perfectly. I have run the V1.4 for 2 weeks with not problems .I upgraded to version 1.5 again and sure enough I got an Email telling me both drives had failed .


Any help here ?

[hilaireg]

Do you have the Make, Model, Part Number, and Firmware version of the HDD's?

[samendolaro]

Here you go...

Drive 1: Segate Barracuda ST3500460AS, pn 98j146-305 500gb, FW:3.AAE
Drive 2: Samsung HD501LJ, p/n 401411dp600339 500GB FW: REV a

[mig]

Did you format the drives with firmware 1.05 or 1.04?

[samendolaro]

Origionally 1 was formated with 1.4 and the new one with 1.5. After I saw I was having problems I copied all my Data from Drive 1 to Drive 2 and reformated Drive 1 with 1.5 .   

Now both drives have been formated with 1.5.

[hilaireg]

Can you verify the info on the Seagate ... can't seem to find 'ST3500460AS'  Also, can you confirm that the Samsung is 'HD501LJ' and not 'HD501IJ'


Samsung: HD501IJ

http://www.samsung.com/global/business/hdd/productmodel.do?group=72&type=61&subtype=63&model_cd=257&ppmi=1155



Once you confirm the model numbers, look at the specifications to ensure that the Seagate & Samsung HDD geometry is identical ... odds are they will not be and thus cause incompatibilities when placed in RAID.

Additionally, it's generally not best practice to mix-n-match your drives ... the D-Link support site and the box the DNS came in also make note that the drives should match.

HTH,

[mig]

You are running the drives as individual disks (right?) so I don't think disk geometry would be causing this problem.  I have read that the DNS-323 format process writes disk serial number to the system flash.  There is a possibility that during the up/down grading and formatting, these values in the flash and the actual drives are not consistent and triggering the failed drive alert.

My only suggestion at this point, would be to "start over" and setup the DNS-323 to v1.05 again.

1. Backup the data
2. Delete the partitions from the drives
3. With no drives installed, flash the DNS-323 with fw v1.05
4. Install both drives and format as individual drives
5. Restore data

I know this is a "sledge hammer" approach , but I can't think of anything else other that just use fw v1.04.

[MeatMan]

Might want to read this thread http://forums.dlink.com/index.php?topic=2430.0 too...  Sounds like the issue might be related.

[ECF]

Origionally 1 was formated with 1.4 and the new one with 1.5. After I saw I was having problems I copied all my Data from Drive 1 to Drive 2 and reformated Drive 1 with 1.5 .   

Now both drives have been formated with 1.5.

Now that you have formatted after updating to firmware 1.05 are you drives now working properly?

[samendolaro]

No, I am back to 1.4. I wanted to use the BT functionality but it is out of the question for the moment .

I'll wait for the release of 1.6 . If it still fails I will try some of the other suggestions here.


Thanks

[vaz]

mixing drives is supposed to be good, that way if there is a an early failure with a particular drive based on the manufacturing line it was made on, you lessen the risk of double drive failure. Although this only matters if you are using 1 disk for redundancy; raid1.

[hilaireg]

IMHO, mixing HDD's in a RAID is never a good idea.  If you're planning on using RAID, I suggest purchasing 3 identical HDD's that have been tested by D-Link Engineering.

This way, you have a spare HDD available at the time when the failure occurs.

Cheers,