Jumat, 29 Oktober 2021

XPENOLOGY-cpu info

 Hello!

https://xpenology.com/forum/topic/13030-dsm-5x6x7x-cpu-name-cores-infomation-change-tool/


 

I am xpenology user. And I am an IT engineer who creates shell scripts as hobbies.

 

Please understand that it is written by a google translate site. because i’m korean who is not fluent in English.

 

I created a tool to change cpu information for Xpenology’s users. Modify the actual cpu name and cores of your pc or server.

 

Howto Run

=============================================================

 

1. Download attached file on your PC (ch_cpuinfo.tar)  (ch_cpuinfo_en.tar) / (ch_cpuinfo_kr.tar is file for korean)

 

2. Upload file to your DSM location (by filestation, sftp, webdav etc....)

 

3. Connect to ssh by admin account. (dsm > control panel > terminal & snmp > terminal > enable ssh check)

 

4. Switch user to root:

sudo su -

(input admin password)

 

 

5. Change directory to where ch_cpuinfo.tar file is located:

cd /volume1/temp

 

6. Decompress file & check file:

tar xvf ch_cpuinfo.tar
ls -lrt

(check root’s run auth)

 

 

7. Run to Binary file

./ch_cpuinfo

or

./ch_cpuinfo.sh  (If you use busybox in DSM 5.x, you can use it as a source file)

8. When you execute it, proceed according to the description that is output.

 

9. Check your DSM’s CPU name, CPU cores at “information center”

 

Extra Action

 

If you want to use ch_cpuinfo in your language

 

Modify and use the LANG.txt file in the same path as ch_cpuinfo.

 

It is possible to use after changing the English content of each variable after translation and changing the value of CUSTLANG in line 8 to Y.

 

Sample image(by Google trans)

ch_cpuinfo_pol.png.0ebc2dae3332f22c1912c0801ac93b29.png

 

ch_cpuinfo_rus.png.c8c1e8e0af914914d8f2ea23ff2bfc88.png

 

 

====================================================

 

Addtional,

 

Adjust binary to excute file made by shc(http://www.datsi.fi.upm.es/~frosal)

 

The tool does not inclue worms, bad code.

 

If you want to edit the CPU information yourself manually, please refer to the contents below.

 

———————————————————————————————————————————————————————————————

Location : /usr/syno/synoman/webman/modules/AdminCenter

Source :  admin_center.js / admin_center.js.gz(above 6.2)

 

Add Before -> if(Ext.isDefined(h.cpu_vendor)&&Ext.isDefined(h.cpu_family)&&Ext.isDefined(h.cpu_series)){

    o.push([_T("status","cpu_model_name"),String.format("{0} {1} {2}",h.cpu_vendor,h.cpu_family,h.cpu_series)])}

 

if(Ext.isDefined(h.cpu_cores)){o.push([_T("status","cpu_cores"),h.cpu_cores])}

 

Add contents: 

h.cpu_vendor="Intel";h.cpu_family="Xeon";h.cpu_series="E3-1220 V3";h.cpu_cores="4 Cores (1 CPU/4 Cores | 4 Threads)";

h.cpu_detail="<a href='https://ark.intel.com/content/www/us/en/ark/search.html?_charset_=UTF-8&q=E3-1220 V3' target=_blank>detail</a>"

 

Change contens:

String.format("{0} {1} {2}",h.cpu_vendor,h.cpu_family,h.cpu_series)

to

String.format("{0} {1} {2} {3}",h.cpu_vendor,h.cpu_family,h.cpu_series,h.cpu_detail)

———————————————————————————————————————————————————————————————

 

Finally,

 

All descriptions are based on version 6.2, and the actual executable file supports 5.x, 6.x and 7.x

 

Publish the source through github(https://github.com/FOXBI/ch_cpuinfo).

 

     For versions DSM 6.x and later, you can use the binary as before.

 

     If you use busybox in DSM 5.x, you can use it as a source file(ch_cpuinfo.sh).

 

Please contact me by comment or bug report, i’ll respond to you as much as possible within my ability.

 

Test & Made Environment

————————————————————————————————————

Base Server : HP ML310e v2 gen8 + VMware ESXi 6.0 + RDM

DSM : DSM 6.2.3-25426 Update 3 (DS3615xs)

 

Base Server : HP ML310e v2 gen8 + VMware ESXi 6.0

DSM : DSM 7.0.1-42214 (DS3615xs)

 

Base Server : HP ML310e v2 gen8 + VMware ESXi 6.0

DSM : DSM 7.0.1-42214 (DS918+)

 

Base Server : HP ML310e v2 gen8 + VMware ESXi 6.0

DSM : DSM 6.2.4-25556 (DS3615xs)

 

Base Server Intel E5-2630 v2 + VMware ESXi 6.7u2

DSM : 6.2.2-24922 Update 2 (DS3617xs)

————————————————————————————————————

 

Change Log

Update new version (ch_cpuinfo ver 3.3.1-r01) 2021.09.30

 - After executing ch_cpuinfo, add the current CPU information output before applying

 - Application of ch_cpuinfo was confirmed 3615, 918+.

 

Update new version (ch_cpuinfo ver 3.1.1-r01) 2021.09.26

 - Support DSM 7.x above

 - admin_center.js file sedding method add

 - Application of ch_cpuinfo was confirmed only in 918+.

    In DS3615, the information page does not appear at all, so I can't check it, but I don't know why. :(

 

Update new version (ch_cpuinfo ver 2.5.2-r01) 2021.06.21

 - CPU information gathering method change for AMD/Intel(ES/Unkown) CPU

 - In the case of AMD, the full name is output, and the ES CPU or Unkown CPU has been modified so that it can be output without error.

 - In addition, it has been modified to respond to the phenomenon that two lines of CPU information are output and errors occur.

   Thanks @Arithon for sharing the error information.

 I hope this version goes well

 

 

 

I am sorry for not being able to actively respond to your inquiries due to busy life. :)


Thank you!! Have a nice day!!

 

 

Cheer up!! We can do it!! 

 

Reduce activity & Stay home & Wear a Mask!!

 

Let's overcome COVID-19 !!

 

 

=============================================

 

Download links:

 

ch_cpuinfo ver 2.5.2-r02 - new version update

-> 

 

ch_cpuinfo ver 3.1.1-r01 - new version update

-> 

 

ch_cpuinfo ver 3.3.1-r01 - new version update

-> ch_cpuinfo.tarUnavailable

 

Reference images

 

 

ch_cpuinfo_001.png.dcc3561bc51a3311a58606d07e27070f.png

 

 

 

ch_cpuinfo_002.thumb.png.04dbe6fd8199a7c2bcaff90ca77ca9b1.png

 

ch_cpuinfo_003.png.274a30192947423455bab64176233e9f.png

 

 

# 1.04b + DS918+

cpu_918.png.018a5436c6bdf3139773bb43fd94868a.png

 

# 1.03b + DS3615xs

cpu_3615.png.2b50e530374b47dacc385bb2810e24e4.png

 

# 1.03b + DS3617xs

cpu_3617.png.c48c4c8fde32282c930aa82d5fbaa273.png

 

# Normal output is possible even when using more than 8core.

ch_cpuinfo_004.png.83472d1d18131b54c3ded84011078a42.png

 

 

# Support DSM 7.x

dsm_7_en.thumb.png.9f70d741538d9cff6be8d0f753406e39.png

dsm_7_3615_en.thumb.png.c0e82514d02ec3a97b5be8f825fba70c.png

 

 

mobile_002.thumb.png.0225ed52dddb9cc06553689121023059.png

 

 

  Update logs Archive (Reveal hidden contents)

 

 

Edited  by FOXBI
new version update

XPENOLOGY-v6.2-ok

 

Install Xpenology (DSM 6.2.1) on ESXi 6.7 – Ready made OVA file

There are plenty of tutorial on how to install Xpenology in virtual environment. I tried few method a year ago and given up. Recently I found newer how-to and success after hitting few bumps. You can refer to this post if you want to try on your own and learn something new along the path. I have decided to improvise it and prepare a ready made OVA file, to ease you importing this VM (or just being lazy to follow the step by step guide :)).

First of all, please download the OVA files from links at the bottom. After that, unzip it and start importing the OVA from your ESXi or VMWare Workstation. This OVA file was exported from ESXi 6.7, and running DSM 6.2.1 – latest version as of this post).

Drag all the 3 files to the import window

Choose Thick for best performance (pre-allocate disk space)

Increase Disk 2 if needed

Click finish to complete import and power on the VM

Wait for 1 minute and locate yoru DSM VM. The VM will obtain ip address from DHCP (you can check from your DHCP server) or just type find.synology.com in your web browser – it will scan your network and find the DSM

When DSM is located, click Connect

Enter your DSM info here

Click “Skip this step”

Go to Storage Manager to create your first disk pool

Drag the available disk from the left to the right

Next is to create volume pool

This is optional but recommended step. Download openvm-tool and install it using Package Center. This is to enable ESXi to have visibility on this VM such as IP Address and allow you to gracefully shutdown the VM from vSphere.

VM info is displayed correctly after open-vm-tool is installed.

Download links:
https://advanxer.com/goto/ofile
https://advanxer.com/goto/ufile
https://advanxer.com/goto/mega