Jump to content
XPEnology Community

man275

Transition Member
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

man275's Achievements

Newbie

Newbie (1/7)

3

Reputation

  1. Really weird... I was struggling to install DSM 6.2.4-25556 on the latest version of ESXi. I had already gone through and successful for it a couple month ago. However this time it keeps returning to DSM installation page (the blue web UI) over and over. Suspected so many things but when I add/connect serial port to vm, it boots successfully which leads to account setting page. I don't know details why it happens, hope this helps for someone like me.
  2. A new DSM 7.0.1 seems just rolled out. https://www.synology.com/en-global/releaseNote/DSM Build number is +4 compared with previous RC 42214.
  3. I also struggled with 6.2.4u2 but no luck with my limited knowledge. Replacing rd.gz zImage with ones from 6.2.4update2 pat before building loader is failed.
  4. Is bromolow with linux-4.4.x.txz? Shouldnt it be 3.x kernel?
  5. Simple replacement of rd.gz and zImage from build img loader file by ones extracted from update2 pat doesnt work. Looking into rd.gz, they seem different. Any method making it happen on 6.2.4update2?
  6. @Orphée Confirmed not working for me as well. Once updated, it goes to recover. Something might be overwritten.
  7. For those who are stuck on file corrupted error (13) during DSM installation step with ESXi, I would like to share my workarounds. There are two things I've missed. 1. Choose SATA mode instead of USB! USB boot is for baremetal (physical usb thumb drive) or virtual USB emulation for hypervisor. The one we used to choose in the previous Jun's loader is just introduced in redpill by the latest update. So try with SATA mode passing synoboot_satadom=2 in grub.cfg. 2. Check your vmdk For long time, I have used a pair of files as bootloader, raw disk image file and dummy vmdk file which is pointing actual image file. This was the mistake. To obtain valid vmdk file, I first convert built img file using "qemu-img convert -f raw -O vmdk redpill-DS918+_6.2.4-25556_b1632162635.img boot.vmdk" in ubuntu shell, then again convert "vmkfstools -i boot.vmdk -d thin bootin.vmdk" in ESXi shell. Please let me know better way to do this. After these two things are resolved, it finishes DSM installation process and finally shows login screen! Thanks!
  8. Always used via browser. Thanks for the reply. It always shows two choices on boot, usb or sata. And tried usb by default. I will search what synoboot_satadom=2 is and try with that. Thanks.
  9. Anyone tried DS918+ 6.2.4 with the latest ESXi 7.0U2d? I used redpill-tool-chain_x86_64_v0.9.zip to build bootloader. SataPortMap=18 and DiskIdxMap=1000 configured for two attached vmdks (sata0:0 for bootloader sata1:0 for dsm installation having 50-100GB) It always failed with the file corrupted error (13) during DSM installation. Instead of compiling myself, I also tried someone else's after modifying grub.cfg but result was the same.
  10. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 6 - Loader version and model: JUN'S LOADER v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: VM - ESXi 7.0 on top of NUC7i5BNH - Additional comments: REBOOT REQUIRED, Some System of configurations have been reset to default (i.e. free port 80 in mustaches, contents in /usr/bin).
×
×
  • Create New...