thomas

Are you using USB 3.0?

@gadreel Use virt-manager to connect to qemu over TCP; add 2 more serial ports to have 3 in total for the VM; start the VM, connect to the console on the 3rd serial port and magic will happen...

Indeed, the image boots with OVMF, but it seems it has issues with Seabios... I deleted my other VM test with Seabios and now I can't replicate it... I don't think this is a nested virtualization I booted the image you're referring to and it only works in Seabios mode and you can see the whole process..

I sent you the whole XML on PM. For me it's working fine. any MAC will do maybe you changed something in the img when you created your own entries... after the menu it should go to a screen like this https://ibb.co/hy1hwF

Both OVMF and Seabios are working First time you need to choose Bare metal Force Install option and after reboot first option... hvm Thomas

Hi, I'm running DSM 6.1 on Unraid (KVM) as VM and it's working fine with synoboot.img from "DS3615xs 6.1 Jun's Mod V1.02-alpha.zip"(http://xpenology.com/forum/viewtopic.php?f=2&t=20216). For the loader (synoboot.img) I used "USB" type, for the virtual drive "SATA" and for the network "e1000". Booting is really fast (~1 minute) I hope this helps you... Thomas

HI, I did the changes in the /etc/rc.subr, in there I found the specified lines, but after reboot there is no difference. Am I missing something? I can mount manually the nfs share, so I think the command is correct... Thanks

The amount of data that's recorded depends on several factors like how much motion you have in the image, changes in luminosity and some others. This usually happens if you have camera's set to do VBR. If you have CBR the files should be almost the same as the software tries to fill up the bit rate to match what you entered.

That's the best way to learn...

Find the VID and PID of the usb and modify the isolinux.cfg file with these values and the usb disk won't appear anymore in the DSM.

The answer is add LABEL test MENU LABEL Ubuntu localboot -1 to the isolinux file and when selecting Ubuntu it will boot from the 1st drive on the machine. In my case 1st drive is Ubuntu and 2nd is the XPEnology. Problem solved...

Hi, I have a XPenology nas and on a spare drive I installed Ubuntu and made the data available to it so I can use Kodi and the HDMI output. I can boot now by selecting the boot drive from BIOS, but it will be easy if I can add a new entry to the boot menu. Please let me know if anybody can give me a hint on how can I do it. Thanks

I tried the one in the answer. For the drive to be attached to the USB you need an adapter with external power. Easiest check is sudo fdisk -l and the answer will be something like Disk /dev/sda: 8589 MB, 8589934592 bytes 255 heads, 63 sectors/track, 1044 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00008ec7 Device Boot Start End Blocks Id System /dev/sda1 * 1 1013 8136891 8e Linux LVM /dev/sda2 1014 1044 249007+ 5 Extended /dev/sda5 1014 1044 248976 83 Linux You have to identify your wd red drive and change the mdadm -A --verbose --run /dev/md3 /dev/sdX5 accordingly. If you have only 1 drive attached to the computer it should be sda, if you have 2 it's either sda or sdb ...

Hi, You can try to mount the drive under linux (ubuntu) and check/copy the data. See the link below for a tutorial http://superuser.com/questions/550064/how-mount-find-recover-data-in-hdd-outside-of-synology-box I tried under ubuntu 14.10 live cd and it worked for me. Make sure that you adapt it for your drive (sdc5).

From my testing the corruption of the BIOS occurs only when you're trying to wake up the nas at a specific time from DSM, all the other settings should be harmless. My fix was to use the "Power by RTC" from the BIOS to wake up the machine at a specific time everyday.

I have updated the bios and it's working fine, also 5.1 and wake on lan.