kraized

Hello, Does anyone know how to get the HP iLO4 AMS (Agentless Management System) working again in DSM7, so DSM can report data directly to iLO?

Hello, thanks for putting this app together. Is there any chance the UI can be tweaked slightly or the app window optimised for use on smaller screens. I have to use a 1366x768 res screen for a while but the layout of the tool doesn't fit within this resolution unfortunately so the navigation is cut off at the bottom.

- Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.1.7-15284 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Using custom extra.lzma: No - Installation type: BAREMETAL - HPE Microserver Gen 8. 16GB RAM. 4 x 4TB HDD + 1 x 120GB Read-only Cache SSD - Additional comments: REBOOT REQUIRED. Server not available on network. Cannot ping IP. HPE iLO 4 also not available. No remote access, no SSH.

Managed to get the server up and running again. It seemed to only work with networking if I selected either the Reinstall or Force Install option in Jun's boot menu. I tried the Migration option at first but it seemed to cause a few issues so went for a Clean Install instead. All data, volumes, shares etc are intact, just packages and settings needing a full reinstall. Seems to be booting normally now and updated to DSM 6.0.2-8451 Update 7 without any issues. Many thanks for everybody's help.

If you have ssh access or serial consol access you could try this https://xpenology.com/forum/topic/5442-downgrade-from-dsm-60/ adapting it to your case (6.1 > 6.0.2). If you can't access through consol/ssh then you will need a ubuntu live USB to access the content of the system partition and modify the VERSION file manually (as explained in the above link) that is located in /etc.defaults. You can edit it with vi or nano if you had the later installed. If you use live ubuntu you will need to install mdadm and lvm2: apt-get install mdadm lvm2 Then you need to check your raid array and partitioning: fdisk -l | grep /dev/sd Mine gives this. Note I only have 2 drives /dev/sda and /dev/sdb [spoiler=] root@server:/etc.defaults# fdisk -l | grep /dev/sd Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors /dev/sda1 256 4980735 4980480 2.4G fd Linux raid autodetect /dev/sda2 4980736 9175039 4194304 2G fd Linux raid autodetect /dev/sda3 9437184 3907015007 3897577824 1.8T f W95 Ext'd (LBA) /dev/sda5 9453280 3907015007 3897561728 1.8T fd Linux raid autodetect Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors /dev/sdb1 256 4980735 4980480 2.4G fd Linux raid autodetect /dev/sdb2 4980736 9175039 4194304 2G fd Linux raid autodetect /dev/sdb3 9437184 3907015007 3897577824 1.8T f W95 Ext'd (LBA) /dev/sdb5 9453280 3907015007 3897561728 1.8T fd Linux raid autodetect System partitions are the ones labeled sda1, sdb1. If you have more drives in the aray, subsequent system partitions will probably be called sdc1, sdd1 so on and so forth. You get the point. Once you figured out all system partitions, then issue (this is for my case, with 2 drives): mdadm -Ee0.swap /dev/sda1 /dev/sdb1 if you have 3 drives then you add /dev/sdc1. You get the idea. Finally issue: mdadm -AU byteorder /dev/md0 /dev/sda1 /dev/sdb1 Same as previous command. Add any additional system partitions that you may have. Beware of the /dev/md0. It's normal, not a mistake. Your system partition should now be mounted and you can navigated to /etc.defaults and edit the VERSION file as explained in the link above. If you want to have access to the data partition instead to recover and backup all your data, simply issue: mdadm -Asf && vgchange -ay This should mount the data partitions. I can't guarantee that modifying the VERSION file will work no matter what path you use. Therefore I wont be able to support beyond this. Good luck. Hello, many thanks for you advice. I managed to edit the VERSION file on /etc.defaults, using an Ubuntu book disk, however for some reason I cannot see the server on my network after a reboot. I'm thinking the network drivers are not getting initialized now though I'm not sure why editing the VERSION file would cause network failure, as before, I could see the server on my network. Any ideas?

Hi all, I need your help. I'm was running Jun's loader with DSM 6.0.2-8451 Update 6 on my HPE Microserver Gen8 Baremetal. Everything was working perfectly until yesterday when DSM auto-upgraded to the beta version of DSM – DSM 6.1-14871. Not sure how, as i thought beta versions had to be installed manually. Unfortunately, the system won't boot now (I'm guessing because the bootloader is still DSM 6.0.2-8451) but get's stuck in a 'Recoverable' state. I can find the DS on my network, though it seems the settings have returned to default via DHCP, whereas before I had two static IP addresses assigned. The DS has still retained its custom serial and MAC addresses however. FWIW, I can see the DS via both browser and the Synology Assistant app. All show the same 'Recoverable' state. If there is a way to get this back up and running on DSM 6.0.2-8451, what would be the best? I'm unsure where to go from here.

Hello, which files have you used to get this working on ESXi 6? I'm sure I've tried everything in this thread numerous times but cannot get it to work.

Hello, which files have you used to get this working on ESXi 6? I'm sure I've tried everything in this thread numerous times but cannot get it to work.