D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: SamC on August 16, 2009, 02:33:03 PM
-
Hi,
I appear to have a new problem with my DLink 323, its just started showing only one of the lights as blue, the other has no light at all, I have 2xSamsung 1TB HDs installed in a Raid 1 configuration, and the status screen is showing the details below. How can I verify (safely) that the 2nd drive is active and working in a Raid 1 config ?
Details from the Status Screen
HARD DRIVE INFO :
Total Drive(s): 2
Volume Name: Volume_1
Volume Type: RAID 1
Sync Time Remaining: Completed
Total Hard Drive Capacity: 982880 MB
Used Space: 556875 MB
Unused Space: 426005 MB
PHYSICAL DISK INFO :
Slot Vendor Model Serial Number Size
1 SAMSUNG HD103UJ S13PJDWQC***** 1000 G
2 SAMSUNG HD103UJ S13PJDWQC***** 1000 G
-
I forgot to mention that I'm using Firmware 1.07
-
Based on the status screen I'd say you're good to go - the unit is seeing both disks and is not showing the sync time remaining as degraded.
There have been reports on the forums of the LEDs failing, I'm guessing that is what has happened to you - might be an idea to have it replaced if it's still under warranty.
-
SamC,
fordem makes a good point. In most all cases, an LED (and it's reporting circuit) simply monitors and reports. So, the good news is... If the LED fries (goes 'open') or, if the circuit really does go bad, it won't otherwise interfere with actual operation of the unit.
However, let's take it another step, or two, or three... Since it may not be 'broken' at all; it may be due to one of several other simple possibilities... Maybe a logic switch (within a chip) got 'hung'. Or, maybe a 'weak' plug/jack connection is causing high resistance (due to repeated heat expansion/contraction, oxidation, etc.). Or, whatever. So, here are a few questions that may provide some insight:
- Do you ever Pwr Off/On the unit?
- Have you ever found it shut down on it's own?
- Do you have the unit plugged into a real Surge Protector or, even better, a UPS?
- Also, what about your Switch, Router, Cbl Modem, or anything else that can let a spike get through a direct (or indirect) path?
Also, since you didn't mention any troubleshooting, I'd suggest:
First test...
- Do an orderly shutdown (of the DNS-323)
- Unplug the Pwr Cbl
- Wait 60 Sec
- Plug in the Pwr Cbl
- Turn it on
- See what happens
Second test (If no change in symptom, or the next time it happens)...
- Do an orderly shutdown (of the DNS-323)
- Unplug the Pwr Cbl
- Wait 60 Sec
- Re-seat the drives -- WARNING: Take care to comply w/ ESD precautions (http://www.radio-electronics.com/info/electronics-design/esd/what-is-basics-electrostatic-discharge-tutorial.php)!
- Plug in the Pwr Cbl
- Turn it on
- See what happens
Third test (If no change in symptom, or the next time it happens)...
- Do an orderly shutdown (of the DNS-323)
- Unplug the Pwr Cbl
- Wait 60 Sec
- Swap the drives around -- WARNING: Take care to comply w/ ESD precautions (http://www.radio-electronics.com/info/electronics-design/esd/what-is-basics-electrostatic-discharge-tutorial.php)! Also, as far as I know, swapping the drives around (in your current configuration) won't affect your data; but, since I've never tried it... you should get an expert opinion before you actually try this one.
- Plug in the Pwr Cbl
- Turn it on
- See what happens
-
PLEASE, Please, please - backup your data before swapping disks around in your DNS-323, especially with a RAID1 configuration - the unit tracks the disks by serial number.
At the very least, you're going to get a message saying that the disks are installed incorrectly and asking you to swap them back - worst case scenario would be that even after swapping them back, the message doesn't go away.
-
Thanks, fordem.
I was hoping you'd step in on that.
BTW... Are you saying f/w versions prior to 1.08b (i.e., 1.07 in this case) actually "cares" about which drive is in which slot when configured as SamC's (and mine) are?
-
Thanks fordem and rws8258, I think that its just the light thats failed.
I've backed up the 550GB of data from the DNS-323 that I had, this took a few days, I've taken out the drive that had the faulty light and placed this in a external USB enclosure, and this appears to be working fine, now that its been reformatted.
I've placed a new HD of the same type (Samsung HD103UJ) into the DNS-323 and its started formatting it, but no light comes on. When this completes, I'll check the status of the Raid and the contents of the Volume_1 volume.
I've not had any problems with the unit before, and its plugged into a surge protector, along with my other IT equipment. The external USB drive that I had also failed around the same time, so it could have been power related. I'll let you know more when it completes the synchronisation on the raid.
Sam
-
The drive has finished formatting and the DNS-323 is showing the status as, but still no light on the drive ...
Total Drive(s): 2
Volume Name: Volume_1
Volume Type: RAID 1
Sync Time Remaining: 161.8 minute(s)
Total Hard Drive Capacity: 982880 MB
Used Space: 558504 MB
Unused Space: 424376 MB
PHYSICAL DISK INFO :
Slot Vendor Model Serial Number Size
1 SAMSUNG HD103UJ S13PJDWS654321 1000 G
2 SAMSUNG HD103UJ S13PJDWQ654321 1000 G
I can't believe that it takes nearly 3 hours to sync up the raid.
Sam
-
rws8258 - I could be wrong, but I believe the serial number tracking was introduced with 1.04, it's certainly been around before the 1.08 beta.
Sam - 3 hours is nothing - I've had "non-DNS" RAID arrays that consistently take just less than 12 hours to resync, and that was with 150GB drives - and others that will resync 80GB in 20 minutes.
-
Thanks, fordem... I understand what you're referring to, now.
SamC, Sounds probable that your USB drive (the one that croaked) probably "kissed" your 323 with it's last breath. However, the possibility exists that the "kiss" was initiated by the 323 and went the other way and killed the USB drive. I realize that one HD LED not working is a scant inconvenience; but, if that USB drive died the same time the HD LED on your 323 quit, I'd definitely RMA the 323 (if it's still under warranty). Why? Well, today it's just an LED, tomorrow it will be something far more significant.
-
Again, many thanks.
I'm not in a position to RMA the unit, as it was given to as a present, and I don't have the purchase details. I'll just put up with the missing light and check the status on a weekly basis. Also RMA'ing the unit, would compromise my backup strategy, with the backups taking place on the 323, then that's backed up on the external USB drive, this way I always have three current copies of the data. Two (mirrored) on the 323 & USB.
Sam
-
You could also setup email notification. Just because the light went out doesn't mean emails don't work :).
-
Just to add a bit to the discussion.. I recently upgraded to 1.07 firmware, and also just noticed one of my drive lights no longer functions. Perhaps it's coincidence, but this is the first LED I've ever had go out on me. Other than install the new firmware, I haven't done anything with the 323.
-Craig
BTW - Looking at the front of the case, its the right drive light.
-
Sorry for bumping an OLD thread, but I just want to note that I have the same exact issue with the right LED...
Seems to be a trend. My warranty is out as well, if I at least had the part number of this light, I'd replace it myself..... =(
-
I suspect you can simply buy any compatible sized dual color LED for this task. I'm a bit shocked that the LED's are burning out. I can't remember having problems with LED lamps that I didn't abuse, they're normally pretty bulletproof.
-
There's actually a little more than just size compatability to pay attention to - dual color (I believe bi-color is the normal term) LEDs come in 2 wire or 3 wire, and 3 wire come in common anode or common cathode - and red/green are far more common than blue/yellow.
I believe these are 3 wire, but I couldn't tell you whether common anode or common cathode.
-
Yep, I assumed it would be easy to see if they're 2-wire or 3-wire. :) Of course, I'm still not convinced it's the LED that has gone bad...