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

jiggysmb · 2009-01-03 18:00:16

After upgarde to 1.06 my drives (RAID1) had a lot of activity throughout the night but by the next morning everything was functional. After powering the unit off for about 48 hours I turned it on and was able to access the device for about 5 minutes then went to see the square led was white and drive LEDs were pinkish. When I powered off the unit they flashed orange/pink for a few seconds then the unit turned off. Now this occurs each time I turn on the device?

Any suggestions would be greatly appreciated.

strobe · 2009-01-05 04:57:37

I upgraded to 1.06 today (RAID1) and had the same issue. I downgraded to 1.05, all seems well for now.

The DNS323 would be functioning for a few minutes and then drop my mapped network drive. I'd refresh view and it would reappear, then same thing a little later. Then the pink LEDs (both drives) appeared, leaving me with no connectivity. Re-booting the NAS would fix it for just a couple minutes, then back to pink. So I went back to 1.05. Don't really need the new features anyway. Good luck!

madpenguin · 2009-01-05 08:43:32

This thread jinxed me. Read it, continued to do work in ssh and 5 minutes later both drive LED's are pink. Network connectivity dropped off but then re-established.

I've had 1.06 for 5 days or so until this started happening...

Also getting weird behavior

Code:

patching file array.c
patching file array.h
patching file arrayfunc.c
patching file bashhist.c
patching file bashhist.h
patching file bashline.c
patching file builtins/common.c
patching file builtins/evalstring.c
patching file builtins/printf.def
patching file builtins/read.def
patching file builtins/set.def
patching file builtins/shopt.def
patching file config-bot.h
patching file config.h.in
patching file configure
patch: **** write error : No space left on device
root@dlink-******:/ffp/src/bash-3.2# pwd
/ffp/src/bash-3.2
root@dlink-******:/ffp/src/bash-3.2# ls /ffp
lrwxrwxrwx 1 root root 14 Dec 29 19:55 /ffp -> /mnt/HD_a2/ffp
root@dlink-******:/ffp/src/bash-3.2# df
Filesystem           1K-blocks      Used Available Use% Mounted on
%root%                    9911      9667         0 100% /
/dev/ram0                 9911      9667         0 100% /
/image.cfs                5760      5760         0 100% /sys/crfs
/dev/md0             958846504 510533508 448312996  54% /mnt/HD_a2
/dev/sda4               497861        10    497851   1% /mnt/HD_a4
/dev/sdb4               497861         7    497854   1% /mnt/HD_b4

WTF?

And this is after a reboot of the NAS

Code:

root@dlink-******:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
%root%                    9911      7463      1936  80% /
/dev/ram0                 9911      7463      1936  80% /
/image.cfs                5760      5760         0 100% /sys/crfs
/dev/md0             958846504 510533396 448313108  54% /mnt/HD_a2
/dev/sda4               497861        10    497851   1% /mnt/HD_a4
/dev/sdb4               497861         7    497854   1% /mnt/HD_b4

Last edited by madpenguin (2009-01-05 09:05:38)

devotee · 2009-01-05 13:04:17

Just a suggestion. When you get the "No space left on device" error and %root% and /dev/ram0 are at 100%, check where the space has been used (using du, for example). You should specially watch directories like /tmp and /var. When you're building from source, the compiler usually stores intermediate files in /tmp (i.e. it creates the object files in /tmp/<random filename> then moves it to <name>.o at the correct place). If the file is too big (more than 1936 blocks) or if there are "trash" files left behind you can get to a point where all space is used.

In the example you gave you were patching, not compiling. However I don't know what's the behaviour of patch or if it also uses /tmp as an intermediate storage location. It fails when patching "configure", is it a big file?

Anyway, if you encounter this problem again, try to locate the missing space before rebooting.

dpw2atox · 2009-01-06 14:48:12

my DNS323 also experienced the same issue. It started off working fine, then randomly the LEDs went pink and i lost my connection on both my laptop and my desktop, however i was still able to access the web interface.

I had to downgrade to the 1.05 firmware as well to resolve the issue. It sounds like a last min bug slipped through in 1.06, i guess i will wait for the next firmware release if no fix is found.

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

Announcement

#1 2009-01-03 18:00:16

Problem with 1.06, now disk LEDs are pink?

#2 2009-01-05 04:57:37

Re: Problem with 1.06, now disk LEDs are pink?

#3 2009-01-05 08:43:32

Re: Problem with 1.06, now disk LEDs are pink?

Code:

Code:

#4 2009-01-05 13:04:17

Re: Problem with 1.06, now disk LEDs are pink?

#5 2009-01-06 14:48:12

Re: Problem with 1.06, now disk LEDs are pink?

Board footer