ARC Loader - English only please (or translated in post)

[Fox Mulder]

ARC Loader is one of the two current Xpenology Loaders in existence. It supports ARC Patch which allows some (or all) of the synology services to work even without a actual synology machine:

https://github.com/AuxXxilium/arc

 

Latest releases can be found here:

https://github.com/AuxXxilium/arc/releases

Current release (at time of writing) is: 1.1.9

 

Let the discussion begin!

[shibby]

Rock solid for me. Works everyting i need including iGPU from 13gen Intel for Plex Transcoding.

[Fox Mulder]

2 hours ago, shibby said:

Rock solid for me. Works everyting i need including iGPU from 13gen Intel for Plex Transcoding.

I wonder if igpu can be used for anything other than transcoding.. or you have to get a NVIDIA card for it.

[Randomized]

Beware of this developer, it's someone who kicks you out of the discord group if you asks support.

 

I asked why the update is failing from 1.1.4 to 1.1.19 (it's now 1.1.22). He told me to use my brain because he told it 10 times in his little discord group?

Well... i have never been on that discord group until today, but beware guys.

 

You need the discord group if you don't have a valid serial no for AME, his patch is doing something with discord registration and that's dangerous. Luckaliy I have a valid serial no for my DSM.

 

This developer is out of control and I think his project should be avoided. I'm rolling back to TCRP, the developer who doesn't miss his users is not a real developer.

 

Btw, the developer failed to give a technical answer/solution, but I have figured it out myself;

 

version 1.1.4. is default configured on the 'next' releases, you don't know that, it's a developer failure. You cannot update that release by doing weird things. Switch it back manually to the stable branch and arc.sh will let you update.

 

Be warned, he will kick you out of his discord community if you smell funny.

 

Also i don't suggest a loader that is dependent on a discord group

Edited December 7, 2024 by Randomized

[Fox Mulder]

8 hours ago, Randomized said:

Beware of this developer, it's someone who kicks you out of the discord group if you asks support.

 

I asked why the update is failing from 1.1.4 to 1.1.19 (it's now 1.1.22). He told me to use my brain because he told it 10 times in his little discord group?

Well... i have never been on that discord group until today, but beware guys.

 

You need the discord group if you don't have a valid serial no for AME, his patch is doing something with discord registration and that's dangerous. Luckaliy I have a valid serial no for my DSM.

 

This developer is out of control and I think his project should be avoided. I'm rolling back to TCRP, the developer who doesn't miss his users is not a real developer.

 

Btw, the developer failed to give a technical answer/solution, but I have figured it out myself;

 

version 1.1.4. is default configured on the 'next' releases, you don't know that, it's a developer failure. You cannot update that release by doing weird things. Switch it back manually to the stable branch and arc.sh will let you update.

 

Be warned, he will kick you out of his discord community if you smell funny.

 

Also i don't suggest a loader that is dependent on a discord group

I've actually communicated with him via github. I think the issues you had with him are due to language barrier. and he is impatient. But I've found his loader to be quite good and offers the ARC Patch that allows the use of synology services, which RR does not.

[apriliars3]

10 hours ago, Randomized said:

Beware of this developer, it's someone who kicks you out of the discord group if you asks support.

 

I asked why the update is failing from 1.1.4 to 1.1.19 (it's now 1.1.22). He told me to use my brain because he told it 10 times in his little discord group?

Well... i have never been on that discord group until today, but beware guys.

 

You need the discord group if you don't have a valid serial no for AME, his patch is doing something with discord registration and that's dangerous. Luckaliy I have a valid serial no for my DSM.

 

This developer is out of control and I think his project should be avoided. I'm rolling back to TCRP, the developer who doesn't miss his users is not a real developer.

 

Btw, the developer failed to give a technical answer/solution, but I have figured it out myself;

 

version 1.1.4. is default configured on the 'next' releases, you don't know that, it's a developer failure. You cannot update that release by doing weird things. Switch it back manually to the stable branch and arc.sh will let you update.

 

Be warned, he will kick you out of his discord community if you smell funny.

 

Also i don't suggest a loader that is dependent on a discord group

 

Discord is just an excuse for coffee support

 

AuxXxilium

 

Synology will eventually make all its services subscription-based, and it won't matter whether you have its hardware or not

[Fox Mulder]

22 hours ago, apriliars3 said:

 

Discord is just an excuse for coffee support

 

AuxXxilium

 

Synology will eventually make all its services subscription-based, and it won't matter whether you have its hardware or not

Well, I never encountered anywhere where he asked for donations or support specifically. Most developers include a "buy coffee" button and it's the least people who want to support their efforts can do for their dedication. As for subscription based services, it may happen, yes. But even if it did, there are still free alternatives, such as Tailscale, DynuDNS, and others.

[Randomized]

On 12/8/2024 at 8:39 AM, Fox Mulder said:

I've actually communicated with him via github. I think the issues you had with him are due to language barrier. and he is impatient. But I've found his loader to be quite good and offers the ARC Patch that allows the use of synology services, which RR does not.

 

It's a fine loader from the operation perspective fot as long as it lasts. I think need trustworthy developers in xpenology land for the loaders. How many of you encountered that they need a new loader for a specific DSM updgrade, and then find out the loader is not developed anymore.

 

But from a dependency perspective, needing discord for a loader with a tyrant banning you in a healthy discussion I have doubts..

 

 

[Fox Mulder]

24 minutes ago, Randomized said:

 

It's a fine loader from the operation perspective fot as long as it lasts. I think need trustworthy developers in xpenology land for the loaders. How many of you encountered that they need a new loader for a specific DSM updgrade, and then find out the loader is not developed anymore.

 

But from a dependency perspective, needing discord for a loader with a tyrant banning you in a healthy discussion I have doubts..

 

 

You don't "need discord" for this or any other loader. You don't have to use ARC Patch, and can still use ARC Loader without issue.

[Sonnenblume]

Thank you @Fox Mulder, it runs with latest version 1.1.25 at my older Laptop Latitude 7390 with one internal SSD.

 

Is it possible to use a micro-SSD or an external USB-SSD as 2nd storage for SHR-Pool?

Edited December 19, 2024 by Sonnenblume

[Fox Mulder]

On 12/19/2024 at 8:05 PM, Sonnenblume said:

Thank you @Fox Mulder, it runs with latest version 1.1.25 at my older Laptop Latitude 7390 with one internal SSD.

 

Is it possible to use a micro-SSD or an external USB-SSD as 2nd storage for SHR-Pool?

I did start this thread, but I am not the author of this, or any other loader. You are welcome to ask him at: https://github.com/AuxXxilium/arc

As far as I know, it can work, but more likely it will work on older hardware rather than new one. 

[Fox Mulder]

Here is a tip. I encountered the need for it with the newest 1.3.1 version release, as entering the data in "cpuinfo" addon section manually would cause the arc loader to fail to load the DSM for some reason. (I will open an issue in github for it at a later time)

But for now, the solution is to use the cpuinfo.sh script itself (it is a part of the ARC Loader itself) manually via SSH connection as follows:

1. Connect to the NAS via ssh with your username and password (after verifying that you opened SSH access in your NAS)
2. cd /usr/bin
3. sudo -i
4. cpuinfo.sh -t "on" --vendor "Intel" --family "Core i7" --series "i7-8700k" --cores 12 --speed 3700
5. exit
6. exit

Naturally, you should change the parameters according to your CPU (the parameters included here are just as an example) so it will match. once you done all this, and refreshed your DSM access webpage, you should be able to see the correct values for your CPU in the Control Panel / Info Center page.

 

Cheers!

P.S.: It did not seem to survive a reboot. Meaning, the values reverted. A ticket has been opened for the issue, and hopefully it will be resolved.

Edited January 5 by Fox Mulder

[Fox Mulder]

On 1/5/2025 at 9:52 PM, Fox Mulder said:

Here is a tip. I encountered the need for it with the newest 1.3.1 version release, as entering the data in "cpuinfo" addon section manually would cause the arc loader to fail to load the DSM for some reason. (I will open an issue in github for it at a later time)

But for now, the solution is to use the cpuinfo.sh script itself (it is a part of the ARC Loader itself) manually via SSH connection as follows:

1. Connect to the NAS via ssh with your username and password (after verifying that you opened SSH access in your NAS)
2. cd /usr/bin
3. sudo -i
4. cpuinfo.sh -t "on" --vendor "Intel" --family "Core i7" --series "i7-8700k" --cores 12 --speed 3700
5. exit
6. exit

Naturally, you should change the parameters according to your CPU (the parameters included here are just as an example) so it will match. once you done all this, and refreshed your DSM access webpage, you should be able to see the correct values for your CPU in the Control Panel / Info Center page.

 

Cheers!

P.S.: It did not seem to survive a reboot. Meaning, the values reverted. A ticket has been opened for the issue, and hopefully it will be resolved.

Anyways, it turns out you can use the edit user info under dsm options in the config screen of the loader, to enter these values (not enclosed in "") and it works fine. (you'll still need to re-build the loader)

[Fox Mulder]

Another insight:

ARC loader should be loaded (the USB stick) in UEFI mode (in the boot order inside the bios you should see both USB and UEFI boot options for the ARC Loader USB stick)

Make sure the UEFI boot option is first. I found that on my Asrock motherboard, if I don't do that, I get no network connection even for the configuration.

Cheers.