Jump to content
XPEnology Community

epicurean

Member
  • Posts

    66
  • Joined

  • Last visited

Posts posted by epicurean

  1. On 11/2/2018 at 6:16 PM, chipped said:

    How to downgrade:

    Replace zImage, extra.gz and rd.gz (open synology.img -> image.img with 7Zip) with the one from DS3615xs (use the opposite of what you have installed currently) so you will force a reinstall of DSM.

     

    You cannot migrate the settings, so you have to do a clean install (keeps your data). Afterwards replace the above files again with your original bootloader, for me its DS3617xs and do a fresh install again.

     

    What this means is, if you have 3617, then download the 3615 loader. Extract the files above using 7zip from the 3615 loader, use OSFMount to modify the 3617 with those files (by replacing them) and then make a USB with this modified 3617 loader.

    Hi, 

    Do you mean to extract synoboot.img, take the image.img from there, and then remove the zimage, extra.lzma and rd.gz ? Can we just take the image.img file from one loader to replaced in the other loader?

  2. On 11/17/2018 at 11:50 PM, jadehawk said:

    To those interested.. 

    • DSM 6.2.1-23824 Update 1 = Did NOT work on ESXi Using DS3617xs (Changing Network vnic to E1000e did not help)
    • DSM 6.2.1-23824 Update 1 = Works 100% on ESXi  Using DS3615xs (Changing Network vnic to E1000e).
    • Migrating the already setup Volume from DS3617xs to DS3615xs was as simple as reassigning the vmdk disks 1-3 to the new VM and repairing the partitions

     

    Thank you @haydibe

     

    Now Running latest DSM version on my HP Microserver Gen8!!!

    Change you change the network vnic back to vmxnet3 after updating? will it affect future DSM updates?

     

  3. 23 hours ago, john_matrix said:

    For ESXi utilization, you only have to edit the VM settings for pointing the boot device to the new bootloader file (and removing the previous one)

    Sorry for my noobieness, but how exactly do you do that?

  4. 4 hours ago, john_matrix said:

    You can flash your USB key to 1.02b the same way you had done with 1.02a ;)

    Don't forget to change your serial and mac address in the grub.conf

    I understand that will be the way for bare metal installation. I was referring to changing to a loader if my installation was as VM in ESXI 6

    I am already on the latest 6.1.1 but I wish to update to the latest 1.02b loader , to be ready for future synology updates

     

    Much thanks for help on changing loader for an esxi installation. :smile:

  5. I did a fresh install on Esxi 6 with the 1.02a 3615 loader. All ok so far

     

    How do I update my loader to the newer 1.02b, in anticipation for the next update from Synology?

  6. On 9/21/2016 at 3:16 PM, NeoID said:

    I have a LSI SAS 9201-16i and it works like a charm on the latest firmware. Don't see the reason why yours shouldn't... any error messages?

    HI NeoID,

    Which exact loader did you use for your LSI 9201-16i to work in esxi?

  7. I have setup on bare metal , a fresh DSM 6 on my supermicro X8SIL motherboard. Everything is fine except that I can never see anything on the screen via the vga connection.

    I did enable the serial port on the motherboard through the bios.

     

    Is there anything else I need to do to be able to see the grub screen?

     

    much thanks for this really helpful tutorial

     

    What does "anything" meaning. Being more specific would help figuring out what your situation is. This said if what I understand is correct, a read of the OP should answer your question. Let me know if it doesn't.

     

    Hi,

    "anything" means all see on the screen in a blank, black screen. No grub menu.Not even an error message.

  8. ESXi does not support VM booting from USB. You can work around the issue with "plop boot manager". Basically, you use CDROM iso as a boot drive in your VM, which then points to the USB stick.

     

    I am not sure it's worth the trouble. If you want to edit the config file on the VM, you can just do that, there's no need to use a USB image as a work around.

     

    It actually does just fine. Just create a new VM with OS Microsoft (whatever version supports EUFI), add a USB controller and USB device, enable EUFI boot in the advanced settings en have the VM boot in UEFI directly. Then just choose the USB drive as boot disk and have fun.

     

    That's what I did. I use 2 USB sticks to run everything:

    Bootdevice USB1 = ESXi (boots the Baremetal)

    Bootdevice USB2 = Synology (boots through ESXi in VM)

     

    OR2Y6Er.png

     

    3N70Yqj.png

     

    Hi Wolfwood,

    Can you detail how you put the raw mapped drives into your esxi setup for this VM? Much thanks

×
×
  • Create New...