• February 25, 2025, 01:53:36 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Problem configuring new DNS-323 - Drive not detected  (Read 4874 times)

craighann

  • Level 1 Member
  • *
  • Posts: 2
Problem configuring new DNS-323 - Drive not detected
« on: March 08, 2011, 12:55:14 PM »

Hi,

I've just bought a DNS-323 and I'm attempting to configure it.  I've got a Seagate ST31000340AS 1TB drive that I've put in, and I'm having a problem with it.

I've put the drive in the left hand bay, and the device is detecting it under STATUS\PHYSICAL DISK INFO. But, the wizard doesn't give me the option to format the drive, and under HARD DRIVE INFO it lists "Total Drive(s)" as 0.  As far as I'm aware the drive is good.

Can anyone help me out with this?

Regards,
Craig.
Logged

craighann

  • Level 1 Member
  • *
  • Posts: 2
Re: Problem configuring new DNS-323 - Drive not detected
« Reply #1 on: March 08, 2011, 01:05:19 PM »

I should add, I've upgraded the device to firmware 1.09 before I started configuring it.

Cheers,
Craig.
Logged

fordem

  • Level 10 Member
  • *****
  • Posts: 2168
Re: Problem configuring new DNS-323 - Drive not detected
« Reply #2 on: March 08, 2011, 01:54:28 PM »

So - you think the drive is good, but the DNS-323 doesn't.
So - if you're right the DNS-323 is defective or you have a bad connection between the drive and the unit, but if you're wrong ...
So - how do we find out who is right?

Either - you get another drive - or - you get another DNS-323 - or - you put the drive in a computer and test it - you have several options there.

Something to watch out for - some drives need to be sent a "turn on" signal before they will start the spindle motor - if I recall correctly the DNS-323 doesn't send one, there may be a jumper setting on the drive to "over ride" this - at least on my Maxtors, that's how it was.


Logged
RAID1 is for disk redundancy - NOT data backup - don't confuse the two.