Leaderboard

can this bootloaer updated to 1.02b ? i'll try it this weekend : JunsMod102a-test-NICadd Thanks

Firstly, you must remember that unless you're passing the entire drive through to DSM to manage, you're effectively creating virtual disks with all the limited overheads created by ESXi. Performance will effectively be less than normal as the virtual drive has to go through multiple layers before it finally hits the real drive. With that out of the way however, your best option is as wer suggested to use single 'drives' with the maximum size you want per drive and then add them. DSM won't likely recognise the increased size of the bigger drive as its already partitioned it and installed DSM on it. You could create 2 x 100 GB virtual drives and JBOD them and then expand the array later by adding an additional 100 GB virtual drive.

reset the bios to defaults, then disable all unnecessary peripherals, set to boot from usb and disable all other boot options. try booting with no drives attached first to see if the nas appears on the network. also try your usb boot loader in another machine as a check that your image/grub settings are good

Hello, my first post and I really want to say thank you to all the community I've upgraded with success from 5.2-5967.1 update 3 to 6.1.2-15132 with loader 1.02b esxi 6.0 update 2 on Microserver gen8 with xeon E3 1220L v2 1 ssd for datastore on internal controller and passthrough of a LSi 9211-8i flashed in IT mode with 4 HDDs migration, no clean install and volume repair what I've done: 1) download the image file from first post here (I've used loader 1.02b ds3615) 2) edit settings of your current vm with xpenoboot 5.2 and write down MAC address 3) login to your DSM 5.2 web interface and write down serial number; shutdown the vm 4) download and install OSFmount, then mount the image file downloaded at point 1 (untick "read-only drive"); choose partiton 0 15MB 5) with notepad++ or similar edit grub.cfg with serial and MAC address from point 2 and 3, you can also change the default timeout; I haven't changed anything related to vid and pid 6) download and install StarWind V2V Image converter; convert the image file with modified grub.cfg (choose VWware ESX server image) 7) this will result in 2 files synoboot.wmdk and synoboot-flat.wmdk 8) upload them to the same datastore where you have xpenoboot.wmdk; you can use datastore browser to upload files 9) edit settings of the vm and delete the hard disk pointing to xpenoboot.vmdk virtual disk 10) add new hard disk scsi 0:0 independent non persistent pointing to synoboot.vmdk 11) I haven't added any serial port 12) start the vm and open immediately the console, because you have to select the third entry of the boot menu, the one related to esxi (I wasn't enough quick and needed a vm reset..) 13) open a web browser to find.synology.com 14) connect, install, migrate, manual install with the latest pat file you can download from links here https://xpenology.com/forum/topic/7294-links-to-dsm-and-critical-updates/ 15) in my case the ip was changed, so log in and update it, then update packeges in the package center... backup and replication is now called hyperbackup hope this helps someone bye

With v1.01 only DSM 6.0.2 will work. For DSM 6.1.1 and 6.1.2 you need v1.02b. The custom extra.lzma provided in the tutorial is only for v1.01 not for v1.02b. If there is no information on the screen (totally black screen) then it means the loader is simply not booting. There should be at least something as mentioned in the tutorial. Try the following on a formatted drive. Install DSM 5.2 or DSM 6.0.2 on your test machine (don't use the custom extra.lzma). Turn off the machine when DSM is installed and you can confirm having access to DSM GUI. Now burn v1.02b and modify the grub.cfg as you did for 5.2 or 6.0.2. When finished plug the usb and re-start the machine. Use Synology Asistant to find the machine and go through the upgrade process.

А подробней? Экстрасенсы в отпусках, отсюда не видно что случилось.. 1. Попробовать 1.02b - оно фиксено для 6.1.2 2. Откатится на 6.1.1 - не исключено что обновление малость кривое