jun

DSM 6.1.x Loader

Recommended Posts

are you sure you got vid & pid correctly modified? try redownload pat file maybe, i have a gen8 and everything when smooth from 5.2

Share this post


Link to post
Share on other sites
tested and everything is working as expected, upgraded my gen8 baremetal from 5.2 to 6.0.2-u3 with all data and config intact, no problem whatsoever, the only thing is that after the upgrade dsm changed my local ip to dhcp instead of let it static but it's not an issue, reverted back to static in 10 seconds.

 

al packages working fine, update3 applied and rebooted with no issue, changed my filesystem to btrfs so i'm pretty happy :smile:

 

edit: one last thing, how can i change max drive shown in the disk manager? it shows 12 slot, i wanted to limit it to 5.

 

edit2: nevermind, synoinfo.conf had maxdrives set to 12, fixed :smile:

 

 

where is synoinfo.conf?? I cant find it!!please someone could tell me it

Share this post


Link to post
Share on other sites
where is synoinfo.conf?? I cant find it!!please someone could tell me it

 

Use ssh and look in /etc and also /etc.defaults both contain different versions of synoinfo.conf.

 

/etc.defaults is required for certain changes that will only become persistent when the change is applied to synoinfo.conf in that location.

 

Edit

 

After upgrading to DSM6 the root account will be independent of the primary admin account for increased security. You need to login with the primary account and password for your ssh session. Then use "sudo su -" or you can find instructions to set a pw for the root account. There is info about changing the root pw here > viewtopic.php?f=2&t=20216&start=420#p74492 .

Share this post


Link to post
Share on other sites
are you sure you got vid & pid correctly modified? try redownload pat file maybe, i have a gen8 and everything when smooth from 5.2

vid&pid are correct

redownload doesn't work

 

I receive some error about port23, wireless & Co, but all ports are ok in router for that device.

 

Untitled.jpg

Edited by Guest

Share this post


Link to post
Share on other sites

SOLVED

 

I changed the usb f***ing stick.

So, don,t use ADATA N005 usb 3.0 people.

 

I hope restore config saved in 5.2 will work. :smile:

Share this post


Link to post
Share on other sites
Anyone know if we can update to 6.0.2-8451 update 3?

 

It worked fine on my ESXi install.

 

ESXi 6.0u2?

 

Which of the loaders did you use?

 

And did you import the OVF or set things up manually?

 

Thanks.

Share this post


Link to post
Share on other sites
I hope restore config saved in 5.2 will work. :smile:

 

Not sure using a restore from an older version is a good idea. :???:

 

Restore config works great. That's actually a a step to move from ext4 to btrfs

Share this post


Link to post
Share on other sites

On an AsRock Q1900 ITX i just edited grub.cfg with OSFMount (just remember to select all partitions and untick read only in options and save it) before burning it to the usb drive .

Worked like a charm..

Now i am on DSM 6.0.2-8451 Update 3

 

Thnx again for everyone's contribution.

 

P.s As for USB drive i use these as they always work with synoboot until now

 

http://www.ebay.ie/itm/162061688953

Share this post


Link to post
Share on other sites
I hope restore config saved in 5.2 will work. :smile:

 

Not sure using a restore from an older version is a good idea. :???:

 

Restore config works great. That's actually a a step to move from ext4 to btrfs

 

That's good to know.

 

Personally I would be very wary of using old config restores especially when it involves major versions. Config's handled by a migration script may handle conflicts by design, where as a straight restore may not handle them as expected? I would rather not assume especially when it has the potential to make a recovery difficult, if vital parameters have been filled with garbage or the files get totally trashed. If you know for sure there's no risk then obviously that's a different kettle of fish.

Share this post


Link to post
Share on other sites

So wait... Is this a new bootloader we can use to upgrade from DSM 5 to DSM 6?

 

If so without going back through 130 pages, could anyone please point me in the right direction to upgrade from 5.2-5967.1 (17/07/2016) to your 6.0.2?

And is this running fine on normal setups not just on VM's?

So I can upgrade my current box?

 

Thanks all, and appreciate your hard work.

Share this post


Link to post
Share on other sites

OK I tried building hyper-v network modules for multiple users asking for a Hyper-V image.

Copying the .ko modules from different won't work, obviously.

 

I've setup the toolchain for DSM6.0 and used the sources from github (https://github.com/quiknick/7274-kernel).

A quick chroot to the toolchain dev env for x86_64 and make oldconfig.

 

Followed by the module itself:

[root@ubuntu16desktop 7274-kernel]# make M=./drivers/net/hyperv/

 

WARNING: Symbol version dump /7274-kernel/Module.symvers

is missing; modules will have no dependencies and modversions.

 

Building modules, stage 2.

MODPOST 0 modules

 

Edit: should clarify: The module isn't found so it won't build. The 4.4 linux kernel source doesn't suffer from this.. anyone have any leads?

Edited by Guest

Share this post


Link to post
Share on other sites

Hello! I have DSM6.0.2 with the updates working on my bare metal installation. I have 4 disks (Raid5), one SSD 128GB (SSD Cache), and one 8TB which was just for backup purpose. In the grub file, I put 6 drives for sataportmap. I see all the drives but can not add the 8TB as a separate volume (Volume 2). When I go to the storage manager, the "Create" under volume is greyed out. Is there something I am missing? I am not sure which ram version I am using in the boot disk.

Share this post


Link to post
Share on other sites
So wait... Is this a new bootloader we can use to upgrade from DSM 5 to DSM 6?

 

If so without going back through 130 pages, could anyone please point me in the right direction to upgrade from 5.2-5967.1 (17/07/2016) to your 6.0.2?

And is this running fine on normal setups not just on VM's?

So I can upgrade my current box?

 

Thanks all, and appreciate your hard work.

 

Read Jun's opening post in this thread and read this post > viewtopic.php?f=2&t=22100 and yes it works for Baremetal builds. Not all the drivers that have been supported in the past are available using Jun's loader though, which could be an issue if your hardware isn't supported.

Share this post


Link to post
Share on other sites

I wanted to post some pictures but I get the error that this board has exceeded its quota for attachments.

 

So my system sees all the disks in Storage Manager. The 8TB drive is initialized and in an unused state. When I go to create a volume, the "Create" is greyed out not letting me create a new volume and add the 8TB drive to the system. Otherwise, everything else works great!

Share this post


Link to post
Share on other sites
I wanted to post some pictures but I get the error that this board has exceeded its quota for attachments.

 

So my system sees all the disks in Storage Manager. The 8TB drive is initialized and in an unused state. When I go to create a volume, the "Create" is greyed out not letting me create a new volume and add the 8TB drive to the system. Otherwise, everything else works great!

 

Your post count maybe too low to add images?

 

Have you tried adding a disk group and then adding the volume after that?

Share this post


Link to post
Share on other sites

I checked but I do not have an option to add disk group. What is the minimum posts I have to have in order to attach images?

Share this post


Link to post
Share on other sites

I should have posted my motherboard specs. I have a GA-B150M-D3H. I dont think there are two separate SATA controllers? If there is, then maybe my problem is the SataPortMap=6?

Share this post


Link to post
Share on other sites
I hope restore config saved in 5.2 will work. :smile:

 

Not sure using a restore from an older version is a good idea. :???:

 

Restore config works great. That's actually a a step to move from ext4 to btrfs

 

You are lucky. I read several reports where people had upgraded to dsm 6.0 then used their dsm 5.2 backed up config file to restore their config and hell broke lose.

Share this post


Link to post
Share on other sites
On an AsRock Q1900 ITX i just edited grub.cfg with OSFMount (just remember to select all partitions and untick read only in options and save it) before burning it to the usb drive .

Worked like a charm..

Now i am on DSM 6.0.2-8451 Update 3

 

Thnx again for everyone's contribution.

 

P.s As for USB drive i use these as they always work with synoboot until now

 

http://www.ebay.ie/itm/162061688953

 

Selecting and opening the partition where the grub file is located is enough. It's the 30 or so MB partition.

Share this post


Link to post
Share on other sites

Thank you Jun for developing this amazing bootloader.

 

I recently bought a Gen8 and wanted to install xpenology to it under esxi. Prior to the actual installation I ran the same setup (ie xpenology on esxi on a virtual machine) on VMWare Workstation to experiment and it all worked fine.

 

However when I try to do the same on the actual Gen8, I got stuck at the stage where I had to burn the bootloader to USB drive and edit the grub file. I tried 2 different computers to do the burn to usb procedure, and tried 2 different USB drive to burn to, but still not success. The problem is that after burned to the usb drive, both computers no longer can read the usb drive's content. The drive is basically not displayed on the "Computer" where you usually see all your C: D: etc. When check using Disk Manager, the USB drive does show it has 4 partitions but you cannot access it. I went and plug the USB drive to my Gen8 and it does boot up correctly and I could start the DSM setup with not problem using find.synology.com (however I didn't proceed further because I have not changed the VID PID and sata_map on the grub file yet). I suspect it was the synoboot.img file i downloaded causing all these problem, so I tried to extract it with WinRAR and osfmount (as another post here mentioned) but could not open with error saying the file may be corrupted. To verify, I downloaded the same file with different computer and even tried the v1.0 but all remain not working.

 

Can someone point me to the right direction? I really have tried but I think the problem is something outside of my current knowledge and really want to get it sorted as I see many people have succeed and only me who faces such issue. Thanks.

Share this post


Link to post
Share on other sites
Thank you Jun for developing this amazing bootloader.

 

I recently bought a Gen8 and wanted to install xpenology to it under esxi. Prior to the actual installation I ran the same setup (ie xpenology on esxi on a virtual machine) on VMWare Workstation to experiment and it all worked fine.

 

However when I try to do the same on the actual Gen8, I got stuck at the stage where I had to burn the bootloader to USB drive and edit the grub file. I tried 2 different computers to do the burn to usb procedure, and tried 2 different USB drive to burn to, but still not success. The problem is that after burned to the usb drive, both computers no longer can read the usb drive's content. The drive is basically not displayed on the "Computer" where you usually see all your C: D: etc. When check using Disk Manager, the USB drive does show it has 4 partitions but you cannot access it. I went and plug the USB drive to my Gen8 and it does boot up correctly and I could start the DSM setup with not problem using find.synology.com (however I didn't proceed further because I have not changed the VID PID and sata_map on the grub file yet). I suspect it was the synoboot.img file i downloaded causing all these problem, so I tried to extract it with WinRAR and osfmount (as another post here mentioned) but could not open with error saying the file may be corrupted. To verify, I downloaded the same file with different computer and even tried the v1.0 but all remain not working.

 

Can someone point me to the right direction? I really have tried but I think the problem is something outside of my current knowledge and really want to get it sorted as I see many people have succeed and only me who faces such issue. Thanks.

 

1 - With Jun's loader v1.0 and V1.01 if you are under Windows 10, after you burn the image to the flash drive the partition with the content should normally show in your file explorer. If you are in Windows 7/XP or basically anything under Windows 10 then you will need to edit the grub file in the .img file first then burn it to the flash dirve. Or if you have a MAC you can mount the EFI partition of the flash drive through a few commands that I will omit here for the sake of simplicity. I have already made a post about it so you can search the thread.

 

2 - If you wish to modify directly the .img file then you need to use OSFmount. Launch OSFmount, select Mount New, then select the .img to open, then select partition 0 (the one that is 30 MB). Click ok. Then at the bottom of the window make sure to untick the "Read only drive". Click ok. The EFI partition should now be mounted in file explorer. You can now edit the grub.cfg file. Save any changes you made. Done. Easy-peasy-lemon-squeezy.

Share this post


Link to post
Share on other sites
I hope restore config saved in 5.2 will work. :smile:

 

Not sure using a restore from an older version is a good idea. :???:

Worked like a charm.

But you have to keep admin user name exactly as in restored settings to avoid headaches. :grin:

Share this post


Link to post
Share on other sites
So wait... Is this a new bootloader we can use to upgrade from DSM 5 to DSM 6?

 

If so without going back through 130 pages, could anyone please point me in the right direction to upgrade from 5.2-5967.1 (17/07/2016) to your 6.0.2?

And is this running fine on normal setups not just on VM's?

So I can upgrade my current box?

 

Thanks all, and appreciate your hard work.

 

Read Jun's opening post in this thread and read this post > viewtopic.php?f=2&t=22100 and yes it works for Baremetal builds. Not all the drivers that have been supported in the past are available using Jun's loader though, which could be an issue if your hardware isn't supported.

 

Thanks for the link!

Will follow that through.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now