x86 homebrew OS6 development: no warranty/support

[howarddavidp]

I have a Pro 6 RNDP6000-200 that I am going to redo this weekend, and hopefully end up with NOS ver. 6.x.

Wish me luck!

Dave

[dejhon]

Has anyone else been having issues with their Pro6 on OS 6?

I'm on 6.4.1 and have to constantly reboot the Pro. It will often drop off the network and I won't be able to access frontview via the name or ip address (static ip).

Only running Plex, Transmission 3 (2.82) and SickRage from RNXtras.

I'm so over needing to babysit this this constantly and any help would be GREATLY appreciated!

[petermac]

No real problems except for fan speeds dropping to zero and ReadyCloud stopping working (and of course there are no diags to figure out why it doesn't work and nothing of course from Netgear)

[dejhon]

---

@petermac wrote:
No real problems except for fan speeds dropping to zero and ReadyCloud stopping working (and of course there are no diags to figure out why it doesn't work and nothing of course from Netgear)

---

How much RAM do you have in your NAS?

[dejhon]

Just clicked diagnostics in RAIDar and I got:

  
Successfully completed diagnostics
System
Disk 3 has 1 Current Pending Sectors
Logs
2015-12-20 17:55:16: general protection fault: 0000 [#1] SMP 
2015-12-20 17:55:16: RIP [ ] poll_freewait+0x64/0xb0
2015-12-20 08:05:35: BUG: Bad page map in process systemd-journal pte:be24ffffffffffff pmd:10167067
2015-12-20 08:05:35: general protection fault: 0000 [#3] SMP 
2015-12-20 02:56:48: systemd-journal: Corrupted page table at address 7f45f2002408
2015-12-20 02:04:34: RIP [ ] btrfs_update_root+0x27a/0x280
2015-12-20 02:04:33: BTRFS critical (device md127): unable to update root key ******************** *** ********************
2015-12-15 18:26:38: python[5186]: segfault at 0 ip 00007f47a8dfde92 sp 00007f4749fd15d0 error 6 in _io.so[7f47a8df2000+1f000]
2015-12-14 04:34:13: python[4886]: segfault at 0 ip 00007f3086f41e92 sp 00007f30257d0870 error 6 in _io.so[7f3086f36000+1f000]
2015-12-13 10:52:06: BUG: Bad page map in process transmission-da pte:02000000 pmd:88b60067
2015-12-13 09:58:36: BUG: Bad page map in process transmission-da pte:2064fb0000003333 pmd:6b795067
2015-12-13 04:33:30: python[7446]: segfault at 0 ip 00007f568d972e92 sp 00007f562b7d4330 error 6 in _io.so[7f568d967000+1f000]
2015-12-12 04:52:38: python[1049]: segfault at 0 ip 00007fa5e23f8e92 sp 00007fa57ffd5330 error 6 in _io.so[7fa5e23ed000+1f000]
2015-12-11 04:29:12: python[18419]: segfault at 0 ip 00007f7bf7fd3e92 sp 00007f7bafffd330 error 6 in _io.so[7f7bf7fc8000+1f000]
2015-12-10 22:38:13: BTRFS critical (device md127): unable to update root key ################ ### ################
2015-12-10 04:37:49: python[4044]: segfault at 0 ip 00007f16e3c89e92 sp 00007f1681fc95d0 error 6 in _io.so[7f16e3c7e000+1f000]
2015-12-09 04:22:03: python[22648]: segfault at 0 ip 00007fbb49750e92 sp 00007fbaeffe55d0 error 6 in _io.so[7fbb49745000+1f000]
2015-12-08 08:29:00: readynasd[17912]: segfault at 244b500 ip 000000000244b500 sp 00007f089affc658 error 15
2015-12-08 04:26:39: python[10264]: segfault at 0 ip 00007ff076b7fe92 sp 00007ff0337fc330 error 6 in _io.so[7ff076b74000+1f000]

[DanEarman]

I am also having the same problem with the Readynas dropping off the network.   It seems to occur every 1-2 weeks and requires a power off reset to get it back.   I am running Firmware 6.4.1 and only running the BTSync add-on.

[petermac]

How did you get diagnostics in RaiDar, I am running 4.3.8 and I have MAC address, Model, HostName IP address and then boxes for volume status, disk status, UPS and Fan status along with a box for firmware version, at the bottom there is Setup, browse, rescan and Locate. I don't see away to get Diags?

[dejhon]

Are you running the new RAIDar? Or still the original one?

[petermac]

4.3.8, I installed 6 and found the diags button, no luck nothing there, thanks though

[mdgm-ntgr]

Is your NAS connected to a 100Mbit router/switch rather than a gigabit one?

Can you send me your logs?

[dejhon]

Nope, connected via either CAT5e or CAT6 cable to my netgear 24port gigabit rack mount switch which is connected via CAT6 to my netgear R7000.

I would but I appear to be having issues booting into it now! It's not going past boot: I tried doing an OS update but said it could extract, so tried an OS reinstall and now just tried USB recovery... :'(

[mdgm-ntgr]

dejhon,

I'm guessing you did a factory reset and got the could not extract error as a result?

If you are still having issues please see my PM

[dejhon]

---

@mdgm wrote:

dejhon,

I'm guessing you did a factory reset and got the could not extract error as a result?

If you are still having issues please see my PM

---

Just replied to your PM mdgm; once again, you are awesome!

[grimloch]

I'm having the same problem as dejhon and DanEarman.  Were you two able to solve it where your NAS was falling off the network on 6.4/6.4.1?

[Spike1000]

As usual I'm late to the party and am only now looking to upgrade my ReadyNAS Pro 6 and ReadyNAS Business from 4.2.28 to 6.x

What the most stable version of 6.x to move to on legacy hardware? I'm guessing 6.2.4 or 6.3.5 rater than anything older or newer.

Spike

[850t5]

Thanks for this instructions and all the information included. Just upgraded my ReadyNAS Ultra 6 from 4.2.x straight to OS6.4.1 without any issues whatsoever. Previously I just did upgrade the memory from 1GB to 4GB in case there is more demand from OS6.

Overall I was amazed how quick this move to OS6 was acomplished: In less than 20 min I was able to configure and restore data using the OS6 Backup feature. The improvements and additional features that come with OS6 are just great. Now waiting for the volume to complete resyncing in the background, which is estimated with 24h (6x 3TB WD Red Disks). But the great thing is that I'm aready able to use the NAS for data restore, app install, media streaming, TimeMachine backups, configure accounts, all without restart... love it!

[Spike1000]

I've done some experimentation with a 4.x to 6.x upgrade but came across an wierd issue.

Looking at the 6.x bin files here:

readynas dot com/contributed/mdgm/r4tor6/

R4toR6 Files
16 objects in this folder, 899.9 MB total.

Sort: Name, Type, Size, Date

 R4toR6_6.1.4.bin        60.8 MB    Nov-30-15
 R4toR6_6.1.8.bin        60.8 MB    Nov-30-15
 R4toR6_6.1.9.bin        60.8 MB    Nov-30-15
 R4toR6_6.2.0.bin        60.8 MB    Nov-30-15
 R4toR6_6.2.1.bin        60.8 MB    Nov-30-15
 R4toR6_6.2.2.bin        60.8 MB    Nov-30-15
 R4toR6_6.2.3.bin        60.8 MB    Nov-30-15
 R4toR6_6.2.4.bin        60.8 MB    Nov-30-15
 R4toR6_6.3.5.bin        60.8 MB    Nov-30-15
 R4toR6_6.4.0.bin        60.8 MB    Nov-30-15
 R4toR6_6.4.1.bin        60.8 MB    Nov-30-15
 R4toR6_latest-beta.bin    60.8 MB    Nov-30-15
 R4toR6_latest.bin        60.8 MB    Nov-30-15
 
I've downloaded a few to test but they all appear to be the same 6.4.1 image despite the different filenames.
 
They have the same internal header eg:
R4toR6_6.2.4.bin
info::name=RAIDiator-x86,version=4.2-6.4.1,time=1448489595,size=63780864,md5sum=c3b5d436a13d2edf7e30ece5219eebb8,arch=x86,descr=ReadyNASOS
R4toR6_6.3.5.bin
info::name=RAIDiator-x86,version=4.2-6.4.1,time=1448489595,size=63780864,md5sum=c3b5d436a13d2edf7e30ece5219eebb8,arch=x86,descr=ReadyNASOS
 
Even the MD5 hashes are the same:
01813b9cc7fd95500d6083fbab3f9d10 *R4toR6_6.2.4.bin
01813b9cc7fd95500d6083fbab3f9d10 *R4toR6_6.3.5.bin

When I tested an upgrade (R4toR6_6.3.5.bin) it installed 6.4.1. . . .

Has something gone wrong with the repostitory or is 6.4.1 the only version to upgrade to now?
 
Spike

[mdgm-ntgr]

I symlinked the older filenames to the 6.4.1 image.

I still have some old R4toR6 upgrade images archived, but generally it's best to go straight to the latest R6 firmware.

[Spike1000]

---

@mdgm wrote:

I symlinked the older filenames to the 6.4.1 image.

I still have some old R4toR6 upgrade images archived, but generally it's best to go straight to the latest R6 firmware.

---

Ah, ha. That'll explain it. Looks like 6.4.1 is the version to use then. Wading through the 1200+ posts on this topic and reading about the 'challenges' on the way it wasn't clear all was good with the latest version. Many thanks for your speedy reply and your time spent creating the images and helping the community.

Cheers

Spike

[DanEarman]

Grimloch,   I am still having issues with my ReadyNAS pro dropping off the network.   However, I saw a reference that the 6.4.2 Beta is supposed to resolve at least one set of lockups.   At this point, I am planning to wait for the official version to come out and then give it a try.

[mvrana]

---

@DanEarman wrote:

I am also having the same problem with the Readynas dropping off the network.   It seems to occur every 1-2 weeks and requires a power off reset to get it back.   I am running Firmware 6.4.1 and only running the BTSync add-on.

---

Add me to the list. Though even a power-off reset doesn't seem to do the trick. Right now my Reaynas Ultra 2 is off the WAN network, though I can reach it locally.

[StephenB]

---

@mvrana wrote:

---

Add me to the list. Though even a power-off reset doesn't seem to do the trick. Right now my Reaynas Ultra 2 is off the WAN network, though I can reach it locally.

---

If you are talking about Readycloud, then that is a different problem.

[doctorv1]

I did not see any further messages about this problem.  Any resolution?  I have exactly the same issue on a Pro 6.  Recovery is stuck at "hda-codec:  No codec parser is available".

Thanks in advance for any insight.

[StephenB]

---

@doctorv1 wrote:

I did not see any further messages about this problem.  Any resolution?  I have exactly the same issue on a Pro 6.  Recovery is stuck at "hda-codec:  No codec parser is available".

Thanks in advance for any insight.

---

This is a 128 page thread.  If you have a problem, please open a new thread and tell us the details.  This one is way too tangled for me to have any idea of what "this problem" even is.

[StephenB · Accepted solution]

mdgm and I have decided that its time to lock this thread.  So please do post any new OS6 on Legacy issues on their own threads.