All Activity

Ce n’est pas si drôle que ça en a l’air ! Je m’en suis rendu compte car ma domotique n’avait plus de données du compteur justement. Ce qui m’inquiète c’est les prochaines facture d’électricité qui ne seront plus aussi fiables. Donc le pb est bien réel! je tente maintenant d’autres tests plus poussés à savoir trouver quel d’ongle USB parmi le Zigbee, le Zwave ou le RFLink qui pourrait engendrer ce pb.

Нужно в конфиге напротив мак адресов false в true переписать.

- Outcome of the update: NO - DSM version prior update: DSM 7.1.1-42962-Update 6 - DSM version AFTER update: DSM 7.2.1-64570-Update 1 - Loader version and model: ARPL-1.1-beta2a DS2422xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Supermicro H11SSL-I,Epyc7551p 32-core, 256 GB Mem. 3x1TB Raid5, 2x2TB Raid1, 2x8TB Raid1, SSD cache, UPS CPU BS650E Notes - manual update, required reboot

its OK

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.1.1-42962-Update 1 - DSM version AFTER update: DSM 7.1.1-42962-Update 6 - Loader version and model: ARPL-1.1-beta2a DS2422xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - Supermicro H11SSL-I,Epyc7551p 32-core, 256 GB Mem. 3x1TB Raid5, 2x2TB Raid1, 2x8TB Raid1, SSD cache, UPS CPU BS650E Notes - manual update, required reboot

так я же написал что реинсталл сделал, или надо как-то по-особому его делать?

после сборки лоадера не перезагружаться а выбрать DSM Reinstall Mode невнимательно прочитал. делали уже так.

привет, dsm установлен в proxmox, на лоадере 23.12 периодически отваливались диски, подключенные через проброшенный в вм lsi контроллер, решил обновиться, думал проблема исчезнет, а исчезла панель управления )) при запуске панели управления сверху появляется миниатюра с вечной загрузкой, нагуглил что подключенные по юсб устройства могут такое вызывать, но у меня ни одного не подключено что может быть? пересборку лоадера с форс реинсталлом пробовал - не помогло

Ich hab's inzwischen mit der entsprechenden Config, inkl. Cache geschafft und bin auch zuversichtlich, dass das bei meiner Datenart sowohl schreiben als auch lesend nützlich ist. Gerade weil viele Accounts parallel schreiben und auch diverse datenintensive Anwendungen per NFS & SMB laufen.

Hi, I have managed to successfully build a tcrp loader for DVA3221 (latest 0.10.0 release). It runs nicely in QEMU/KVM environment. My intention is to pass through an nvidia GPU to it. I have put the loader onto a virtio disk (that gets ignored by the DSM) installer and added 1 SCSI disk into the virtual host. Unfortunately, the DSM installer (I picked DSM_DVA3221_64570.pat from the Synology download center) failed. I managed to extract /var/log/messages from the failed installation and I can look further around if needed. The log file is full of various errors but kinda hard to tell where to start. Would anybody be willing to have a brief look into it? Thank you, Jonathan Below is a brief extract from the log + full log is in the attachment. I am a former embedded Linux developer, so I can investigate in any direction somebody could point me to. May 12 19:01:50 kernel: [ 24.129288] Brand: Synology May 12 19:01:50 kernel: [ 24.129689] Model: DVA-3221 May 12 19:01:50 kernel: [ 24.130092] This is default settings: set group disks wakeup number to 1, spinup time deno 1 May 12 19:01:50 kernel: [ 24.131289] synobios cpu_arch proc entry initialized May 12 19:01:50 kernel: [ 24.132008] synobios crypto_hw proc entry initialized May 12 19:01:50 kernel: [ 24.132730] synobios syno_platform proc entry initialized May 12 19:01:50 kernel: [ 24.141747] Module [denverton_synobios] is removed. May 12 19:01:50 kernel: [ 24.142458] synobios: unload May 12 19:01:50 kernel: [ 24.207574] md: md0 stopped. May 12 19:01:50 kernel: [ 24.208569] md: bind<sda1> May 12 19:01:50 kernel: [ 24.209252] md/raid1:md0: active with 1 out of 16 mirrors May 12 19:01:50 kernel: [ 24.256748] md0: detected capacity change from 0 to 8589869056 May 12 19:01:50 kernel: [ 24.455029] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities May 12 19:01:50 kernel: [ 24.479963] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) May 12 19:01:50 kernel: [ 24.559274] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities May 12 19:01:50 kernel: [ 24.622080] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: prjquota,rootprjquota May 12 19:01:50 kernel: [ 25.882473] VFS: opened file in mnt_point: (/dev), file: (/urandom), comm: (ttyd) May 12 19:01:50 kernel: [ 25.883709] VFS: opened file in mnt_point: (/dev), file: (/null), comm: (sh) May 12 19:01:50 kernel: [ 25.884861] VFS: opened file in mnt_point: (/dev), file: (/null), comm: (sh) May 12 19:01:50 kernel: [ 25.906925] VFS: opened file in mnt_point: (/dev), file: (/urandom), comm: (ttyd) May 12 19:01:50 kernel: [ 25.908113] VFS: opened file in mnt_point: (/dev), file: (/null), comm: (sh) May 12 19:01:50 kernel: [ 25.909209] VFS: opened file in mnt_point: (/dev), file: (/null), comm: (sh) May 12 19:01:50 kernel: [ 25.990325] md: md1 stopped. May 12 19:01:50 kernel: [ 25.991847] md: bind<sda2> . . May 12 19:01:57 findhostd: ninstaller.c:698 Dev: sda, DiskPath: /dev/sda, Partition version: 9 May 12 19:01:57 findhostd: ninstaller.c:139 Mount partion /dev/md0 /tmpRoot May 12 19:01:57 kernel: [ 35.572654] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities May 12 19:01:57 root: Failed to curl [https://dataupdate7.synology.com/juniorexpansionpack/v1/getUpdate?platform=denverton&buildnumber=64570][7] May 12 19:01:57 findhostd: ninstaller.c:168 umount partition /tmpRoot May 12 19:01:57 kernel: [ 35.640131] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) May 12 19:01:57 avahi-daemon[6058]: /etc/avahi/services/http.service: parse failure: service group incomplete. May 12 19:01:57 avahi-daemon[6058]: Failed to load service group file /etc/avahi/services/http.service, ignoring. May 12 19:01:57 findhostd: ninstaller.c:139 Mount partion /dev/md0 /tmpRoot May 12 19:01:57 kernel: [ 35.746642] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities May 12 19:01:57 findhostd: ninstaller.c:168 umount partition /tmpRoot May 12 19:01:57 kernel: [ 35.762100] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) May 12 19:01:57 findhostd: ninstaller.c:139 Mount partion /dev/md0 /tmpRoot May 12 19:01:57 kernel: [ 35.790132] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities May 12 19:01:57 findhostd: ninstaller.c:446 failed to get upnpmodelname from [/tmpRoot/etc.defaults/synoinfo.conf]. May 12 19:01:57 findhostd: ninstaller.c:453 failed to get buildnumber from [/tmpRoot/etc.defaults/VERSION]. May 12 19:01:57 findhostd: ninstaller.c:460 failed to get productversion from [/tmpRoot/etc.defaults/VERSION]. May 12 19:01:57 findhostd: ninstaller.c:462 failed to get majorversion from [/tmpRoot/etc.defaults/VERSION]. May 12 19:01:57 findhostd: ninstaller.c:465 failed to get minorversion from [/tmpRoot/etc.defaults/VERSION]. May 12 19:01:57 findhostd: lib/system/system_platform_get.c:35 failed to get unique from /tmpRoot/etc.defaults/synoinfo.conf errno=[0x0900 file_get_key_value.c:28] May 12 19:01:57 findhostd: ninstaller.c:477 failed to get platform from [/tmpRoot/etc.defaults/synoinfo.conf]. May 12 19:01:57 findhostd: lib/system/system_max_align_get.c:93 [/tmpRoot/.system_info/pgsql_alignment] doesn't exist, check model name for alignment May 12 19:01:57 findhostd: lib/system/system_endian_get.c:61 [/tmpRoot/.system_info/endian] doesn't exist, check model name for endian May 12 19:01:57 findhostd: lib/system/system_bit_get.c:58 [/tmpRoot/.system_info/bits] doesn't exist, check model name for bits May 12 19:01:57 findhostd: ninstaller.c:510 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way May 12 19:01:57 findhostd: ninstaller.c:390 /tmpRoot/usr/syno/etc/www/DSM.json not exist May 12 19:01:57 findhostd: ninstaller.c:513 fail to get admin port from /tmpRoot/usr/syno/etc/www/DSM.json May 12 19:01:57 findhostd: ninstaller.c:541 failed to get nvr key from [/tmpRoot/etc.defaults/synoinfo.conf]. May 12 19:01:57 kernel: [ 35.805486] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) May 12 19:01:57 findhostd: util_junior.c:348 fail to read [unique] from [/tmpRoot//etc.defaults/synoinfo.conf] May 12 19:01:57 findhostd: ninstaller.c:880 Model not match [/etc.defaults/synoinfo.conf, /tmpRoot//etc.defaults/synoinfo.conf] May 12 19:01:57 findhostd: ninstaller.c:1265 SYSTEM_NORMAL, [Recoverable=0] May 12 19:01:57 findhostd: ninstaller.c:168 umount partition /tmpRoot May 12 19:01:57 findhostd: ninstaller.c:1180(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0 May 12 19:01:57 findhostd: ninstaller.c:1181(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData May 12 19:01:57 findhostd: ninstaller.c:1289 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0 May 12 19:02:02 synoagentregisterd: synoagentregisterd.c:151 Generating register key... May 12 19:02:02 synoagentregisterd: synoagentregisterd.c:165 Generated register key [90DC452A.1992.4AF2.BA01.D42CCB97C300]. May 12 19:02:27 root: Failed to curl [https://dataupdate7.synology.com/juniorexpansionpack/v1/getUpdate?platform=denverton&buildnumber=64570][7] May 12 19:02:29 login[6120]: root login on 'console' May 12 19:02:57 root: Failed to curl [https://dataupdate7.synology.com/juniorexpansionpack/v1/getUpdate?platform=denverton&buildnumber=64570][7] May 12 19:02:58 synoupgrade: synoupgrade.c:1257 fail to perform curl, CURLcode returns 60 May 12 19:02:58 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk' May 12 19:02:58 kernel: [ 97.126257] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities May 12 19:02:59 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero . . . May 12 19:03:37 install.cgi: ninstaller.c:510 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way May 12 19:03:37 install.cgi: ninstaller.c:390 /tmpRoot/usr/syno/etc/www/DSM.json not exist May 12 19:03:37 install.cgi: ninstaller.c:513 fail to get admin port from /tmpRoot/usr/syno/etc/www/DSM.json May 12 19:03:37 install.cgi: ninstaller.c:541 failed to get nvr key from [/tmpRoot/etc.defaults/synoinfo.conf]. May 12 19:03:37 install.cgi: util_junior.c:348 fail to read [unique] from [/tmpRoot//etc.defaults/synoinfo.conf] May 12 19:03:37 install.cgi: ninstaller.c:880 Model not match [/etc.defaults/synoinfo.conf, /tmpRoot//etc.defaults/synoinfo.conf] May 12 19:03:37 install.cgi: ninstaller.c:1265 SYSTEM_NORMAL, [Recoverable=0] May 12 19:03:37 install.cgi: ninstaller.c:168 umount partition /tmpRoot May 12 19:03:37 install.cgi: ninstaller.c:1180(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0 May 12 19:03:37 install.cgi: ninstaller.c:1181(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData May 12 19:03:37 install.cgi: ninstaller.c:1289 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0 May 12 19:03:37 install.cgi: synoupgrade.c:785 system status = 2 May 12 19:03:37 install.cgi: ninstaller.c:1772 CreateDataVol=[0] May 12 19:03:37 install.cgi: ninstaller.c:168 umount partition /tmpData May 12 19:03:37 install.cgi: ninstaller.c:172 Fail to execute [/bin/umount -f /tmpData > /dev/null 2>&1] May 12 19:03:37 install.cgi: ninstaller.c:1783 installer cmd=[/usr/syno/sbin/installer.sh -r >> /tmp/installer_sh.log 2>&1] May 12 19:03:37 burnin: B1 not started May 12 19:03:37 kernel: [ 131.181913] md0: detected capacity change from 8589869056 to 0 May 12 19:03:37 kernel: [ 131.182949] md: md0: set sda1 to auto_remap [0] May 12 19:03:37 kernel: [ 131.183688] md: md0 stopped. May 12 19:03:37 kernel: [ 131.184173] md: unbind<sda1> May 12 19:03:37 kernel: [ 131.189095] md: export_rdev(sda1) May 12 19:03:37 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/mdadm -S /dev/md0" Error="mdadm: stopped /dev/md0 " May 12 19:03:37 raidtool: raid_internal_lib.c:160 [Info] clean RAID superblock of /dev/md0 May 12 19:03:37 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not name, not match any port type May 12 19:03:37 raidtool: disk/disk_port_to_container.c:38 Unknown diskType May 12 19:03:37 raidtool: partition_path_enum.c:35 Failed to parsing device: name May 12 19:03:37 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type May 12 19:03:37 raidtool: disk/disk_port_to_container.c:38 Unknown diskType May 12 19:03:37 raidtool: partition_path_enum.c:35 Failed to parsing device: ram0 May 12 19:03:37 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type May 12 19:03:37 raidtool: disk/disk_port_to_container.c:38 Unknown diskType May 12 19:03:37 raidtool: partition_path_enum.c:35 Failed to parsing device: ram1 May 12 19:03:37 raidtool: external/extern[ 1427.445064] serial8250: too much work for irq4 al_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type May 12 19:03:37 raidtool: disk/disk_port_to_container.c:38 Unknown diskType May . . . May 12 19:03:52 install.cgi: RemoveUpgradeFile: Remove /tmpData/upd@te.pat... May 12 19:03:52 install.cgi: Verify checksum of [/tmpData/upd@te]... May 12 19:03:54 install.cgi: Pass checksum of /tmpData/upd@te... May 12 19:03:54 updater: updater.c:6194 Start of the updater... May 12 19:03:54 updater: updater.c:3277 orgBuildNumber = 64570.0, newBuildNumber = 64570.0 May 12 19:03:54 updater: util/updater_util.cpp:90 fail to read company in /tmpRoot//etc.defaults/synoinfo.conf May 12 19:03:54 updater: util/check_patch_support_hw_revision.cpp:63 This patch supports HW revision of this machine May 12 19:03:54 updater: child exit normally with [0] May 12 19:03:54 updater: updater.c:6501 ==== Start flash update ==== May 12 19:03:54 updater: updater.c:6505 This is X86 platform May 12 19:03:54 updater: updater.c:5823 Failed to mount boot partition May 12 19:03:54 updater: updater.c:3195 No need to reset reason for v.64570 May 12 19:03:54 updater: updater.c:7120 Failed to accomplish the update! (errno = 21) May 12 19:03:54 install.cgi: ninstaller.c:1652 Executing [/tmpData/upd@te/updater -v /tmpData > /dev/null 2>&1] error[21] May 12 19:03:57 install.cgi: ninstaller.c:139 Mount partion /dev/md0 /tmpRoot May 12 19:03:57 install.cgi: ninstaller.c:1621 Moving updater for configuration upgrade...cmd=[/bin/mv -f /tmpData/upd@te/updater /tmpRoot/.updater > /dev/null 2>&1] May 12 19:03:57 install.cgi: ninstaller.c:168 umount partition /tmpRoot May 12 19:03:57 install.cgi: ErrFHOSTCleanPatchDirFile: After updating /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1] May 12 19:03:57 install.cgi: ErrFHOSTCleanPatchDirFile: Remove /tmpData/upd@te.pat... May 12 19:03:57 install.cgi: ErrFHOSTDoUpgrade(1986): child process failed, retv=-21 May 12 19:03:57 install.cgi: ninstaller.c:2008(ErrFHOSTDoUpgrade) err=[-1] May 12 19:03:57 install.cgi: ninstaller.c:2012(ErrFHOSTDoUpgrade) retv=[-21] May 12 19:03:57 install.cgi: install.c:458 Upgrade by the manual patch fail. May 12 19:03:57 install.cgi: install.c:760 Upgrade by the uploaded patch /tmpData/@autoupdate/upload.pat fail. Jan 1 00:00:00 install.cgi: ninstaller.c:168 umount partition /tmpData Jan 1 00:00:04 root: Failed to curl [https://dataupdate7.synology.com/juniorexpansionpack/v1/getUpdate?platform=denverton&buildnumber=64570][7] Jan 1 00:01:14 synoupgrade: synoupgrade.c:1257 fail to perform curl, CURLcode returns 60 Jan 1 00:01:14 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk' Jan 1 00:01:14 kernel: [ 225.518858] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jan 1 00:01:14 kernel: [ 225.622128] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jan 1 00:01:14 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero Jan 1 00:01:14 synoupgrade: get_disk_dsm_version.c:59 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber' Jan 1 00:01:14 synoupgrade: get_disk_dsm_version.c:36 failed to load key 'buildnumber' from /_disk/etc.defaults/VERSION Jan 1 00:01:14 synoupgrade: get_disk_dsm_version.c:65 failed to read dsm version on '/_disk' Jan 1 00:01:14 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk' Jan 1 00:01:14 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero Jan 1 00:01:14 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0 Jan 1 00:01:14 synoupgrade: synoupgrade.c:248 unable to get dsm version from disk device Jan 1 00:01:14 synoupgrade: synoupgrade.c:312 unable to append query string of disk dsm version dva3221-in-kvm-failed-install-messages.txt

In any case, your efforts are worthy of Respect

No problem, it's unfortunate that we couldn't get it to work. I do this multiple times in a virtual machine and physical PC and it works always.

спасибо за помощь, не получилось так не получилось.

Maybe @wangsiji can help? But since @wangsiji has not been around for almost a year, maybe @darknebular? libsynoame-license.so has MD5 09e3adeafe85b353c9427d93ef0185e9, but after patching it fails, why? Is it because CPU?

в первый раз сервер отключался когда я команду ввел. У него настроено время отключения 22.00

This is strange, patch says retcode = 256 but here it's 0 which is normal...

MD5 mismatch is normal the second time you apply the patch because it is already patched. If you want to revert this patch you must uninstall/reinstall AME from the PackageCenter, but in any case I don't know why it does not work.

I don't know why it does not work for you... Just run this and share the result: /var/packages/CodecPack/target/usr/bin/synoame-bin-check-license & printf '%d\n' $?

вот, тогда сервер в 22.00 выключился

Same as mine. Run this: wget https://gist.githubusercontent.com/ner00/b30dd24d53f3a8bda8fd651c130316a2/raw/a5abbba3e0a506749356dbe8ac3636fa422538e6/ame72.py && python ame72.py

09e3adeafe85b353c9427d93ef0185e9

Uninstall and reinstall AME first and then run again: md5sum /volume1/@appstore/CodecPack/usr/lib/libsynoame-license.so

2edfd2cf278f76d9254d3f63fa2c15a1