NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

drawding's avatar
drawding
Aspirant
Sep 07, 2014

NV+ hanging up every 7 days

I have a strange issue that has been happening for the last three weeks. It seems that every Sunday morning my NV+ hangs up. I'm usually not able to control it via the web management or ssh. I can't even get a reaction to the front buttons. So I end up unplugging it and plugging it back in.

When it boots up I log in via ssh at kill the quota check (takes hours) and then reboot from the cli. When it comes back up again I'm back in business. A fsck usually does not find any issues. I can't for the life of me figure out why it's doing this? While writing this I looked at the health and logs in the web management and there was nothing. So I just looked at /var/log/messages and found that there were no entries since the last reboot until 6:47 this morning when I see this:

Sep  7 06:47:01 TWC-NAS kernel: X_RAID_DUMP
Sep  7 06:47:01 TWC-NAS kernel: 
Sep  7 06:47:01 TWC-NAS kernel: VERSION/ID    : SB=(V:0.1.0) ID=<0ea55712.00000000.00000000.00000000> CT:4de5751a
Sep  7 06:47:01 TWC-NAS kernel: RAID_INFO     : DISKS(TOTAL:4 RAID:4 PARITY:1 ONL:4 WRK:4 FAILED:0 SPARE:0 BASE:0)
Sep  7 06:47:01 TWC-NAS kernel:                 SZ:1953108616 UT:00000000 STATE:0 LUNS:2 EXTCMD:1 LSZ:1953108614
Sep  7 06:47:01 TWC-NAS kernel: LOGICAL_DRIVE : 0: B:0000000002 E:0004096000 R:1 O:1 I:1:000000000 DM:f
Sep  7 06:47:01 TWC-NAS kernel: LOGICAL_DRIVE : 1: B:0004096002 E:1949012614 R:4 O:1 I:1:640684034 DM:f
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 0: DISK<N:0/1,hdc(22,0),ID:0,PT:1,SZ:1953108616,ST: B:online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 1: DISK<N:1/2,hde(33,0),ID:1,PT:1,SZ:1953108616,ST:P :online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 2: DISK<N:2/3,hdg(34,0),ID:2,PT:1,SZ:1953108616,ST:  :online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 3: DISK<N:3/4,hdi(56,0),ID:3,PT:1,SZ:1953108616,ST:  :online>
Sep  7 06:47:01 TWC-NAS kernel: CURRENT_DRIVE : DISK<N:0/1,XXX(22,0),ID:0,PT:1,SZ:1953108616,ST: B:online>
Sep  7 06:47:01 TWC-NAS kernel: 
Sep  7 06:47:01 TWC-NAS kernel: VERSION/ID    : SB=(V:0.1.0) ID=<0ea55712.00000000.00000000.00000000> CT:4de5751a
Sep  7 06:47:01 TWC-NAS kernel: RAID_INFO     : DISKS(TOTAL:4 RAID:4 PARITY:1 ONL:4 WRK:4 FAILED:0 SPARE:0 BASE:0)
Sep  7 06:47:01 TWC-NAS kernel:                 SZ:1953108616 UT:00000000 STATE:0 LUNS:2 EXTCMD:1 LSZ:1953108614
Sep  7 06:47:01 TWC-NAS kernel: LOGICAL_DRIVE : 0: B:0000000002 E:0004096000 R:1 O:1 I:1:000000000 DM:f
Sep  7 06:47:01 TWC-NAS kernel: LOGICAL_DRIVE : 1: B:0004096002 E:1949012614 R:4 O:1 I:1:640684034 DM:f
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 0: DISK<N:0/1,hdc(22,0),ID:0,PT:1,SZ:1953108616,ST: B:online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 1: DISK<N:1/2,hde(33,0),ID:1,PT:1,SZ:1953108616,ST:P :online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 2: DISK<N:2/3,hdg(34,0),ID:2,PT:1,SZ:1953108616,ST:  :online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 3: DISK<N:3/4,hdi(56,0),ID:3,PT:1,SZ:1953108616,ST:  :online>
Sep  7 06:47:01 TWC-NAS kernel: CURRENT_DRIVE : DISK<N:1/2,XXX(33,0),ID:1,PT:1,SZ:1953108616,ST:P :online>
Sep  7 06:47:01 TWC-NAS kernel: 
Sep  7 06:47:01 TWC-NAS kernel: VERSION/ID    : SB=(V:0.1.0) ID=<0ea55712.00000000.00000000.00000000> CT:4de5751a
Sep  7 06:47:01 TWC-NAS kernel: RAID_INFO     : DISKS(TOTAL:4 RAID:4 PARITY:1 ONL:4 WRK:4 FAILED:0 SPARE:0 BASE:0)
Sep  7 06:47:01 TWC-NAS kernel:                 SZ:1953108616 UT:00000000 STATE:0 LUNS:2 EXTCMD:1 LSZ:1953108614
Sep  7 06:47:01 TWC-NAS kernel: LOGICAL_DRIVE : 0: B:0000000002 E:0004096000 R:1 O:1 I:1:000000000 DM:f
Sep  7 06:47:01 TWC-NAS kernel: LOGICAL_DRIVE : 1: B:0004096002 E:1949012614 R:4 O:1 I:1:640684034 DM:f
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 0: DISK<N:0/1,hdc(22,0),ID:0,PT:1,SZ:1953108616,ST: B:online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 1: DISK<N:1/2,hde(33,0),ID:1,PT:1,SZ:1953108616,ST:P :online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 2: DISK<N:2/3,hdg(34,0),ID:2,PT:1,SZ:1953108616,ST:  :online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 3: DISK<N:3/4,hdi(56,0),ID:3,PT:1,SZ:1953108616,ST:  :online>
Sep  7 06:47:01 TWC-NAS kernel: CURRENT_DRIVE : DISK<N:2/3,XXX(34,0),ID:2,PT:1,SZ:1953108616,ST:  :online>
Sep  7 06:47:01 TWC-NAS kernel: 
Sep  7 06:47:01 TWC-NAS kernel: VERSION/ID    : SB=(V:0.1.0) ID=<0ea55712.00000000.00000000.00000000> CT:4de5751a
Sep  7 06:47:01 TWC-NAS kernel: RAID_INFO     : DISKS(TOTAL:4 RAID:4 PARITY:1 ONL:4 WRK:4 FAILED:0 SPARE:0 BASE:0)
Sep  7 06:47:01 TWC-NAS kernel:                 SZ:1953108616 UT:00000000 STATE:0 LUNS:2 EXTCMD:1 LSZ:1953108614
Sep  7 06:47:01 TWC-NAS kernel: LOGICAL_DRIVE : 0: B:0000000002 E:0004096000 R:1 O:1 I:1:000000000 DM:f
Sep  7 06:47:01 TWC-NAS kernel: LOGICAL_DRIVE : 1: B:0004096002 E:1949012614 R:4 O:1 I:1:640684034 DM:f
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 0: DISK<N:0/1,hdc(22,0),ID:0,PT:1,SZ:1953108616,ST: B:online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 1: DISK<N:1/2,hde(33,0),ID:1,PT:1,SZ:1953108616,ST:P :online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 2: DISK<N:2/3,hdg(34,0),ID:2,PT:1,SZ:1953108616,ST:  :online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 3: DISK<N:3/4,hdi(56,0),ID:3,PT:1,SZ:1953108616,ST:  :online>
Sep  7 06:47:01 TWC-NAS kernel: CURRENT_DRIVE : DISK<N:3/4,XXX(56,0),ID:3,PT:1,SZ:1953108616,ST:  :online>
Sep  7 06:47:01 TWC-NAS kernel: 
Sep  7 06:47:01 TWC-NAS kernel: VERSION/ID    : SB=(V:0.1.0) ID=<0ea55712.00000000.00000000.00000000> CT:4de5751a
Sep  7 06:47:01 TWC-NAS kernel: RAID_INFO     : DISKS(TOTAL:4 RAID:4 PARITY:1 ONL:4 WRK:4 FAILED:0 SPARE:0 BASE:0)
Sep  7 06:47:01 TWC-NAS kernel:                 SZ:1953108616 UT:00000000 STATE:0 LUNS:2 EXTCMD:1 LSZ:1953108614
Sep  7 06:47:01 TWC-NAS kernel: LOGICAL_DRIVE : 0: B:0000000002 E:0004096000 R:1 O:1 I:1:000000000 DM:f
Sep  7 06:47:01 TWC-NAS kernel: LOGICAL_DRIVE : 1: B:0004096002 E:1949012614 R:4 O:1 I:1:640684034 DM:f
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 0: DISK<N:0/1,hdc(22,0),ID:0,PT:1,SZ:1953108616,ST: B:online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 1: DISK<N:1/2,hde(33,0),ID:1,PT:1,SZ:1953108616,ST:P :online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 2: DISK<N:2/3,hdg(34,0),ID:2,PT:1,SZ:1953108616,ST:  :online>
Sep  7 06:47:01 TWC-NAS kernel: PHYSICAL_DRIVE: 3: DISK<N:3/4,hdi(56,0),ID:3,PT:1,SZ:1953108616,ST:  :online>
Sep  7 06:47:01 TWC-NAS kernel: CURRENT_DRIVE : DISK<N:0/1,XXX(22,0),ID:0,PT:1,SZ:1953108616,ST: B:online>
Sep  7 06:47:01 TWC-NAS kernel: 
Sep  7 06:47:01 TWC-NAS kernel: RUN_PARAMETERS: raid_running=1,last_word=ok,interface_start_at=1,fake=0
Sep  7 06:47:01 TWC-NAS kernel: RAID_REBUILD  : sync=0,logical=0,parity=1,sectors/TOTAL=0/4294967295
Sep  7 06:47:01 TWC-NAS kernel:               : source=f, total_drives=4, auto_sync=1
Sep  7 06:47:01 TWC-NAS kernel: RAID_P_CHECK  : chck=0,logical/total=0/2,raid_level=0
Sep  7 06:47:01 TWC-NAS kernel:               : err/sectors/TOTAL=0/0/0,report_err=1
Sep  7 06:47:01 TWC-NAS kernel:               : initialized=0xf,initialize_error=0x0,initializing=0x0
Sep  7 06:47:01 TWC-NAS kernel:               : where=0,total=0
Sep  7 06:47:01 TWC-NAS kernel: SIZE_INFOR    : sb_size=9440,sections_size=32/256,disk_t_size=128
Sep  7 06:47:01 TWC-NAS kernel:               : sb=f8134294,disks=512/1536,luns=2048/3168,thisdisk=5216/128,diskid=5344/4096
Sep  7 06:47:01 TWC-NAS kernel: DJO_RECORD    : dj_raid=NO_RAID,chns=0,source=0,disks=0 parity=0,chn_image=f,
Sep  7 06:47:01 TWC-NAS kernel:               : sectors=3955906/0x3c5cc2,need_IO=0
Sep  7 06:47:01 TWC-NAS kernel: IO__RECORD    : 0=803604248,1=320464,2=187170098,3=3719570, busy=0/0/0/0/0,t_d=f

Then nothing until I forced the restart around 9 AM when I noticed the problem. Anyone ever seen anything like this? Any pointers as to what may be causing the problem? This device has been running for a few years now without issue or problem. Nothing has really changed that I can think of that would be causing this to happen.

Thanks!
Other Discussions
Questions

28 Replies

Replies have been turned off for this discussion
Show More
  • drawding's avatar
    drawding
    Aspirant
    Sep 08, 2014
    It's out of warranty. I have a couple of new drives of similar capacity that I purchased for a different NAS. Sounds like at lease replacing the (potentially) failing drive is a start but I have doubts that it's going to solve the problem. At least it's something to try!

    I'll report back and let you know how it goes.
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    Sep 08, 2014
    It might not solve the hanging problem, but it likely fixes a worse problem.
  • drawding's avatar
    drawding
    Aspirant
    Sep 14, 2014
    Well replaced the drive and all seemed OK. Then again this morning right on time the NAS hung again....

    Back to the drawing board.
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    Sep 14, 2014
    Can you backup your data then try a factory reset and restore your data from backup?
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    Sep 15, 2014
    Well diagnosing why this is happening could take a long time too.

    So it hangs at the same time each regardless of when the last reboot was or 7 days after the last reboot?
  • chirpa's avatar
    chirpa
    Luminary
    Sep 15, 2014
    6:47AM on Sunday is exactly when cron weekly tasks run.

    Something in /etc/cron.weekly/ must be triggering this lock up.

    # /etc/crontab: system-wide crontab
    # Unlike any other crontab you don't have to run the `crontab'
    # command to install the new version when you edit this file
    # and files in /etc/cron.d. These files also have username fields,
    # that none of the other crontabs do.

    SHELL=/bin/sh
    PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

    # m h dom mon dow user	command
    17 *	* * *	root    cd / && run-parts --report /etc/cron.hourly
    25 6	* * *	root	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
    47 6	* * 7	root	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
    52 6	1 * *	root	test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
  • drawding's avatar
    drawding
    Aspirant
    Sep 15, 2014
    Logs sent. It does seem to coincide with the cron jobs.

    I'm trying to clear some vm's off it so I can reset. Thanks for looking at the logs!
  • mdgm-ntgr's avatar
    mdgm-ntgr
    NETGEAR Employee Retired
    Sep 15, 2014
    One of your disks has 55 reallocated sectors which could be the problem.

    Are you able to power down the NAS and check the disks using SeaTools?

    Also can you PM me or email the contents of /var/log/cron.log ?

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More