ReadyNAS Pro 6 general protection fault: 0000 [#2] SMP

[ninjasniper85_]

 should not be that painful i think.

they not a lot of backup only a few files

can do a factory restart maybe during the last week of march

just camera footage anyway always delete every month

re-config should be easy

[ninjasniper85_]

i didn't forgot about this

factory reset is done and doing a memory test that is on 69 hours atm image provide below

[ninjasniper85_]

can i turn of the NAS cause the System already surpass 100+ PASS in Memory Test it already been like a almost a week now

167:05:15 TIme

PSS 132
Err 0

[StephenB]

---

@ninjasniper85_ wrote:

can i turn of the NAS cause the System already surpass 100+ PASS in Memory Test it already been like a almost a week

---

Yes.  It will continue to run until you stop it.

[ninjasniper85_]

alright i will monitor now hopefully it not NAS hardware is failure

[ninjasniper85_]

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at admin@localhost to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

https://pastebin.com/s8sRUXAK kernel 

https://pastebin.com/KfrvG5SK system 1 

https://pastebin.com/PtSxt5cQ system 2 

2023-04-13 18:51:31: general protection fault: 0000 [#8] SMP
2023-04-13 18:51:31: RIP [] kmem_cache_alloc+0x9b/0xea
2023-04-13 18:51:31: general protection fault: 0000 [#9] SMP
2023-04-13 18:51:31: general protection fault: 0000 [#10] SMP
2023-04-13 18:51:31: general protection fault: 0000 [#11] SMP
2023-04-13 18:51:31: general protection fault: 0000 [#12] SMP
2023-04-13 18:51:31: general protection fault: 0000 [#13] SMP
2023-04-13 18:51:31: general protection fault: 0000 [#14] SMP
2023-04-13 18:51:28: general protection fault: 0000 [#7] SMP
2023-04-13 18:51:28: RIP [] kmem_cache_alloc+0x9b/0xea
2023-04-13 18:50:37: general protection fault: 0000 [#6] SMP
2023-04-13 18:50:37: RIP [] kmem_cache_alloc+0x9b/0xea
2023-04-13 18:49:58: general protection fault: 0000 [#5] SMP
2023-04-13 18:49:58: RIP [] kmem_cache_alloc+0x9b/0xea
2023-04-13 18:49:56: general protection fault: 0000 [#3] SMP
2023-04-13 18:49:56: RIP [] kmem_cache_alloc+0x9b/0xea
2023-04-13 18:49:56: general protection fault: 0000 [#4] SMP
2023-04-13 18:49:55: general protection fault: 0000 [#2] SMP
2023-04-13 18:49:55: RIP [] kmem_cache_alloc+0x9b/0xea
2023-04-13 18:49:49: general protection fault: 0000 [#1] SMP
2023-04-13 18:49:49: RIP [] anon_vma_interval_tree_insert+0x2f/0x80
2023-04-13 18:49:11: BUG: Bad page map in process fwbroker.cgi pte:5f02fb00005e0001 pmd:7c1a8067
2023-04-13 18:49:10: BUG: Bad page map in process fwbroker.cgi pte:5000d404ffdd16ea pmd:7c1a8067
2023-04-13 18:49:09: BUG: Bad page map in process fwbroker.cgi pte:3100ffffffffffff pmd:7c1a8067
2023-04-13 18:48:40: BUG: Bad page map in process dbbroker.cgi pte:30000010001000c pmd:7c1aa067
2023-04-13 18:48:39: BUG: Bad page map in process dbbroker.cgi pte:10080819b99aec9 pmd:7c1aa067
2023-04-13 18:48:38: file:libxml2.so.2.9.1 fault:filemap_fault mmap:btrfs_file_mmap readpage:btrfs_readpage
2023-04-13 18:48:37: file:libxml2.so.2.9.1 fault:filemap_fault mmap:btrfs_file_mmap readpage:btrfs_readpage
2023-04-13 18:48:36: BUG: Bad page map in process dbbroker.cgi pte:00007801 pmd:7c1a9067
2023-04-13 18:48:35: file:libnml.so.0 fault:filemap_fault mmap:btrfs_file_mmap readpage:btrfs_readpage
2023-04-13 18:48:34: file:libreadynas.so.0.1.1 fault:filemap_fault mmap:btrfs_file_mmap readpage:btrfs_readpage
2023-04-13 18:48:33: file:libc-2.19.so fault:filemap_fault mmap:btrfs_file_mmap readpage:btrfs_readpage
2023-04-13 18:48:32: file:libc-2.19.so fault:filemap_fault mmap:btrfs_file_mmap readpage:btrfs_readpage
2023-04-13 18:48:31: BUG: Bad page map in process dbbroker.cgi pte:630373616e796461 pmd:7c1ae067
2023-04-13 18:48:30: BUG: Bad page map in process dbbroker.cgi pte:a8c00101a8c0e403 pmd:7c1ae067
2023-04-13 18:48:29: BUG: Bad page map in process dbbroker.cgi pte:c9c0bf54ea331f00 pmd:7c1ae067

[ninjasniper85_]

10 April 2023
Memory Test image below

[StephenB]

---

@ninjasniper85_ wrote:
2023-04-13 18:49:11: BUG: Bad page map in process fwbroker.cgi pte:5f02fb00005e0001 pmd:7c1a8067
2023-04-13 18:49:10🐛 Bad page map in process fwbroker.cgi pte:5000d404ffdd16ea pmd:7c1a8067
2023-04-13 18:49:09: BUG: Bad page map in process fwbroker.cgi pte:3100ffffffffffff pmd:7c1a8067
2023-04-13 18:48:40: BUG: Bad page map in process dbbroker.cgi pte:30000010001000c pmd:7c1aa067
2023-04-13 18:48:39: BUG: Bad page map in process dbbroker.cgi pte:10080819b99aec9 pmd:7c1aa067
2023-04-13 18:48:38: file:libxml2.so.2.9.1 fault:filemap_fault mmap:btrfs_file_mmap readpage:btrfs_readpage
2023-04-13 18:48:37: file:libxml2.so.2.9.1 fault:filemap_fault mmap:btrfs_file_mmap readpage:btrfs_readpage
2023-04-13 18:48:36: BUG: Bad page map in process dbbroker.cgi pte:00007801 pmd:7c1a9067
2023-04-13 18:48:35: file:libnml.so.0 fault:filemap_fault mmap:btrfs_file_mmap readpage:btrfs_readpage
2023-04-13 18:48:34: file:libreadynas.so.0.1.1 fault:filemap_fault mmap:btrfs_file_mmap readpage:btrfs_readpage
2023-04-13 18:48:33: file:libc-2.19.so fault:filemap_fault mmap:btrfs_file_mmap readpage:btrfs_readpage
2023-04-13 18:48:32: file:libc-2.19.so fault:filemap_fault mmap:btrfs_file_mmap readpage:btrfs_readpage
2023-04-13 18:48:31: BUG: Bad page map in process dbbroker.cgi pte:630373616e796461 pmd:7c1ae067
2023-04-13 18:48:30: BUG: Bad page map in process dbbroker.cgi pte:a8c00101a8c0e403 pmd:7c1ae067
2023-04-13 18:48:29: BUG: Bad page map in process dbbroker.cgi pte:c9c0bf54ea331f00 pmd:7c1ae067

These unfortunately do point to hardware, despite the passed memory test.

Do you have other memory you can try?  How much ram is in the NAS now?

[ninjasniper85_]

Sadly i don't have other memory to try but i know it 2x2GB =  4GB stick

[ninjasniper85_]

i did upgrade the RAm and CPU
i did my research first i got this CPU for it

Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz

will check ram and test them 1 by 1 to see how they go for few days when i have time  tmr

[StephenB]

If you have two 2 GB sticks, then I suggest removing one and see if the problem disappears.

If it recurs, then swap with the other stick.

[Sandshark]

Before swapping the processor, did you make sure your BIOS is up to date?  I don't recommend a quad-core processor.  Not sure where you did your research, but many who did that (because they were using it for something that needed more CPU throughput) have found the stock cooling to be insufficient when running those CPU-intensive tasks.  Are you seeing any high CPU temperature warnings?

[ninjasniper85_]

https://pastebin.com/vDmQB761

did you make sure your BIOS is up to date? How do i update the BIOS i try looking for resource and stuff my research on the Netgear Community

Also The only Task running IS FTP
5 Camera POE Image and Video > FTP > NAS

https://pastebin.com/vDmQB761 bios_ver.log

[Sandshark]

Before you worry about updating it, let's see if it's already the latest version.  I  the downloaded log zip, look in bios_ver.log.  The latest is 07/26/2010 FLAME6-MB V2.0.  If yours really is a "Pro6", not an older ProBE or Pro Pioneer, it likely is.

[ninjasniper85_]

FYI i got this a while back on Facebook Marketplace for cheap mostly 6 bay nas goes around $800+ up AUD got this one $100-300 was missing a 2 bay drive but got replacement one cause so one had Duo and it was broken so i bargain with them for the 2 bay

so the Bios Version is 10/03/2008 FLAME6-MB V1.6

[StephenB]

---

@Sandshark wrote:

Before you worry about updating it, let's see if it's already the latest version. 

10/03/2008 FLAME6-MB V1.6 per the link @ninjasniper85_ posted earlier

[ninjasniper85_]

Ram is

Legend  L256423G-PPOS2L2S 2GB DDR2800

1 stick is in the system

1 stick is out of the system

[ninjasniper85_]

MY NAS Model: rndp6350-100nas

[Sandshark]

That's a Pro Business Edition (ProBE), then, not a Pro6.  Pro6 models are -200's.  Same motherboard, different processor.  Though, of course, you've updated yours, anyway.

With that BIOS version, I'm surprised your NAS is booting at all.  I have always believed that the fastest processor that can be used with that old version of the BIOS is an E6600.  I guess I was mistaken that it won't boot with a faster processor, but I do suspect that has a lot to do with your problems.

Frankly, the easiest way to update the bios is to use a spare drive in place of your current drive set to convert the unit back to RAIDiator 4.2.x, then use the Bios update add-on, then revert back to OS6.  That was true even before Debian Jessie became unsupported and you could still easily get the necessary tools to manually update using apt.

[ninjasniper85_]

Frankly, the easiest way to update the bios is to use a spare drive in place of your current drive set to convert the unit back to RAIDiator 4.2.x, then use the Bios update add-on, then revert back to OS6.  That was true even before Debian Jessie became unsupported and you could still easily get the necessary tools to manually update using apt.

Please Step By Step

is this to download? https://kb.netgear.com/000038793/RAIDiator-x86-Version-4-2-31

[StephenB]

---

@ninjasniper85_ wrote:

Please Step By Step

---

https://community.netgear.com/t5/ReadyNAS-Storage-Apps-Current/Downgrade-to-RAIDiator-x86-from-Ready...

[ninjasniper85_]

Thanks Will try this later https://community.netgear.com/t5/ReadyNAS-Storage-Apps-Current/Downgrade-to-RAIDiator-x86-from-Read...

i will try the memory first to see if it the memory or not

i have uptime Kuma to let me know if the any problem network wise if the readynas having problem with network so i will wait to see if one of the ram is bad

[ninjasniper85_]

Well it has been on a while some stuff happen with my internet so i had to restart the readynas so it has been up for 13 days

can still access it 🙂

could be the other ram stick i have is faulty who know 🙂

will keep updates this post but not alot maybe when i check the nas and stuff

[ninjasniper85_]

Ok i swap ram
The last one was in there lasted 14 days Ish+

This one last it 5 hours 😐

so one of the ram is faulty and maybe a hardware is faulty for the https://community.netgear.com/t5/ReadyNAS-Storage-Apps-Current/Downgrade-to-RAIDiator-x86-from-Ready...

is there a video for this? cause my learning styles is different and i am not studying into networking i have a IT Technology  and Telecommunications Technology background this is way out of my zone 😐

going switch the ram again

[StephenB]

---

@ninjasniper85_ wrote:

is there a video for this?

---

Not sure what you are asking for - do you want instructions on downgrading back to 4.2????