NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Downgrading Readynas from OS 6.10 to 6.9.x
The title says it all. I upgraded and now I cannot compile virtualbox 5.1 using the linux linux-4.4.190-x86_64 kernel. I know the postings say do not, but is there anyway to go back in conjunct...
Thanks.
For anyone else contemplating the same thing:
I just tested this on a virtual NAS. It is not necessary to modify the time. Instead of modifying the length, delete one byte after the header to make up for the one added in the header. To verify everything is aligned, go to 0x4000 and verify that the ASCII data csums.md5 starts exactly at 0x4000.
I called the "update" 6.10.8. The file name doesn't matter, BTW, just how it identifies itself in the file header.
I did not see any immediate issues with access, but funglenn did see Samba issues, so consider that this downgrade may cause you to have to factory default to fix issues caused by downgrading Samba, and act accordingly.
THANK YOU! i used a hex editor and changed the version and padded the time as well.
As expected, the machine would not boot properly--the GUI would not load due to the changes in apache. However after a factory reset, it all came back up nicely as 6.9.4
now to wait for the resync and get back to work! i love this forum!
Sandshark you are amazing.
Thanks.
For anyone else contemplating the same thing:
I just tested this on a virtual NAS. It is not necessary to modify the time. Instead of modifying the length, delete one byte after the header to make up for the one added in the header. To verify everything is aligned, go to 0x4000 and verify that the ASCII data csums.md5 starts exactly at 0x4000.
I called the "update" 6.10.8. The file name doesn't matter, BTW, just how it identifies itself in the file header.
I did not see any immediate issues with access, but funglenn did see Samba issues, so consider that this downgrade may cause you to have to factory default to fix issues caused by downgrading Samba, and act accordingly.
thanks. after a full factory reset back at 6.9.6. I find it to be faster than the 6.10 for the GUI--which is strange as Apache states that the 2.4 upgrade is supposed to be not only security related but also provide for a faster experience. However most importantly, I had lamented the loss of a few apps like GateOne and Tauitulli for Plex.
However funny enough i tried to revert the virtual NAS image from 6.6.0 to 6.3.x and it refused work, even using the tricks that I used for the real Readynas 516.... go figure....
Going back that far, there may be additional checks. I don't think the legacy NAS conversion process on which I based this existed back that far, and maybe the change is even to support that (though it's still unofficial). I think 6.6.x was the current version when I first did it.
Also, I don't believe the VM acts identically to the real NAS (there is no boot loader code for instance).
Actually the VM does use a syslinux boot loader though obviously it doesn't need the custom boot loader code for the various hardware used (LEDs, reset button etc.)
Watching it boot, it appears it uses the standard boot code. I can see it check for a display and some other things, then it goes on when it doesn't find them. It ultimately identifies itself as a VM in the GUI where other NAS have their model number.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
