dynax

I know it can be done as Quicknick did it in his loader configuration tool. Maybe he made entry that loads the Linux kernel and run a script by passing init=/path/script or he pass custom argument on the kernel command line. I've never tried so I can't pin down the specific. You may want to contact him to see how he did it. It's best to get a DNS server up and running on your ESXi host. Then you can SSH onto the ESXi host to see the IP address of your xpenology (or any VM for that matter). If you don't have physical access to the hardware then how are you going to get the hard drives for your NAS installed? For best/most stable config, you'll need to PCI-pass thru the entire HBA controller.

I am very sure HD hibernation does not work wit Jun's loaders when the loaders came out. I am not sure if anyone ever work out a patch for it. I was away for months so I am not that up to date on what's going on with xpenolgy.

You can host another VM (win/linux etc) on the same ESXi host to use find.synology.com from that VM (via remote log in that VM).

Polanskiman/everyone last time I check, DSM 6.0 won't let the HDD go to sleep mode. Is this fixed in the current version? Does anyone has a ovf for ESXi 5.5 of the newest loader? Thanks

I would tape close the inlet holes right below the hot swap bays. I would also tape close the side panel inlet holes. That way all the air is forced thru the hot swap bays cooling the HDD. As a trade off, your CPU and other components will run hotter. If everything gets too hot then get a spot cooling fan and mount it over the hot components to mix the air up and remove hot stagnant air.

the update addresses are stored in /etc/synoinfo.conf here are some text from the file # DSM auto update default server rss_server="http://update.synology.com/autoupdate/genRSS.php" package_update_channel="beta" update_server="http://update.synology.com/" small_info_path="http://update.synology.com/smallupdate" enable_pkg_autoupdate_all="no" pushservice_ds_info_updated="yes" rss_server_ssl="https://update.synology.com/autoupdate/genRSS.php" dsm_autoupdate_type="download" Change it to whatever to be on a safe side. dynax

I am not sure exactly what you mean from your post. But if you want Xpenology to see to use your RAID share natively (as volume2 for example), you can do just that. On your Xpenology, create a very small volume2. Then ssh onto your Xpenology box Edit the file /etc/rc search for the line # checking and Mounting filesystem(s) ... /usr/syno/bin/synobootseq --set-check-fs >/dev/null 2>&1 /etc.defaults/rc.volume start /etc.defaults/rc.syn start Add the above line (/etc.defaults/rc.syn start) below the rc.volume start Now you need to create file rc.syn in /etc.defaults In that rc.syn file put in the 3 lines: umount /volume2 sleep 2 mount -t nfs 192.168.1.100:/mnt/Vol01/Synology /volume2 Make the rc.syn file executable. Obviously, I use 192.168.1.100 as your host IP and /mnt/Vol01/Synology is just an example share location. Change it to match your setup. root users on both your xpenology and host must have the same password. After everything is done, in Xpenology you'll see that your small dummy volume2 is replaced with your RAID share. You can create shares and stuffs in Xpenology on that volume2.

BTFRS vs SHR is the same as Apple vs Orange. One is a file system, the other is a RAID management.

sorry i'm just guessing, its what i would try so .... looking further into the extra.lzma, there is /etc/rc.modules ... EXTRA_FIRMWARES="bnx2/bnx2-rv2p-09ax-6.0.17.fw bnx2/bnx2-rv2p-09-6.0.17.fw bnx2/bnx2-rv2p-06-6.0.15.fw tigon/tg3_tso5.bin tigon/tg3_tso.bin tigon/tg3.bin" ... so looks like the firmware file has to be mentioned in that file to work? Tossed a kernel ID? Not sure what that is supposed to mean but if modules were not compiled against the proper source code they would simply not work. Do not confuse modules and firmware. All modules within the v1.02a (or v1.02a2) loaders are compiled against DSM 6.1 source code and made to work with linux kernel 3.10.102. There is no other way around. In your case, the firmware seems to be missing. I checked the extra ramdisk and it is not there. The rc.modules also needs to be updated with the added firmware or whatever module you add in the ramdisk else it wont be loaded during kernel boot. I have made the necessary changes in the ramdisk. Let me know if it works (or not). I can't test it myself since I do not have that NIC. https://mega.nz/#!OQplzISJ!L6HzXJq2ZwX- ... k99jYVwKBc note to myself: This ramdisk only contains the additional firmware bnx2-mips-09-6.2.1b.fw on top of the default ones added by Jun. Nothing else. The original DSM 6.0 loader/modules was compiled with beta source code. Are you saying the DSm 6.1 loader (1.02a and such) was compiled with the released source code? if I remember correctly, the loader was available before the source code was. thanks

If you have a real Synology box, take a picture of it with MAC address/serial number then contact them. They'll get you sorted out. Until then, don't use quick connect. It will only be a matter of time before all external-access apps calls home for validation when they got sick of the abuse.

xpenology 5.2 works well with ASRock q1900-itx board. In BIOS, set the boot csm to legacy.

If you use ESXi 5.5 (or newer) 1) Use this loader (jun's) https://mega.nz/#!5koz0ZjZ!SLWdLCD2db22 ... m-aJQ4w2gI 2) Add a HDD 3) Then download the 6.1 pat file (DSM_DS3615xs_15047.pat) and install that That is a clean install. If you want to upgrade from your previous DSM. then skip step (2). Reboot and you are done.

Try this https://mega.nz/#!Ul5RXKQR!_IiCurbduvbR ... ggqj5vo_Sg I think it would work with LSI-9211. It has been a while and I don't even remember if the driver for your control was included or not.

Is this loader still based on the beta code similar to jun's loader?

[quote name="cuspess" Hey people' date=' while I am hoping to hear some experience sharing regarding the problem I faced, I have been researching and came across a statement saying "USB boot is not supported in ESXi". Can someone with related knowledge confirm that?? Thanks[/quote] ESXi does not support VM booting from USB. You can work around the issue with "plop boot manager". Basically, you use CDROM iso as a boot drive in your VM, which then points to the USB stick. I am not sure it's worth the trouble. If you want to edit the config file on the VM, you can just do that, there's no need to use a USB image as a work around.