DSM-G600, DNS-3xx and NSA-220 Hack Forum

Installed this morning and everything is fine for the moment !

djcult wrote:

US site:

ftp://ftp.dlink.com/Multimedia/dns323/F … re_108.zip

Installed this morning. Although installation went okay I'm now unable to log into the root account using telnet or WinSCP.

I've tried using both the PW I set for the root account and no password. I'm able to login okay using another account however that account won't allow me access to the volumes. With this account I'm caught in the BusyBox shell and cannot get out.

Any pointers would be appreciated.

Does the Vista gadget work with 1.08?
http://philwigglesworth.net/BlogEngine. … adget.aspx

Anything special regarding an existing fun plug 0.5 installation?

Anyone test that feature?
39. Normal to Raid1: Creates a new volume for the remaining disk space after creating the Raid partition.

The fanspeed command works with the 1.08 firmware as followed:

root@dlink:~# fanspeed w 1000
fanspeed - query and set the FAN Speed control

Usage: fanspeed [function]

Functions:
 h     high speed(7000rpm)
 l     low speed(2700rpm) 
 s     stop fan 
 g     get fan status
      the below option only support in a1 and b1 hardware board  
 w rpm,    set fan speed(rpm range:0 for stop, 2700~7000) 
root@dlink:~#

Look's like all fanspeed control skripts use the "fanspeed w" command. Any solution for hardware boards other than a1 or b1? Which other boards does exist?

i have been using the 1.08 firmware for a while, so far alright.

until today i put a new 1T seageat harddisk into the 2nd bay, it detects it, but no able to format it, had to downgrade back to 1.07 to format then upgraded it back.

I would rename the fun_plug file. Then reboot the nas. Then do the firmware upgrade, and then rename fun_plug file again to it's original.

I noticed in the readme for 1.08 that EXT3 is now supported.  Any reason I should rebuild my RAID-1 array and restore all data on an EXT3 raid array?  Also, I plan to disable fun_plug, reboot, upgrade the firmware from 1.06 to 1.08 and then re-enable fun_plug. Is that safe? (The Raid-1 array will be backed up to tape first).

Thanks... My first inclination regarding a change from EXT2 to EXT3 was to not mess with it.  The DNS has been rock solid running 2x 1TB in Raid-1 with EXT2 and I do have it on a UPS (although its not configured to auto-shutdown).  So I think for now just a simple upgrade to 1.08 is all I really need.

Last edited by jesbo (2010-03-14 22:49:59)

j.smith wrote:

The ext3 file system also provides considerable benefits when it comes to running file system checks (fsck) to check disk consistency and/or fix broken files.  The journal can be consulted for how the data should be and easily fixed - a fsck scan could take a lot less time compared to an ext2 filesystem.

A matter of opinion that I am not prepared to debate - let me ask you this however - in your average linux system, how often do you run a file system check?  When & why is this necessary?

I can't say with any proof, but I bet any performance gains you get from using ext2 over ext3 are quite likely completely nullified or insignificant when trying to copy files via SMB/CIFS.  I get about 10M/s if I'm lucky with jumbo frames on a GigE network, which isn't enough to stress the hdd's in the NAS.  Besides, if you use the NAS enough to make use of the potential performance benefits of ext2 (if there are any), chances are you're using the NAS in such a way that you would actually be safer using ext3.

Do the tests - I have, there is a distinct drop in throughput - and since I see no benefit to using ext3, why should I give up any performance at all.

On a completely unrelated topic of fw 1.08, it seems that they have finally encrypted (or done something) to the exported configuration data.  In 1.07, if you exported the configuration, it was a plain text file which could be edited.  In 1.08, it is now garbled binary data, no longer allowing us to tinker with the configuration data as easily.

Yes - it is now a binary file - it also prevents the noobs amongst us from screwing up the configuration as easily.

fordem wrote:

j.smith wrote:

On a completely unrelated topic of fw 1.08, it seems that they have finally encrypted (or done something) to the exported configuration data.  In 1.07, if you exported the configuration, it was a plain text file which could be edited.  In 1.08, it is now garbled binary data, no longer allowing us to tinker with the configuration data as easily.

Yes - it is now a binary file - it also prevents the noobs amongst us from screwing up the configuration as easily.

Open the configuration file in 7-zip.  This will give you access to all the configuration items inside.  See the attached screenshot.

Cheers,
DaveN

---

Attachments:
dns-323_New_CfgBackup.jpg, Size: 102,146 bytes, Downloads: 316

fordem wrote:

A matter of opinion that I am not prepared to debate - let me ask you this however - in your average linux system, how often do you run a file system check?  When & why is this necessary?

I don't use linux as a workstation, only as servers, so the answer is actually, quite few (hopefully), however I do set my systems to force a fsck after some mounts/uptime... though that does honestly rarely ever get triggered since the systems stay up for a long time.  However... because they are servers, and I KNOW that if I ever reboot them or something happens and they have to power up, that the time to run an fsck would be a long time (had it happen in the past... wondered why a server took like 1hr to come up).  So for that reason, I really prefer to have it as ext3 so that my boots aren't overly delayed due to fscks.

fordem wrote:

Do the tests - I have, there is a distinct drop in throughput - and since I see no benefit to using ext3, why should I give up any performance at all.

I noticed that you had mentioned that after I posted - I admit I haven't done any tests, though for me personally I don't mind giving up some performance to use ext3.  I don't do transfer-heavy stuff to my NAS... it's just a backup system for me.

Let me put it this way - without a backup, your data is at risk - you could lose just as easily removing & replacing the disk as you can leaving it in place.  You could decide not to upgrade until you have backed it up and then lose it 30 seconds later in a power failure.

Having said that - the risk of losing it during a firmware upgrade from 1.07 to 1.08 is, in my opinion, minimal, the firmware changes do not require a reformat and should not cause one to occur, so your data should be safe whether the upgrade is done with the disk in situ or removed - so the question becomes, (and I paraphrase Microsoft here ) what chance do you want to take today ...

a) Loss of data due to inactivity?
b) Loss of data caused by disk removal?
c) Loss of data caused by disk replacement?
d) Loss of data caused by a firmware upgrade with the disk in place?
e) Loss of data caused by a firmware upgrade with the disk removed?

In case you're curious. the order of those options is based on the length of the line, nothing more sinister - the risk is the same for all - in my opinion slim to nil - so, do you feel lucky?  Well - do ya?