NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Disc degraded after Firmware upgrade to 6.5.2
Hi,
My NAS have been working fine with the only issue being very slow acces via Windows Exporer. I turned of the real-time anti-virus scanner and the issue went away.
I then updated to the latest firmeware 6.5.2 and after the upgrade the disc status shows up as degraded.
I have rebooted the unit a couple of times and and shut it down. I have take the "bad" disc out and etc.
Is the disc likely to have been corrupted as part of the firmware upgrade?
The logs can be found here: https://drive.google.com/file/d/0B9URWpaz62voc2ZFenlPVjkxUzQ/view?usp=sharing
Thanks
Marcus
5 Replies
Replies have been turned off for this discussion
I think it be wise to shut down the system and test disk 2 in a windows PC with lifeguard. If you don't have a backup you should certainly make one - your data is at risk.
One way to proceed is to back everything up, do a factory reset and then rebuild the NAS, and restore the data.
There are some odd things going on in the logs. hopefully netgear will take a look. spindown.log enables spindown on disk 2, but the disk never is spundown. This goes back to last June (as far as spindown goes back), so it is not new.
disk_info.log only shows disk 1. smart_history shows both disks (and both have a couple of pending sectors errors).
There are a couple of other issues going on, which I don't really understand the cause.
One is this snippet (which repeats)
Sep 29 06:52:31 Rosen-NAS smbd[23255]: [2016/09/29 06:52:31.607780, 0] ../source3/smbd/oplock.c:192(update_num_read_oplocks)
Sep 29 06:52:31 Rosen-NAS smbd[23255]: PANIC: assert failed at ../source3/smbd/oplock.c(192): d->num_share_modes == 1
Sep 29 06:52:31 Rosen-NAS smbd[23255]: [2016/09/29 06:52:31.611268, 0] ../source3/lib/util.c:788(smb_panic_s3)
Sep 29 06:52:31 Rosen-NAS smbd[23255]: PANIC (pid 23255): assert failed: d->num_share_modes == 1
Sep 29 06:52:31 Rosen-NAS smbd[23255]: [2016/09/29 06:52:31.612039, 0] ../source3/lib/util.c:899(log_stack_trace)
Sep 29 06:52:31 Rosen-NAS smbd[23255]: BACKTRACE: 0 stack frames:
Sep 29 06:52:31 Rosen-NAS smbd[23255]: [2016/09/29 06:52:31.612518, 0] ../source3/lib/dumpcore.c:318(dump_core)
Sep 29 06:52:31 Rosen-NAS smbd[23255]: dumping core in /var/coresThere are also regular ethernet over-runs, which might be related to your poor performance.
Sep 29 19:22:26 Rosen-NAS kernel: [395773.553715] mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024
Sep 29 19:22:29 Rosen-NAS kernel: [395775.997205] mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024
Sep 29 19:22:35 Rosen-NAS kernel: [395782.477936] mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024
Sep 29 19:22:35 Rosen-NAS kernel: [395782.477960] mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=512
Sep 29 19:22:39 Rosen-NAS kernel: [395786.820422] mvneta d0074000.ethernet eth0: bad rx status 0f830000 (overrun error), size=1024The disks may have hardware issues. This wouldn't be caused by the firmware upgrade.
Do you have a backup?
It is unlikely that your disk failed due to an upgrade. Typically, if you have used a disk for awhile but you aren't processing much data on it (it just sits around), then you don't activate any bad sectors, but upgrading/rebooting might cause it to pass over bad sectors and fall out,.
It looks like your drives have counted up a few errors historically (see smart_history.log), but not too many.On Sept 30 around 19:33:16, your disk tried to come online but it was having some kind of read errors.
You can see constant complaints in the dmesg.log trying to identify the disk.
[Fri Sep 30 19:34:15 2016] ata1.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
Your drive in bay 2 seems to have been collecting errors, as well. Not too many though.
Thanks for all the replies. :)
I'm backing up all the data on external drives right now (likely to take some time).
Is it likely that I need to replace the Bay 2 drive or could it be the NAS itself?
How can I proceed one all the data is backed up?
You can hook the disks up to a PC and test them using the vendors tools e.g. SeaTools for SeaGate disks or WD Data LifeGuard Diagnostics for WD disks.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
