Jump to content
XPEnology Community

Leaderboard

Popular Content

Showing content with the highest reputation on 11/13/2019 in all areas

  1. Hello! 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 5-1. in another way, Download ch_cpuinfo.tar with wget wget https://github.com/FOXBI/ch_cpuinfo/releases/download/ch_cpuinfo/ch_cpuinfo.tar 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” made a video of the how to run ch_cpuinfo. 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) ==================================================== 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 4.2.0-r01) 2023.02.18 - Application of AMD's CPU information collection function improvement - xpenlib(cpu_info.sh) refered https://github.com/FOXBI/xpenlib/blob/main/cpu_info.sh Update new version (ch_cpuinfo ver 4.2.1-r01) 2023.03.05 - Fixed error when users of previous version perform redo with version 4.2.0-r01 (Thanks for the @Mentat report.) 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 !! Let's pray and support together for the two countries where the earthquake caused great damage and many deaths and missing people. ============================================= Download links: ch_cpuinfo ver 4.2.0-r01 - new version update -> ch_cpuinfo ver 4.2.1-r01 - new version update -> ch_cpuinfo.tar Reference images # 1.04b + DS918+ # 1.03b + DS3615xs # 1.03b + DS3617xs # Normal output is possible even when using more than 8core. # Support DSM 7.x
    1 point
  2. По просьбам трудящихся )))) Запускаем клиент iVMS-4200, находим свою камеру и начинаем править, но не во вкладке "Устройство" , а во вкладке "Группа". Ищем там свою камеру и правим вкладку "Time". Я сменил сервер времени. И почему то, замена Домена не сработала, а сработал только IP Время изменилось. Смотрим скрин ниже.
    1 point
  3. https://xpenology.com/forum/topic/13011-generate-an-original-synology-usb-key/ with the right usb flash drive and the right tool you can do what manufacturer in china do and enter your own vid/pid i did this last year but had not much use for it and gave it to someone here in the forum i was using DynaMassStorageProductionTool, maybe even wrote about it here in the forum (can't remember) that was the initiator article https://xpenology.com/forum/topic/9897-flash-transplant/?tab=comments#comment-85621 edit: still have one for testing Device Type: Mass Storage Device Protocal Version: USB 2.00 Current Speed: High Speed Max Current: 500mA USB Device ID: VID = F400 PID = F400 Device Vendor: Synology Device Name: Diskstation Device Revision: 0100 Manufacturer: Synology Product Model: Diskstation Product Revision: 0100 Controller Vendor: SMI Controller Part-Number: SM3259AA1 - ISP 161122-DG1 Flash ID code: 45DE9493 - SanDisk SDTNRGAMA-008G - 1CE/Single Channel [MLC-16K] -> Total Capacity = 8GB
    1 point
  4. Multiple vulnerabilities allow remote authenticated users to execute arbitrary commands or conduct denial-of-service attacks, or allow remote attackers to delete arbitrary files via a susceptible version of DiskStation Manager (DSM). Note: Synology recommends to update DSM to 6.2.2-24922-4. Before updating please check the updates report section. If your system is not open to the internet (NAT, port forwarding, QuickConnect, etc.) you should be safe. Further infos on Synology website.
    1 point
  5. Я нашёл решение. Достаточно поставить "maxlanport="5" в файле /etc.defaults/synoinfo.conf и видятся все порты. Заодно убавил количество пустых ячеек для дисков.
    1 point
  6. even in kernel 4.4.59 of the 918+ (newer kernel then th other two) the latest i can see in the kernel driver is SAS3108 so it will need to build from external source and i do have newer source but we tried it with the 36165/17 (older kernel) and it did not work maybe with the newer kernel 4.4. of the 918+ it will work atm i do have a SAS2008 and my new nas hardware (not in use yet) for testing so i can at least compile a new driver and test is with the older card i will try this in the next hours a i'm on the 918+ drivers for a new 1.04b extra.lzma package [18.12.2017] new 4.4, ... update driver mpt3sas to v23 for SAS93xx/SAS94xx support, ... ... [14.01.2018] new 4.5, revert driver mpt3sas to jun's and in case of 916+ to kernel default as SAS94xx support did not work (kernel oops), ... no, its not just compiling it :: Loading module mpt3sas[ 4.449175] BUG: unable to handle kernel paging request at 000000010000008f [ 4.456576] IP: [<ffffffff813a42b0>] scsi_setup_command_freelist+0x80/0x280 [ 4.463961] PGD 45131b067 PUD 0 [ 4.467420] Oops: 0000 [#1] PREEMPT SMP [ 4.471614] Modules linked in: mpt3sas(OE+) megaraid_sas(E) megaraid(E) mptctl(E) mptspi(E) mptscsih(E) mptbase(E) raid_class(E) libsas(E) scsi_transport_sas(E) scsi_transport_spi(E) megaraid_mbox(E) megaraid_mm(E) vmw_pvscsi(E) BusLogic(E) usb_storage xhci_pci xhci_hcd usbcore usb_common imwz(OE) [ 4.499888] CPU: 1 PID: 4197 Comm: insmod Tainted: G OE 4.4.59+ #24922 [ 4.507930] Hardware name: Gigabyte Technology Co., Ltd. B360M-HD3/B360M HD3, BIOS F13 06/05/2019 [ 4.517334] task: ffff880456a06100 ti: ffff880450bc8000 task.ti: ffff880450bc8000 [ 4.525264] RIP: 0010:[<ffffffff813a42b0>] [<ffffffff813a42b0>] scsi_setup_command_freelist+0x80/0x280 [ 4.535257] RSP: 0018:ffff880450bcbac0 EFLAGS: 00010202 [ 4.540881] RAX: ffff880456a06100 RBX: ffff8804579b4000 RCX: ffffffffa0187140 [ 4.548422] RDX: ffff880456a5b580 RSI: 0000000000000001 RDI: ffffffff818536c0 [ 4.555943] RBP: ffff880450bcbaf8 R08: 000000000000000a R09: ffff8804542d6800 [ 4.563519] R10: 0000000000000001 R11: 0000000000000000 R12: 00000000024000c0 [ 4.571068] R13: ffff8804579b4030 R14: 000000010000007f R15: ffffffffa0187140 [ 4.578633] FS: 00007f46e7af9700(0000) GS:ffff88046e480000(0000) knlGS:0000000000000000 [ 4.587206] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 4.593292] CR2: 000000010000008f CR3: 00000004578e8000 CR4: 00000000003606f0 [ 4.600856] Stack: [ 4.602998] ffffffff8129a6dd 00000001579b4000 ffff8804579b4000 ffff8804579b4208 [ 4.610910] ffff88045b995090 ffff88045b995090 ffff8804579b4000 ffff880450bcbb30 [ 4.618831] ffffffff813a4a6f 0000000000000000 ffff8804579b4788 ffff88045b995000 [ 4.626796] Call Trace: [ 4.629391] [<ffffffff8129a6dd>] ? __blk_queue_init_tags+0x3d/0x80 [ 4.636001] [<ffffffff813a4a6f>] scsi_add_host_with_dma+0x9f/0x310 [ 4.642646] [<ffffffffa015284a>] _scsih_probe+0x64a/0xc80 [mpt3sas] [ 4.649376] [<ffffffff812ffbcc>] pci_device_probe+0x8c/0x100 [ 4.655460] [<ffffffff81387681>] driver_probe_device+0x1f1/0x310 [ 4.661888] [<ffffffff81387822>] __driver_attach+0x82/0x90 [ 4.667773] [<ffffffff813877a0>] ? driver_probe_device+0x310/0x310 [ 4.674420] [<ffffffff81385711>] bus_for_each_dev+0x61/0xa0 [ 4.680409] [<ffffffff81387119>] driver_attach+0x19/0x20 [ 4.686139] [<ffffffff81386d43>] bus_add_driver+0x1b3/0x230 [ 4.692128] [<ffffffffa018e000>] ? 0xffffffffa018e000 [ 4.697562] [<ffffffff8138802b>] driver_register+0x5b/0xe0 [ 4.703464] [<ffffffff812fe6a7>] __pci_register_driver+0x47/0x50 [ 4.709898] [<ffffffffa018e1ea>] _mpt3sas_init+0x1ea/0x203 [mpt3sas] [ 4.716708] [<ffffffff810003b6>] do_one_initcall+0x86/0x1b0 [ 4.722706] [<ffffffff8111703d>] ? __vunmap+0x8d/0xf0 [ 4.728141] [<ffffffff810e1b48>] do_init_module+0x56/0x1be [ 4.734050] [<ffffffff810b7d8d>] load_module+0x1dfd/0x2080 [ 4.739962] [<ffffffff810b51f0>] ? __symbol_put+0x50/0x50 [ 4.745767] [<ffffffff811160c5>] ? map_vm_area+0x35/0x50 [ 4.751469] [<ffffffff8111740c>] ? __vmalloc_node_range+0x13c/0x240 [ 4.758196] [<ffffffff810b810f>] SYSC_init_module+0xff/0x110 [ 4.764281] [<ffffffff810b81a9>] SyS_init_module+0x9/0x10 [ 4.770096] [<ffffffff8156a74a>] entry_SYSCALL_64_fastpath+0x1e/0x92 [ 4.776900] Code: 8b 8b c0 00 00 00 41 81 e4 bf 00 40 02 41 83 c4 01 8b b1 68 01 00 00 85 f6 74 71 4c 8b b1 70 01 00 00 4d 85 f6 0f 84 da 00 00 00 <41> 8b 46 10 85 c0 74 7d 83 c0 01 48 c7 c7 c0 36 85 81 41 89 46 [ 4.798263] RIP [<ffffffff813a42b0>] scsi_setup_command_freelist+0x80/0x280 [ 4.805751] RSP <ffff880450bcbac0> [ 4.809434] CR2: 000000010000008f [ 4.812946] ---[ end trace af6f0f37cfffe320 ]---
    0 points
×
×
  • Create New...