× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: ReadyNAS in Lifesupport

jonj03
Aspirant

ReadyNAS in Lifesupport

Hello,

 

I am having a bit of trouble. I replaced a disk resently, and once the sync finished, on the front of my ReadyNAS it says "Vol C lifesupp!" When I go to the health page, it shows my new disk (disk 2) as "Spare, and now disk 4 says "Dead." I still have access to my data from what it appears. When I reboot the NAS, Disk 2 begins to sync again, it it shows disk 4 as healthy - until the sync finishes again. I have tried to do a volume scan and quota scan as well just to see if that would clean anything up, but to no avail. I have tried rebooting and resyncing at least 4 times at this point, but it always seems to end up the same. I would have assumed if both disks crashed that I would not have access to my data, but as of right now I do. I have the logs as well in case these might help. If anyone could offer and suggestions, I would appreciate it. I have another drive I could replace disk 4 with right now, but I'm unsure what the effect will be with my data. Again, any help would be appreciated!

 

Logs located <redacted>

 

 

Jon

Model: RNDU4000 (ReadyNAS Ultra 4)|READYNAS ULTRA 4 (DISKLESS)|EOL
Message 1 of 11
StephenB
Guru

Re: ReadyNAS in Lifesupport

Please don't post logs publicly - there is some privacy leakage when you do that. I've redacted your link.

 

The most important thing to do now is back up all your data, since it is certainly at risk.   You might not be able to get all of it.

 

In parallel, you send a private message to one of the mods ( perhaps @JohnCM_S ) with the link to your logs, and ask him to analyze them.  You send a PM by clicking on the envelope icon in the upper right of the forum.

 

FWIW, I did take the liberty of taking a quick look at your logs. There are problems.  @JohnCM_S  might see things that I've missed.

 

System.log:

May 17 08:54:37 Jergens-NAS kernel: end_request: I/O error, dev sdd, sector 3352498240
May 17 08:54:37 Jergens-NAS kernel: md/raid:md2: read error not correctable (sector 3343060984 on sdd5).
May 17 08:54:37 Jergens-NAS kernel: md/raid:md2: Disk failure on sdd5, disabling device.
May 17 08:54:37 Jergens-NAS kernel: <1>md/raid:md2: Operation continuing on 2 devices.
May 17 08:54:37 Jergens-NAS kernel: md/raid:md2: read error not correctable (sector 3343060992 on sdd5).
May 17 08:54:37 Jergens-NAS kernel: md/raid:md2: read error not correctable (sector 3343061000 on sdd5).
May 17 08:54:37 Jergens-NAS kernel: md/raid:md2: read error not correctable (sector 3343061008 on sdd5).
May 17 08:54:37 Jergens-NAS kernel: md/raid:md2: read error not correctable (sector 3343061016 on sdd5).
May 17 08:54:37 Jergens-NAS kernel: md/raid:md2: read error not correctable (sector 3343061024 on sdd5).
May 17 08:54:37 Jergens-NAS kernel: md/raid:md2: read error not correctable (sector 3343061032 on sdd5).
May 17 08:54:37 Jergens-NAS kernel: md/raid:md2: read error not correctable (sector 3343061040 on sdd5).
May 17 08:54:37 Jergens-NAS kernel: md/raid:md2: read error not correctable (sector 3343061048 on sdd5).
May 17 08:54:37 Jergens-NAS kernel: md/raid:md2: read error not correctable (sector 3343061056 on sdd5).
...
May 17 09:02:37 Jergens-NAS RAIDiator: Detected increasing pending sector count[906] on disk 4 [WDC WD20EARS-00MVWB0, WD-WCAZA4957797].
...
May 17 09:02:55 Jergens-NAS RAIDiator: RAID sync finished on volume C. The array is still in degraded mode, however. This can be caused by a disk sync failure or failed disks in a multi-parity disk array.
May 17 09:02:56 Jergens-NAS RAIDiator: RAID event detected. (Jergens-NAS) : RAID sync finished on volume C. The array is still in degraded mode, however. This can be caused by a disk sync failure or failed disks in a multi-parity disk array.\n\n[Fri May 17 09:02:52 EDT 2019]

So disk 4 (sdd) has failed (over 900 pending sectors).

 

I also see disk 2 (sdb) marked as a spare, so it's not clear to me why you still have access to your data.

mdstat.log

Personalities : [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] 
md2 : active raid5 sda5[4] sdd5[3](F) sdc5[5] sdb5[6](S)
      5846379648 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/2] [U_U_]
      
md1 : active raid6 sda2[4] sdd2[3] sdc2[5] sdb2[6]
      1048448 blocks super 1.2 level 6, 64k chunk, algorithm 2 [4/4] [UUUU]
      
md0 : active raid1 sdb1[6] sda1[4] sdd1[3] sdc1[5]
      4194292 blocks super 1.2 [4/4] [UUUU]
      
unused devices: <none>

Whatever's going on, I don't think you should reboot the NAS until after you've backed it up.  

 

 

Message 2 of 11
jonj03
Aspirant

Re: ReadyNAS in Lifesupport

Sounds good, I am attempting to back up now.

Message 3 of 11
JohnCM_S
NETGEAR Employee Retired

Re: ReadyNAS in Lifesupport

Hi jonj03,

 

Aside from disk 4, the disk 2 has failed as well. It has 407 reallocated sectors and 1386 pending sectors already.

 

As @StephenB has mentioned, if you can still backup your data, please do so then replace the faulty drives afterward.

 

Regards,

Message 4 of 11
jonj03
Aspirant

Re: ReadyNAS in Lifesupport

I just replaced disk 2 - it is brand new. So are you saying that brand new disk is bad? Or that it's just not syncing because disk 4 has failed during the sync?

 

Jon

Message 5 of 11
StephenB
Guru

Re: ReadyNAS in Lifesupport


@jonj03 wrote:

I just replaced disk 2 - it is brand new. So are you saying that brand new disk is bad? Or that it's just not syncing because disk 4 has failed during the sync?

 


I believe that he's talking about the WD20EARS disk with the serial number ending in 4066.  disk_smart_2019_05_12.log shows the counts he mentions.  I'm not seeing  those errors with the ST4000DM004 (serial ending in QDX) - which I think is your replacement disk. 

 

I am seeing a couple of weird stats with the Seagate though - for example power-on hours is crazy (120735825657895 hours).

 

After you back up the NAS you should probably test all the drives in a PC (Seatools for the Seagate, Lifeguard for the Western Digital).

Message 6 of 11
JohnCM_S
NETGEAR Employee Retired

Re: ReadyNAS in Lifesupport

Hi jonj03,

 

Sorry. That disk smart stats that I read was for the previous disk 2. There are no issues on the new disk 2.

 

Regards,

Message 7 of 11
jonj03
Aspirant

Re: ReadyNAS in Lifesupport

Strange as this sounds, I rebooted the device and removed disk 2. It came up fully intact, identifying as healthy disk 4. I then was able to copy everything i needed over. I guess at this point I'll simply shut down the ReadyNas, reinsert disk 2, replace disk 4, and copy the data back over. I guess disk 4 is simply at the cusp of being bad, but not quite yet, or else I would not be able to access data.

 

If anyone has a better option, let me know! But my data is safe, so there's that!

 

 

Jon

Message 8 of 11
StephenB
Guru

Re: ReadyNAS in Lifesupport


@jonj03 wrote:

I guess at this point I'll simply shut down the ReadyNas, reinsert disk 2, replace disk 4, and copy the data back over.


I'd reinsert disk 2 with the NAS running, and see if it resyncs (not as a spare).  If it does, then replace disk 4 with the NAS running.

 

If the first resync fails you'll likely need to do a factory reset.

 

 

Message 9 of 11
jonj03
Aspirant

Re: ReadyNAS in Lifesupport

Sounds good, I'll give it another shot

 

Message 10 of 11
jonj03
Aspirant

Re: ReadyNAS in Lifesupport

it came back up as a spare, so I replaced the drive and factory reset it. Didn't lose any data (that I know of) so I'm pretty happy overall.

Curious as to how much longer this thing is gonna last though, hardware wise. The Ultra 4 I have, I can't even remember when I bought it. Curious if anyone knows how long they typically last for. 

 

Thanks for the help guys!

 

Jon

Message 11 of 11
Top Contributors
Discussion stats
  • 10 replies
  • 1581 views
  • 0 kudos
  • 3 in conversation
Announcements