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 showed the message "mv_xor_status +88". I tried to reboot it but it wouldnt respond. I pulled the power and now it wont boot properly. Now i get the meesage "kmem_cache_alloc+5c". What do I do?!?!

Nienkerk wrote:Okey, I have factory reseat the system now. It's says it resynch my system and it supposed to take 80hours, that seems to be a very long time for file system structure. Don't you think? It's not creating a file system - it is computing and writing the RAID array parity blocks. Every disk sector of every drive is either read or written. This is needed even if the file system is empty.

Hello Nienkerk, As mdgm requested, please provide the model number of your NAS and its FW version. Also, answers to the following questions will help us: How many disks are currently inserted? What is the size of each? Please include brand and make. Do you have full backup of the data? Does RAIDar still detect the NAS? Where exactly do you see the error messages? Regards,

Nienkerk wrote:I fint know what RAIDar is RAIDar is a PC app that can make it easier to manage your NAS. You'll find it here: http://kb.netgear.com/app/answers/detail/a_id/20684/~/readynas-downloads#raidar

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.

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.

Front Panel Shows error "kmem_cache_alloc+5c" - #27013537

21 Replies

Replies have been turned off for this discussion

mdgm-ntgr
NETGEAR Employee Retired
Jun 14, 2016
Which model is this on and which firmware?

Can you elaborate on what you have done recently (i.e. what disks were installed before you started replacing/adding disks and what disks are installed now)?
Nienkerk
Aspirant
Jun 14, 2016
I hade replaced two 1tb disks with four 4tb disks. I have done it one at a time and let the system resynch after each disk. Last night I read that it was on 96% on the last disk and when I woke up it showed the first message. I tried to connect but nothing happened so I tried to push the power switch but nothing happens so I cut the power. When it booted up I got the second message.
- JennC
  NETGEAR Employee Retired
  Jun 14, 2016
  Hello Nienkerk,
  
  As mdgm requested, please provide the model number of your NAS and its FW version.
  
  Also, answers to the following questions will help us:
  
  How many disks are currently inserted?
  
  What is the size of each? Please include brand and make.
  
  Do you have full backup of the data?
  
  Does RAIDar still detect the NAS?
  
  Where exactly do you see the error messages?
  
  Regards,
  - Nienkerk
    Aspirant
    Jun 15, 2016
    Hi again!
    
    I have installed RAIDar now and run diagnostics and this is the log.
    
    Logs
    
    2016-06-14 19:05:35: BUG: Bad page state in process kworker/u2:4 pfn:173b3
    
    2016-06-14 19:05:25: BUG: Bad page state in process udevd pfn:173b8
    
    2016-06-14 16:20:33: BUG: Bad page state in process udevd pfn:19e40
    
    2016-06-14 16:20:32: BUG: Bad page state in process kworker/u2:3 pfn:19e42
    
    2016-06-14 07:20:45: flags: 0x200(arch_1)
    
    2016-06-14 07:20:44: BUG: Bad page state in process mount pfn:177b8
    
    2016-06-13 21:57:15: [2289330.634689] BUG: Bad page state in process python pfn:0f344
    
    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.
    
    2016-06-12 10:04:40: [2160182.488173] BUG: Bad page state in process copy pfn:1024a
    
    2016-06-12 00:03:34: [2124116.874766] BUG: Bad page state in process btrfs-cleaner pfn:06ba6
    
    2016-06-12 00:03:32: [2124114.725545] BUG: Bad page state: 39 messages suppressed
    
    2016-06-11 12:16:18: [2081672.912577] BUG: Bad page state in process Plex DLNA Serve pfn:1a497
    
    2016-06-11 12:16:17: [2081672.855261] BUG: Bad page state in process sabnzbd pfn:029f1
    
    2016-06-11 12:16:12: [2081672.830894] page:dfc4e9a0 count:0 mapcount:0 mapping: (null) index:0x2
    
    2016-06-11 12:16:11: [2081672.830872] BUG: Bad page state in process systemd-journal pfn:088a4
    
    2016-06-11 12:16:08: [2081672.791480] page:dffe93f8 count:0 mapcount:0 mapping: (null) index:0x2
    
    2016-06-11 12:16:07: [2081672.791457] BUG: Bad page state in process Plex Media Serv pfn:1f9b3
    
    2016-06-11 12:16:03: [2081668.528518] BUG: Bad page state in process kworker/u2:0 pfn:1c378
    
    2016-06-11 12:15:57: [2081661.971039] BUG: Bad page state in process sabnzbd pfn:137e1
    
    2016-06-11 12:15:56: [2081661.694890] BUG: Bad page state in process sabnzbd pfn:13608
    
    2016-06-11 12:15:55: [2081661.304119] BUG: Bad page state in process sabnzbd pfn:08f2c
    
    2016-06-11 12:15:52: [2081657.676397] BUG: Bad page state in process sabnzbd pfn:07b31
    
    2016-06-11 12:15:49: [2081655.329149] BUG: Bad page state in process sabnzbd pfn:1659a
    
    2016-06-11 12:15:48: [2081653.986193] BUG: Bad page state in process readynasd pfn:0781e
    
    2016-06-11 12:15:46: [2081651.576489] BUG: Bad page state in process sabnzbd pfn:09b82
    
    2016-06-11 12:15:44: [2081650.163043] BUG: Bad page state in process sabnzbd pfn:0f425
    
    2016-06-11 12:15:43: [2081649.313060] BUG: Bad page state: 1101 messages suppressed
    
    2016-06-11 12:14:55: [2081590.465941] BUG: Bad page state in process Plex DLNA Serve pfn:1a61c
    
    2016-06-11 12:14:54: [2081589.531603] BUG: Bad page state in process sabnzbd pfn:08433
    
    2016-06-11 12:14:53: [2081589.076022] BUG: Bad page state in process sabnzbd pfn:08871
    
    2016-06-11 12:14:52: [2081589.003693] BUG: Bad page state in process sabnzbd pfn:1a5b6
    
    2016-06-11 12:14:51: [2081588.976008] flags: 0x200(arch_1)
    
    2016-06-11 12:14:50: [2081588.976002] bad because of flags:
    
    2016-06-11 12:14:49: [2081588.975993] page dumped because: PAGE_FLAGS_CHECK_AT_PREP flag set
    
    2016-06-11 12:14:48: [2081588.972369] flags: 0x200(arch_1)
    
    2016-06-11 12:14:46: [2081588.965321] BUG: Bad page state: 781 messages suppressed
    
    2016-06-11 12:13:55: [2081530.759633] BUG: Bad page state in process python pfn:0c1e1
    
    2016-06-11 12:13:54: [2081529.594178] BUG: Bad page state in process Plex DLNA Serve pfn:120a6
    
    2016-06-11 12:13:53: [2081528.948428] BUG: Bad page state in process Plex Media Serv pfn:0b723
    
    2016-06-11 12:13:51: [2081528.944476] flags: 0x200(arch_1)
    
    2016-06-11 12:13:50: [2081528.944471] bad because of flags:
    
    2016-06-11 12:13:49: [2081528.944463] page dumped because: PAGE_FLAGS_CHECK_AT_PREP flag set
    
    2016-06-11 12:13:47: [2081528.940907] flags: 0x200(arch_1)
    
    2016-06-11 12:13:46: [2081528.933736] page:dfc3ea28 count:0 mapcount:0 mapping: (null) index:0x2
    
    2016-06-11 12:13:43: [2081528.933713] BUG: Bad page state in process Plex Media Serv pfn:08241
Nienkerk
Aspirant
Jun 15, 2016
4 disk (4tb WD Red PRO)
I think i can get full backup of the data.
I fint know what RAIDar is
On the display on the box

I got the box running yesterday and turned all the apps off. I reinstalled and rebooted the device. Then I let it continue with the reshape of data on the last disk. Got a error message this morning again "mv_xor_status+88". I couldn't connect to it so I pulled the plug again. What do i do now?
- StephenB
  Guru - Experienced User
  Jun 15, 2016
  Nienkerk wrote:
  
  I fint know what RAIDar is
  
  RAIDar is a PC app that can make it easier to manage your NAS. You'll find it here: http://kb.netgear.com/app/answers/detail/a_id/20684/~/readynas-downloads#raidar
  - Nienkerk
    Aspirant
    Jun 15, 2016
    Do you think this problem has to do with the HDDs or the OS?
    
    Can RAIDar help me?
Nienkerk
Aspirant
Jun 17, 2016
Okey, I have factory reseat the system now. It's says it resynch my system and it supposed to take 80hours, that seems to be a very long time for file system structure. Don't you think?
- StephenB
  Guru - Experienced User
  Jun 17, 2016
  Nienkerk wrote:
  Okey, I have factory reseat the system now. It's says it resynch my system and it supposed to take 80hours, that seems to be a very long time for file system structure. Don't you think?
  
  It's not creating a file system - it is computing and writing the RAID array parity blocks. Every disk sector of every drive is either read or written. This is needed even if the file system is empty.
Nienkerk
Aspirant
Jun 17, 2016
The good news is that, because of these problems, I've learned a lot about my little NAS. Even though it's been a long week with lots of new words.

Forum Discussion

Front Panel Shows error "kmem_cache_alloc+5c" - #27013537

21 Replies

Related Content

Front display control

RNDU 2000 connection impossible front view

RN424 Front Panel funktioniert nicht

Domain Fronting / Inability to Block Sites

Front View not rendering for ReadyNAS Ultra 6

NETGEAR Academy

ProSupport for Business