auxxxilium / arc Goto Github PK

enabled qemu-qa addon but proxmox dont find qemu agent running in DSM VM.

VM setting:
q35
cpu: host

i think we miss virtio-serial module

Describe the bug
After clicking on build the loader, the image can’t be downloaded from Synology upstream.
arc: build 23.6.31a
Synology Target: 7.2-64561 (Not 100% sure, maybe it was 7.2-64570, I can verify tomorrow)

Screenshots
First line says: Cleaning Cache

Anyway to add the adaptec driver to your modules?

https://raw.githubusercontent.com/pocopico/rp-ext/master/aacraid/rpext-index.json

Hello, is it possible to disable FMA check in loader? My N2807 can run dva3221 on TCRP 9.0.3 but it doesn't run with this loader. The reason why I want to use this specific loader is because it has dva3219 same architecture as 3221 but both of them cannot run. Even dva1622 cannot be installed while it is working fine in TCRP.
When in UI I hit Run Loader it just freezes, and after manual reboot it shows ip but never connects to it. DS918+ however works fine.

Edit: Update
After DS918+ I went to edit config and changed model to dva3221 and it worked. Then migrated and loaded.

Update2:
Dva3219 works as well. Thank you for your hard work you can close issue.

Describe the bug
I try to migrate my old ARPL installation to your ARC version. Therefore I changed to bootloader to the lastest arc version.
There I wanted to use the DSM recovery function to determine the build and model version an the SN as well.
As you can see in the screenshot, the function is some kind broken and not able to extract these information.
The arpl-i18n fork and the fork of jimmyGALLAND are able to recover this information without any problems.

Screenshots

Additional context
I testet all of your versions since arc-23.6.31a

I add a reboot addon during assembly, but the task does not appear in the DSM scheduler. The powersched addon also does not work

On all versions after 23.6.53, the NAS does not ping after DVA3219 is loaded. Module e1000e

My bootloader lives in a ESXi. After installing the DSM and the countdown, this page appears:

Then the virtual machine turns off. Restart does the same. Tried different versions of the operating system (7.2, 7.1.1), the behavior is the same. Bootloader version 23.5.106a. Storage Model DS3617xs

After showing this error loop for about 1 minute, the network adapter is identified.
23.6.36a on proxmox and virtio network adapter.

DS923+ shows serial number on first boot, but not after DSM is installed

Describe the bug
I'm trying to move an existing DSM 7.0 installation running under proxmox from the original arpl to arc.
I've replaced the loader drive and rebuilt the image, but when I try to start DSM, it finds the eth0 device, prints the correct IP and finishes with "This interface will not be operational.".
DSM itself is also not reachable, I can't even ping the IP.
Screenshots

Additional context
The network adapter is a RTL8125B, I've tried passing it as Intel E1000 (this worked with arpl before) and Virtio device.
The Cmdline arguments are identical (with the exception of "withefi" or "noefi" depending on whether I activate UEFI or not).

My friend!
Thank you for your work!
Please add the DS1821+

Describe the bug
I'm following This guide.
Using the latest image 23.6.54b
But upon booting it says not a bootable image.
Am i missing something? Proxmox is v7

Umgebung:

ESXI Host Version : ESXi-7.0U3k-21313628-standard

Ich habe die Dateien arc.vmdk und die arc-flat.vmdk auf den ESXi Host hochgeladen.

Die Disk arc.vmdk kann nicht zur VM hinzugefügt werden siehe Screenshot.

Das Problem besteht erst nach dem ich den ESXi Host auf Version ESXi-7.0U3k-21313628-standard geupdatet habe.

I've been testing the 16 bay version as a proxmox VM on n4020,
1 core 1 thread + 2048 memory since I'm only gonna be using it for SS.

but streaming with DS CAM on android is too slow to be usable.
CPU is not even maxed out, only hovers around 40-60%, and neither is the memory
I have lowered the live and mobile view to "low bandwidth" but it didn't make much difference.
Is there any minimum hardware requirements or other more ideal platform choice for SS?

Just tried version 23.6.2 on Proxmox with 2 virtual disks and tried to create an encrypted volume.
It looks like the volume ist created but it fails to unlock.

desmg -T shows:
[Fri Jun 2 15:09:02 2023] device-mapper: table: 249:3: crypt: Error allocating crypto tfm
[Fri Jun 2 15:09:02 2023] device-mapper: ioctl: error adding target to table

Looks like the kernel is missing the right crypto configuration?!

The network card receives ip on the boot arc and works.
after setting up the arc and building dsm, I restarted my computer.
arc boots up and gets ip via realtec 8169 network card.
when the arc shows DSM kernel loading, network card hang, stopped flashing lights on the network card, boot process hang, the port speed switches to 100M (normal speed 1G).
this happens when I insert a raid controller, without it the network card works fine, both pci-e and built-in.
If at this moment you switch the cable to another card, it starts working at full speed, but does not receive an address.
Raid adapter in raid mode and another adapter in it(jbod) mode does not affect, the built-in network card and the pci-E network card stop working after loading the dsm kernel.

Screenshots
If applicable, add screenshots from Arc - Sysinfo menu.

Additional context
Add any other context about the problem here.

Describe the bug
https://raw.githubusercontent.com/AuxXxilium/arc/main/rss/7.2/rss.xml has been removed and the status of DSM Update now shows "Connection failed. Please check your Internet connection."
Screenshots

I have with the version 23640 ixgbe driver is removed in the log over and over 49 times then the loader boot but with 23635 there is no such issue

Screenshots
If applicable, add screenshots from Arc - Sysinfo menu.

Additional context
Add any other context about the problem here.

Hello again.

I switched for my Thecus N7770-10G from DS3622xs+ broadwellnk to DS2422+ VT1000-DT because it boots reliably.
But my 10GBit Tehuti TN9210 is not recognized.

Could you please integrate the tn40xx driver into this release?

Hi here

Big thank for your awesome works.
However, since I can't install Arc with mod patch cause My HP Proliant Gen8 have no EFI with 2.5.55, I tried to install 23.5.60.
I saw you removed EFI condition to install arc mod, but with this new version my baremetal dont boot on the USB key.
No problem with earlier versions.
Any idea ?
Thanks

I have change mac2 address in user-config, save and then reboot but in DSM - Info Center, the mac2 address is still the same, please fix it

Hi,
Have you encountered any issues with not being able to dhcp?

In PVE, vmxnet3 cannot obtain a valid IP address
Some r8125 in physical machines are also unable to obtain IP addresses,

According to the test, these will be alleviated after canceling the MAC of cmdline. But it's not a very good solution.
Have you ever encountered it? Or have any insights?

hello I have loader 22.12.05 and work !
After loader update and rebuild, it doesn't start anymore but why?

this is my configuration:

I suppose you know that in the last loader 7.2 still doesn't work, but 7.1.1 does work, I leave a video for people to see:

https://youtu.be/95950c5tv3Q

I leave you DSM_DS920+_64561.pat and DSM_RS4021xs+_64561.pat
in case you can include them in the loader to patch them instead of downloading them from synology, since I downloaded them in case they were worth it to install it without downloading

Unterstützt der Arc Loader kein Legacy Boot? UEFI funktioniert, aber mein HP ProLiant Microserver Gen8 hat kein UEFI

Hallo. Ich habe gelesen das die 7.2 keine Beta mehr ist.
Ist das bei dir schon alles erledigt?

Wollte mal nett nachfragen.
Du hast sehr gute Arbeit geleistet, muss man mal sagen.
MFG Maiki

Ich habe V 23.6.51a Image neu erstellt, aber bei "Build loader" kommt die Meldung "no DSM Image found"

After setting up a new DSM VM in Proxmox with 23.6.21e, the Proxmox shutdown command does not work anymore. In version 23.5.100, it worked fine so far.

Proxmox Config

Sysinfo

(all modules are selected)

If information for further analysis are missing, I am happy to provide them.

Thank you for your effort and support!

Is your feature request related to a problem? Please describe.
not found wiki instructions for upgrade version loader without reset configs

Additional context

As i said in the title, i tried this option cause i have a minipc with no fan and one sata port, in this configuration the 5tb 2.5 hard disk reaches easily the 60c. I use that option before building the loader but after the boot the synology doesnt recognize the disk at all (tried with different disks and system, same result) while everything works fine with sata.

DVA1622 loader is missing

Me again ^^
Ok, I redid several tests as it should.

VM: arc23.5.60 & DSM 7.2-64561
It is the compilation in 7.2 Beta that poses a problem with Proxmox driver VirTio (I cannot turn off the machine from Proxmox)
It's weird because with version 7.2 RC the Virtio drivers work

VM: arc23.5.60 & 7.1.1update 5
On DSM 7.1.1update 5 and loader 23.5.60 everything works fine on Proxmox. 👍

Thanks :

Thank you for your work and your updates.

I just updated the Loader arc23.5.28 to arc23.5.55. Now it is no longer possible to compile without switching the VM to EFI.

Since the obligation to be in EFI , the commands from proxmox shutdown or reboot no longer work, I don't really understand this choice because everything was working fine?
The VM in i440FX or Q35, commands from Proxmox no longer work.
Before this update the VM remained by default: SeaBios / i440FX and everything worked perfectly.

Thanks ^^

I tried older versions but the result is the same. Loader has internet access.

Hello,
This version looks good, it boots on my Thecus N7770-10G but cannot install BS.

in serial conolse i got this message:

BusyBox v1.30.1 () built-in shell (ash)

SynologyNAS> [ 100.635666] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[ 100.679699] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 107.027578] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[ 107.057838] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 132.136741] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[ 132.183432] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
SynologyNAS> [ 100.635666] EXT4-fs (md0): couldn't mount as ext3 d
ue to feature incompatibilities
-ash: syntax error: unexpected "("
SynologyNAS> [ 100.679699] EXT4-fs (md0): mounted filesystem with ordered data
mode. Opts: (null)
-ash: syntax error: unexpected "("
SynologyNAS> [ 107.027578] EXT4-fs (md0): couldn't mount as ext3 due to feature
incompatibilities
-ash: syntax error: unexpected "("
SynologyNAS> [ 107.057838] EXT4-fs (md0): mounted filesystem with ordered data

Can you fix this?

Hi Auxxxilium
all Loader bigger as 23.5.53 in virtual envirormens like VMware Workstation / VMM /virtualbox the maschine will crash.
Steps to reproduce doing en install any modell tested with 3622 / 920+ DSM Version 7.1.42962 in virtual envoriments
create the loader with ARC Patch without etc/
the issue is happen with uefi and MBR / without addons / with Addons
first boot configure the loader all is fine
VBox.log
VBoxHardening.log
vmware.log
vmware-0.log

and by the Second boot when DSM is installed the virtual Maschine is going off and in the log stays the virtual Maschine is destoyed.

with the loader 23.5.53 the Loader is working

Hello, thanks for the work.
In the arc-23.5.100a version, the sas controller recognizes me perfectly in TI mode, in later versions it does not recognize the sas disks

After updating ARC from 23.5.15 to 23.5.16 the physical disks attached to a passthroughed LSI SAS controller are not mounted anymore. I have running ARC on ESXi 8.0 U1 VMs.

ARC sees the disks:

But in DSM the disks are not mounted. You see the active server with all disks (ARC 23.5.15) and the passive server (ARC 23.5.16):

Btw. the shown model in the Synology HA app depends on the amount of mounted disks:

when creating the boot this error appears:

1.I am unable to perform some Synoinfo deletions. It hangs itself to go to the Add/edit Synoinfo Item menu.

2. In synoinfo added support_memory_compatibilty: no

But in etc.defaults/synoinfo.conf
support_memory_compatibilty: yes

It caused the message Ram is not recommended by Synology.

I'm using ARC 23.5.55

Thank you for your work, can you put the description of the changes you have made on the updates please?
Thanks

Describe the bug
ESXi 8.0 VM with LSI HBA passed through. This is working fine with 23.5.55 and all attached disks are recognized.
With 23.5.60 it is not working anymore. No disks are recognized.

Hello, i have the hardware listed below:

MB INTEL S1200BTL/XEON E3-1220/32Gb ECC DDR3/LSI 9211-8i HBA (IT firmware)/set of different disks (14 pcs).

i make USB installation (32Gb flash drive). Installation was simple and fast (autoconfiguration) and all works fine, except LSI card (in WEB UI i see only 6 discs on MB AHCI controller). But this card (LSI) works fine on ancient version TCRP (i dont remember number of version, but i did this installation last summer). Model choosen for installation RS4021xs+, DSM 7.2-64551.

I try some manual configurations based on SataPortMap and SasIdxMap and have no result (this link issue 216, and this issue 721)

All modules and addons are included, autoconfiguration says about SAS controller, but nothing happened. Some screenshots for explanations:

Sata MAP menu:

Config:

I try to insert below this string SasIdxMap: "0" and nothing happened.

WEB UI discs:

Some BIOS pics of controller UI:

Thank s a lot!

Can you please add support of the model DVA1622?

It's already implemented in the following repo: https://github.com/wjz304/arpl-i18n

Thanks in advance

since version 23.6.51a I always get the error: error checking new version for all update options. That happens in my VM and on my real NAS as well.

ARC Loader v 22.12.18 starts and gets a working IP.
After selecting any modell and building the loader the boot afterwards results in an not reachable system - the shown IP is not reachable (target would be 918+).
Rebooting into config mode again, the system is reachable again.

'lsmod' shows 1000e loaded - here is the 'lspci -tvnnq' output:
-[0000:00]-+-00.0 Intel Corporation 10th Gen Core Processor Host Bridge/DRAM Registers [8086:9b63]
+-02.0 Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc8]
+-14.0 Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller [8086:43ed]
+-14.2 Intel Corporation Tiger Lake-H Shared SRAM [8086:43ef]
+-15.0 Intel Corporation Tiger Lake-H Serial IO I2C Controller #0 [8086:43e8]
+-16.0 Intel Corporation Tiger Lake-H Management Engine Interface [8086:43e0]
+-17.0 Intel Corporation Device [8086:43d2]
+-1c.0-[01]--
+-1d.0-[02]--
+-1f.0 Intel Corporation Device [8086:4387]
+-1f.4 Intel Corporation Tiger Lake-H SMBus Controller [8086:43a3]
+-1f.5 Intel Corporation Tiger Lake-H SPI Controller [8086:43a4]
-1f.6 Intel Corporation Ethernet Connection (14) I219-V [8086:15fa]

Board is the ASUS Pro B560M-C.

Other related searches show a mapping problem with the i219-V (appendix).

Any idea or steps I can do to get it working ? Thanks in advance !

The storage manager amd san manger from DSM is missing

Tested the latest version V23.1.23 ,it cannot use.
config completed -->① reboot --> recovery the DSM --> reboot --> update flashdisk --> reboot --> after a while network card stop work，IP lose.
Previous versions stop at ① reboot