Orbi WiFi 7 RBE973
Reply

Formerly "Volume Degraded" drive is now fine after recovery

dmachr2
Aspirant

Formerly "Volume Degraded" drive is now fine after recovery

One of my drives recently said "volume degraded", (Western Digital Red, WD40EFRX) but then after a few days of automatic data recovery, the disk reads as healthy. I had started an RMA with WD, but should I send it back? Even though it says healthy now, should I worry about it? The 4 drives (4tb each) are in RAID 5, so data wasn't lost in the process... I dont want to send something back if i dont need to

Model: RN104|ReadyNAS 100 Series 4- Bay
Message 1 of 13
StephenB
Guru

Re: Formerly "Volume Degraded" drive is now fine after recovery

Have you looked at the smart stats?

 

Using the green icons in RAIDar or the web ui isn't a good way to assess disk health.

Message 2 of 13
dmachr2
Aspirant

Re: Formerly "Volume Degraded" drive is now fine after recovery

OH good call. Just checked the logs... opened up "status" file. Is this what you mean? Below is some recent logs from it

 

[20/08/23 11:24:43 EDT] notice:volume:LOGMSG_RESILVERCOMPLETE_DEGRADED_VOLUME The resync operation finished on volume data. However, the volume is still degraded.
[20/08/23 11:25:45 EDT] notice:disk:LOGMSG_ADD_DISK Disk Model:WDC WD40EFRX-68N32N0 Serial:WD-WCC7K1SFPUH7 was added to Channel 1 of the head unit.
[20/08/23 11:26:00 EDT] notice:volume:LOGMSG_RESILVERSTARTED_VOLUME Resyncing started for Volume data.
[20/08/24 01:00:16 EDT] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume data is Degraded.
[20/08/24 11:50:24 EDT] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[20/08/24 11:50:27 EDT] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume data is Degraded.
[20/08/24 11:50:27 EDT] notice:volume:LOGMSG_RESILVERSTARTED_VOLUME Resyncing started for Volume data.
[20/08/24 11:50:27 EDT] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send.
[20/08/24 11:50:51 EDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[20/08/25 01:00:44 EDT] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume data is Degraded.
[20/08/26 01:00:36 EDT] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume data is Degraded.
[20/08/26 07:59:41 EDT] notice:volume:LOGMSG_RESILVERCOMPLETE_VOLUME Volume data is resynced.
[20/08/26 07:59:42 EDT] notice:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Degraded to Redundant.
[20/08/26 07:59:43 EDT] notice:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 1 (Internal) changed state from RESYNC to ONLINE.

Message 3 of 13
JohnCM_S
NETGEAR Employee Retired

Re: Formerly "Volume Degraded" drive is now fine after recovery

Hi dmachr2,

 

You may open the disk_info.log to check the SMART stats of the disks.


Regards,

Message 4 of 13
dmachr2
Aspirant

Re: Formerly "Volume Degraded" drive is now fine after recovery

This is what appears after the disk that was causing issues..doesn't seem like anything is wrong now?


Health data
ATA Error Count: 0
Reallocated Sectors: 0
Reallocation Events: 0
Spin Retry Count: 0
Current Pending Sector Count: 0
Uncorrectable Sector Count: 0
Temperature: 37
Start/Stop Count: 7339
Power-On Hours: 9687
Power Cycle Count: 19
Load Cycle Count: 7327

Message 5 of 13
JohnCM_S
NETGEAR Employee Retired

Re: Formerly "Volume Degraded" drive is now fine after recovery

Hi dmachr2,

 

Can you post the complete disk_info.log? (Please omit the serial numbers of the hard drives.)

 

You may also send me the complete system logs of your NAS so we can check it. You may upload it to a file-sharing site then send me the download via private message.

 

Regards,

Message 6 of 13
JohnCM_S
NETGEAR Employee Retired

Re: Formerly "Volume Degraded" drive is now fine after recovery

Hi dmachr2,

 

I looked in the logs and it appears that your volume is not degraded anymore. All the disks are healthy when I checked the disk_info.log. It just has degraded status when disk 1 is still resyncing. Your volume has redundancy now after it finished resyncing. 

 

[20/08/26 07:59:42 EDT] notice:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Degraded to Redundant.

 

Regards,

Message 7 of 13
dmachr2
Aspirant

Re: Formerly "Volume Degraded" drive is now fine after recovery

Any idea what could have caused it? Would it have been the readymade itself? Would it say that the volume is degraded if it would’ve lost contact somehow? (Maybe the connection isn’t great??)
Message 8 of 13
StephenB
Guru

Re: Formerly "Volume Degraded" drive is now fine after recovery

Do you see anything in your logs before 20/08/23 11:24:43?

 

There are a couple of questions here - the big one is what triggered the resilvering?  Normally that would either be a result of a scrub (run from volume settings wheel), or inserting a new drive.

 

Though if you didn't shut down the NAS cleanly (for instance if there was a power failure or you pulled the plug), then there might have been some cached writes that were lost.  That can also trigger a resilvering (usually called a resync in the web ui).

 


@dmachr2 wrote:
Would it say that the volume is degraded if it would’ve lost contact somehow? (Maybe the connection isn’t great??)

The relevant "connections" are the SATA and power connections to the disk drives.  If the drive isn't well seated, then that could have caused it.  You could power down the NAS, and then pull each drive and reinsert it.  But don't do that with the NAS running.

 

Another possibility is that the drive was slow to start up when the system was booted, and came on-line after the volume was mounted. Or a command timeout or some other error might have brought the drive off-line.

 

Of course the chassis could be at fault (the SATA backplane or the controller).

 

 

Message 9 of 13
dmachr2
Aspirant

Re: Formerly "Volume Degraded" drive is now fine after recovery

@StephenB  this is what the rest of the log looks like. i've only had it operational for about a year or so:

 

[19/07/18 06:09:02 PDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[19/07/18 06:09:01 PDT] notice:system:LOGMSG_FIRMWARE_UPGRADED Firmware was upgraded to 6.4.0.
[19/07/18 06:09:34 PDT] notice:volume:LOGMSG_RESILVERSTARTED_VOLUME Resyncing started for Volume data.
[19/07/18 06:15:52 PDT] notice:system:LOGMSG_MODIFY_HOSTNAME Host name was changed to .
[19/07/18 09:34:36 EDT] notice:system:LOGMSG_SYSTEM_REBOOT The system is rebooting.
[19/07/18 09:38:19 EDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[19/07/18 09:38:18 EDT] notice:system:LOGMSG_FIRMWARE_UPGRADED Firmware was upgraded to 6.5.2.
[19/07/18 09:38:29 EDT] alert:account:LOGMSG_ACCOUNT_USERNAME_CHANGED User  was renamed to .
[19/07/18 09:38:51 EDT] notice:volume:LOGMSG_RESILVERSTARTED_VOLUME Resyncing started for Volume data.
[19/07/19 11:56:19 EDT] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[19/07/19 11:56:24 EDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[19/07/19 11:56:56 EDT] notice:volume:LOGMSG_RESILVERSTARTED_VOLUME Resyncing started for Volume data.
[19/07/22 02:05:44 EDT] notice:volume:LOGMSG_RESILVERCOMPLETE_VOLUME Volume data is resynced.
[19/07/22 14:59:12 EDT] notice:system:LOGMSG_SYSTEM_REBOOT The system is rebooting.
[19/07/22 15:03:35 EDT] notice:system:LOGMSG_FIRMWARE_UPGRADED Firmware was upgraded to 6.10.1.
[19/07/22 15:03:36 EDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[19/07/23 09:01:39 EDT] info:system:LOGMSG_SPINDOWN_ENABLE Automatic disk spin-down enabled.
[19/07/23 09:03:45 EDT] info:system:LOGMSG_PROTOCOL_DISABLED Service protocol AFP is disabled.
[19/07/24 08:11:28 EDT] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[19/07/24 08:11:54 EDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[19/07/24 08:21:43 EDT] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[19/07/24 08:22:10 EDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[19/07/24 08:42:28 EDT] info:account:LOGMSG_ADD_USER User '' was added.
[19/07/24 08:43:35 EDT] info:system:LOGMSG_PROTOCOL_DISABLED Service protocol readycloud is disabled.
[19/07/24 08:44:41 EDT] info:share:LOGMSG_DELETE_SHARE Share Music was deleted.
[19/07/24 08:46:10 EDT] info:share:LOGMSG_ADD_SHARE Share  was added.
[19/07/24 09:02:18 EDT] info:account:LOGMSG_ADD_USER User '' was added.
[19/07/24 09:21:33 EDT] info:share:LOGMSG_DELETE_SHARE Share Pictures was deleted.
[19/07/24 09:22:29 EDT] info:share:LOGMSG_DELETE_SHARE Share Documents was deleted.
[19/07/24 09:25:03 EDT] info:share:LOGMSG_DELETE_SHARE Share was deleted.
[19/07/24 09:38:20 EDT] notice:system:LOGMSG_APPLICATION_ADD_SUCCESS_NOREBOOT Application is installed successfully.
[19/07/24 10:01:14 EDT] info:system:LOGMSG_SET_ALERTCONTACT Alert contact information was saved.
[19/07/24 10:01:14 EDT] info:system:LOGMSG_SET_ALERTCONFIG Alert settings are updated.
[19/07/24 10:01:27 EDT] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send.
[19/08/26 12:11:58 EDT] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[19/08/26 12:12:25 EDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[19/09/01 10:46:40 EDT] notice:system:LOGMSG_SYSTEM_HALT The system is shutting down.
[19/09/01 10:46:40 EDT] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send.
[19/09/01 15:28:15 EDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[19/09/01 15:47:41 EDT] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[19/09/01 15:48:08 EDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[19/11/20 17:37:17 EST] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[19/11/20 17:37:43 EST] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[20/01/10 15:38:08 EST] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
[20/01/10 15:38:33 EST] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[20/06/01 08:22:35 EDT] notice:system:LOGMSG_SYSTEM_REBOOT The system is rebooting.
[20/06/01 08:22:35 EDT] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send.
[20/06/01 08:29:06 EDT] notice:system:LOGMSG_FIRMWARE_UPGRADED Firmware was upgraded to 6.10.3.
[20/06/01 08:29:29 EDT] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.
[20/06/01 08:37:15 EDT] alert:account:LOGMSG_ACCOUNT_PASSWORD_CHANGED User password has been changed.
[20/06/01 08:37:15 EDT] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send.
[20/08/12 15:50:39 EDT] info:system:LOGMSG_PROTOCOL_ENABLED Service protocol readycloud is enabled.
[20/08/22 12:04:08 EDT] warning:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Redundant to Degraded.
[20/08/23 00:00:04 EDT] notice:system:LOGMSG_SYSTEM_HALT The system is shutting down.

Message 10 of 13
StephenB
Guru

Re: Formerly "Volume Degraded" drive is now fine after recovery

Try looking in system.log (in your log zip), and see if there are errors around 20/08/22 12:04:08.

 

Also, something appears to be going wrong with your email alerts.  You should fix that.

Message 11 of 13
dmachr2
Aspirant

Re: Formerly "Volume Degraded" drive is now fine after recovery

Yeah i need to fix something in my gmail settings. I guess the main question I have now is, can these NAS drives repair themselves? I've had regular hard drives that start to show signs of failing, and then eventually fail. I know this one is redundant now, but was that a warning sign that it may fail later? And would sending the drive into WD only to get a refurbished drive be any better?

 

 

Message 12 of 13
StephenB
Guru

Re: Formerly "Volume Degraded" drive is now fine after recovery


@dmachr2 wrote:

 can these NAS drives repair themselves?


No.

 

But we don't know what actually caused the resync - or if anything at all wrong with the disks.

 

It if were my own system, I'd be keeping a close eye on it, and making sure my backups are kept up to date.

Message 13 of 13
Top Contributors
Discussion stats
  • 12 replies
  • 3868 views
  • 0 kudos
  • 3 in conversation
Announcements