mXfored

could not really get it running. Used args: -device 'piix3-usb-uhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/101/synoboot.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot' with boot: 3 in my case ( verfied with ESC ) but it never booted under proxmox 4.x with the JUNI bootloader https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng!ZoFxDQgB

what is your boot image? I had no issues with upgrades at all using it at a qcow2 image - could you explain a bit more?

A little update on my side, updated from 1.0.1jun+6.0.2update9 straight to 1.02b+6.1.2latest - went very smooth. Updates has been done on a HP Microserver Gen8 (Xeon), the installation is based on Proxmox4.x latest with drives passthrough. Hint: - after the first reboot, the VMware/ESXI grub entry is booted, be sure to reboot and select the first one - otherwise your drives wont be detected - virtio NIC / virtio drives still do not work

Some little additions ( i did not use this guide, but i think its more or less a good start ): 1. you want to add a serial console to the KVM, just add `serial0: socket` to the {VM_ID}.conf and then use qm terminal {VM_ID} to connect to the console This will let you see the bootstrap, see potential issues, login via tty and also see installation/migration progress steps 2. virtio for NIC/drives is not supported for the juni loader, even the current 1.02b one. So you stick to SATA and e1000 here 3. You might want to just convert the synoboot.img to a qcow2 image and use it as a drive : qemu-img convert synoboot.img -O qcow2 vm-100-disk-1.qcow2 Just create a qcow2 disk before, no matter which size, then convert the image and replace your disk in /var/lib/vz/images/{VM_ID}/vm-100-disk-1.qcow2 Then edit /etc/pve/qemu-server/{VM_ID}.conf and fix the "size" parameter of the drive to match the actual size: ls -la vm-100-disk-1.qcow2 4. Be sure to _also_ install a second test-VM where you do not use passthrough drives but rather images - install the same version and clone/snapshot/backup this VM When you plan to upgrade your production one, snapshot the test-vm, try to upgrade the bootloader/DSM there - if it fails, just revert to your old snapshot and report and the forum / wait until it gets fixed. When it fixed and it worked, make a new backup and now update your production system why this is important? Because VM-backups/snaphots of the production NAS wont help, since you use passthrough drives. --- I am running this on PVE 4.x stable ( latest ) and i had this running for 1.0.1 juni + 6.0.2 and today upgraded to 1.02b + 6.1.2

Hey Tom, interesting. Thats how i installed my Xpenology viewtopic.php?f=2&t=20216&start=1990#p92047 I am also using a Gen8 (though/also with Proxmox) I have a test VM i tried the 1.0.2 alpha bootloader with, but actually i could never discover it with the synology assistent ( network card issue ) - so basically e1000 is not working probably, i do not exactly know. What setup do you have with 6.1 / 1.0.2?

thank you for this awesome post and all your work! Looking at the drive changes, Virtio-net should be present, but it does not ( i cannot ) get it worked. Installed my system on a proxmox 4.2 described as here ( viewtopic.php?f=2&t=20216&p=92047#p92047 ) nothing special, just straight forward, but using the juni loader. After that, and after the update to 6.0.2u9 i tried to pick virtio-net, but that did not work. Question 1 - does switching to quicknick help with virtio-net? I could switch the loader to quicknick, but as stated in your first post, it does not really change much until just the most recent drivers, virtio seems to be there for a while. And also what made me sceptic is, that in you KVM-Installation guide, you also use e1000 - so shall i switch the loader to quickboot or is it not worth it? Question 2 - does quicknick support virti scsi drivers? Looking at viewtopic.php?f=2&t=24308#p81999 i guess its not the case. I am using the default SCSI controller type, but well, would love to use virtio for the disks ( passthrough ) for the performance

Installed on a proxmox4.4 KVM host today, Howoto Prepare - create a new vm with 1 drive _SATA0_, 50MB, qcow2 (not virtio, not SCSI) .. lets call this VM with the id 100 - again i assume your VMID is 100 for now, replace ALL 100 strings in the commands if you have something else ( to be expected, right ) - add a e1000 network card (NOT virtio) - download juni 6.0.2 - 1.0.1 ( https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcn ... A!k5NxiIjI ) .. see the original first post for updates viewtopic.php?f=2&t=20216 - unzip, convert the ESXI-base image with: qemu-img convert synoboot.img -O qcow2 synoboot.qcow2 - copy synoboot.qcow2 s over the disk you created before in proxmox cp synoboot.qcow2 /var/lib/vz/images/100/vm-100-disk-1.qcow2 Now you should use passthrough to add you storage-drives, again, use SATA (not SCSI and not virtio) - to do this use as often you have drives. Repeat this with all drives, qm set 100 -sata1 /dev/sdb If you have more drives qm set 100 -sata2 /dev/sdc (notice the sata2, for slot 2) Installation: - download DSM_DS3615xs_8451.pat from the original sources: https://usdl.synology.com/download/DSM/ ... s_8451.pat - do NOT use any other version for now - Just boot the VM now, AND select "barebone" NOT Vmware/ESXI ( this will not detect your extra drive later) - you will see "booting kernel.." an nothing more, thats all fine, use your synology assistant to install Update: - after the boot, go to upgrades and select "only important updates", then install update9. - do not install 6.1 since this will for now brick your box, also with the new 6.1 - 1.0.2-alpha loader - i had to hard-reset my VM after the first reboot on the update, but then everything worked just fine

Hello, Until now, i had a ubuntu installed on the nuc ( since debian had issues booting the time i tried it...due to the NUC being a PITA in those terms). I mounted the Zyxel using NFS and installed Plex on the nuc, and some minor stuff. But if you compare write speeds with native-nuc eSATA and zyxel...thats just awesome. 462MB/s read, 150MB/w with nuc .. while having arroudn 8MB/s on the zyxel (when running a raid1 on mdadm base ). Its a huge plus having nuc + esata running compare to nuc + seperate NAS. Now iam using a eSata attached RAID1 icybox with and additional internal SSD for the OS. I have a Zyxel 325v2, but i want to consolidate things. I even mixed up things, i dont have an i5 build in, but rather and i3. Havint this solution, i have a superior performance. Iam very familiar with proxmox and esxi, iam running huge infrastructures on those, but i think that is plain waste for the home-usage case. Its wasting performance ( esp. IO wise ) for the solution. - I tried nanoboot https://app.box.com/XPEnoboot but it seems my ethernet card is failing to init.. AFAIR nucs using an e1000e - but it has to be a quiet recent one. - booting up looked ok though, just cannot find the DSM using the assitent ( due to the offline eth0 adapter ) - Booting from USB is not trivial with NUC due to all the issue. My trick is using 2 USB sticks, this way both get recognized..using one..you cant even select one to boot (what intel did here is horrible..so fragile) - even with the latest bios. a) So my question is, if there is a more recent e1000e nanoboot image? b) what are the login credentials for the nanoboot image - maybe i can fix it myself? c) shall i try a USB2eth solution? Your questions/additions: Iam very pleased with the "hidden raid1" feature using the icybox. Both drives can be read as single drives on failures without issues - most of the NAS raids fail hard on this, making nas-hardware failure a plain nightmare. I dont need, by all means, a transparent Raid on the NAS OS. To be honest, i am pick Synology just due the Photo Station - anything else offered is convenient, but not needed. I can setup AFP / Timemachine / btsync myself in pretty much no time I have 15 years of linux knowledge and hope to get this running with some help. Hopefully!

Hello, using the search, mainly russion/frensh topics have been found related to nuc - iam not able to read them sorry. I am planning to run the the Synology build on my nuc i3 with an externa eSATA jbod raid and an internal SSD for the OS. UPDATE1: - I tried nanoboot https://app.box.com/XPEnoboot but it seems my ethernet card is failing to init.. AFAIR nucs using an e1000e - but it has to be a quiet recent one. - booting up looked ok though, just cannot find the DSM using the assitent ( due to the offline eth0 adapter ) - Booting from USB is not trivial with NUC due to all the issue. My trick is using 2 USB sticks, this way both get recognized..using one..you cant even select one to boot (what intel did here is horrible..so fragile) - even with the latest bios. a) So my question is, if there is a more recent e1000e nanoboot image? b) what are the login credentials for the nanoboot image - maybe i can fix it myself? c) shall i try a USB2eth solution? Thanks!