supernoman Posted February 19, 2016 Share #1 Posted February 19, 2016 I just recently installed on ESXi 6 using a guide on here. Can anyone link me to instructions on how to update the XPenoboot to recently release XPEnoboot 5.2-5644.5? I am currently migrating my data over to it and don't want to break it. Thanks! Link to comment Share on other sites More sharing options...
brantje Posted February 19, 2016 Share #2 Posted February 19, 2016 What DSM version are you on currently? Posted via MyXpenology Link to comment Share on other sites More sharing options...
supernoman Posted February 19, 2016 Author Share #3 Posted February 19, 2016 5.2-5644 Update 3. I got the notice of the update 5 available in DSM so I jumped on here to see if it would be safe to install. Then I see new xpenoboot and thus my post. Current installed xpenoboot is 5.2-5644.4. Link to comment Share on other sites More sharing options...
rhplus Posted February 20, 2016 Share #4 Posted February 20, 2016 It's simple and easy as 1-2-3. - Just download new vmdk bootloader file. - Upload them into right datastore folder. - And replace boot disk in virtual machine settings. More complex view on same problem https://idmedia.no/projects/xpenology/installing-or-upgrading-to-xpenology-5-2-or-later/ Link to comment Share on other sites More sharing options...
supernoman Posted February 21, 2016 Author Share #5 Posted February 21, 2016 So I had created a xpenoboot folder and added the .4 vmdk. I just uploaded .5 vmdk to same folder. -rw-r----- 1 root root 17891328 Feb 15 16:38 XPEnoboot_DS3615xs_5.2-5644.4.vmdk -rw-r--r-- 1 root root 18153472 Feb 20 15:18 XPEnoboot_DS3615xs_5.2-5644.5.vmdk When I created the VM, I named it xpenology and pointed it to existing vmdk as instructed by tutorial. Here are the contents of the xpenology VM folder. -rw------- 1 root root 65536 Feb 17 18:11 XPEnoboot_DS3615xs_5.2-5644.4.vmdk-s001.REDO_qKbRMv -rw------- 1 root root 379 Feb 17 18:11 XPEnoboot_DS3615xs_5.2-5644.4.vmdk.REDO_qKbRMv -rw-r--r-- 1 root root 174680 Feb 15 18:12 vmware-3.log -rw-r--r-- 1 root root 666749 Feb 15 22:26 vmware-4.log -rw-r--r-- 1 root root 158776 Feb 15 23:08 vmware-5.log -rw-r--r-- 1 root root 42453 Feb 17 18:08 vmware-6.log -rw-r--r-- 1 root root 42453 Feb 17 18:09 vmware-7.log -rw-r--r-- 1 root root 42453 Feb 17 18:09 vmware-8.log -rw-r--r-- 1 root root 2079417 Feb 21 21:14 vmware.log -rw------- 1 root root 171966464 Feb 17 18:11 vmx-xpenology-4250321199-1.vswp -rw------- 1 root root 0 Feb 15 22:26 xpenology-fd56c12f.vswp -rw------- 1 root root 34359738368 Feb 21 21:14 xpenology-flat.vmdk -rw------- 1 root root 8684 Feb 21 21:04 xpenology.nvram -rw------- 1 root root 471 Feb 17 18:11 xpenology.vmdk -rw-r--r-- 1 root root 0 Feb 15 17:05 xpenology.vmsd -rwxr-xr-x 1 root root 3067 Feb 17 18:11 xpenology.vmx -rw------- 1 root root 0 Feb 17 18:11 xpenology.vmx.lck -rwxr-xr-x 1 root root 3067 Feb 17 18:11 xpenology.vmx~ The xpenology-flat.vmdk is the additional drive I created to be for synology to create apps on. Which boot disk am I supposed to replace? Link to comment Share on other sites More sharing options...
rhplus Posted February 21, 2016 Share #6 Posted February 21, 2016 In ESXi actual setup, bootloader file XPEnoboot_DS3615xs_5.2-5644.4.vmdk is used as boot disk. (probably with value Virtual Device Node - IDE (0:0)). The goal is replace this disk with new boot loader XPEnoboot_DS3615xs_5.2-5644.5.vmdk. Link to comment Share on other sites More sharing options...
unmesh Posted February 22, 2016 Share #7 Posted February 22, 2016 It's simple and easy as 1-2-3. - Just download new vmdk bootloader file. - Upload them into right datastore folder. - And replace boot disk in virtual machine settings. More complex view on same problem https://idmedia.no/projects/xpenology/installing-or-upgrading-to-xpenology-5-2-or-later/ I use the "complex" method myself. How do you edit the serial number in the vmdk file? Link to comment Share on other sites More sharing options...
supernoman Posted February 22, 2016 Author Share #8 Posted February 22, 2016 In ESXi actual setup, bootloader file XPEnoboot_DS3615xs_5.2-5644.4.vmdk is used as boot disk. (probably with value Virtual Device Node - IDE (0:0)). The goal is replace this disk with new boot loader XPEnoboot_DS3615xs_5.2-5644.5.vmdk. That is the goal. Should I just power down the VM and copy XPEnoboot_DS3615xs_5.2-5644.5.vmdk over to XPEnoboot_DS3615xs_5.2-5644.4.vmdk and power on or is there a way to replace the boot disk without creating a new VM. Link to comment Share on other sites More sharing options...
supernoman Posted February 22, 2016 Author Share #9 Posted February 22, 2016 In ESXi actual setup, bootloader file XPEnoboot_DS3615xs_5.2-5644.4.vmdk is used as boot disk. (probably with value Virtual Device Node - IDE (0:0)). The goal is replace this disk with new boot loader XPEnoboot_DS3615xs_5.2-5644.5.vmdk. That is the goal. Should I just power down the VM and copy XPEnoboot_DS3615xs_5.2-5644.5.vmdk over to XPEnoboot_DS3615xs_5.2-5644.4.vmdk and power on or is there a way to replace the boot disk without creating a new VM. Link to comment Share on other sites More sharing options...
Diverge Posted February 22, 2016 Share #10 Posted February 22, 2016 1) Copy new VMDK to datastore location of your choice 2) Shut down your XPEnology VM 3) Edit the XPEnology VM settings > remove old boot image disk 4) Add new boot image disk pointing to new VMDK of boot image. 5) Start your XPEnology VM Link to comment Share on other sites More sharing options...
Recommended Posts