Polanskiman

Tutorial: Install/Migrate DSM 5.2 to 6.1.x (Jun's loader)

Recommended Posts

try editing /etc.defaults/synoinfo.conf.

 

You did not post much information about your system.  Are your disks passthrough?  How many controllers?  How many ports on those controllers? Did you have a custom setting for DiskIdxMap and/or SataPortMap in your loader?

 

Share this post


Link to post
Share on other sites
18 hours ago, flyride said:

try editing /etc.defaults/synoinfo.conf.

 

You did not post much information about your system.  Are your disks passthrough?  How many controllers?  How many ports on those controllers? Did you have a custom setting for DiskIdxMap and/or SataPortMap in your loader?

 

 

Thank you for your answer.

I did try to edit /etc.defaults/synoinfo.conf. That was the first thing I tried. But even though I changed the values to 24 disks, there is still only 8 disks visible in DSM Storage Manager. I think this must be the problem, right? Why doesn't the change in synoinfo.conf reflect in the Synology?

 

About my system:

I have a Supermicro Motherboard with a built in LSI controller with 8 SATA ports (on the mother board). The controller works as a regular PCI HBA and is passed through to the Synology server. I also have a regular 8 port PCI LSI HBA that is passed through in the same way.

 

I don't recognize DiskIdxMap and SataPortMap. I have never changed any of those values before. Is that something new with version 6?

 

Share this post


Link to post
Share on other sites

The values in /etc.defaults/synoinfo.conf are copied to /etc/synoinfo.conf each reboot.

 

You will probably need SataPortMap=188 and DiskIdxMap=180008 for your drives to be properly visible spanning controllers.  If you are asking whether this is new for version 6, you need to go to the FAQs and spend some time reviewing the 6.x loader instructions and how to implement those settings into the loader.

 

Share this post


Link to post
Share on other sites
2 hours ago, flyride said:

The values in /etc.defaults/synoinfo.conf are copied to /etc/synoinfo.conf each reboot.

 

You will probably need SataPortMap=188 and DiskIdxMap=180008 for your drives to be properly visible spanning controllers.  If you are asking whether this is new for version 6, you need to go to the FAQs and spend some time reviewing the 6.x loader instructions and how to implement those settings into the loader.

 

Thanks. I will study.

In the mean time, is it possible to downgrade 5.2 5967?

Share this post


Link to post
Share on other sites
Posted (edited)

Cheers
One consulta, por favor ayuda cuál de estas opciones es más estable, compatibilidad con DSN versión 6.2 y si no es mucho pedir en el futuro
1.-Servidor HP Proliant DL380 g4 Intel Xeon 3.8
2.-HP Proliant DL160 G6 Servidor Intel Xeon CPU L5630 2.13GHz
3.-HP Proliant DL120 G7 Servidor Intel Xeon E3-1220
4.-SERVIDOR DELL PowerEdge T40 Intel Xeon E-2224G
gracias de antemano

Edited by deivis

Share this post


Link to post
Share on other sites
Posted (edited)
On 10/28/2018 at 6:01 AM, ed_co said:

@Polanskiman Thanks for the amazing tutorial!! Just one thing, for macOS, you didn't say how to mount the partition to change the extra.lzma, just to change the grub.cfg. Could you please provide the info?

Thank you very much!!

 

Please add to the macOS tutorial, how to mount the other partition, in order to modify the extra.lzma/extra2.lzma:

mkdir /tmp/partition2
sudo mount -t msdos /dev/disk2s2 /tmp/partition2

Although I find a problem to eject/unmount it properly... and that's why I wanted to have some help with that

 

Edited by ed_co

Share this post


Link to post
Share on other sites
Posted (edited)

Hi

Thanks for the detailed tutorial!

Been trying to update my 5.2 Synology server. Running on HP DL180G6

Run faultlessly on Xpenoboot for DSM5.2 for years but well past time to update now as many packages etc aren't compatible any longer!

As this server has a P410 Raid controller this is listed as not working in the extra ramdisk post and therefore the loader won't work with the server

Is there any other loaders I would be able to migrate my current 5.2 installation to?

Would a migration be possible using 1.01 and DSM 6.0 or migrate using 1.03 and DSM 6.2?

Thanks

 

Edited by JCon

Share this post


Link to post
Share on other sites

Thanks for all information updat.

Finally I can update a baremetal HP N40L (mod bios & using onboard NIC) with 6 HDDs, from nanoboot DSM 5.2-5644 to Jub1.03b loader for DS3615xs with DSM6.2.3-25426 directly.

Data migration is straight forward & perfectly smooth. Only needs to ensure C1 disabled in BIOS.

 

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.