Panja Posted January 14, 2014 Share #76 Posted January 14, 2014 Why would I want to change the MAC address and/or the serial? What's the reason people change it? Quote Link to comment Share on other sites More sharing options...
myhtpc Posted January 14, 2014 Share #77 Posted January 14, 2014 If you want to Run two synologies / xpenologies, you need to change one's Mac adress. WOL also requires modification to be aligned with the adress of the (virtual) Adapter. Quote Link to comment Share on other sites More sharing options...
Panja Posted January 14, 2014 Share #78 Posted January 14, 2014 Ok, clear. Thanks for the answer. I'm only running 1 Xpenology. Quote Link to comment Share on other sites More sharing options...
martin Posted January 16, 2014 Share #79 Posted January 16, 2014 - Just add the link in first post to Tuatara's how to CIFS mount : I will update modules (compiled with the "esxi" sources) to fix it Thanks Trantor, I'm waiting for this to be fixed together with NFS (which has been fixed already), I know you're doing this on your own free time but you think I should upgrade from the ESXi v1.0 to the v1.1beta to get NFS working or rather wait some weeks for cifs to be fixed? BR Quote Link to comment Share on other sites More sharing options...
Trantor Posted January 16, 2014 Author Share #80 Posted January 16, 2014 - Just add the link in first post to Tuatara's how to CIFS mount : I will update modules (compiled with the "esxi" sources) to fix it Thanks Trantor, I'm waiting for this to be fixed together with NFS (which has been fixed already), I know you're doing this on your own free time but you think I should upgrade from the ESXi v1.0 to the v1.1beta to get NFS working or rather wait some weeks for cifs to be fixed? BR In your running v1.0 just copy modules provided in v1.1 to /lib/modules/. Reboot and NFS should work Quote Link to comment Share on other sites More sharing options...
costib Posted January 21, 2014 Share #81 Posted January 21, 2014 @ Trantor: Could not wait till the weekend starts, just tried now...See here: viewtopic.php?f=2&t=558&p=10088#p10088 IT WORKS! so we have VMTools up and runnig Doc! Looking further for the next complete release. Something like v5 Beta for bare-metal install, would be nice to have: NFS + CIFS + bootstratp + open-vm-tools + Update 4 included into a complete package - ESXi v1.2 maybe ? Quote Link to comment Share on other sites More sharing options...
martin Posted January 21, 2014 Share #82 Posted January 21, 2014 Thanks Trantor, upgraded to v1.0 update4, with modules from v1.1 - NFS working like a charm now just to fix that CIFS.. Quote Link to comment Share on other sites More sharing options...
jokies Posted January 28, 2014 Share #83 Posted January 28, 2014 This is not an official synology productThis is only design for testing purpose not for production. No warranty for any damages, loss of data or anything else. This is based on jukolaut's work. Create the virtual machine to esxi and add hardware: - IDE controller with single harddisk (vmdk file in archive). Boot from this. - PVSCSI controller and raw harddisks or vmdk files for data. - VMXNET3 / E1000 network. - Boot, install with pat file from standard build with Synology Assistant, Enjoy Version 1.1 is now available : http://xpenology.trantor.be/esxi/ (please click on ad to help me with this project) How to install optware bootstrap and open-vm-tools (thanks to Tuatara) I'm not an ESXi expert, if someone can help me improve this version Changelog: v1.1 (22/12/2013) - Fix NFS support (copy modules to /lib/modules) v1 (15/12/2013) - Patch kernel source with jukolaut fix to get VMware PVSCSI working - Patch synobios to prevent SYNOIO messages - Build special ESXi kernel - All drivers included in standard version are also present here except SATA ones TODO LIST: - Make full repack (pat + vmdk) - Build open-vm-tools Today I connected a Synology Audio port (It's actually a USB sound card with several output methods) which I used to use with my 713+ to my ESXi server. I found that my DSM on ESXi will crash if I play a song through the Audio port. It will not crash immediately, only after the song is finished will the problem show up. After that I cannot connect though both ssh and web interface of DSM, inside the log I can see "Audio interface registered" but nothing else. The USB Synology Audio port is manually assigned to DSM instead of working under passthrough mode because my CPU doesn't support it. Inside the Audio port there are one C-Media CM102S+ audio chip and a GL850G USB 2.0 HUB Controller. Any idea? Even how to debug it? Thank you all the same. Quote Link to comment Share on other sites More sharing options...
gooba Posted January 29, 2014 Share #84 Posted January 29, 2014 Hi, I have a problem with this image XPEnology DS3612xs DSM 4.3 build 3810 (ESXi v1.1)... when I boot the VM, I see an error "Error internal NIC devices 1 does not equal to internal NIC number 4". The main problem is, that ESX 5.5 and all other VMs stops responding to the network requests. So I need to shutdown virtual xpenology via ESXi shell. Any Idea?? br Quote Link to comment Share on other sites More sharing options...
gooba Posted January 29, 2014 Share #85 Posted January 29, 2014 Tried some more to resolve(adding multiple network adapters)...no success it boots normally only if I add no network adapters. But this is not good as this is NAS and needs network Quote Link to comment Share on other sites More sharing options...
mattyj1085 Posted January 31, 2014 Share #86 Posted January 31, 2014 Ignore - fixed Quote Link to comment Share on other sites More sharing options...
stanza Posted February 1, 2014 Share #87 Posted February 1, 2014 Hi, I have a problem with this image XPEnology DS3612xs DSM 4.3 build 3810 (ESXi v1.1)... when I boot the VM, I see an error "Error internal NIC devices 1 does not equal to internal NIC number 4". The main problem is, that ESX 5.5 and all other VMs stops responding to the network requests. So I need to shutdown virtual xpenology via ESXi shell. Any Idea?? br Change your grub.conf file Has something like nwinf=4 Change the number to 1 Reboot Quote Link to comment Share on other sites More sharing options...
obermotz Posted February 12, 2014 Share #88 Posted February 12, 2014 Hi, I have just installed DSM4.3 on my Microserver N40L running ESXi 5.5 . Everything but raw HDD mapping seems to work fine. I followed this guide: http://forza-it.co.uk/esxi-5-1-using-raw-device-mappings-rdm-on-an-hp-microserver/ . Unfortunately the mapped HDD does not appear in Storage Manager, altough I can see it using fdisk -l as /dev/sdq (it's a 2TB Toshiba drive which has data on it / was used before in another XPEnology install). Any advice on this would be greatly appreciated. Disk /dev/sdq: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdq1 1 311 2490240 fd Linux raid autodetect Partition 1 does not end on cylinder boundary /dev/sdq2 311 572 2097152 fd Linux raid autodetect Partition 2 does not end on cylinder boundary /dev/sdq3 588 243201 1948793440+ fd Linux raid autodetect Quote Link to comment Share on other sites More sharing options...
sl0n Posted February 13, 2014 Share #89 Posted February 13, 2014 Any advice on this would be greatly appreciated. Being on ESXi console, please do "ls -al //" and show us the output. Vladimir Quote Link to comment Share on other sites More sharing options...
sl0n Posted February 13, 2014 Share #90 Posted February 13, 2014 Any advice on this would be greatly appreciated. Being on ESXi console, please do "ls -al //" and show us the output. Vladimir Quote Link to comment Share on other sites More sharing options...
obermotz Posted February 13, 2014 Share #91 Posted February 13, 2014 Any advice on this would be greatly appreciated. Being on ESXi console, please do "ls -al //" and show us the output. Vladimir Here you are: /vmfs/volumes/52fabec3-1e8a19f1-8f9e-009c02aa64fd/DSM # ls -al total 52465680 drwxr-xr-x 1 root root 2100 Feb 12 23:18 . drwxr-xr-t 1 root root 1960 Feb 12 21:47 .. -rw------- 1 root root 2000398934016 Feb 12 22:34 2TB_HITA-rdmp.vmdk -rw------- 1 root root 500 Feb 12 22:35 2TB_HITA.vmdk -rw------- 1 root root 53687091200 Feb 12 23:17 DSM-flat.vmdk -rw------- 1 root root 8684 Feb 12 23:17 DSM.nvram -rw------- 1 root root 465 Feb 12 22:58 DSM.vmdk -rw-r--r-- 1 root root 0 Feb 12 21:47 DSM.vmsd -rwxr-xr-x 1 root root 2947 Feb 12 23:18 DSM.vmx -rw-r--r-- 1 root root 258 Feb 12 21:47 DSM.vmxf -rw-r--r-- 1 root root 32440320 Dec 22 18:17 synoboot_trantor_3810_esxi_v1.1-s001.vmdk -rw------- 1 root root 362 Feb 12 21:52 synoboot_trantor_3810_esxi_v1.1.vmdk -rw-r--r-- 1 root root 204443 Feb 12 22:16 vmware-1.log -rw-r--r-- 1 root root 151516 Feb 12 22:48 vmware-2.log -rw-r--r-- 1 root root 151918 Feb 12 23:18 vmware.log Quote Link to comment Share on other sites More sharing options...
obermotz Posted February 13, 2014 Share #92 Posted February 13, 2014 Any advice on this would be greatly appreciated. Being on ESXi console, please do "ls -al //" and show us the output. Vladimir Here you are: /vmfs/volumes/52fabec3-1e8a19f1-8f9e-009c02aa64fd/DSM # ls -al total 52465680 drwxr-xr-x 1 root root 2100 Feb 12 23:18 . drwxr-xr-t 1 root root 1960 Feb 12 21:47 .. -rw------- 1 root root 2000398934016 Feb 12 22:34 2TB_HITA-rdmp.vmdk -rw------- 1 root root 500 Feb 12 22:35 2TB_HITA.vmdk -rw------- 1 root root 53687091200 Feb 12 23:17 DSM-flat.vmdk -rw------- 1 root root 8684 Feb 12 23:17 DSM.nvram -rw------- 1 root root 465 Feb 12 22:58 DSM.vmdk -rw-r--r-- 1 root root 0 Feb 12 21:47 DSM.vmsd -rwxr-xr-x 1 root root 2947 Feb 12 23:18 DSM.vmx -rw-r--r-- 1 root root 258 Feb 12 21:47 DSM.vmxf -rw-r--r-- 1 root root 32440320 Dec 22 18:17 synoboot_trantor_3810_esxi_v1.1-s001.vmdk -rw------- 1 root root 362 Feb 12 21:52 synoboot_trantor_3810_esxi_v1.1.vmdk -rw-r--r-- 1 root root 204443 Feb 12 22:16 vmware-1.log -rw-r--r-- 1 root root 151516 Feb 12 22:48 vmware-2.log -rw-r--r-- 1 root root 151918 Feb 12 23:18 vmware.log Quote Link to comment Share on other sites More sharing options...
obermotz Posted February 13, 2014 Share #93 Posted February 13, 2014 I had a look at dmesg and looked for 'sdq' (the HDD which is detected by fdisk but not by Storage Manager) and 'sda' which is the smallish IDE HDD where DSM is installed. I could not find anything peculiar (most likely due to my noobness) but I in case anyone cares here it is: http://drose1.homelinux.com/dmesg.zip Quote Link to comment Share on other sites More sharing options...
obermotz Posted February 13, 2014 Share #94 Posted February 13, 2014 I had a look at dmesg and looked for 'sdq' (the HDD which is detected by fdisk but not by Storage Manager) and 'sda' which is the smallish IDE HDD where DSM is installed. I could not find anything peculiar (most likely due to my noobness) but I in case anyone cares here it is: http://drose1.homelinux.com/dmesg.zip Quote Link to comment Share on other sites More sharing options...
matsca2m Posted February 14, 2014 Share #95 Posted February 14, 2014 Hi, I have a problem with LSI SAS 9211-8i. I am using ESXI 5.5 and have enabled Direct passthrough for the LSI SAS and connected 8 Sata 2TB sata drives to the controller. When I start the Virtual machine it finds 8 harddisks but when I try to install the software it all ends up with that the information was lost. According to the first post, LSI SAS 9211-8i was supported. Quote Link to comment Share on other sites More sharing options...
matsca2m Posted February 14, 2014 Share #96 Posted February 14, 2014 Hi, I have a problem with LSI SAS 9211-8i. I am using ESXI 5.5 and have enabled Direct passthrough for the LSI SAS and connected 8 Sata 2TB sata drives to the controller. When I start the Virtual machine it finds 8 harddisks but when I try to install the software it all ends up with that the information was lost. According to the first post, LSI SAS 9211-8i was supported. Quote Link to comment Share on other sites More sharing options...
sl0n Posted February 14, 2014 Share #97 Posted February 14, 2014 obermotz, here is mine for 3TB disks, I wonder if your 510 size is an issue here [spoiler=ls output]~ # ls -al /vmfs/volumes/local_ssd_230g/rdm/ total 1032 drwxr-xr-x 1 root root 840 Dec 13 06:29 . drwxr-xr-t 1 root root 2660 Jan 25 2014 .. -rw------- 1 root root 3000592982016 Jan 22 2014 3TB_WD2DWMC4N1321806-rdmp.vmdk -rw------- 1 root root 512 Dec 13 06:29 3TB_WD2DWMC4N1321806.vmdk -rw------- 1 root root 3000592982016 Dec 12 16:35 3TB_WD2DWMC4N1538824-rdmp.vmdk -rw------- 1 root root 512 Dec 13 06:29 3TB_WD2DWMC4N1538824.vmdk Quote Link to comment Share on other sites More sharing options...
sl0n Posted February 14, 2014 Share #98 Posted February 14, 2014 obermotz, here is mine for 3TB disks, I wonder if your 510 size is an issue here [spoiler=ls output]~ # ls -al /vmfs/volumes/local_ssd_230g/rdm/ total 1032 drwxr-xr-x 1 root root 840 Dec 13 06:29 . drwxr-xr-t 1 root root 2660 Jan 25 2014 .. -rw------- 1 root root 3000592982016 Jan 22 2014 3TB_WD2DWMC4N1321806-rdmp.vmdk -rw------- 1 root root 512 Dec 13 06:29 3TB_WD2DWMC4N1321806.vmdk -rw------- 1 root root 3000592982016 Dec 12 16:35 3TB_WD2DWMC4N1538824-rdmp.vmdk -rw------- 1 root root 512 Dec 13 06:29 3TB_WD2DWMC4N1538824.vmdk Quote Link to comment Share on other sites More sharing options...
muhh3 Posted February 14, 2014 Share #99 Posted February 14, 2014 can somebody provide a full repack with patched pat & rdy openvm-tools for this version please. Quote Link to comment Share on other sites More sharing options...
muhh3 Posted February 14, 2014 Share #100 Posted February 14, 2014 can somebody provide a full repack with patched pat & rdy openvm-tools for this version please. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.