Dadudeondacouch

Kinda busy atm but I had a quick look and sorry if this is no help at all but i'm pretty sure that ones because you are installing over the boot drive? To do this for virtualbox install I had to... write the boot img file to a usb drive and pass that physical drive through as a vmdk (raw img) boot from that vmdk (which is booting using your usb drive) once ready to install remove the usb boot drive and start the install when synology assistant says restarting with like 220 seconds you plug the boot drive back in and it should reboot and use the usb drive to start normally once you have it all installed remove the virtual/physical drive and replace it with the original boot hdd img if you install while the boot drive is mounted then it writes over the drive and destroys the boot files. you may be able to just unmount the boot img on vmware before you install and then once done remount it, I havent looked at dsm stuff for awhile but if you are booting up and seeing diskstation login on the console screen I'm pretty sure thats the fix.

I have tested it with mine but it always fails to create the link I know my switch supports it I have done it with a real synology nas, I haven't been able to test any other switches as I am not at work for another week. will check and report back when I can. BTW currently still on 4.2

did you set the mac address correctly in the network settings in virtualbox? I think I use 00113208D62A, I ran into the same problem once I can't remember how I fixed it.

viewtopic.php?f=2&t=1353

Your welcome, hdd will be fine (more reliable) I just had a spare ssd so I used it

On my n54l nothing happens, poweroff was working fine I double checked the file and permissions all ok. maybe wifi connection, bt or usb ups is causing a problem/telling dsm not to shutdown? I will test more tomorrow time for sleep now, I have been at work since 5am I had to drive for 7.5hrs swap over a server and drive 7.5hrs back to the office.

Probably should have mentioned I don't know much about linux lol

When I replace poweroff with syno_poweroff_feasible_check nothing happens even though dsm is idle? no shutdown, am I missing something?

make a copy of the boot image file before you install and when it says error writing config (it corrupts boot image file because it writes files to it) you need to delete the original and mount the good copy you made earlier. You can also write synoboot.img to a usb drive using win32diskimager and then create a vmdk of the physical drive and mount it in the vm, boot the vm and remove the usb drive then select pat file and install, once setup says rebooting quickly plug usb drive back in so it boots up normally (you can mount the original boot image and forget the usb drive once the install is finished).

I have 12gb ram but don't use much at all maybe 2-3 most of the time unless I have multiple vm's running in virtualbox, you only need to disable the things I said if you install onto an ssd, there are a few programs to help such as ssd tweaker and the samsung magician program that comes with samsung ssd's, if you google "optimize windows on ssd" you will see how to manually disable them.

I didn't get any errors when I tested but the dsm was idle, should I not use this method until you guys have refined it?

Windows take less than 30 seconds to fully load I also have virtualbox autostart and boot xpenology vm and it uses normal hard drive for all packages and data inside the vm, I don't use the ssd for caching within dsm. If you install windows onto ssd you should disable things like indexing, defragging, pagefile etc to limit reading and writing to the ssd otherwise they don't last long.

Maybe try Xpenology for dummies - viewtopic.php?f=2&t=514 Download the virtualbox files then open virtualbox on your pc and go to file then import appliance and it will create an xpenology vm. Open the vm settings and change the network adapter to the one on your pc, and also add any extra virtual drives you want to use (by default small boot drive and 20gb dynamic) If you are trying to use a real hard drive in the virtual machine look at this http://www.virtualbox.org/manual/ch09.html#rawdisk

OMG I LOVE YOU!!! Tested and working great on my N54L

Antivirus? I just installed a free lightweight av (microsoft security essentials) I also have antivirus on the nas (clam av) so most of the files are scanned by dsm. The ssd it makes the system run so much faster I like it very much and I only paid about $100 AUD for 128gb.

There may be a way to get it working on a single hard drive but I doubt it and if the host os is running at the same time as the guest they are reading and writing to the same drive at the same time so it will slow down the drive and wear it out alot quicker, as a nas you don't want it to slow down at all so you need to separate the guest and host onto different disks. I have a similar setup except with windows 7 and I had to do it like this to get good performance... 1st drive - 128gb ssd with windows + virtualbox with 2 virtual disks (boot disk and 20gb dsm) and my physical drive below. 2nd drive - 2tb sata2 hdd (uninitialised/turned off) in windows so that the dsm will use it properly. The 2nd drive has to be turned off in windows for it to work maybe this is also an issue in linux aswell but you can't turn it off because it is your os drive. I was unable to do it using just the 2tb drive I had to get another drive I think you may have the same problem. Goodluck, I think american users wake up soon so someone else might be able to help.

You might find your answer on this page http://www.virtualbox.org/manual/ch09.html#rawdisk After looking at your specs I see you have 1 HDD and you are trying to give the guest os (xpenology) access to just the 2nd partition while linux mint is on the 1st partition, I'm not 100% sure but I think you can only give xpenology full access to the whole drive. I think you need 2 HDD, 1st (small) drive for linux mint and then 2nd (large) drive for xpenology, even if you could use 1 hard drive for both os, the host and guest would be reading/writing at the same time. when dsm makes a volume it looks something like this... | 2gb partition | 2gb partition | rest of the space | But you are not giving xpenology access to the whole drive so it's messed up, that's the problem I think.

I had same problem but using windows it would start creating the volume then stop with an error it was caused by corrupt/incorrect vmdk I remade the vmdk and it worked fine. the windows command I used is... vboxmanage.exe internalcommands createrawvmdk -filename C:\disk1.vmdk -rawdisk \\.\PhysicalDrive1 Unfortunately I'm not using a linux host so I don't know the linux commands. If you look at the drives in storage manager do they look correct? size, details etc.

its 64 bit, the 3bit version is RS3413xs+ DSM 4.2-3211 x86 have a look at the sticky's

The usb thing would be awesome and may one day be possible but I'm guessing its complicated because its a major change to the way dsm operates and every path would need to be changed or patched which would likely cause even more issues with package updates etc. One thing with updating you can always test it with vm's first but even then I will still be worried lol I have enough storage in my server so I will temporarily copy my data off the nas when I update.

1. I prefer hardware over virtual machine, I'm using a hp n54l it seems to have really good performance. 2. Sometimes you can update sometimes you can't from what I've read. I haven't had to do it yet. How often do you really need to update dsm, features don't change that much. 3. You can fire up a vm with the same version dsm that was on your physical machine and connect the physical drives to the vm and get the data off them etc. I have tested that, the setup can easily be changed between vm and physical machine without losing data. YES each hard drive has the dsm installed, it's so if one fails it boots to the other (same as synology) YES I had the same worries but I feel safe with a raid10 and backup the most essential data to an old 2tb drive once a week. YES synology devices cost a fortune and I think they are over-priced considering what you get but still they are so damn sexy.

what the lol how did I read all that and somehow skip that post

Apparently in newer versions the spindown issue is fixed. dsm is installed onto all hard drives, each drive has a couple of small partitions before the data partition that has the dsm etc so if the first drive fails the os can be loaded from one of the others, I use a .sh script to un mount my internal usb driver after boot I just put it in the rc.d folder. this is all the script is and it seems to work great... sync; /usr/syno/bin/synousbdisk -umount sdk1; >/tmp/usbtab

Pretty sure thats to do with different board revisions or something, if the board has dual bios and the first gets corrupted it uses the 2nd bios to boot and repairs the first, if the board has a single bios then it corrupts and goes to default settings. I've never had an issue with it on mine (not very old).

I did have 2 3tb red nas drives in raid1 on my n54l and I was getting 100mb+ everything is new I have change my setup now though. I use the bays custom bios and trantor's x64 3211 build.