D-Link Forums

The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: gugaucb on January 31, 2008, 05:46:29 AM

Title: Did anyone have any trouble after updating to 1.04
Post by: gugaucb on January 31, 2008, 05:46:29 AM
Did anyone have any trouble after updating to 1.04? Is it needed to format hds?  Are there troubles???
Title: Re: Update to 1.04
Post by: fordem on January 31, 2008, 06:56:26 AM
Yes - and - not if you're already using ext2.

Well - since the original poster has edited his question - I guess I need to reword my answer - so.

I've upgraded with no problems, I did not need to reformat, and I don't see any reason why it should be needed if you're already using ext2
Title: Re: Troubles after update to 1.04.
Post by: D-Link Multimedia on January 31, 2008, 10:07:01 AM
Did Somebody updated to 1.04? Is it needed to format hds?  Are there troubles???

The title of this thread is a little missleading. Should be more like "Did anyone have any trouble after updating to 1.04".
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: dicrouthamel on January 31, 2008, 06:33:09 PM
No problems here.  Everything working nicely.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: skypx on January 31, 2008, 07:15:37 PM
No trouble here. Working great!
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: DN on February 01, 2008, 02:57:52 AM
1.03 to 1.04:
- Lost network shares configuration (other config ok)
- Swedish characters () i file names are corrupt. Guess that Samba 3 & utf8 causes the change. New files created with Swedish characters work find when accessed from Vista, XP and Ubuntu.

Any ideas on how batch "rename" thousands of existing files that had Swedish characters in version 1.03??

Regards, Dan

Title: Re: Did anyone have any trouble after updating to 1.04
Post by: skypx on February 01, 2008, 01:07:17 PM
No issues. Working as it should.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: dicrouthamel on February 01, 2008, 05:09:21 PM
1.03 to 1.04:
- Lost network shares configuration (other config ok)
- Swedish characters () i file names are corrupt. Guess that Samba 3 & utf8 causes the change. New files created with Swedish characters work find when accessed from Vista, XP and Ubuntu.

Any ideas on how batch "rename" thousands of existing files that had Swedish characters in version 1.03??

Regards, Dan



Yup, I have to report that as well now - didn't see it at first.  I lost my setup of network share configuration.  I had things setup specifically for me to acess (everything), and separate access for other family members.  It turned out that after updating to 1.04, it was configured for R/W access to everything for everyone!!
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Banshee1971 on February 02, 2008, 06:33:30 AM
It fix something with Vista :
- It was impossible to start an EXE file from the NAS under Vista
- Everytime i open an Excel file from the NAS, and click on "record", it always ask me if i want to overwrite or create a backup file

now, it's fixed ! 

The only thing that still don't know if it's working properly, is the DOWNLOAD SCHEDULER. I have nothing that tell me the schedule work's great, and if something goes wrong, nothing to help me find what's wrong (password, username, wrong origin or destination,.. name of the file copied, date,...)

But for now, it's a good start.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Banshee1971 on February 03, 2008, 10:58:17 AM

Printserver not working anymore.
I can't print anything under WinXP or Vista.
I re-install the network printer, reboot the NAS, reset to factory default, reboot the printer... nothing works at all.

The document seem to go to the NAS, but the printer do nothing !
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Banshee1971 on February 03, 2008, 01:59:14 PM
I downgrade to V1.03, and it solve the problems.

So their is something in V1.04 that broke something. It fix problems, but add new one also !
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: rcblackwell on February 03, 2008, 02:00:22 PM
It fix something with Vista :
- It was impossible to start an EXE file from the NAS under Vista
now, it's fixed ! 

I'm still having this problem. Which version of Windows and how are your NAS groups configured?

Bob Blackwell
Pickering, ON
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Banshee1971 on February 03, 2008, 03:06:34 PM
Windows XP : no problems. V1.03 and 1.04 works OK to start EXE file direct from the NAS.
Windows Vista Familly edition Premium : Cannot start EXE from the NAS (V1.03), but wit Version 1.04, it's finaly working.

I have both version in French. I connect using this command line (it's a basic Windows command line)

net use m: \\YOURNASNAME\Volume_xxx\documents /user:yourusername yourepassword /persistent:yes

YOURNASNAME = The name of you're nas, visible under my network place. You must use the same WORKGROUP for all device (computer, NAS,..)
Volume_xxx = The DLINK Volume. Usualy Volume_1 or Volume_2
\Documents : The folder where you want to start
yourusername = the username you create on the NAS. This username must have access to the desire folder.
after the name = you put the password
/persistent:yes = that mean after you type this command, it will keep the drive letter and try to login again after reboot. If you choose "no", the driveletter diseaper after a reboot.


Note : with Version 1.04, i was unable to use the NAS NAME, so i replace the NASNAME with the IP Adresse of the NAS.

Note to all : i use a DHCP to fix the NAS adress with the MAC adress of the NAS. So it's the same IP all the time. But, i also try to manually enter the IP adress, with better result.

Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Rodent on February 04, 2008, 01:33:14 AM
After I updated the firmware from v1.03 to v1.04 I lost all of the network shares and the default volume_1 share with full access to all users was created, I only had three shares so I just re-created them and they are working fine.

Thanks
Rodney

1.03 to 1.04:
- Lost network shares configuration (other config ok)
- Swedish characters () i file names are corrupt. Guess that Samba 3 & utf8 causes the change. New files created with Swedish characters work find when accessed from Vista, XP and Ubuntu.

Any ideas on how batch "rename" thousands of existing files that had Swedish characters in version 1.03??

Regards, Dan


Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Rodent on February 04, 2008, 01:44:32 PM
Here is saying thanks for adding Time Zone for (GMT+09:30) Adelaide,Darwin good to see, now if Daylight Saving Time could be added so that we could use the newly added Time Zones that would be even better.

Does not matter what NTP Server I use the time is out 1 hour because of Daylight Savings.

Anyone have any solution to this problem ???

Thanks
Rodney
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Banshee1971 on February 05, 2008, 05:29:26 AM


After returning to V1.03, it "scrap" my second drive (integrity). The Download Scheduler was not able to copy file from Drive_1 to Drive_2 correctly. And the result was a directory structure impossible to delete.

So i shutdown the device, remove the GOOD drive, restart the device, go on the RAID configuration utility to format the Drive.
After i reboot the unit to see if the drive works fine, shutdown agait. Re-slot the Drive_1, and start-it again...

Funny, Drive_2 are now Called Drive_1 (the drive # 2 are on bay # 2), and Drive_1 are called Drive_2.

So, i shutdown again, swap Drive on bay # 2, to bay # 1. Restart the NAS ... it's ok.. Drive_1 are on Bay # 1 ... I shut down, re-slot the other drive on Bay#2, and reboot... The drive on bay # 2 are called Drive_2 ...


After i swap Drive_1 with Drive_2 on the bay, i copy all data from Drive_2 to Drive_1 (because i want to normalized my installation like all my login script), and it's working again.


My experience with V1.04 ? .... a mess. Someone did'nt do his works correctly.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: fordem on February 05, 2008, 07:50:18 AM
So - you've told us what problems you had downgrading from 1.04 back to 1.03 - you haven't told us why you felt the need to revert to the earlier firmware, other than

Quote
My experience with V1.04 ? .... a mess. Someone did'nt do his works correctly.

which doesn't tell us why you feel that way.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Banshee1971 on February 05, 2008, 11:49:33 AM
So - you've told us what problems you had downgrading from 1.04 back to 1.03 - you haven't told us why you felt the need to revert to the earlier firmware, other than

which doesn't tell us why you feel that way.

I already report all troubles, fiew thred up (look all the message on this thred, and you will find the troubles i report). But if you did'nt find the info, here they are :
After upgrade from V1.03 to V1.04 :
- Lost PrintServer. Cannot use it anymore. Try all different way, i can see the printer, but it not working. Try reboot, reset, factory default, nothing. Even under XP or Vista
- Lost DNS support. I cannot contact the NAS using his DNS name. It won't respond. But i can contact it using the IP (this is not a major issue for me).

I give here the result of Downgrading for only 1 reason : check if what i lost are working again after backtrack the firmware version.
Result : Printer working again, and DNS also.

of course, i need to recreate the sharing permission for file access, and i lost control of one HARDDRIVE (force to format the drive), but it's working again.

If i was'nt lost the printer the first time, i will keep the V1.04 ... and hopping the V1.05 solve this issue, and the Scheduler issue.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: gugaucb on February 06, 2008, 11:53:29 AM
I updated my unit and I had only two troubles. First, I lose my network shares configuration and second the unit wake up some times although nobody was accessing. Did anyone know why happend this situation?

The refresh options  of UPnP and iTunes is disable.

Regards,
Gustavo
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: ECF on February 06, 2008, 04:13:36 PM
If you are using the DNS-323 as a print server you may have print jobs in the queue. Try clearing the print job queue. This feature is added in firmware 1.04 the "Clear print queue(s)" button is located in the status tab of the web configuration.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: rcblackwell on February 06, 2008, 05:01:00 PM
net use m: \\YOURNASNAME\Volume_xxx\documents /user:yourusername yourepassword /persistent:yes

Thanks for the information. unfortunately it didn't solve my problem. By chance are the user rights on your NAS established at the root of the drive (Volume_1) or is it up a level or two. If at the root, would you be willing to move it up a level or two and report on your findings; ability to run *.exe's?

Bob Blackwell
Pickering, ON
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Banshee1971 on February 07, 2008, 01:22:13 PM
The right are at the root for my config. From V1.03 to V1.04, the ability to Run EXE are fixed only in V1.04. But it seem to be Vista related. I don't remember to have seen that problems under XP.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: rcblackwell on February 10, 2008, 10:56:23 AM
The right are at the root for my config. From V1.03 to V1.04, the ability to Run EXE are fixed only in V1.04. But it seem to be Vista related. I don't remember to have seen that problems under XP.


I concur; problem doesn't exist under XP regardless of which firmware version is in use.

The NAS has been updated to 1.04. Yesterday I reformatted the drives (RAID1) and rebuilt the file structure. This action was necessary due to a Directory and 1.5 GB of files that I couldn't gain control over and delete ???

After all this I'm still unable to run *.exe's from the NAS. Like you I suspect Vista however I don't know where to turn or what yo adjust. Any ideas?

Bob Blackwell
Pickering, ON
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Banshee1971 on February 11, 2008, 04:23:23 AM
 :o
 I don't want to effraid you ... but i'm think we will need to wait until V1.05 or V1.06 before they fix what they broke...

And if we are lucky, they won't broke more thing..

For now, i'm a little deceived of this product. I miss my old buffalo, but, i confort my self because the DNS-323 have the possibility to rapidly change the hardrive (something the afordable buffalo product can't do for now).
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: gugaucb on February 11, 2008, 07:58:44 AM
Yesterday, the UPnP server stopped work in my unit. I need reboot the unit to came back work.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Banshee1971 on February 11, 2008, 09:27:46 AM
If you are using the DNS-323 as a print server you may have print jobs in the queue. Try clearing the print job queue. This feature is added in firmware 1.04 the "Clear print queue(s)" button is located in the status tab of the web configuration.

sorry. Not working. Even if i reset to factory default, or dance near the unit.

It seem that i'm not the only one who complain about this issue.
Did someone test the Printserver before release V1.04 ? And what was their test ?
I'm not using a multifonction printer, so i'm not suppose to have any problems related to my printer.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: fordem on February 11, 2008, 01:56:37 PM
For what it's worth - I've used the print server in both 1.03 and 1.04 - with no problems other than the occasional need to clear the queue.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Banshee1971 on February 12, 2008, 06:03:30 AM
For what it's worth - I've used the print server in both 1.03 and 1.04 - with no problems other than the occasional need to clear the queue.

What model/brand of Printer you are using ? i'm using a Dell 1100 Laser Printer. And the connexion to the Printer are very slow, with no result at the end (with V1.04). I test the Clear Print Job, reset after the NAS (to factory default), reboot it, erase the printer from my Laptop (winXp) and my desktop (Vista) and re-install it. Nothing... exept i lost time try anything.
I also try to map it from "network connxion", and also by connect a TCPIP port ...
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Tipstaff on February 23, 2008, 03:59:04 PM
Same problems with the print server. Prior to updating to 1.04 I was able to print to my Samsung ML-1520 with no problems (except for the clearing of the print queue issue, which I could get around). Now I can't print. Windows sees the printer attached to the NAS, and as well the NAS sees the printer in it's Status page. However, when I try to print to it I immediately get an error. I've tried rebooting the NAS, tried clearing the print queue, and tried reinstalling the drivers on the systems. Nothing works. Bye bye print server.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: zehninguem on February 24, 2008, 01:41:40 PM
Hey guys, are you asking DLink to solve the printer server problem???

Just a joke, I was waiting someone to put the blame at MS since Wndows can not print from DNS-323 with FW1.4. Or do I need a Mac?

Now being serious. Please guys at DLink, can we have FW 1.5 with a better Samba (printer server) and well tested before realease? Clear the queue is just a turn around and does not work with the 5 different printers that I tested.

Thanks
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: fordem on February 24, 2008, 04:45:12 PM
Hey guys, are you asking DLink to solve the printer server problem???

Just a joke, I was exploitive deleted someone to put the blame at MS since Wndows can not print from DNS-323 with FW1.4. Or do I need a Mac?

Now being serious. Please guys at DLink, can we have FW 1.5 with a better Samba (printer server) and well tested before realease? Clear the queue is just a turn around and does not work with the 5 different printers that I tested.

Thanks

Look four posts above yours - I have no problem printing from Windows (XP) using either 1.03 or 1.04
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: zehninguem on February 24, 2008, 07:52:54 PM
Soory forbem but looks like you are the only one, plz see all other posts of lots o people.\I'm glad for you but DLink should provide us something that work for all other users that had printers working with 1.3
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: fordem on February 25, 2008, 04:19:32 AM
Try this

a) Install the printer directly connected to your Windows system, make sure it works
b) Disconnect the printer from the Windows system and connect it to the DNS-323
c) Open the printer properties, select the ports tab, then add a new local port, name it \\<DNS-323_ip_address>\lp

Try printing to it - what happens?
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: zehninguem on February 25, 2008, 06:52:21 AM
I will give it a try tonight and let you know.

Thanks a lot
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: fordem on February 25, 2008, 03:11:32 PM
Just in case anyone is interested - I borrowed my son's laptop (Vista Business), and using the instructions I provided above, I have been able to print to my Samsung ML1210 through the DNS-323 with firmware v1.04.

I have been able to print to a printer attached to the DNS-323 running firmware 1.04, from both XP Professional & Vista Business
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: riopato on March 07, 2008, 06:12:04 PM
Any files I add now to my ftp folder can no longer be accessed outside my network. Keep getting an error saying that I don't have the required permissions. I can see the folders but I can't download anything inside it. I'm afraid to reconfigure the ftp server for fear that I will not be able to access the rest of my files! >:(
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: mbelli on March 11, 2008, 11:55:37 PM

I had my FTP server running great until I installed 1.04, then had some issues regarding file and folder permissions on the FTP server.

I reset up the server from scratch but still was getting weird stuff from IE or Firefox using ftp://myIP#. After two hours of scratching my head I remember that I didn't reformat my drives because from firmware 1.03 to this, I read it wasn't necessary. I decided to reformat the drives after having exhausted every other solution to the problem and was convinced that I'd have to go back to 1.03. BUT AFTER A REFORMAT -- all was perfect again.

BTW, I find 1.04 much better, it seems snappier and the drives on the DNS-323 are more responsive!!!! Example, when writing to a drive on the DNS-323 (copying a file) if I tried to change the name of a folder on the same drive, the DNS-323 would stall and take like 20 seconds to make the name change (due to the fact stuff was being copied to the drive). Now there's no stalling and the name change happens almost instantly.

Title: Re: Did anyone have any trouble after updating to 1.04
Post by: mcalautt on April 02, 2008, 01:32:34 PM
I am currently on Firmware Version: 1.03.
Dlinks site claims u need to move all your data and reformat the drives after the update.
I cant do that. thats the reason i bought the 323 for more space. I dont have any place to move the data to

I have it as a raid1 config but im not sure how my drives are formated. I assume they are not ext2
because I have it mapped to a linux machine  as CIFS.  I have a linux machine and 2 vista machines attached to my dns-323

can I just update to 1.04 without reformatting the drives ?

Title: Re: Did anyone have any trouble after updating to 1.04
Post by: riopato on April 02, 2008, 05:21:04 PM
I had my FTP server running great until I installed 1.04, then had some issues regarding file and folder permissions on the FTP server.

I reset up the server from scratch but still was getting weird stuff from IE or Firefox using ftp://myIP#. After two hours of scratching my head I remember that I didn't reformat my drives because from firmware 1.03 to this, I read it wasn't necessary. I decided to reformat the drives after having exhausted every other solution to the problem and was convinced that I'd have to go back to 1.03. BUT AFTER A REFORMAT -- all was perfect again.

BTW, I find 1.04 much better, it seems snappier and the drives on the DNS-323 are more responsive!!!! Example, when writing to a drive on the DNS-323 (copying a file) if I tried to change the name of a folder on the same drive, the DNS-323 would stall and take like 20 seconds to make the name change (due to the fact stuff was being copied to the drive). Now there's no stalling and the name change happens almost instantly.



I've notice an improvement in file transfers also and streaming via browser as well. If anything there has been an increase in performance especially after vistas sp1 update.
What I had to do to get around the permissions issue was to reset up the users and group section and reactivate the ftp server with the new settings. Looks like users has to have a group now in order for the ftp to work. I assume this has something to do with the new folder hierarchy. I also had to change the name of my dns since it doesn't accept numbers as the first character in the name???
There was still some random files that had permission issues but the weird thing was all I had to do was copy the files either on my computer or on the dns itself. Luckily I still had space to do this on my dns which is the fastest way to do this. For some reason the permissions were corrected and the ftp is working the same way since firmware 1.03 but now with improved transfer speeds! Also I turned off some of the vista related features on the dns but don't know if that has any affect to the way it works.
I think the permissions issues is due to the way the dns works with vista since certain security settings don't even exisits with xp??? Anyone out there is only using win xp and the dns-323 and has this trouble?
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: D-Link Multimedia on April 02, 2008, 07:31:23 PM
I am currently on Firmware Version: 1.03.
Dlinks site claims u need to move all your data and reformat the drives after the update.
I cant do that. thats the reason i bought the 323 for more space. I dont have any place to move the data to

I have it as a raid1 config but im not sure how my drives are formated. I assume they are not ext2
because I have it mapped to a linux machine  as CIFS.  I have a linux machine and 2 vista machines attached to my dns-323

can I just update to 1.04 without reformatting the drives ?



I believe you have misread the quote on the DNS-323 support site. We do not require you to format your drives UNLESS you are upgrading from 1.00 or 1.01 firmware. Upgrading from 1.03 to 1.04 will not require you to format however you should always keep backups of your most important data in multiple locations.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: fordem on April 02, 2008, 08:32:31 PM
I am currently on Firmware Version: 1.03.
Dlinks site claims u need to move all your data and reformat the drives after the update.
I cant do that. thats the reason i bought the 323 for more space. I dont have any place to move the data to

I have it as a raid1 config but im not sure how my drives are formated. I assume they are not ext2
because I have it mapped to a linux machine  as CIFS.  I have a linux machine and 2 vista machines attached to my dns-323

can I just update to 1.04 without reformatting the drives ?



To answer your question - you can upgrade to 1.04 without formatting the drives IF they were originally formatted ext2 - you may not get the benefit of unicode, but you may not need it.

Now - what your drives are mapped as has no relevance to how they are formatted - they ARE formatted either ext2 or ext3, they are exported as CIFS, so they are mapped as CIFS

Last - you don't have the space to move your data, that's why you bought the DNS-323 - consider this - you have no backup (RAID1 is not a backup).  Place a value on that data - $100, $200, $300?  How much will it cost you for the additional space?  It's your data, it's your money.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: mcalautt on April 03, 2008, 04:58:29 PM
I actually use the raid1 323 as my backup.

so I backup my laptop, wifes laptop and my linux machine to the 323.

the raid1 is for obvious reasons.

I cant remember if I used ext2 or 3.
is there anyway to determine ?

thanks for the help
mike
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: mig on April 04, 2008, 12:22:32 PM
mcalautt, just curious, what is the "obvious reasons" you run RAID1 on the
storage device you place your backups?
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Fatman on April 04, 2008, 01:13:30 PM
Because raid 1 offers redundancy in case of a failed drive one would assume.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: fordem on April 04, 2008, 04:24:49 PM
Because raid 1 offers redundancy in case of a failed drive one would assume.

So - what we have are redundant backups eh?  Personally, I would rather have the redundancy on the primary storage
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Fatman on April 04, 2008, 04:38:04 PM
in an ideal world either drives would never fail and would last till the end of time or we would have redundant backups in every corner of the globe.

It just depends on what your data is worth to you.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: fordem on April 04, 2008, 08:43:21 PM
You just lowered my opinion of D-Link a notch there - redundant data & redundant disks are totally different things

The most common reason for the use of redundant disks is to reduce and hopefully eliminate the impact of the down time caused by disk failure - if you do not have redundant disks and your system experiences a disk failure, processing comes to a halt until such time as the failed disk can be replaced and the data restored - this "halted processing" is what's known as down time, and in some cases can be measured literally in terms of $x/minute.  If the system is fitted with redundant disks, a disk failure will usually not cause a shutdown - in some cases corrective action can be taken and the disk replaced without shutting the system down, and in others, the required down time can be scheduled for a less critical time.

Let us now specifically consider disk failure in a backup system - the data in a backup system is required only in case of a problem within the primary storage, this problem can take the form of a disk failure or it can be deletion or corruption of the data - for a failed disk in a backup system to have an impact, the failure must occur within a specific timeframe of a problem also occurring with the primary storage - it's not that this is impossible, but, one needs to ask how likely is it to happen - what is the probability?
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Fatman on April 07, 2008, 08:58:07 AM
Please for the love of whatever being you seek for guidance do not confuse my last post as a lack of understanding.

My posts are meant for every user here, not just for the ones who have a bone to pick.  I was answering a question from another user, a simple question that did not require any deliberation.  Unfortunately it drew some.  I responded simply to your quip as I felt that we would both understand what I was trying to get across without the need for long winded posts that wouldn't assist anyone who didn't already know what we are talking about.

The type of backup you are referring to wouldn't be put into a network storage device anyhow, to do so invites risk.  We are not talking about a literal backup here.

We are talking about a home user who wants to have a place to store communal files of importance, this is his primary storage.

And most of all if this was his an off site backup for a well funded entity with crucial data, the type of entity which makes real backups and sweats down time we would not be discussing a DNS-323.

Now that I have that off my chest I am going to ask that we get at most 1 more rebuttal on this subject and then move on, to something like, i don't know, the thread at hand.

P.S. A situation no matter how improbable may be worth guarding against, as we both said before, it is a matter of what your data is worth to you.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: fordem on April 07, 2008, 05:09:21 PM
Fatman - whilst I understand where you're coming from, the simple truth is that I see too many statements, very similar to that made by mcalautt - folks who have their own concept of what RAID is all about - to jest about it.  Too often I see this product, and others like it, condemned by people whose expectations are/were incorrectly set.

For me the strange thing was that mig's post mirrored my thoughts when I read mcalautt's post, almost word for word - when I read it, I was stunned - I had actually typed those words, or words very similar to them, before making a conscious decision not to respond, and it took me more than a few seconds to realise it was not my post that I was reading.

By the way - I think you need to recognise that not every entity that makes real backups and sweats down time is well funded - there is a many a small business with data stored on a shared drive in a desktop, that can benefit from a reliable NAS with mirrored drives - that is the reason I went out and purchased the DNS- 323 when it first hit the market - with the hope of introducing it to my SMB clients, one and two man shops, where down time does make a difference.  Unfortunately it is taking a little longer than I care for to mature, and I can only hope that once it matures that D-Link does not simply phase it out - for all it's quirks (which are mostly, at least for me, understandable - given it's linux base), it's a fine product.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Fatman on April 08, 2008, 08:32:07 AM
Perhaps I was also too hasty, I see enough questions worded like mig's that require a simple answer that I guess I started grouping all questions that way.  My apologies to mig for this as I may have assumed that the simple literal question was the correct one because I read every last post made in these forums so they tend to get the breakneck speed read.

And fordem, I do understand the need for less than well funded companies to make backups, I was working from the assumption that for your data to be valuable to it implies that it is going to receive an investment proportional to it's value.  This assumption is flat false in any real life scenario for a number of reasons.  I was also taking everything to either the 0th or the nth power and not stopping in between.  I understand perfectly well how important a product like the DNS-323 can be in an SMB environment, that is a major part of why I am here.  In other words I apologize if we got off on the wrong foot.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: William on April 12, 2008, 03:21:48 AM
Yes, I have also lost the print server function after updating and
the clearing the queue doesnt help. The other problem that
I was looking for a fix with this update was the disk spindown problem.
It didnt fix it so I had to funplug the NAS to keep the disk down
when idle. The fancontrol patch from Fonz is very usable too and works
fine. Now the NAS is almost noiseless when idle. Hope that those
bugs from firmware will be corrected to next version so we dont
have to do hacking to get it work like it should.

W
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: fordem on April 12, 2008, 06:15:51 AM
If you haven't fixed the print server problem yet, head over to the other forum, there's a solution posted over there that does require the use of fun_plug
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: William on April 12, 2008, 12:31:37 PM
If you haven't fixed the print server problem yet, head over to the other forum, there's a solution posted over there that does require the use of fun_plug

I havent found that..? Only clearing buffer solution and it doesnt help in my case.

W
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: Scay on April 28, 2008, 03:15:10 PM
Well, can't really comment on introduced problems since I don't have any real life experience on 1.03. What I can comment on is the fact that my DNS-323 falls back to degraded mode every now and then for no obvious reason forcing me to re-format or use funplug/telnet to re-insert the "faulty" drive into the raid-1-array. (A process that takes about 3 hours on my 2x Seagate 7200.11 1TB discs)
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: ECF on April 29, 2008, 09:27:34 AM
D-Link will be releasing new firmware to address the print server functionality issue. I am very sorry for the inconvenience.
Title: Re: Did anyone have any trouble after updating to 1.04
Post by: tsourbier on May 09, 2008, 04:12:18 PM
I upgraded last night from 1.03 to 1.04. My 323 is configured in Raid-1 and a few minutes after the update the light of the right drive went "pink" and the status on the web showed as downgraded :-[ :-[ Rebooting the unit led to the same result (a few minutes all blue, then the light turning pink). It seems that I'm faced with the same issue as Scay.

The drive are fairly new (November) and both the same : Samsung Spinpoint T166 S-ATA - 500 Go - 16 Mo drives.

Any chance the new firmware could also resolve this issue?

Cheers,

T.

Title: Re: Did anyone have any trouble after updating to 1.04
Post by: ECF on May 09, 2008, 04:39:09 PM
I am very sorry but I do not yet have the release notes for firmware 1.05. This pink LED incident seems to happen only using RAID1 after a firmware update in the few I have seen. If you are getting a pink LED I would recommend reverting back to firmware 1.03 or backup your data and reformat in RAID1.