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

fordem · 2009-01-10 03:36:58

When the unit hibernates the LED behind the Logo/power button goes dim - so by looking at the front panel you can see when the unit wakes up and typically you can hear the disks spin backup - sort of like a very small jet engine starting.

frodo · 2009-01-10 03:53:49

Use fun_plug and syslog. Though I put the logs on a USB disk not to wake up the disks ;-)

Jan 10 02:00:01 Nasse cron.notice crond[1845]: USER root pid 20030 cmd /usr/sbin/offl_chk two &
Jan 10 02:00:01 Nasse cron.notice crond[1845]: USER root pid 20032 cmd /usr/sbin/getdhcp&
Jan 10 02:01:03 Nasse user.warn kernel:
Jan 10 02:01:03 Nasse user.warn kernel: #######################################
Jan 10 02:01:03 Nasse user.warn kernel: # HD0 awake now ! #
Jan 10 02:01:03 Nasse user.warn kernel: #######################################
Jan 10 02:01:10 Nasse user.warn kernel:
Jan 10 02:01:10 Nasse user.warn kernel: #######################################
Jan 10 02:01:10 Nasse user.warn kernel: # HD1 awake now ! #
Jan 10 02:01:10 Nasse user.warn kernel: #######################################
Jan 10 02:10:37 Nasse user.warn kernel:
Jan 10 02:10:37 Nasse user.warn kernel: ***************************************
Jan 10 02:10:37 Nasse user.warn kernel: * HD0 stand by now! *
Jan 10 02:10:37 Nasse user.warn kernel: ***************************************
Jan 10 02:10:37 Nasse user.warn kernel:
Jan 10 02:10:37 Nasse user.warn kernel: ***************************************
Jan 10 02:10:37 Nasse user.warn kernel: * HD1 stand by now! *
Jan 10 02:10:37 Nasse user.warn kernel: ***************************************

dudu_georgescu · 2009-01-10 05:32:19

fordem wrote:
When the unit hibernates the LED behind the Logo/power button goes dim - so by looking at the front panel you can see when the unit wakes up and typically you can hear the disks spin backup - sort of like a very small jet engine starting.

That's what I was thinking (the noise at least) but I had to check to make sure For you how often are the HDDs awaken?

fordem · 2009-01-10 23:21:16

Only when I access them.

bogd · 2009-01-11 11:21:39

I just upgraded to firmware version 1.06 (yesterday night ), and the first thing I noticed was that "something" kept accessing my HDDs. The HDD LEDs kept blinking even after removing the ethernet cable, so it was definitely something in the firmware that caused it.

I turned the NAS off and back on (using the power button at the front), and so far it seems to have stopped. The HDDs went to sleep after 15 minutes, woke up in the early morning (when my PC started its backup to the NAS), and went back to sleep after another 15 minutes. The NAS has cooled down, so even the fan has stopped now

I'm using the DNS-323 with 2 Seagate 7200.11 1TB HDDs in RAID1.

[ LE: I just left for a couple of hours, and upon my return I found the NAS warm, and the HDDs spinning. No disk accesses this time - just idle HDD spinning.

I'm seriously considering downgrading to 1.05 until this problem is fixed... ]

Last edited by bogd (2009-01-11 12:24:01)

Dex · 2009-01-14 07:28:30

Hate to state the obvious - but have you guys tried logging onto the STATUS menu and hitting the "clear print queue(s) button. Nobody has mentioned that here although it's in the Known Issues post. Worked for me.

fordem · 2009-01-14 14:46:31

Dex wrote:
Hate to state the obvious - but have you guys tried logging onto the STATUS menu and hitting the "clear print queue(s) button. Nobody has mentioned that here although it's in the Known Issues post. Worked for me.

Just stating the obvious

Either you didn't read my earlier post (#22) or you didn't understand what it said.

fordem wrote:
... that go down for 2 mins every 10 mins and then spin back up is reminescent of the old "uncleared print job in the spool file issue" where the unit would try to spool up every 10 minutes until you cleared the spool file, so reformatting the drives, which would have deleted anything in the \.lpd folder, would have exactly the same effect.

frodo · 2009-01-14 22:29:02

fordem do you have the offl_chk cron entry?

fordem · 2009-01-15 00:27:50

frodo wrote:
fordem do you have the offl_chk cron entry?

Linux noob here - if you tell me how to check for it, I'll be happy to. I'm not running ffp, but I do have a minimal fun_plug that gives me telnet access.

atx32 · 2009-01-15 00:51:48

frodo wrote:
fordem do you have the offl_chk cron entry?

As another data point, I do have that as a cron entry (and can see it execute in the syslog too) and I have no issue with disks spinning up periodically.

Dex · 2009-01-15 03:02:19

Hate to state the obvious - but have you guys tried logging onto the STATUS menu and hitting the "clear print queue(s) button. Nobody has mentioned that here although it's in the Known Issues post. Worked for me.

Sorry fordem, I did read your post and it did help me to solve the problem. But there was no 10 min or 2 mins involved. The disks would power down at whatever interval I had set and then power up in around 3-30 secs later.

You must appreciate that many newbies like me search for solutions in these posts and although your post was helpfull in getting there, many others may not have made it.

frodo · 2009-01-15 10:56:23

fordem wrote:
frodo wrote:
fordem do you have the offl_chk cron entry?
Linux noob here - if you tell me how to check for it, I'll be happy to. I'm not running ffp, but I do have a minimal fun_plug that gives me telnet access.

crontab -l

should give you the answer.

frodo · 2009-01-15 11:00:02

atx32 wrote:
frodo wrote:
fordem do you have the offl_chk cron entry?
As another data point, I do have that as a cron entry (and can see it execute in the syslog too) and I have no issue with disks spinning up periodically.

Do you write your logs to a USB disk?

fordem · 2009-01-15 15:45:31

frodo wrote:
fordem wrote:
frodo wrote:
fordem do you have the offl_chk cron entry?
Linux noob here - if you tell me how to check for it, I'll be happy to. I'm not running ffp, but I do have a minimal fun_plug that gives me telnet access.
crontab -l

should give you the answer.

# crontab -l

32 2 * * * /usr/sbin/rtc -s
30 2 2 * * /usr/sbin/rtc -c
59 1 * * */usr/sbin/daylight &
*/10 * * * * /usr/sbin/offl_chk two &
*/60 * * * * /usr/sbin/getdhcp&
# #

Now - how about an explanation of what I'm doing and seeing ...

as far as I can tell crontab is a table of what the "cron" daemon is going to do, and cron is used to run a specified task at a specified time, but that's the extent of my knowledge - why would my DNS-323 be running daylight - presumably some daylight saving time thing - if I have it disabled (we don't use DST where I am), and likewise, why run getdhcp on a unit configured for static addressing?

Last edited by fordem (2009-01-15 15:47:41)

atx32 · 2009-01-15 18:14:07

frodo wrote:
atx32 wrote:
As another data point, I do have that as a cron entry (and can see it execute in the syslog too) and I have no issue with disks spinning up periodically.
Do you write your logs to a USB disk?

No, I do not have a USB disk set up at all. Syslogd writes to the default /var/log/messages file.

frodo · 2009-01-15 18:27:28

fordem wrote:
# crontab -l

32 2 * * * /usr/sbin/rtc -s
30 2 2 * * /usr/sbin/rtc -c
59 1 * * */usr/sbin/daylight &
*/10 * * * * /usr/sbin/offl_chk two &
*/60 * * * * /usr/sbin/getdhcp&
# #

Now - how about an explanation of what I'm doing and seeing ...

as far as I can tell crontab is a table of what the "cron" daemon is going to do, and cron is used to run a specified task at a specified time, but that's the extent of my knowledge - why would my DNS-323 be running daylight - presumably some daylight saving time thing - if I have it disabled (we don't use DST where I am), and likewise, why run getdhcp on a unit configured for static addressing?

Strange. I only have one line now since I removed dhcp. Though I had to run the wizard to make it stick...
I disabled time sync and instead run ntp from fun_plug. Same goes for daylight savings. That probably explains why I only have one?!

# crontab -l
*/10 * * * * /usr/sbin/offl_chk two &

Anyway here is some info:
# /usr/sbin/rtc -h
rtc - query and set the hardware clock (RTC)

Usage: rtc [function]

Functions:
-h show this help
-r read RTC time and print it
-w read time from system and write to rtc(SYS -> RTC)
-s read time from rtc and write to sys(RTC -> SYS)
-c increase RTC 227 sec. each month
-d set rtc and system time to default time 2005/01/01 00:00:00

frodo · 2009-01-15 18:28:28

atx32 wrote:
frodo wrote:
atx32 wrote:
As another data point, I do have that as a cron entry (and can see it execute in the syslog too) and I have no issue with disks spinning up periodically.
Do you write your logs to a USB disk?
No, I do not have a USB disk set up at all. Syslogd writes to the default /var/log/messages file.

That is a very small fs so it could easily be filled.

danzig777 · 2009-01-18 12:29:22

I'm also having the trouble of the drives keep spinning after upgrading to 1.06 from 1.03. I have two Samsumg drives in a Raid 1 configuration.

I ran offln_chk under strace and the interesting bits are here:

ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B38400 opost isig icanon echo ...}) = 0
stat("/tmp/formatting", 0xbed1cc14) = -1 ENOENT (No such file or directory)
brk(0) = 0x13000
brk(0x14000) = 0x14000
open("/web/sib.conf", O_RDONLY) = 6
ioctl(6, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbed1cb6c) = -1 ENOTTY (Inappropriate ioctl for device)
brk(0x15000) = 0x15000
read(6, "CF-SYS-MODEL-STR = \"dlink-ED5F43"..., 4096) = 1230
close(6) = 0
open("/proc/mdstat", O_RDONLY) = 6
ioctl(6, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbed1cbd8) = -1 ENOTTY (Inappropriate ioctl for device)
read(6, "Personalities : [linear] [raid0]"..., 4096) = 141
close(6) = 0
exit(0) = ?

I'm not sure what would keep the disks spinning. Does reading /proc/mdstat do that?

jotka · 2009-03-18 10:32:08

dudu_georgescu wrote:
Maybe this is stupid, but how do you guys determine that the HDDs wake-up?

blue leds ?

SnowMan23 · 2009-03-19 20:42:07

Bit of a Noob question regarding this. I am running 1.06 and have to because I have two 1.5TB drives in it and 1.05 didn't recognize them properly. I also have the problem mentioned here were the disks are constantly going. I was playing around with the cron jobs and removed a couple of them that I know don't need to be run with the "crontab -e" command. Thing is they reappear when the unit is rebooted. How/where do I go to permanently remove the cron jobs that I don't want so that it stays in the same state when rebooted? (I have ffp installed so I have SSH access).

Also, I noticed that this thread basically stopped in January. Any more information about this issue and ways to resolve? Thanks.

ac3 · 2009-03-21 20:46:47

Ditto here....n00b member, and also having similar drive spin-up issues.

Just got the DNS-323 a few weeks ago, immediately upped to f/w 1.06. Using a Seagate ES.2 500gb , and a Seagate 7200.11 1.5tb...not running raid - running as single disks. BT client was installed and used - torrents are removed from list after seeding, so nothing there.

Everything (and I mean everything) is disabled, except for power management - set to spin down after 5 minutes. No printer installed, but just for kicks I emptied the already empty printer queue with no change. Even assigned a static IP from my WRT54g router (running Tomato), no change. D-Link tech support had no clue, suggested the box was defective (even though it sounds more like a f/w issue to me), so I just replaced it while my retailer still would...and same problem. Senior D-Link tech told me they would try to replicate the issues in house...but I haven't heard back.

every 1 minute past the hour, and every 20 minutes or so thereafter, the 500gb drive (with the hidden sys folder) will spin up for no reason, and go back to sleep after the 5 minutes have elapsed. The other 1.5tb drive remains asleep when this happens.

While the LAN led flashes at random (background traffic I'll assume, though multicast is not enabled in the router) when the drives are sleeping, checking my router logs for traffic to the nas shows nothing aside from initial IP lease.

Having a 1.5tb, f/w 1.05 isn't an option. Leaving it on 24/7 neither. With 3 unnecessary spin-ups per hour, each hour, I'm just wearing down the drive for no reason at all

Haven't played with fun_plug yet, but not sure what the best way to proceed would be - set up a logger and post results here, or does anybody have any script mods that I might want to try for resolving this issue? Or do I just dump the hidden sysfile (and lose the bt client)? The gpl just came out for 1.06, so hopefully somebody may _see_ somethin' that D-Link is overlooking!

Cheers

mets · 2009-03-24 11:10:53

I'm using two Samsung 1TB HD103UI (5400rpm) in RAID1 with firmware 1.06

i thought i had this issue, but it was my NAS gadget waking it up all the time. Closed the
gadget and from then on the NAS remains asleep.

jesbo · 2009-04-03 05:39:51

SnowMan23 wrote:
... I was playing around with the cron jobs and removed a couple of them that I know don't need to be run with the "crontab -e" command. Thing is they reappear when the unit is rebooted. How/where do I go to permanently remove the cron jobs that I don't want so that it stays in the same state when rebooted? (I have ffp installed so I have SSH access).

Just modify your fun plug startup script and add the "crontab -e" commands you used to remove the standard entries.

frenchybe · 2009-05-09 17:25:51

Hi all,

As a lot of people here, I'm trying to hibernate my hard-drives.
I hope we'll find a solution.

Here's the symptoms for me:

The right led is always blinking.

Firmware Version wrote:
1.07

HARD DRIVE INFO wrote:
Total Drive(s): 2
--------------------------------------------------------------------------------
Volume Name: Volume_1
Volume Type: JBOD
Total Hard Drive Capacity: 1475695 MB
Used Space: 1191201 MB
Unused Space: 284494 MB

PHYSICAL DISK INFO wrote:
Slot Vendor Model Serial Number Size

--------------------------------------------------------------------------------

1 Seagate ST3750330AS 9QK02HWJ 750 G
2 Seagate ST3750330AS 3QK02QCY 750 G

ffp.log wrote:
**** fun_plug script for DNS-323 (2008-04-13 tp@fonz.de) ****
Sat May 9 16:08:01 DST 2009
ln -snf /mnt/HD_a2/ffp /ffp
* Running /ffp/etc/rc ...
* /ffp/start/rcS.sh ...
utmp:x:22:
* /ffp/start/adjtimex.sh inactive
* /ffp/start/passwd.sh ...
Saving /etc/passwd to /etc/passwd.orig ...
Changing shells: /bin/sh -> /ffp/bin/sh ...
Updating /etc/shadow ...
* /ffp/start/shells.sh ...
* /ffp/start/syslogd.sh inactive
* /ffp/start/SERVERS.sh inactive
* /ffp/start/usbdisk.sh inactive
* /ffp/start/portmap.sh inactive
* /ffp/start/unfsd.sh inactive
* /ffp/start/nfsd.sh inactive
* /ffp/start/ntpd.sh inactive
* /ffp/start/LOGIN.sh inactive
* /ffp/start/telnetd.sh ...
Starting /ffp/sbin/telnetd -l /ffp/bin/sh
* /ffp/start/sshd.sh inactive
* /ffp/start/rsyncd.sh inactive
* /ffp/start/mediatomb.sh inactive
* /ffp/start/kickwebs.sh inactive
* /ffp/start/lighttpd.sh inactive
* /ffp/start/inetd.sh inactive
* OK

crontab -l wrote:
/ # crontab -l
32 2 * * * /usr/sbin/rtc -s
30 2 2 * * /usr/sbin/rtc -c
59 1 * * * /usr/sbin/daylight &

Does someone see anything strange? because for me everything is OK.
I also tried to clear the print queue (but never used the print with the NAS).

Can you tell-me what I can try to stop this f#*ùµ led to blink

Thanks

truxntrax · 2009-08-05 18:06:55

Also waiting for a solution. Worried my drives are going to fail due to the constant spinning.

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

Announcement

#26 2009-01-10 03:36:58

Re: Constant disk access with Firmware v 1.06

#27 2009-01-10 03:53:49

Re: Constant disk access with Firmware v 1.06

#28 2009-01-10 05:32:19

Re: Constant disk access with Firmware v 1.06

fordem wrote:

#29 2009-01-10 23:21:16

Re: Constant disk access with Firmware v 1.06

#30 2009-01-11 11:21:39

Re: Constant disk access with Firmware v 1.06

#31 2009-01-14 07:28:30

Re: Constant disk access with Firmware v 1.06

#32 2009-01-14 14:46:31

Re: Constant disk access with Firmware v 1.06

Dex wrote:

fordem wrote:

#33 2009-01-14 22:29:02

Re: Constant disk access with Firmware v 1.06

#34 2009-01-15 00:27:50

Re: Constant disk access with Firmware v 1.06

frodo wrote:

#35 2009-01-15 00:51:48

Re: Constant disk access with Firmware v 1.06

frodo wrote:

#36 2009-01-15 03:02:19

Re: Constant disk access with Firmware v 1.06

#37 2009-01-15 10:56:23

Re: Constant disk access with Firmware v 1.06

fordem wrote:

frodo wrote:

#38 2009-01-15 11:00:02

Re: Constant disk access with Firmware v 1.06

atx32 wrote:

frodo wrote:

#39 2009-01-15 15:45:31

Re: Constant disk access with Firmware v 1.06

frodo wrote:

fordem wrote:

frodo wrote:

#40 2009-01-15 18:14:07

Re: Constant disk access with Firmware v 1.06

frodo wrote:

atx32 wrote:

#41 2009-01-15 18:27:28

Re: Constant disk access with Firmware v 1.06

fordem wrote:

#42 2009-01-15 18:28:28

Re: Constant disk access with Firmware v 1.06

atx32 wrote:

frodo wrote:

atx32 wrote:

#43 2009-01-18 12:29:22

Re: Constant disk access with Firmware v 1.06

#44 2009-03-18 10:32:08

Re: Constant disk access with Firmware v 1.06

dudu_georgescu wrote:

#45 2009-03-19 20:42:07

Re: Constant disk access with Firmware v 1.06

#46 2009-03-21 20:46:47

Re: Constant disk access with Firmware v 1.06

#47 2009-03-24 11:10:53

Re: Constant disk access with Firmware v 1.06

#48 2009-04-03 05:39:51

Re: Constant disk access with Firmware v 1.06

SnowMan23 wrote:

#49 2009-05-09 17:25:51

Re: Constant disk access with Firmware v 1.06

Firmware Version wrote:

HARD DRIVE INFO wrote:

PHYSICAL DISK INFO wrote:

ffp.log wrote:

crontab -l wrote:

#50 2009-08-05 18:06:55

Re: Constant disk access with Firmware v 1.06

Board footer