VolaLazioVola

Hi guys I have the DSM up with bootloader XPEnoboot DS3615xs5.2-5644.4. There is an update from Synology which I can do directly inside DSM (I am already on U3 or U4 don't remember it). I have actually see there is a new bootloader called XPEnoboot DS3615xs5.2-5644.5. I think this is a different update and it is not related to the DSM, right? Thanks

Thanks a lot guys for the replies. I don't want to go in such deals as it would be painful. I prefer to go with the HP Microserver and install XPEnology into a vm on ESXi (already tried on a lab server). Then I can connect hard drives into the HP Microserver bays and use it in raw format.

Hi Is it possible to install XPEnology on the latest Raspberry Pi 2? I was thinking to have the XPEnoboot on the internal microsd and then install DSM on the hard drive connected to the usb port of the Raspberry Pi. Thanks Mario

Hi Thanks for the post. Actually I did follow it to install the latest "XPEnoboot_DS3615xs_5.2-5644.4". Everything went fine except for what is one of the main reason of these steps: when you are done there won't be any extra "unused" disk showing up in DSM I did modify the syslinux.cfg adding “rmmod=ata_piix” at the end of the lines and result is what you see below. I believe I needed to put at the end of each APPEND line which contains the different options. LABEL xpenology MENU LABEL XPEnology DSM 5.2-5644 KERNEL /zImage APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 rmmod=ata_piix LABEL debug MENU LABEL XPEnology DSM 5.2-5644 Debug KERNEL /zImage APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 debug=1 rmmod=ata_piix LABEL install MENU LABEL XPEnology DSM 5.2-5644 Install/Upgrade KERNEL /zImage APPEND root=/dev/md0 ihd_num=0 netif_num=4 syno_hw_version=DS3615xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 loglevel=0 vga=0x305 upgrade=5.2-5644 rmmod=ata_piix When I get into DSM Storage Manage I do see both the 32gb volume1 for OS and apps and the small nanoboot vmdk. I am not sure I have done something wrong. Thanks