meimeiriver Posted February 26, 2017 Share #2001 Posted February 26, 2017 Just migrated one of my "test" bare metal boxes from jun's v1.01 loader running 6.02-8451 Update 9 to jun's v1.02-Alpha loader running 6.1-15047. Migration to DSM 6.1-15047 completed without error. Testing of packages begins. Thanks jun. Thanks for the feedback. I will be using this method then. Quote Link to comment Share on other sites More sharing options...
Rusty Posted February 26, 2017 Share #2002 Posted February 26, 2017 No good for me upgrading either. HP Gen8 Microserver... boots up, lots of drive activity, no network though. Guess I'll try the clean install, it doesn't hurt the data anyway. Quote Link to comment Share on other sites More sharing options...
boOmLa Posted February 26, 2017 Share #2003 Posted February 26, 2017 Just migrated one of my "test" bare metal boxes from jun's v1.01 loader running 6.02-8451 Update 9 to jun's v1.02-Alpha loader running 6.1-15047. Migration to DSM 6.1-15047 completed without error. Testing of packages begins. Thanks jun. Hi, is there a step by step to the migration u did, i would like to migrate. I use to clean install running now jun's 1.01 loader dsm 6.02-8451 Update 9. thanx in advanced .. Quote Link to comment Share on other sites More sharing options...
dr_drache Posted February 26, 2017 Share #2004 Posted February 26, 2017 Quck update... 1.02Alpha doesn't support LSI 2xxx cards - it never boots after initial installation; remove the card and you get the "please install harddrives" message. Quote Link to comment Share on other sites More sharing options...
Rusty Posted February 26, 2017 Share #2005 Posted February 26, 2017 "Clean" install went fine. As nothing is deleted you can copy the /volume1/@appstore/*/var directory from your apps somewhere and restore it back. Slower than an upgrade, but not difficult by any stretch. Quote Link to comment Share on other sites More sharing options...
Trantor Posted February 26, 2017 Share #2006 Posted February 26, 2017 Clean OP, add link to Pokanskiman's tutorial and add download mirror. DMS 6.1 uses updated kernel (3.10.102). The kernel sources for 6.0.2 (3.10.77) has not been released yet so don't hope anything from Syno before months. Like before no sources = no loader jun's v1.01 loader CAN'T support DSM 6.1 so DO NOT UPGRADE ! I've rebased the vendor changes on 3.10.77 to 3.10.102, seems still works. jun your are the MAN Next step is I think to troubleshoot the network issue on some system that "prevent" network driver to load at boot. How can I (or the community) help you to debug ? How do you display/access the early boot stage without serial console ? Quote Link to comment Share on other sites More sharing options...
FiberInternetUser Posted February 26, 2017 Share #2007 Posted February 26, 2017 Just migrated one of my "test" bare metal boxes from jun's v1.01 loader running 6.02-8451 Update 9 to jun's v1.02-Alpha loader running 6.1-15047. Migration to DSM 6.1-15047 completed without error. Testing of packages begins. Thanks jun. Hi, is there a step by step to the migration u did, i would like to migrate. I use to clean install running now jun's 1.01 loader dsm 6.02-8451 Update 9. thanx in advanced .. I believe there have been others who have written tutorials on migration. Polanskiman has written an excellent migration guide taking you from 5.2 to 6.0. The general idea is the same going from 6.0 to 6.1. http://xpenology.com/forum/viewtopic.php?f=2&t=22100 Please read his turorial. It is an excellent guide. This is just a quick summary of what I did to perform the migration. 1. I created a new boot thumb drive using jun's v1.02-Alpha loader. I won't go into detail but this means you need to update the vid, pid, s/n, mac, etc. in the grub.cfg file. 2. I powered down the "test" bare metal box that was running jun's v1.01 loader and DSM 6.02-8451 Update 9. 3. I powered up the "test" bare metal box with the thumb drive I created in step 1. 4. After powering up, you can use either Synology Assistant or "find.synology.com" to find your system. If your system is not found then jun's v1.02-Alpha loader doesn't contain a driver for your network card. Go back to your original thumb drive containing jun's v1.01 loader, boot from it and you should be back to DSM 6.02-8451. 5. If your system is found and you are connected via a web browser, you will be presented with a screen which will step you through the migration of updating the DSM that is installed on your hard drives. 6. After following the instructions, DSM 6.1 will be downloaded from Synology and your system will reboot. 7. When it comes up, you should be on DSM 6.1-15047 Caveat, YMMV, my "test" box has an intel cpu and legacy bios, jun's v1.02 - Alpha Loader had the driver for my network card. Important: Backup your data before trying. Quote Link to comment Share on other sites More sharing options...
boOmLa Posted February 26, 2017 Share #2008 Posted February 26, 2017 Just migrated one of my "test" bare metal boxes from jun's v1.01 loader running 6.02-8451 Update 9 to jun's v1.02-Alpha loader running 6.1-15047. Migration to DSM 6.1-15047 completed without error. Testing of packages begins. Thanks jun. Hi, is there a step by step to the migration u did, i would like to migrate. I use to clean install running now jun's 1.01 loader dsm 6.02-8451 Update 9. thanx in advanced .. I believe there have been others who have written tutorials on migration. Polanskiman has written an excellent migration guide taking you from 5.2 to 6.0. The general idea is the same going from 6.0 to 6.1. http://xpenology.com/forum/viewtopic.php?f=2&t=22100 Please read his turorial. It is an excellent guide. This is just a quick summary of what I did to perform the migration. 1. I created a new boot thumb drive using jun's v1.02-Alpha loader. I won't go into detail but this means you need to update the vid, pid, s/n, mac, etc. in the grub.cfg file. 2. I powered down the "test" bare metal box that was running jun's v1.01 loader and DSM 6.02-8451 Update 9. 3. I powered up the "test" bare metal box with the thumb drive I created in step 1. 4. After powering up, you can use either Synology Assistant or "find.synology.com" to find your system. If your system is not found then jun's v1.02-Alpha loader doesn't contain a driver for your network card. Go back to your original thumb drive containing jun's v1.01 loader, boot from it and you should be back to DSM 6.02-8451. 5. If your system is found and you are connected via a web browser, you will be presented with a screen which will step you through the migration of updating the DSM that is installed on your hard drives. 6. After following the instructions, DSM 6.1 will be downloaded from Synology and your system will reboot. 7. When it comes up, you should be on DSM 6.1-15047 Caveat, YMMV, my "test" box has an intel cpu and legacy bios, jun's v1.02 - Alpha Loader had the driver for my network card. Important: Backup your data before trying. Tahnx alot for your fast reply and clearing things up for me - looking into it now Quote Link to comment Share on other sites More sharing options...
Cs-Freak Posted February 26, 2017 Share #2009 Posted February 26, 2017 Thanx Jun for the newest loader 1.02-alpha and Polanskiman for his tutorial how to install. Its working like a charm on my Supermicro X11SAE-M motherboard with a i5 6400T / 16Gb DDR4. And still no bugs found on this release Quote Link to comment Share on other sites More sharing options...
stelle007 Posted February 26, 2017 Share #2010 Posted February 26, 2017 Hi. Just opgraded my test server, to 6.1 (Intel S1200BTL Board), Network working fine, and also, Jumbo Frames works perfect, it didn't work on 1.0.1. Very happy about it working now now I can try Clustering. I also have issue with Broadcom Nic's, don't show up in DSM Thanks for your great work June. Quote Link to comment Share on other sites More sharing options...
dr_drache Posted February 26, 2017 Share #2011 Posted February 26, 2017 Quck update... 1.02Alpha doesn't support LSI 2xxx cards - it never boots after initial installation; remove the card and you get the "please install harddrives" message. I was wrong - after using the OVF download in another thread - everything is perfect. this was an user error (mine). Quote Link to comment Share on other sites More sharing options...
jay101uk Posted February 27, 2017 Share #2012 Posted February 27, 2017 Anyone able to point me to a step by step guide to install 6.1 as a VM in VMware using the new bootloader? Quote Link to comment Share on other sites More sharing options...
chege Posted February 27, 2017 Share #2013 Posted February 27, 2017 Anyone able to point me to a step by step guide to install 6.1 as a VM in VMware using the new bootloader? Just create standard linux VM and add synology.vmdk as 1st hdd. I had to do nothing more than that to run it on ESXI 6. On VM start you need to choose ESXI option from grub Quote Link to comment Share on other sites More sharing options...
jun Posted February 27, 2017 Author Share #2014 Posted February 27, 2017 Clean OP, add link to Pokanskiman's tutorial and add download mirror. DMS 6.1 uses updated kernel (3.10.102). The kernel sources for 6.0.2 (3.10.77) has not been released yet so don't hope anything from Syno before months. Like before no sources = no loader jun's v1.01 loader CAN'T support DSM 6.1 so DO NOT UPGRADE ! I've rebased the vendor changes on 3.10.77 to 3.10.102, seems still works. jun your are the MAN Next step is I think to troubleshoot the network issue on some system that "prevent" network driver to load at boot. How can I (or the community) help you to debug ? How do you display/access the early boot stage without serial console ? Based on my unintentionally migration from ds3615xs to ds3617sx, and feedbacks from this forum, I guess some drivers are not correctly updated in the rootfs, thus caused network failure, a clean installation does not suffer from this problem. I use VM to do preliminary test, does not have the luxury to test on baremetals. As before, I do not have much time to build and test drivers, if developers and users can help in these area, then more hardware will be supported. Quote Link to comment Share on other sites More sharing options...
snoopy78 Posted February 27, 2017 Share #2015 Posted February 27, 2017 i just did a quick test with my current toy baremetal system and got Jun's DS3617xs "DS3617xs 6.1 Jun's Mod V1.02-alpha" working. Had to use "force install" but so far for an alpha it's fine. Quote Link to comment Share on other sites More sharing options...
tuonoazzurro Posted February 27, 2017 Share #2016 Posted February 27, 2017 Tried upgrading my test machine with new loader 1.02 alpha. First boot it say migrable, did the migration and now it goes in bootloop, i can see the loader, then starting the loader, 2 seconds and it reboot the pc Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted February 27, 2017 Share #2017 Posted February 27, 2017 Quck update... 1.02Alpha doesn't support LSI 2xxx cards - it never boots after initial installation; remove the card and you get the "please install harddrives" message. I was wrong - after using the OVF download in another thread - everything is perfect. this was an user error (mine). If there's any critique to be had about this site, it would have to be that it's rather chaotic. This OVF, I'm sure you found it somewhere, but not in any place obvious (like the start-post). Would be nice if the powers that be were a little more systematic about all of this. Now, flame away! Quote Link to comment Share on other sites More sharing options...
cuspess Posted February 27, 2017 Share #2018 Posted February 27, 2017 Tried upgrading my test machine with new loader 1.02 alpha. First boot it say migrable, did the migration and now it goes in bootloop, i can see the loader, then starting the loader, 2 seconds and it reboot the pc I am beginning to think case like this, if you still had your old loader 1.01 with you, you could still boot with 1.01 and have your DSM 6 working like before the upgrade. Someone please confirm if my thought is right, otherwise I think it is fair to say it is safe to try upgrading. cheers Quote Link to comment Share on other sites More sharing options...
dgrigo Posted February 27, 2017 Share #2019 Posted February 27, 2017 I used the alpha loader that jun posted, and everything is fine so far, except an issue with bios losing data and time (aka reset) so display again press f1 to continue. That was not happening with 6.02 i had it from day 1 of juns loader, any ideas? Thanks Dinos Quote Link to comment Share on other sites More sharing options...
tuonoazzurro Posted February 27, 2017 Share #2020 Posted February 27, 2017 Tried upgrading my test machine with new loader 1.02 alpha. First boot it say migrable, did the migration and now it goes in bootloop, i can see the loader, then starting the loader, 2 seconds and it reboot the pc I am beginning to think case like this, if you still had your old loader 1.01 with you, you could still boot with 1.01 and have your DSM 6 working like before the upgrade. Someone please confirm if my thought is right, otherwise I think it is fair to say it is safe to try upgrading. cheers SOLVED! 1. During installing the usb loader went corrupted (tried twice). So after install you had to clean the usb drive(all partition) and reflash image. 2. Upgrade not work. so the only working route is to choose clean install (data folder are not deleted, you only have to rejoin domain or recreate user and assign permission. App are lost instead) Quote Link to comment Share on other sites More sharing options...
lysin Posted February 27, 2017 Share #2021 Posted February 27, 2017 I've tried migrating to the new alpha, but got this error instead: "We've detected errors on the hard drives (6), and the SATA ports have also been disabled. Please shut down your DS3615xs to replace or remove the hard drives and try again." I'm using the same SATA configuration as 6.0.2 loader (SataPortMap=4), and I also tried SataPortMap=1, SataPortMap=5 and SataPortMap=6. No luck. I´ll try again later today using the forced mode. Quote Link to comment Share on other sites More sharing options...
sagrotan Posted February 27, 2017 Share #2022 Posted February 27, 2017 (edited) Offtopic (like a lot in this thread ): Do we have some kind of mods here in the forum? A DSM6.1 loader would be a good start for a new thread, isn't it?. The devs and the loaders are awesome, but the forum discipline is a mess. A more structured approach with the forum would also reduce the flood of noob questions over and over again. BTW: I am also one of them... I will not be able to contribute something to the loader sources, but if you need support with the forum management, I would help for sure! Edited February 27, 2017 by Guest Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted February 27, 2017 Share #2023 Posted February 27, 2017 Offtopic (like a lot in this thread ):Do we have some kind of mods here in the forum? A DSM6.1 loader would be a good start for a new thread, isn't it?. The devs and the loaders are awesome, but the forum discipline is a mess. A more structured approach with the forum would also reduce the food of noob questions over and over again. BTW: I am also one of them... I will not be able to contribute something to the loader sources, but if you need support with the forum management, I would help for sure! ^^ Where's that Upvote button when you need it?! Seriously, this is precisely what I was saying earlier today. This forum is full of very talented programmers, but it's often very hard to find anything. I had to call a friend, the other day, to ask what image we used again was, and he was like "Remember, it was in thread X, page Y, Z post from the top?!" It's gotten a little better, as some things have been moved to the start-post. Still, there are all these different threads going on, all relevant in there own way. Like that OVF mentioned earlier: I'm sure it's in some of the other threads; but yeah, would be nice if we had some forum manager add a wee bit of sctructure to it all. Quote Link to comment Share on other sites More sharing options...
Rusty Posted February 27, 2017 Share #2024 Posted February 27, 2017 SOLVED! 1. During installing the usb loader went corrupted (tried twice). So after install you had to clean the usb drive(all partition) and reflash image. 2. Upgrade not work. so the only working route is to choose clean install (data folder are not deleted, you only have to rejoin domain or recreate user and assign permission. App are lost instead) Your apps are only not installed, all your data is still there, if you backup the @appstore folder before you reinstall your apps, you can copy back the var folder to retain settings. Quote Link to comment Share on other sites More sharing options...
meimeiriver Posted February 27, 2017 Share #2025 Posted February 27, 2017 SOLVED! 1. During installing the usb loader went corrupted (tried twice). So after install you had to clean the usb drive(all partition) and reflash image. 2. Upgrade not work. so the only working route is to choose clean install (data folder are not deleted, you only have to rejoin domain or recreate user and assign permission. App are lost instead) Your apps are only not installed, all your data is still there, if you backup the @appstore folder before you reinstall your apps, you can copy back the var folder to retain settings. That is a good tip! Thanks. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.