All Activity

Вопрос про диск, заданный выше, вполне уместен.... Виртуалка на proxmox имеет не один диск. И и это диск загрузчика и диск системы. Диск загрузчика наверное не имеет смысл увеличивать, а вот диск под Хрень, тут есть смысл. Если всё делать руководствуясь инструкциями, то ничего не пропадёт. Посмотрите тему, там найдёте ответы на свои вопросы: Как установить XPEnology DSM 7 в Proxmox

Вопрос не понятен. Вроде как тема про установку на проксмокс .... и резонный вопрос про дальнейшие манипуляции с диском. Как его в дальнейшем расширить по объему и к чему это приведёт к потерю данных или нет

thank you for your reply and shared thoughts. I'll not spend more time here with trial and error for evaluating the best setup to get expected bandwidth between my Windows Server 2022 and the Synology box. I also will not use anymore the Intel X540 T2 NIC - it's even slow when used on another Windows server System (X9DRD-iF) during my own tests performed. My Synology (configured as 3615xs DSM 7.1.1-42962 Update 6) is currently using an Emulex OCE14102-NT 2x 10GB which is running fine as expected.

Какого диска? Хде?

sorry...6MBit/s is a typo......my fault. IT should be ~6GBit/s instead as mentioned in the title.

Outcome of the update: SUCCESSFUL DSM version prior update: DSM 7.2.1-69057 Update 4 Loader version and model: RR 23.11.1 | DS3622xs+ Installation type: BAREMETAL – HP Microserver Gen8 Additional comments:

Добрый день, если потребуется увеличить объем диска, то в этом случаи как быть ? Данные удаляться ?

Thank Very

Work with me ARC loader

Sussess thank very

use the patch from @darknebular - it's easy

J ai pris le temps de parcourir le web et revoir ce qui clochait dans ma conf , grace aux log. C etait mon coral TPU en PCIE ! Probleme resolu , je suis en 6.8

In order for DSM 7.2 to be available to you, you need model modding on one of the following models: DS1517+ DS1817+ RS818(RP)+ RS1219+ RS2416(RP)+ Take a look at this in the related topic: https://xpenology.com/forum/topic/70401-synology-plus-series-internal-flashdom-repair-and-model-modding

i use xpexlogy ARP DSM 7.1.1-42962 Update 6 but cannot install AME ( See picture ) I read many board he use DMS 7.1.42661 But i don know to install this version thank very

Hi, I've been trying to get this to work on my setup: - Loader is ARPL v1.1-beta2a - DSM 7.2.1-69057 Update 5 - AME 3.1.0-3005 First run I get this: sudo python ./ame72-3005.py Patching Checking whether patch is successful... Patch is unsuccessful, retcode = 256 If I run a second time I get: sudo python ./ame72-3005.py Patching MD5 mismatch I'm not a linux expert, so need things spelled out to me :). Anyone know if the 7.2 patcher will work on the latest DSM and AME. I only want it so the Synology Photos will work. Thanks

Thanks for the reply. This is why I was asking before I started pulling my hair out and spending hours trying to resolve it but only to find out that the MSI board my no support it. The only thing I found strange is that I had a ds2422+ with @fbelavenuto REDPILL it powered off but not on then I used your REDPlILL to update to a ds1823xs+ and it worked for a few days. Then I was getting that network error so I used your REDPILL wiped the drives and rebuilt it to a clean ds1823xs+ now it only shuts down. Strange yes I know. I am not saying it's anything you are anyone did just that it is intermittent.

Да завсегда на здоровье ....)))

Спасибо за помощь! Сразу и не додумался, есть же инструмент подсчета места за день, увеличил соответственно на 100 и 130 гб, будем смотреть

И вам дня доброго Есть у меня подозрение, что выделенные вами ограничение в 10гб тому виной. Маловато будет У меня пятидневный архив занимает более 400гб. Если подсчитать необходимое место, то на день выходит 80гб.

Здравствуйте, не подскажете почему не сохраняется архив? В настройках выставил хранение записей 5 дней, а он все равно сохраняет только текущий день...

Aucun soucis pour ma part avec la dernière MAJ de Proxmox avec kernel 6.8.4-2-pve, sur 2 systèmes différents.

"7.2.1-69057 Update 5" just released, how to update to it? Can I simply do it from GUI, or the scripts will be missing after that?

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2.1 69057 Update 4 - Loader version and model: RR v24.4.7 | DS3622xs+ - Using custom extra.lzma: NO - Installation type: BAREMETAL - HP Prodesk 400 G2 Mini - i3-6100T - 8GB DDR4 - Additional comments: 1. Created new USB boot disk, using RR v24.4.7 .img 2. Used menu.sh to create the loader 3. findsynology > Recover 4. Once back into DSM, performed update to U5 from the web console, reboot

in a original system the usb vid/pid would always be the same (f400/f400), not sure if they would check that for upgrading to a different system as it is by default the same on original systems we can start guessing and try to check and test in /etc/synoinfo.conf is a entry "dsm_installtion_id" that looks like it could be the culprit when the new loader re-creates (changes) a new synoinfo.conf from its loader config it might get lost in best case it might solve the problem by just placing the old value after installing and reboot, but it also could be a value that is created as a fingerprint on every boot and we dont know how its created so it ends up different on a loader changed system also a reminder there are things like "synowedjat" https://xpenology.com/forum/topic/68080-synology-backdoor/ so synology is identifying and tracking every system individually and thats need fingerprinting and id's, the SN and MAC's is not the only thing for sure @AuxXxilium or @Peter Suh might know more about hat individual id? i guess that kind of scenario is not part of the loaders (migration from a different loader and reading stuff from the old installation, i'd guess they look for there own loader config file on the boot media and what the user inputs there) that rabid hole can be pretty deep in worst case, for a simple use it might be easier to just document it and know that when using hyperbackup and replication scenarios the id of systems will change and these things will have to start from scratsch

- Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 7.2.1-69057 update-4 - Loader version and model: redpill.v0.9.4.9 - DS3622xs+ - Using custom extra.lzma: NO - Installation type: Proxmox VE 8.1.4 - Additional comments