Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 07/06/2021 in all areas

  1. No, but many people forget the prefix "0x" i.e. 0x058F
    1 point
  2. there are xpenology users not having updated for years ... most of the stuff you are worried about should have been answered by yourself before installing xpenology for more then testing "bricking" (its not like that because its still possible to downgrade or do other things) can be prevented by disabling internet access to the ip address of you xpenology box and only installing proven updates manually (or disable access to all domains involved in updating) if security is most important don't use xpenology, you rely on a lot of code from the loader and drivers (or 3rd party packages) that you cant check, you trust a lot of people you dont know anything about and even if you trust them there is no guarantee about 3rd party hacking the one you are trusting or a man in the middle attack you can use open media vault as alternative to xpenology, its even possible to use it temporary by booting omv from a added media (can be usb or hdd), you might need to fix the volume label to mount the dsm data volume with omv but thats not a problem for later using dsm again https://xpenology.com/forum/topic/42793-hp-gen8-dsm-623-25426-update-3-failed/?do=findComment&comment=200475 if you prepare that media you can switch at any time and still access you data by local network beside this its also good to have backup(s), should be normal as beside security/hacking there are also risks with hardware involved (specifically when dsm's ssd cache is involved i'd recommend having recent backup all the time)
    1 point
  3. You can find more info here. I do not know if this post can answer all your questions... For now, while kiler129 still tries to make a new loader to support 6.2.4+ there is hope. He answered also questions about DSM 7... in the post he also said that Synology did not do this on purpose in order to stop XPE...they changed the kernel enough to break the loader. This is all they did and it was not in purpose... Anyway, read the post I believe you will find it very interesting and educational.
    1 point
  4. in dont think so, synology had 7.0 preview/beta for DS3615xs and DS3617xs so people having installed that would not be able to downgrade back to 6.2.4 and should not be able to get 7.0 release? seems unlikely, maybe they will just wait a little longer for some units to release 7.0 [a litltle search on the internet and a few minutes later] "... DSM 7.0 final release for FS, SA, XS/XS+ and DVA series models is currently under development and will be available in Q4 (October – November – December) of 2021. ..." so there is no cpu problem as they will still support older units with 7.0 but as we need a new loader it might depends on the decision of the one making it what unit will be supported but i guess having one that still supports older cpu's will be a thing as a lot of user use older hp microsevers and older server in general maybe if some people haven't seen yet, there is a ongoing effort to document jun's loader and use that knowledge to make a new loader https://xpenology.com/forum/topic/44311-dsm-624-7-loader-major-kernel-changes/ so there is still hope we might see a loader for 6.2.4 or 7.0
    1 point
  5. So I leave 3 days on holidays and everyone forgets the rules... They are rather simple and stated just above the first post. All Off-Topic posts have been moved.
    1 point
×
×
  • Create New...