TOS 5.1.17 (X86) Beta is Released for update
Re: TOS 5.1.17 (X86) Beta is Released for update
I am trying to perform the manual update but the apply button is greyed out. Not sure why...
Re: TOS 5.1.17 (X86) Beta is Released for update
Never mind, I'm dumb. Don't extract the file first! :)
Re: TOS 5.1.17 (X86) Beta is Released for update
Hi Ryan, thanks for responding.
Yes, I had a Crucial 16GB DDR4 3200MHz CL22 1.2V Non-ECC SODIMM installed. Removing this solved the boot cycle.
I tried first removing the hard disk with the Crucial ram on, still same issue.
Removing the Crucial ram solved it.
Next, I tried to downgrade back to 5.1.13 but it wouldn't let me. Is there a guide to downgrade firmware?
Will await the next update to solve this.
Thanks.
TMRyan wrote:
> [quote=wilson post_id=24389 time=1675681139 user_id=6227]
> F2-423 just updated.
>
> It is in endless reboot cycle. 4 beeps and another beep to indicate reboot.
>
> What should I do next?
> [/quote]
> Do you have other brands of memory installed?
> If yes, you need to reinstall the previous version or wait for us to update
> the next system version.
> Does it restart when the hard disk is not inserted?
Yes, I had a Crucial 16GB DDR4 3200MHz CL22 1.2V Non-ECC SODIMM installed. Removing this solved the boot cycle.
I tried first removing the hard disk with the Crucial ram on, still same issue.
Removing the Crucial ram solved it.
Next, I tried to downgrade back to 5.1.13 but it wouldn't let me. Is there a guide to downgrade firmware?
Will await the next update to solve this.
Thanks.
TMRyan wrote:
> [quote=wilson post_id=24389 time=1675681139 user_id=6227]
> F2-423 just updated.
>
> It is in endless reboot cycle. 4 beeps and another beep to indicate reboot.
>
> What should I do next?
> [/quote]
> Do you have other brands of memory installed?
> If yes, you need to reinstall the previous version or wait for us to update
> the next system version.
> Does it restart when the hard disk is not inserted?
Re: TOS 5.1.17 (X86) Beta is Released for update
Hi All!
Reporting that update was easy at F4-422, now running version TOS 5.1.17-00298.
I have 12Gb RAM installed and SSD cache disk.
Only one reboot from shell was need.
On first installation I've use 1Gbe interface and manual installed address .16 dismiss me, main present connection at 10Gbe with .17. I'm just set DHCP for 1Gbe and all fine.
How to track new beta version for download? May be good idea to show it on download page with date of that beta?
Thanks,
Alex
Reporting that update was easy at F4-422, now running version TOS 5.1.17-00298.
I have 12Gb RAM installed and SSD cache disk.
Only one reboot from shell was need.
On first installation I've use 1Gbe interface and manual installed address .16 dismiss me, main present connection at 10Gbe with .17. I'm just set DHCP for 1Gbe and all fine.
How to track new beta version for download? May be good idea to show it on download page with date of that beta?
Thanks,
Alex
Re: TOS 5.1.17 (X86) Beta is Released for update
F4-223 updated to this release and am having issues with Plex hardware transcoding. CPU transcoding works fine but not GPU.
Installed
PlexMediaServer-1.31.0.6654-02189b09f-x86_64_TOS5.tpk
Thanks
Jeff
Installed
PlexMediaServer-1.31.0.6654-02189b09f-x86_64_TOS5.tpk
Thanks
Jeff
Re: TOS 5.1.17 (X86) Beta is Released for update
[quote=jster71 post_id=24417 time=1675789697 user_id=6440]
F4-223 updated to this release and am having issues with Plex hardware transcoding. CPU transcoding works fine but not GPU.
Installed
PlexMediaServer-1.31.0.6654-02189b09f-x86_64_TOS5.tpk
Thanks
Jeff
[/quote]
Also when I restart the NAS my Plex app is disabled until I manually enable it in TOS.. Not sure if it's because it was disabled before the update; that never happened before
F4-223 updated to this release and am having issues with Plex hardware transcoding. CPU transcoding works fine but not GPU.
Installed
PlexMediaServer-1.31.0.6654-02189b09f-x86_64_TOS5.tpk
Thanks
Jeff
[/quote]
Also when I restart the NAS my Plex app is disabled until I manually enable it in TOS.. Not sure if it's because it was disabled before the update; that never happened before