All Activity

права на папки и файлы остаются для старого логина, и если пробую их менять выбирая владельцем новый логин, ничего не менятся(

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2-64570 update-3 - Loader version and model: TinyCore RedPill Loader - Using custom extra.lzma: NO - Installation type: BAREMETAL: i5-9500 - ASRock Z390M Pro4 - 32GB DDR4 - 4 HDD - 2 NICs - Additional comments: Manual Update, reboot and everything seems to be OK

это не действительная ссилка, там нету этой версии

Hey vista, glad to hear it. Then i try to use this new loader but my motherboard is an H61, intel 2 gen aka Bromolow and this loader wont support it (3615XS). Even try the 3617xs but at the page to load the Pat file it stops at 56%.

Suena increíble, planeo hacer lo mismo, ahora tengo mi px6 con 6.1.7, podrían decirme los pasos a seguir para actualizarlo a DSM 7.2, gracias de antemano

Just got a very interesting error that I couldn't recover from. It looks like md device was unable to heal, but bad sector count also didn't show anything. Clean smart tests. DSM 7.1-42661 Update 4 running on a Thecus NAS with WD Red in a raid 5 config. Volume fall back to readonly on reboot. 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.617036] BTRFS critical (device dm-0): corrupt leaf: block=17324287705088 slot=68 extent bytenr=17301599223808 len=16384 unknown inline ref type: 144 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.630685] md2: [Self Heal] Retry sector [1099922016] round [1/2] start: sh-sector [137490272], d-disk [3:sdc3], p-disk [7:sdh3], q-disk [-1:null] 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.643940] md2: [Self Heal] Retry sector [1099922024] round [1/2] start: sh-sector [137490280], d-disk [3:sdc3], p-disk [7:sdh3], q-disk [-1:null] 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.657181] md2: [Self Heal] Retry sector [1099922032] round [1/2] start: sh-sector [137490288], d-disk [3:sdc3], p-disk [7:sdh3], q-disk [-1:null] 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.670415] md2: [Self Heal] Retry sector [1099922040] round [1/2] start: sh-sector [137490296], d-disk [3:sdc3], p-disk [7:sdh3], q-disk [-1:null] 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.683658] md2: [Self Heal] Retry sector [1099922016] round [1/2] choose d-disk 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.691054] md2: [Self Heal] Retry sector [1099922016] round [1/2] finished: return result to upper layer 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.700608] md2: [Self Heal] Retry sector [1099922024] round [1/2] choose d-disk 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.707992] md2: [Self Heal] Retry sector [1099922024] round [1/2] finished: return result to upper layer 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.717543] md2: [Self Heal] Retry sector [1099922032] round [1/2] choose d-disk 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.724926] md2: [Self Heal] Retry sector [1099922032] round [1/2] finished: return result to upper layer 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.734473] md2: [Self Heal] Retry sector [1099922040] round [1/2] choose d-disk 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.741857] md2: [Self Heal] Retry sector [1099922040] round [1/2] finished: return result to upper layer 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.751428] BTRFS critical (device dm-0): corrupt leaf: block=17324287705088 slot=68 extent bytenr=17301599223808 len=16384 unknown inline ref type: 144 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.765106] md2: [Self Heal] Retry sector [1099922016] round [1/2] start: sh-sector [137490272], d-disk [3:sdc3], p-disk [7:sdh3], q-disk [-1:null] 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.778394] md2: [Self Heal] Retry sector [1099922024] round [1/2] start: sh-sector [137490280], d-disk [3:sdc3], p-disk [7:sdh3], q-disk [-1:null] 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.791642] md2: [Self Heal] Retry sector [1099922032] round [1/2] start: sh-sector [137490288], d-disk [3:sdc3], p-disk [7:sdh3], q-disk [-1:null] 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.804912] md2: [Self Heal] Retry sector [1099922040] round [1/2] start: sh-sector [137490296], d-disk [3:sdc3], p-disk [7:sdh3], q-disk [-1:null] 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.848248] md2: [Self Heal] Retry sector [1099922016] round [1/2] choose d-disk 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.855666] md2: [Self Heal] Retry sector [1099922016] round [1/2] finished: get same result, retry next round 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.865663] md2: [Self Heal] Retry sector [1099922024] round [1/2] choose d-disk 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.873059] md2: [Self Heal] Retry sector [1099922024] round [1/2] finished: get same result, retry next round 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.883048] md2: [Self Heal] Retry sector [1099922032] round [1/2] choose d-disk 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.890448] md2: [Self Heal] Retry sector [1099922032] round [1/2] finished: get same result, retry next round 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.900442] md2: [Self Heal] Retry sector [1099922040] round [1/2] choose d-disk 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.907832] md2: [Self Heal] Retry sector [1099922040] round [1/2] finished: get same result, retry next round 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.917828] md2: [Self Heal] Retry sector [1099922040] round [2/2] start: sh-sector [137490296], d-disk [3:sdc3], p-disk [7:sdh3], q-disk [-1:null] 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.931036] md2: [Self Heal] Retry sector [1099922032] round [2/2] start: sh-sector [137490288], d-disk [3:sdc3], p-disk [7:sdh3], q-disk [-1:null] 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.944240] md2: [Self Heal] Retry sector [1099922024] round [2/2] start: sh-sector [137490280], d-disk [3:sdc3], p-disk [7:sdh3], q-disk [-1:null] 2023-12-05T04:13:19-06:00 thecus kernel: [ 105.957466] md2: [Self Heal] Retry sector [1099922016] round [2/2] start: sh-sector [137490272], d-disk [3:sdc3], p-disk [7:sdh3], q-disk [-1:null] 2023-12-05T04:13:20-06:00 thecus kernel: [ 105.984666] md2: [Self Heal] Retry sector [1099922040] round [2/2] choose p-disk 2023-12-05T04:13:20-06:00 thecus kernel: [ 105.992065] md2: [Self Heal] Retry sector [1099922040] round [2/2] finished: get same result, give up 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.001269] md2: [Self Heal] Retry sector [1099922032] round [2/2] choose p-disk 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.008669] md2: [Self Heal] Retry sector [1099922032] round [2/2] finished: get same result, give up 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.017894] md2: [Self Heal] Retry sector [1099922024] round [2/2] choose p-disk 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.025279] md2: [Self Heal] Retry sector [1099922024] round [2/2] finished: get same result, give up 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.034491] md2: [Self Heal] Retry sector [1099922016] round [2/2] choose p-disk 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.041890] md2: [Self Heal] Retry sector [1099922016] round [2/2] finished: get same result, give up 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.051146] BTRFS critical (device dm-0): corrupt leaf: block=17324287705088 slot=68 extent bytenr=17301599223808 len=16384 unknown inline ref type: 144 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.064802] ------------[ cut here ]------------ 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.069428] WARNING: CPU: 0 PID: 17296 at fs/btrfs/disk-io.c:916 btree_io_failed_hook+0x12d/0x220 [btrfs]() 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.079167] Modules linked in: fuse 8021q ocs_fc_lio(PO) tcm_qla2xxx(O) qla2xxx(O) libfc scsi_transport_fc vhost_scsi(O) vhost(O) tcm_loop(O) iscsi_target_mod(O) target_core_user(O) target_core_ep(O) target_core_multi_file(O) target_core_file(O) target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) vfat fat udf isofs synoacl_vfs(PO) btrfs ecryptfs zstd_decompress zstd_compress xxhash raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq adt7475 zram aesni_intel glue_helper lrw gf128mul ablk_helper broadwellnk_synobios(PO) hid_generic usbhid hid usblp uhci_hcd etxhci_hcd bnxt_en(O) bnx2x(O) mdio qede(O) qed(O) mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) atlantic_v2(O) atlantic(O) r8168(O) tn40xx(O) i40e(O) ixgbe(O) be2net(O) i2c_algo_bit igb(O) 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.150446] dca sg dm_snapshot dm_bufio crc_itu_t crc_ccitt psnap p8022 llc hfsplus md4 hmac sit tunnel4 ipv6 flashcache_syno(O) flashcache(O) syno_flashcache_control(O) dm_mod arc4 crc32c_intel cryptd ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance processor cpufreq_stats vxlan ip6_udp_tunnel udp_tunnel ip_tunnel loop sha256_generic synorbd(O) synofsbd(O) e1000e(OE) usb_storage xhci_pci xhci_hcd ehci_pci ehci_hcd usbcore usb_common mv14xx(O) [last unloaded: adt7475] 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.195440] CPU: 0 PID: 17296 Comm: kworker/u16:13 Tainted: P OE 4.4.180+ #42661 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.203857] Hardware name: Intel Corporation SugarBay Platform/SCPT_CRB, BIOS TBML_T06 03/12/2012 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.212722] Workqueue: btrfs-endio-meta btrfs_endio_meta_helper [btrfs] 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.219335] 0000000000000000 ffff880629da3c20 ffffffff812dca8b 0000000000000009 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.226767] 0000000000000000 ffff880629da3c58 ffffffff81050f82 ffff8806287f3040 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.234199] 0000000000001000 ffff880644b0a000 ffff8806440e0240 00000fc1a003c000 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.241632] Call Trace: 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.244073] [<ffffffff812dca8b>] dump_stack+0x4d/0x72 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.249199] [<ffffffff81050f82>] warn_slowpath_common+0x82/0xa0 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.255189] [<ffffffff81051055>] warn_slowpath_null+0x15/0x20 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.261018] [<ffffffffa0cd2a6d>] btree_io_failed_hook+0x12d/0x220 [btrfs] 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.267887] [<ffffffffa0d055ba>] end_bio_extent_readpage+0x18a/0x910 [btrfs] 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.275009] [<ffffffff812f0615>] ? find_next_bit+0x15/0x20 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.280574] [<ffffffff812b3449>] bio_endio+0xa9/0x120 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.285710] [<ffffffffa0cd1687>] end_workqueue_fn+0x27/0x40 [btrfs] 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.292063] [<ffffffffa0d15466>] btrfs_worker_helper+0xc6/0x390 [btrfs] 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.298750] [<ffffffff8107c935>] ? sched_clock_cpu+0xa5/0xb0 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.304492] [<ffffffffa0d15799>] btrfs_endio_meta_helper+0x9/0x10 [btrfs] 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.311352] [<ffffffff8107130a>] worker_run_work+0x9a/0xe0 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.316920] [<ffffffffa0d15790>] ? btrfs_endio_helper+0x10/0x10 [btrfs] 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.323606] [<ffffffff810692bb>] process_one_work+0x1db/0x4e0 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.329426] [<ffffffff810695ed>] worker_thread+0x2d/0x4a0 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.334899] [<ffffffff810695c0>] ? process_one_work+0x4e0/0x4e0 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.340890] [<ffffffff8106d9a3>] kthread+0xd3/0xf0 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.345757] [<ffffffff8106d8d0>] ? kthread_worker_fn+0x160/0x160 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.351839] [<ffffffff81563baf>] ret_from_fork+0x3f/0x80 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.357227] [<ffffffff8106d8d0>] ? kthread_worker_fn+0x160/0x160 2023-12-05T04:13:20-06:00 thecus kernel: [ 106.363335] ---[ end trace 8daff8e233f959d2 ]---

Hi, sorry for the long time. I was traveling for business. Here my feedback after 2 month of running ARPL-i18n v23.9.7 DS918+ 6.2(25556u7) (yes, latest u7) on IntelN100 with ASM1166 PCIx4 add-on The system is rock stable and fast responding, I could load config export from a DS415play (x86/32bit Intel Atom) The setup of the disks was at first trick, the documentation is a bit thin, had to read and try some time until it works. Also working the PCIe-NVMe "hack" for M2.E+B slot SSD as read cache - BUT only when patching manually, the script does not work ( xpenology.com/forum/topic/13342-nvme-cache-support/page/3/#comment-126807) But I did switch to use 2x SATA-SSD as read and write cache, the write performance on small files improved from 6mb/s to 38mb/s (using small file test from Microsoft disk benchmark tool) In 5 weeks I did run multiple 4-5 day CPU burn in tests, also I transferred 35TB+ files to and from the NAS via the onboard 1GBit nic. Update from my todo list in post #1: My 3x10TB disks where moved successful from my legacy Syno-Hardware, including encrypted folders The M2.WiFi Sata Adapter did not work. the Board/Chipset only supports Intel CNVi WiFi Adapter (but all of them, not only latest gen) My current Hardware: Asrock N100DC-ITX board with Intel N100 4xE-Core Cpu (no HT) - powered by 19V Laptop PSU r8169 onboard GBit NIC 32 GB Ram (Samsung, from the compatibility list of Asrock!) 2x SATA on board with 256GB Sata-SSD for Read/Write cache PCIx4 Sata-Card 6-ports with ASM1166 chip 3x 10TB Exos Seagate disks on Sata Add-In Controler (4k/512n sectors) DS 918+ DSM 6.2.4-update7 25556u7 An finally a dump of my config: Model: DSM918+ Version: 6.2 Addons: nvmecache: hdddb codecpatch misc addincards acpid storagepanel reboottoarpl Modules: mii r8169 -> Modules setting: Priority use of official drivers: true User Commandline: SataPortMap: 26 Model inherent cmdline: HddHotplug: 0 syno_hdd_detect: 0 syno_hdd_powerup_seq: 0 vender_format_version: 2 elevator: elevator Sysinfo entries: usbportcfg: 0x0000003F00 │ maxdisks: 14 │ netif_seq: 0 1 2 3 4 5 6 7 │ support_disk_compatibility: no │support_memory_compatibility: no │ support_syno_hybrid_raid: │supportraidgroup: │ internalportcfg: 0x000000003F │ support_led_brightness_adjustment: no │ buzzeroffen: 0xffff │ maxlanport: 8 | esataportcfg: 0x00000000C0 │ support_leds_lp3943: (to get sysinfo entries for disk mapping use the sheet with macros, if you can not find it send me PM, my setup is for 2xSata on-board controller 1, 6xSata on controller 2, 6x USB disks) Advanced Options: Switch LKM version: prod │ Switch direct boot: false │ Timeout of get ip in boot: 30 │ Timeout of boot wait: 10 │ kernel switching method: kexec

bon j'ai changer le SN et les 2 adresses mac mais ca ne fonctionne toujours pas Votre média d'entrée ne peut être ouvert: VLC ne peut pas ouvrir « http://192.168.0.12:50002/transcoder/videotranscoding.cgi/MediaServer/id=6613?TransProfile=mpegts_hd480_mpeg2_vb3000_mp2_ab128&mime=video/mpeg&DLNA_PN=&DLNA_OP=11&KillTransProcess=yes&isAAC=yes ». Vérifier les messages du journal pour plus de détails. par compte avec celui la pas de soucis http://192.168.0.12:50002/v/NDLNA/4236.mp4file:///C:/Users/famille/Downloads/dms(1).dmslog

There should be no error between the PC time and the actual time. Sent from my iPhone using Tapatalk

Comment tu as fait pour installer aac ?

Salut j'arrive pas active ceci sur mon DS3622xs+

Hello, I try to install xpenology on the above named thinclient. I have one drive attached to the internal sata port. I chose the DSM Hardware platform, because @rufik uses the same for his S720, the little brother. I used the latest TCRP loader and did every step from the tutorial. DSM is found successfully via find.synology.com I downloaded DSM_DS3622xs+_64570.pat (409Mb), but when I try to install it, I get the message, that the .pat file seems damaged. I doubt it, the second download gives me the same message. Does any one have an idea, what is going wrong? Regards, Tomte.

Same issue here. Tried both DVA3221 on ESXi 8.x and baremetal (MSI Nightblade X2B i7 6th generation, Nvidia GTX 1070 and Killer E2400 Gigabit LAN). (I got it working once on ESXi, but had to increase disk space and could never get it working thereafter because of corrupt pat file at 55% progress). I get an IP address when booting TCRP Friend, but it doesn't respond on that IP address when connecting with ip:5000 and it's never found in finds.synology.com. Tried both realmac and random mac. I would very much like to run face recognition etc on my cameras using Synology Surveillance Station. How can this be resolved? Can someone please look into network setup/drivers?

Content de savoir qu'il y a un loader pour remplacer Arpl, moi aussi je passerai un peu plus tard sur Arc. En tout cas, merci pour l'info.

Today I installed the latest Arc 23.12.4a ( network card r8168 DS3622xs+) and everything works as it should, so the Loader was the problem. My network card recognized after running the dsm kernel 😅

Aujourd'hui, j'ai installé la dernière version d'Arc 23.12.4a et tout fonctionne comme il se doit, donc le chargeur était le problème. Ma carte réseau r8168 reconnue après avoir exécuté le noyau DSM 😅

Bonjour à tous, Ce n'est qu'une information, mais cela peut aider quelqu'un. J'ai installé une carte réseau 4 ports 1GB de chez HP NC365T à base de Intel 82580 et elle est parfaitement reconnue dans la dernière version de RR Vers 23.11.10. J'ai donc créé un "Bond" de 4GB. (Coût : 25€ sur un site de revente) Gastonzz

thanks mate. it is actually working. like wow. thanks.

je vais tenter ca ce soir j'ai un vrai couple de numéro de série/mac pas grave si c'est pas le meme modele que celui du loader ?

OOOK! donc le pb est bien un souci de serial/mac. Si tu veux que ça marche avec arpl-i18n il te faut nécessairement un vrai couple SN/Mac. Pour changer le le SN et la mac il faut aller dans la config du loader (Cmdline menu) AVANT de lancer le build. Là tu saisis les dites infos puis tu lances le build. MAIS il te faut un vrai SN...

Столкнулся с проблемой отображения IP адресов. Имеется белый адрес, купленный домен и все необходимые ДНС записи для поддоменов. Доступ осуществляется через реверс прокси в лице nginx ( на роутере проброшены 80 и 443 порты до виртуальной машины с centos и nginx, с нее на виртуалку с Xpenology). Доступ есть без проблем, в access log пишет реальный адрес клиента, но в самом веб интерфейсе в мониторинге отображается адрес реверс прокси. Как это побороть? P.S. в настройках доверенный прокси тоже добавлен.

Alors je suis passé de VMWare ESXi à Proxmox. Et je dois dire que pour un usage perso, je ne reviendrai pas en arrière. Comme impératif, la carte mère doit être capable de faire du IOMMU (VT-d) mais c'est déjà vrai aussi pour ESXi. Il faut configurer le grub de Proxmox pour activer le passthrough. Pour ma part j'ai du également activer le ACS override pour isoler dans des groupes IOMMU séparé chaque composant PCIe. Je n'ai pas étudié la faisabilité avec AMD, je n'utilise que du Intel. C'est assez bien détaillé : https://pve.proxmox.com/wiki/PCI_Passthrough Ma ligne grub ressemble à ça : GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt pcie_acs_override=downstream,multifunction initcall_blacklist=sysfb_init" Il y a un petit script bash qui permet de voir les groupes IOMMU : #!/bin/bash shopt -s nullglob for g in $(find /sys/kernel/iommu_groups/* -maxdepth 0 -type d | sort -V); do echo "IOMMU Group ${g##*/}:" for d in $g/devices/*; do echo -e "\t$(lspci -nns ${d##*/})" done; done; En gros, quand tu décides de passthrough un composant, tous les composants associés au même groupe IOMMU doivent être passthrough dans le même package... C'est pour ça que j'ai du activer le pcie_acs_override. Sans ça mes 2 cartes graphiques étaient dans le même groupe et je ne pouvais pas les séparer (obligé donc de les passthrough les 2 dans la même VM...) Mais une fois que tous les prérequis sont "OK", c'est assez simple... Tu ajoutes simplement un nouveau périphériques PCI depuis l'IHM Proxmox dans la config hardware. Ce que j'ai surtout trouvé génial avec Proxmox, c'est la gestion du port série, et l'affichage via HTML5. Pour débug Xpenology, c'est le feu, pas besoin de putty, ni de galérer avec l'ouverture de ports spécifiques depuis ESXi... Il suffit simplement d'ajouter un "Serial Port" depuis l'IHM, puis quand on clique sur "Console" : Ca ouvre directement la console en HTML5 : Et du coup ça marche de n'importe où, même depuis l'extérieur (si t'as ouvert l'accès web vers proxmox), puisque ça passe par l'accès web proxmox. Et c'est officiellement gratuit/opensource... pas besoin de trouver une licence sur le web pour accéder aux fonctions "premium" (comme l'accès au serial port via TCP par exemple...) Et accessoirement, OVH propose des template Proxmox parmi les choix possible quand on loue un serveur chez eux, du coup on est pas dépaysé pour se monter une config dans le cloud. Et just for fun :

merci de ton éclaircissement je n'ai pas basculer d'un loader A vers B j'avais un NAS que j'ai remplacer complétement en recopiant les données de l'un a l'autre via RSYNC entre les deux j'ai utiliser le loader arpl-i18n en laissant par defaut numéro serie / mac par compte je trouve aucune procédure pour changer ce numéro de série et les 2 adresses mac

Realtek NIC are nightmares since begenning. On my case, the R8125B on the MSI B460I doesn't let DSM boot when plateform is DS920+, but OK with DS918+ (apparently with a screen plugged). Seems ARPL-i18n more stable in my case than ARC. Will have to test also TCRP when possible. But as there are designed a bit differently, and so many settings and parameters to cross-test, it's a bit hard to isolate and identify the troublemaker.

Hi there, I´m trying to create a new loader -= m-shell 1.0.0.5 - and I´m getting this: Any suggestion? Best regards.