Decebalus

Since I have installed from scratch 6.2.3 using June's loader 1.03b for 3615xs on one of my old machines, I was wondering what would be the best approach to upgrade to 6.2.3 for those of us who have custom extra.lzma. Would it make sense to boot up with the current USB stick containing custom extra.lzma and after booting up, taking out the stick, reimage it with original June's 1.03b loader (and modifying grub.cfg accordingly, of course), plugging it back in the USB port, install manually 6.2.3 from Control Panel and reboot? Sorry, it may be a stupid question but I have never went through a similar process before. Any suggestions are definitely appreciated and I hope this will help others in similar situation. Thanks in advance!

I am wondering what made them decide to revert back to older driver support. Just asking, not complaining 😀. I pray we will be so lucky with DSM 7.0 - I know, it's a very long shot but still...

I can also can confirm that djvas335 is right! I have installed 6.2.3 using June's loader version 1.03b unmodified (original extra.lzma, rd.gz and zimage) and installing DSM_DS3615xs_25423.pat. That is on a very old hardware using Asus P5Q motherboard. Everything seems to be working fine. I will report later if I encounter any issues. djvas335, thank you so much for mentioning this!

IG-88, I just wanted to say that you are GOD when it comes to trying to keep compatibility with older hardware and I cannot express enough my gratitude and appreciation for all the work you have been doing and the time invested in this! I am sure I am not the only one appreciating all your work, time and dedication. Hats off in front of you and thanks a million, my friend! YOU ROCK!

I apologize up front if this has been clarified/mentioned by someone else, however, I can confirm that it is possible to upgrade from 6.1.7 directly to 6.2.2 using IG-88's extra.lzma without losing the data, by choosing "Reinstall DSM" option and selecting 6.2.2 pat file mentioned by IG-88 in his first post. It goes w/o saying that you will have to reinstall all packages, users, configuration but you are saving a ton of time by not having to restore the data. As I stated previously in one of my replies in this post, I was not able to go through a migration process successfully from 6.1.7 to 6.2.2 but choosing the option to reinstall the DSM worked flawlessly. I have used that approach successfully on my last 2 NAS' that had 6.1.7 (one of them is so old that it has a Q9500 CPU) and are now running happy on 6.2.2. Hope that helps.

Thank you. Yup, got it today and confirmed it’s fine.

Hi IG-88, Sorry to bother you - just have a quick question: do you expect this SATA controller to be compatible with 6.2.2? https://www.amazon.ca/dp/B081DM6Y9L/ref=pe_3034960_236394800_TE_dp_1 I can't tell if it has a port multiplier or not (even though each SATA port is placed separately on the board). Thanks in advance for your help, as always.

I would suggest to contact IG-88 first based on the below. I would see if that works first. I was not able to complete the upgrade and ended up with a fresh install after which I copied back the data (had backups). On 1/27/2020 at 11:38 AM, IG-88 said: if you still have the usb in the state as it was after the 6.2.2 update (dont mind the different 0.6 extra.lzma) the you could just copy a new "recovery" extra.lzma version to the usb and all problems solved - i will send you a link to that new beta version, i had one tester with a N3150 and he solved the problems with it

See my posts earlier in this thread regarding updating from 6.1.7 to 6.2.2. I had the same issues and I ended up performing a fresh install.

For 1., make sure that the VID and PID values on the USB stick in the grub.cfg file are correct. Normally “file is corrupt” message is related to those values not being correct. For 2., how did it successfully migrate if you got the file is corrupt message?

If this has started after the upgrade, slim chance it's the MB. Too much of a coincidence...

Correct, IG-88. Mainly those were Synology packages and, in fact, File Station was one of them I had issues with. In any case, absolutely no issues with a fresh 6.2.2 install.

Another update: server has been syncing the data all night long with 0 issues, no network dropouts (including VPN connection) and no error logs. Stable as expected. At this point I can state that using IG-88’s extra.lzma and steps work perfect for a fresh install bare metal on HP Microserver gen8 without the need of 6.2 compatible NIC. Thank you, IG-88! I would not recommend to perform a direct upgrade from 6.1.7 to 6.2.2 if you have a lot of packages but that is a DSM issue and has nothing to do with IG-88’s work. Hope this helps.

I gave up on the migration and here are the reasons why: 1. I had a lot of packages, more than 15-20 installed, including docker. 2. While the containers in docker were the easiest to update with the latest docker API, a number of packages did not start and, what is worse, I was not even able to uninstall them 3. The packages I was able to start manually (including Synology packages) ended up stopping after a while. In fact, a couple of times I noticed that all packages started manually, stopped after a while 4. I have noticed random network dropouts and trying to open Control Panel would kill the session. In fact, I was not able to open control panel once. In conclusion, the system was not stable and it may be related to the direct jump from 6.1.7 to 6.2.2 that might have affected the packages which might’ve caused the instability of the system. I remember seeing in the past that Synology prompted to install a version between updates. Maybe this is the case here as well but I am just speculating. As a result, I have performed a fresh 6.2.2 install with the same USB image and the system has been rock solid after 1TB of data transfer. I have also installed most of the packages that I had previously without any issues. I will leave the system overnight to complete the data restore from another backup NAS and will provide another update tomorrow once it has been completed. Bottom line, if you have a significant number of packages installed, the direct jump from 6.1.7 to 6.2.2 may cause problems or maybe it’s just me. Hope the above will help others and a ton of thanks again to IG-88 for his tremendous help!

OK. Tried to do the migration without success at this point. A few things that I have noticed: 1. Despite that the fresh install worked like a charm and the server rebooted during the installation process and ended up with the latest Update 4 for 6.2.2, this did not happen during the migration (using the same USB stick, haven't changed anything). After 10 mins, the server ended up off the network and I had to reboot it manually 2. After the reboot, the DSM version is 6.2.2-24922 only (no update version) 3. I have tried this several times: once I reboot (or boot up) the server, it shows on the network for approx. 5 min; even the login page comes up. However, after that it drops off the network. If I try to log in through the login page during those 5 mins, it says "Loading..." but I am not able to get to the Synology home page 4. Now, the interesting part: while the server does not show on the network in Synology Assistant or find.synology.com, I am able to connect to it through the DSM mobile app. However, when I try to go to the Firmware option and tries to check for the most recent update (I am expecting to find Update 4), it throws an error message "Connection failed. Verify your network connection" or something similar. With that said, I can see on the mobile app that the data is still there. While I will be trying more things, I have a question: does the "Reinstall" option in Jun's loader wipe the data on the drives? I was wondering if I can use that to try to reinstall 6.2.2. Any suggestions/recommendations regarding the nest steps you think I should try, are more than welcome.

fully agreed. In that case, I am not sure why the other 2 members have experienced issues with the add-ons. Doesn’t really make sense to me unless I am missing something. The only situation that may occur would be when changing the model of Synology during the upgrade, perhaps. With that said, I think I will still proceed with the migration and report back. Thanks a million, IG-88!

Did you have any add-ons/packages installed on 6.1.7? If yes, did you encounter any issues with those after the upgrade to 6.2.2?

Interesting. I do have a lot of add-ons. Since I have already ordered a N360T NIC before I performed this testing, should I wait to install the NIC and use Jun’s 1.03b loader with the 6.2.2 pat without copying the files to the 2nd partition then? What would you recommend?

Never mind. Already tested it and I can confirm internal NICs are recognized. See here for more details.

Great work, IG-88! You rock! On my side, I can report that the fresh install on my HP Gen8 micro server went smooth like butter. Used one HDD and new USB to test the installation. Both built-in NICs are recognized. A note that during the DSM install, the server rebooted by itself before I was able to go through the set up process. I am sure that's expected but I wanted to throw it out there as an FYI. With that said, it seems to me that DSM automatically updated to the latest version (Update 4) which, if that's the case, that's great. Copied extra.lzma, rd.gz and zImage files to 2nd partition (the 30MB size one), as per instructions. One question though: should I understand that for the minor updates under 6.2.2 we should be good with the USB created and those may be required again only for major updates in the future? Next step would be to test the migration from 6.1.7 to 6.2.2. I will provide update once completed. Hardware: HP Microserver Gen8 micro Bootloader: 1.03b DSM Version: 6.2.2 24922 Update 4 Install Method: Fresh install

Hi, First, thank you for creating this thread. Having also a HP gen8 with the latest 6.1.7 DSM, the question I have is around the use of custom extra.lzma. I have noticed that quite a number of people are using a custom extra.lzma with June 1.03b loader and are able to use the NICs on the server. Should I understand that following the instructions from the thread below will work to upgrade to 6.2.2 without compatible NIC? Has anyone from this thread tried it successfully?