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

Forum Discussion

jukkaforss's avatar
Jun 27, 2019
Solved

kernel bug ReadyNASOS 6.10.1 screen massage __extent_writepsge_io+1d3

Hi, My Readynas hit kernel bug, it running latests code 6.10.1. Dmesg output after it happened. I needed to power cycle to get it rebooted. [1108355.142034] ------------[ cut here ]------------ [1...
  • StephenB's avatar
    StephenB
    Jun 28, 2019

    Shrinking this one down ...

     


    jukkaforss wrote:

    sdb part 1

     

    root@readynas:~# smartctl -x /dev/sdb
    
    ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
      1 Raw_Read_Error_Rate     POSR-K   200   200   051    -    159
      9 Power_On_Hours          -O--CK   028   028   000    -    52621
    
    Error 9 [8] occurred at disk power-on lifetime: 50321 hours (2096 days + 17 hours)
    Error: UNC at LBA = 0x12fdf7710 = 5098141456
    
    Error 8 [7] occurred at disk power-on lifetime: 50321 hours (2096 days + 17 hours)
    Error: WP at LBA = 0x12fdf7710 = 5098141456
    
    Error 7 [6] occurred at disk power-on lifetime: 41988 hours (1749 days + 12 hours)
    Error: UNC at LBA = 0xcf083840 = 3473422400
    
    Error 6 [5] occurred at disk power-on lifetime: 41988 hours (1749 days + 12 hours)
    Error: WP at LBA = 0xcf083840 = 3473422400
    
    Error 5 [4] occurred at disk power-on lifetime: 38618 hours (1609 days + 2 hours)
    Error: UNC at LBA = 0xe824a0c0 = 3894714560
    
    Error 4 [3] occurred at disk power-on lifetime: 38618 hours (1609 days + 2 hours)
    Error: WP at LBA = 0xe824a0b8 = 3894714552
    
    Error 3 [2] occurred at disk power-on lifetime: 38618 hours (1609 days + 2 hours)
    Error: UNC at LBA = 0xe824a0b8 = 3894714552
    
    Error 2 [1] occurred at disk power-on lifetime: 38615 hours (1608 days + 23 hours)
    Error: WP at LBA = 0x11616d4b8 = 4665562296
    

     


    I saw a similar pattern on one of my WD60EFRX drives a while ago, and when I tested it with Lifeguard it failed.   Though a second disk with the same pattern passed Lifeguard.  So I recommend testing this disk (and perhaps replace it even if it does pass).

     

    The most recent logged error was about 2000 hours ago (~ 3 months), so that particular error didn't cause the most recent crash.  But I'm thinking that this disk likely triggered it anyway.

     

    FWIW, I haven't seen any explanation of how to decode the raw read error rate.  But it is quite a bit higher on this drive than your other ones.

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