D-Link Forums

The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: nm9p on April 17, 2011, 11:45:06 AM

Title: Lost Volume_1, BT and Web Folder still there?
Post by: nm9p on April 17, 2011, 11:45:06 AM
I have searched the forum and didn't find this one....
My DBS-323 has 2 WD 500B drives in Raid 1 and firmware 1.9
I have two users  and two groups.

Computers are a Vista Laptop and a Mepis (Debian) Desktop.

Recently my file folder "Volume_1" which has all my data dissappeared from the network listings on both computers.  The BT folder and web_page folder are still there.

I know that the information is still there, because my music files are still being served by the Itunes server, but I can't bring the man file list up on either computer.

I have done a restart on the DNS-323 and rebooted both computers and it is still missing on both computers.

I have checked the config on the 323 and both groups and users are correct.

What else should I check before doing a hard reset?  and what will I have to reprogram after a hard reset?

Thanks or any help...

Ken - NM9P




Title: Re: Lost Volume_1, BT and Web Folder still there?
Post by: RRE on April 20, 2011, 12:57:45 PM
Probably this one can help you:

ftp://files.dlink.com.au/products/DNS-323/REV_B/SetupGuides/Troubleshooting_-_Connecting_Vista_PC_to_network_drives.pdf

RRE
Title: Re: Lost Volume_1, BT and Web Folder still there?
Post by: jamieburchell on April 22, 2011, 11:55:01 AM
Log in to the NAS's web admin, and check that the "Volume_1" share is actually there.
Title: SOLVED! Re: Lost Volume_1, BT and Web Folder still there?
Post by: nm9p on April 29, 2011, 10:10:07 AM
SOLVED!  But I stil don't know what happened.

I loaded the latest 1.10 firmware.  And did a "toothpick" reset (the button on the back)
Then reentered User & sharing data.  It took about an hour for the Volume_1 to show up on my laptop.

Things are working fine now. 
I still would love to know why it dissapeared, but that mystery will remain unsolved.
I guess it was a static glitch.