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

Forum Discussion

jonj03's avatar
jonj03
Aspirant
May 17, 2019

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

10 Replies

Replies have been turned off for this discussion
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    May 17, 2019

    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.  

     

     

    • jonj03's avatar
      jonj03
      Aspirant
      May 17, 2019

      Sounds good, I am attempting to back up now.

    • JohnCM_S's avatar
      JohnCM_S
      NETGEAR Employee Retired
      May 17, 2019

      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,

      • jonj03's avatar
        jonj03
        Aspirant
        May 17, 2019

        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

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