NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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:
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!
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!
28 Replies
Replies have been turned off for this discussion
- Do you have an up to date backup?
What version of RAIDiator are you running? - I tried to make a backup to an attached usb drive but it failed. However most of the important stuff is backed up on other devices.
The RAIDiator version is 4.1.13. Not sure if it's the latest for this box but when I go to System -> Updates it does not show a newer version. - 4.1.13 is the latest.
You could of course connect the USB drive to a PC, and back up over the network. - Thanks for the advice so far but backing up is not my main concern. The weekly locking up is the major issue. Just can't figure out why this keeps happening.
- And FYI, the nas is at 38% capacity so not a space issue.
- A filing OS partition creates a number of odd symptoms, including hangs - but I don't think any other poster has seen a precise rhythm.
You can't see the OS partition; your 38% number is for the data partition. - OS partition is only at 22%.
TWC-NAS:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 1.9G 434M 1.5G 22% /
tmpfs 16k 0 16k 0% /USB
/dev/c/c 2.7T 1.1T 1.6T 39% /c - StephenB, do you know what the warranty period is on the drives? Looking at the SMART settings it looks like I have a drive that may be failing. Looks like drive 3 (Seagate ST31000524AS) has a fair number of reallocated sectors but more troubling a large amount of ATA errors.
Now I would assume the the x-raid would not be affected by a bad drive and the issue I see appears to be every 7 days I'm not sure there is a correlation. However since I can't find a better answer at this point it's time to start looking at other things.... - You should be able to enter the serial number of the drive into Seagate's warranty website
http://support.seagate.com/customer/en- ... dation.jsp
There are also instructions for how to rma a drive. - If you have a failing disk, then definitely replace that first. Seagate warranties are confusing (they depend on the time of manufacture, and whether the drive was sold as "retail" or "oem"). You need to use the link vandermerwe posted.
The best approach is to get a new disk for the NAS. I'd suggest a NAS drive - which in your case would mean a WD10EFRX (western digital), because the Seagate NAS line starts at 2 TB. Search this forum for the model before you purchase. A NAS drive has a 3 year warranty, desktop drives are only 1 year.
If the drive is covered, Seagate will rma you a re-certified drive (not new), and they will substitute models - so you are not guaranteed to get a ST31000524AS in exchange.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
