NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Front Panel Shows error "kmem_cache_alloc+5c" - #27013537
Hello!
I have just upgraded to the last disk and it was on 96% last night of several days of resynch. When I woke up this morning I couldnät connect so I had a look at the box. The display show...
Do you think this problem has to do with the HDDs or the OS?
Can RAIDar help me?
RAIDar can often give you some information on the NAS status (and allow you to download the logs) even if the web ui is not responsive. It won't fix anything, but it might help get the relevant info.
Have you looked at the disk health? Try to download the log zipfile while the system is running, and look in smart_history.log.
I looked in the smart log and found this
time model serial realloc_sect realloc_evnt spin_retry_cnt ioedc cmd_timeouts pending_sect uncorrectable_err ata_errors
------------------- -------------------- -------------------- ------------ ------------ -------------- ---------- ------------ ------------ ----------------- ----------
2013-04-23 16:20:40 TOSHIBA DT01ACA100 33453RGPS 0 0 0 -1 -1 0 0 0
2013-04-23 16:20:40 TOSHIBA DT01ACA100 334489ENS 0 0 0 -1 -1 0 0 0
2016-06-10 16:45:16 WDC WD4001FFSX-68JNU WD-WMC5D0D2N1W3 0 0 0 -1 -1 0 0 0
2016-06-10 19:06:28 WDC WD4001FFSX-68JNU WD-WCC5D6RZUEL7 0 0 0 -1 -1 0 0 0
2016-06-11 11:19:05 WDC WD4001FFSX-68JNU WD-WCC131AXFYZD 0 0 0 -1 -1 0 0 0
2016-06-13 06:39:57 WDC WD4001FFSX-68JNU WD-WMC130D0ZD5C 0 0 0 -1 -1 0 0 0Looks like nothing but its not my first language if you know what I mean :)
Nienkerk wrote:
I looked in the smart log and found this
time model serial realloc_sect realloc_evnt spin_retry_cnt ioedc cmd_timeouts pending_sect uncorrectable_err ata_errors
------------------- -------------------- -------------------- ------------ ------------ -------------- ---------- ------------ ------------ ----------------- ----------
2013-04-23 16:20:40 TOSHIBA DT01ACA100 33453RGPS 0 0 0 -1 -1 0 0 0
2013-04-23 16:20:40 TOSHIBA DT01ACA100 334489ENS 0 0 0 -1 -1 0 0 0
2016-06-10 16:45:16 WDC WD4001FFSX-68JNU WD-WMC5D0D2N1W3 0 0 0 -1 -1 0 0 0
2016-06-10 19:06:28 WDC WD4001FFSX-68JNU WD-WCC5D6RZUEL7 0 0 0 -1 -1 0 0 0
2016-06-11 11:19:05 WDC WD4001FFSX-68JNU WD-WCC131AXFYZD 0 0 0 -1 -1 0 0 0
2016-06-13 06:39:57 WDC WD4001FFSX-68JNU WD-WMC130D0ZD5C 0 0 0 -1 -1 0 0 0Looks like nothing but its not my first language if you know what I mean :)
That means no error seen by readynasd (the service running part of readynas OS). If there were errors here, that would have brought some explanation. As there isn't any, the answer is elsewhere.
You should double check in disk_info.log that sdb is actually clean.
Looks okey to me..
Device: sdd
Controller: 0
Channel: 0
Model: WDC WD4001FFSX-68JNUN0
Serial: WD-WMC130D0ZD5C
Firmware: 81.00A81
Class: SATA
RPM: 7200
Sectors: 7814037168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: e341204
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: 38
Start/Stop Count: 32
Power-On Hours: 151
Power Cycle Count: 32
Load Cycle Count: 16Device: sdc
Controller: 0
Channel: 1
Model: WDC WD4001FFSX-68JNUN0
Serial: WD-WMC5D0D2N1W3
Firmware: 81.00A81
Class: SATA
RPM: 7200
Sectors: 7814037168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: e341204
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: 41
Start/Stop Count: 18
Power-On Hours: 97
Power Cycle Count: 10
Load Cycle Count: 9Device: sdb
Controller: 0
Channel: 2
Model: WDC WD4001FFSX-68JNUN0
Serial: WD-WCC5D6RZUEL7
Firmware: 81.00A81
Class: SATA
RPM: 7200
Sectors: 7814037168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: e341204
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: 40
Start/Stop Count: 15
Power-On Hours: 95
Power Cycle Count: 10
Load Cycle Count: 6Device: sda
Controller: 0
Channel: 3
Model: WDC WD4001FFSX-68JNUN0
Serial: WD-WCC131AXFYZD
Firmware: 81.00A81
Class: SATA
RPM: 7200
Sectors: 7814037168
Pool: data
PoolType: RAID 5
PoolState: 1
PoolHostId: e341204
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: 39
Start/Stop Count: 20
Power-On Hours: 95
Power Cycle Count: 18
Load Cycle Count: 8
The smart stats you posted are fine, but this is not:
- 2016-06-13 06:40:31: [2234330.419804] md/raid:md1: Disk failure on sdb2, disabling device.
- 2016-06-13 06:37:58: [2234177.455464] md/raid:md127: Disk failure on sdb3, disabling device.
- 2016-06-13 06:37:53: [2234172.500388] md/raid1:md0: Disk failure on sdb1, disabling device.
And all those bad page states are clearly issues too.
Based on the bad page errors, I am thinking this is more likely a memory problem than a disk problem. You might try contacting support.
I've contacted support now and they are suppose to get back to me soon. Not really sure what they can do but I hope its an easy fix.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
