Jump to content
XPEnology Community

XPEnology DS3612xs DSM 4.3 build 3827 (ESXi v1.2)


Trantor
 Share

Recommended Posts

This is not an official synology product

This 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 in 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 the pat file with Synology Assistant, Enjoy :smile:

 

 

Version 1.2 is now available : http://xpenology.trantor.be/esxi/ (please click on ad to help me with this project)

 

 

To install open-vm-tools : Install the provided .spk with the package center (thank gnoboot)

 

To install bootstrap : Connect to ssh as root, and type : sh syno-i686-bootstrap_1.2-7_i686.xsh then reboot

 

 

How to install optware bootstrap and open-vm-tools (old method) (thanks to Tuatara)

 

 

Changelog:

v1.2 (15/03/2014)

- Update to 4.3-3827 build
- Use *REAL* mac adresses (thank gnoboot)
- Change the default serial number (edit grub.conf to change it)
- Add PS2 keyboard support (you can now write in the esxi console)
- NFS and CIFS mount working
- iSCSI (block & regular) in iet mode working (For regular mode, LUN must be created with advanced LUN features disabled)
- Update mpt2sas to v18
- Sound drivers included
- HBA drivers are included (install DSM on a HBA is not supported)


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

Link to comment
Share on other sites

Since the release of your first ESXi version "3211_repack-trantor_v1.2a_beta2a", the main VM was in production without any problems, thanks!

 

Installed now a test VM with this version, looks good, no problems so far :ugeek: (no more error after installation, which was gone after reboot, with this version).

I plan to keep testing it for some time, to see if it's reliable enough.

If everything goes well, I hope to replace the 3211 version in the following weeks, with the next ESXi release of 4.3.

Luckily until then maybe we have the working vm-tools (the only important thing missing until now) and also the last official update included.

 

Once again, many thanks Trantor. You gave us a nice present for this Christmas :mrgreen:

PS: The patience has paid off :cool:

Link to comment
Share on other sites

Now i get timeout Creating NFS share

insmod: can't insert '/lib/modules/auth_rpcgss.ko': No such file or directory

 

I will look about this module.

 

Just tried now: "Connection failed. Please check your network settings" , and no apps are displayed.

But adding 3rd party repository sources works :???: .

 

This is strange because on my ESXi 5.5 package manager work and I can install apps... :???:

Does the console show anything ?

Link to comment
Share on other sites

Now i get timeout Creating NFS share

insmod: can't insert '/lib/modules/auth_rpcgss.ko': No such file or directory

 

I will look about this module.

 

Just tried now: "Connection failed. Please check your network settings" , and no apps are displayed.

But adding 3rd party repository sources works :???: .

 

This is strange because on my ESXi 5.5 package manager work and I can install apps... :???:

Does the console show anything ?

 

 

package Manager works now ... maybe there server was down?!?

 

Sk%C3%A6rmbillede%202013-12-16%20kl.%2012.42.33.png

Link to comment
Share on other sites

auth_rpcgss is build-in the kernel so module.

According /usr/syno/etc/rc.d/S83nfsd.sh we need : rpcsec_gss_krb5.ko, exportfs.ko and nfsd.ko.

When we try to insmod exportfs.ko there is an error : invalid module format, on the xpenology console : duplicate symbole (own by kernel).

 

Kernel need recompil to remove build-in exportfs.

 

Does tNFS work on the standard build ?

 

EDIT:

 

I don't know how to get EXPORTFS=m because NFSD=m/y force EXPORTFS=y :sad:

If someone know some kernel config voodoo magic ^^

Link to comment
Share on other sites

auth_rpcgss is build-in the kernel so module.

According /usr/syno/etc/rc.d/S83nfsd.sh we need : rpcsec_gss_krb5.ko, exportfs.ko and nfsd.ko.

When we try to insmod exportfs.ko there is an error : invalid module format, on the xpenology console : duplicate symbole (own by kernel).

 

Kernel need recompil to remove build-in exportfs.

 

Does tNFS work on the standard build ?

 

EDIT:

 

I don't know how to get EXPORTFS=m because NFSD=m/y force EXPORTFS=y :sad:

If someone know some kernel config voodoo magic ^^

 

NFS works in XPEnology_DS3612xs_3810-repack-trantor-v1.0 :-| in ESXI 5.5

Enabling NFS in XPEnology_DS3612xs_3810-repack-trantor-v1.0

Sk%C3%A6rmbillede%202013-12-17%20kl.%2008.41.45.png

 

The problem here is the missing ParaVirtual, under LSL logic SAS i get Disk overheating at random times, says 0`C not -1`C as the ESXI v1 version.

 

Enabling NFS in Esxi V1 gives :

Sk%C3%A6rmbillede%202013-12-17%20kl.%2009.07.24.png

Link to comment
Share on other sites

The problem here is the missing ParaVirtual, under LSL logic SAS i get Disk overheating at random times, says 0`C not -1`C as the ESXI v1 version.

 

Can you give more informations about this ?

 

 

Yes.. When i run XPEnology_DS3612xs_3810-repack-trantor-v1.0 in ESXI 5.5, it loops (reboots with ParaVirtual) guessing a missing driver?

When i tell it to use LSL Logic SAS as virtual SCSI, it boots, but under hard drive it shows disk temp at 0`C not -1 as we are used to, the real problem

comes when the disk is used, if you tab back and forth between the disk info tabs, sometimes if you're lucky you can see disk temp suddenly jump from 0`C to maybe

66`C next refresh ( switching tabs) it says 0`C again, but after a random time ( 2 - 10 mins) DSM shutdown, Message says " disk drive overheating DSM shutting down"

 

I think its becomes the incorrect temp has jumped over shutdown value in /usr/syno/etc.defaults/scemd.xml or /usr/syno/etc/scemd.xml file

 

t2ai.png

Disk temp jumping up and down, should be -1 ??

 

Was that the kind of info you where thinking about? :wink:

 

tYzG.png

Edited by Guest
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...