Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[fordem]

I had upgraded from 1.05 to 1.06 with no hiccups - system was running a pair of 80GB drives in a RAID1 configuration and as these neared capacity, I decided to backup to another older NAS and run some tests with the new 1.06 firmware, before upgrading to 250GB drives.

The first step was to "fail" a drive - so I hot unplugged the right bay drive - within a matter of minutes I received the amber LED and email alerts, I then powered the system off and inserted a used, but clean (no partitions or data) 250GB drive and powered it back on.

I received a second email alert - this is new - and on logging in received the expected prompt to format the drive, accepting this prompt, brings up a second new screen, one that allows me to select auto or manual rebuilds, I selected manual and away we went - up to the dreaded 94% screen.

This is the first time I'm seeing this screen - I'm running IE7, popup blocker disabled, so we know that it's the unit hanging rather than the alert being blocked by the browser - this has to be considered a step backward, since I have not seen this screen personally in any of the firmwares, and this is a step I have done with every firmware since 1.02.

Hold down the power button till the unit goes off and then power it back on - no email this time - log in and again the prompt to format, again select manual rebuild (it actually says disable rebuild) - and again it hangs at 94%.

This time it's truly hung - holding down the power button does nothing I have to unplug the power - I power it up one more time - and this time, when I log in, I get no prompt to format, a quick check of the status screen and it shows me 21 minutes to complete the resync.

More on this later as my 1.06 exploration continues 

[fordem]

I spent part of the day playing around with the DNS-323 - in between other tasks.

Reset to defaults & reconfigured, formatted a 250 GB Seagate, no problems - put some data on it, added a second one and let it build a RAID1 array, did everything it said it would.

Enabled Auto-Rebuild in the RAID page and can't figure out what that does - see my other thread here.

Next up - reinstall my fun_plug, which only provides me with telnet access so I can do unattended shutdowns and poke around the interface - and run the QCheck endpoint for throughput tests.

Tomorrow - probably fool around with RAID0 & JBOD and maybe standard volumes - if I recall correctly, older firmwares didn't detect a drive failure with separate volumes, I have a feeling this one will - we'll soon see.

[fordem]

Something else I noticed

.lpd - the print spool folder is once again in HD_a2 - if my memory is right pre 1.04 it was in HD_a2 and 1.04 & 1.05 had it in HD_a4 - it was this change that broke the print server.

Anyone running the print server in 1.06?  Does it still work?

[Cliff]

print server works for me  in 1.06

Are you using local downloads in 1.06 (re: my other thread).

[fordem]

Cliff - I'm not using local downloads, I did use it briefly with an earlier firmware rev.

I just ran printer test page - so I found out for myself that the print server works and noticed that it did not even spin the drives up.  Maybe it depends on the size of the job.

[fordem]

This morning I'm trying to reformat the drives to have two separate, standard, volumes - three attempts, three reported format failures.

I can understand needing "new" drives when replacing a failed drive in a RAID1 array - but should a user attempting to switch from a RAID configuration to any other configuration really have to "replace" the disks?

OK - it looks like I can switch from a RAID1 to JBOD without a problem.

[fordem]

Two 250GB drives in a JBOD configuration - wrote data to them and, found it quite interesting, the data was written to the left side drive (based on the drive LEDs), I would have expected it to go to the right side first, but what do I know.

Hot unplugged the right drive - so the data is definitely still online - I got the expected amber LED and email.

Files on the remaining drive remain available, but no new data can be written - until such time as the unit is rebooted.

[fordem]

OK coming from JBOD, the unit let me reformat the disks for separate, standard volumes - and yes, it will report a disk failure - but only if the disk fails whilst the unit is running.

[badbob]

Just updated from 1.05 to 1.06 (UK user here) Flash ok but noticed fan is spinning much higher than usual- to the point will have to more to another room too loud for the HT room although on idle it seems quieter. System temp 109°F / 43°C, two Samsung 500GB.