PTinTX

Happy New Year 2021! DSM7.0 BETA release is available now from here: https://prerelease.synology.com/en-global/download/dsm70_beta? It does not have DSM7 for DS1511+ (the cousin of DS1010+) but can you please check the beta and if good please release your method to upgrade old NAS to lastest DSM version. Thanks!!!! Bonne Année 2021! La version DSM7.0 BETA est maintenant disponible à partir d'ici: https://prerelease.synology.com/en-global/download/dsm70_beta? Il n'a pas de DSM7 pour DS1511 + (le cousin de DS1010 +) mais pouvez-vous s'il vous plaît vérifier la version bêta et si elle est bonne, veuillez publier votre méthode pour mettre à niveau l'ancien NAS vers la dernière version de DSM. Merci!!!!

Honestly i got tired of waiting so I decided to try myself.... I failed but not completely. This was my experience (and likely how simkard also proceeded): 1) I tried first with the latest 6.2 build for 1511+ and in short after edits (which will be described below) when trying to update via manual update in DSM it said it failed and to try an earlier v6.0.1 build 7321 which I did and points below is what I did with this build. NOTE: I had to uninstall the current plex package as a warning told me to do so because it was incompatible with the v6 build I was using. 2) depacked the .pat file as it's just a renamed tar 3) Modified the VERSION and GRUB_VER files; basically replaced any 1511 with 1010 4) using last step mentioned in https://xpenology.com/wiki/en/building_xpenology and using the synochecksum from https://github.com/andy928/synochecksum I updated the checksum.syno file with the new checksums (and totals on the bottom line if needed). NOTE: I did not do part 3 "synobios modification". 5) packed in all back together into a tar and renamed to pat. 6) used manual install on the DSM 5.2 and gave it this modified pat file.... it ran all the way to 100% and then the 1010+ rebooted. 7) when it came back up it give me the flashing orange. connecting to it via browser it open web synology assistant, it showed me a migration page like as if I was migrating the disks/volume from a 1511+ to a 1010+, incidentally it was also showing the device info as running DSM 6 (pc synology assistant also showed it running DSM 6 but with "migratable" as status) 8 ) tried to migrate with "keep settings" asked for a pat file again gave it the same modified one and it failed; tried without keep settings and still failed. 9) I then started to try roll back changes which is a nightmare if you go in blindly. 10) rollback step 1, you need to get telnet enabled, which I found could be done by pc synology assistant when you tell it to install and give it a unmodified pat file and which fails and then opens telnet port for diagnostics (there may be other ways to do this see next step). NOTE: usually the clock resets and the default root password is 101-0101 BUT if you take too long the clock may update along with password (see this for what to do: https://wiki.mbirth.de/know-how/hacking/synology-telnet-password.html but perhaps just easier to reboot and be faster next time) 11) rollback step 2, using steps in this https://www.reddit.com/r/synology/comments/64eu39/downgrading_synology_dsm_61_to_52_and_then_to_602/ and the DSM 5.2 for 1010+ pat 12) used web synology assistant and gave it the the unmodified 1010+ pat file; "downgrade" worked and when the 1010+ rebooted it was back to normal, volume was there, data was there ... it's as if nothing had happened (save that plex was uninstalled ) Perhaps this is where simkard got to before he tried to engage xpenology community. Perhaps the synobios modification is needed I don't know. I don't know how long @simkard is going to keep us waiting and while I understand that yes in the past hackers have held back the exploit because of an imminent new release of xxxx, they don't keep it indefinitely (and usually when there is STRONG evidence that a new release is coming with DAYS/WEEKS not MONTHS see https://www.youtube.com/watch?v=l5sLB1nCNQY&feature=youtu.be directly from Synology PLM they say end of this year!) and it would be more beneficial for the community of everyone at least gets 6.2 now than waiting for DSM 7. It's a cat and mouse game, leave the problem of getting DSM 7 for another day, if synology do indeed close the initial exploit. It maybe that DSM 7 on day 1 would not be vulnerable to the exploit regardless....