I am having fun problems and trying to address. seeking help please

[hombre]

I am using Arc Bootloader 2.5.9 was working find but upgraded to 7.2.2 and I did not run the sh commands for surveillance station and removed... So I then wanted to downgrade back to 7.2.1. That is when the fun started.

I have created a new bootloader and want to either load to 7.2.2 or 7.2.1 now. I do not care but would prefer back to 7.2.1.

 

I can't get past ARC config now. when I try to add my NAS that I want and go thru menus, it gets to a place where is says "Please upload the DSM Boot File to /mnt/p3/user". I mounted this partition in Ubuntu and added the files (tar and pat files form Arc site here). But the issue still persists.

I did have to do this in the past.

 

I just want to get BACK to DSM across the drives and get back to my NAS.. I have spend 5 plus hours at it moving files back and forth to no success. So now I am seeing help...

 

1) I have use Arc config, selected hardware, automated deployment and also manual with serial number I have. Everytime when I go to build, I get the "please uploade the DSM Boot file..with a github address and a tar file (I can find on site and put in the user folder) but it still does not work..

 

What is the BEST way to get back into NAS with DSM striping across drives as I cannot get Arc Loader to do...

 

I also cannot get into Discord room either. I can pay for some coffee. Just need to get this fixed.

 

Thanks in advance.

 

I can post more of my details if needed, but just need the best/easiest way to get back into the NAS files structure and DSM...

[Peter Suh]

I am the developer of TCRP-MSHELL, another loader different from ARC.

 

I did a little research on ARC and it seems to expect and look for user-config.yml.

But it seems to be in a different location than expected, so the error message is a bit strange.

 

 

User config files are sometimes corrupted.

 

If there is no solution, try building a DVA with my MSHELL loader.

 

https://github.com/PeterSuh-Q3/tinycore-redpill/releases

 

I am using DVA3219 as my real machine.

 

 

Edited June 28 by Peter Suh

[hombre]

Thank you. Can you send me the link for installation on this forum. 
Is it this link? Or is there a newer one? Thanks.

 

[Peter Suh]

This guide is a very old command-oriented guide.
Now all loaders have changed to menu-based.
For the installation guide, please refer to this link.

 

https://github.com/PeterSuh-Q3/tinycore-redpill/blob/main/README.md

 

How to use the menu is explained about halfway through this README.md.

[hombre]

There is one thing remaining. I want to use static IP addresses for my 2 NICs. I thought I edited json correctly, but still not working. Is there a menu item that I am missing to do this or, can you please provide sytax for doing in the config file.

 

I show that it provides an address and I can see it via finds.synology.com but when it tries to go to it, it does not reach Network Error.

 

Thanks

 

[Peter Suh]

I don't know what NIC chipset you are using, but the most compatible and recommended model is SA6400. It is not too late to set the static IP after you have normally received the IP from DHCP. And my message space is always insufficient. Please avoid PMs.

[hombre]

OK so I am able to get IP address and boot to DSM with your loader, however, I think I know what the issue is... I WAS running 7.2.2 with Arc Loader. I downgraded and then tried to install 7.2.1. It is now failing installing DSM 7.2.1 with your loader. I can access the IP address and it does not matter if I use stored PAT or use internet, I cannot get 7.2.1 to install on drives.. What is command/process to clear the DSM stripping on the drives to be able to put 7.2.1 onto system?

See below screen capture of when trying to install DSM software.

 

Thanks.

 

[hombre]

More info. When I rebuild the loader after going thru the menu, it says detect internet... and then connects. However, if I reboot the system and try to boot right into DSM mode, it does not connect to the internet,,, No internet found... But then represents a private IP address I can use to get to DSM interface...

 

I have also tried to use Junior mode at boot to re-install DSM, but due to no internet, it says Boot timeout exceeded, booting.

 

I do see the DSM version having issues .-0. I have used ChatGPT to tell me what to do but would like confirmation if possible please...

 

🧼 Step 1: Wipe the Boot Disk (Not the USB!)

The . -0 version issue is often caused by leftover system partitions from failed or mismatched DSM versions.

🛑 Identify your boot disk:

Boot into TinyCore and run:

bash

CopyEdit

lsblk

 

💣 Wipe the first 100MB:

bash

CopyEdit

sudo dd if=/dev/zero of=/dev/sdX bs=1M count=100

Replace sdX with the correct drive (e.g., sda). DO NOT WIPE your USB boot device.

 

🧹 Step 2: Clean and Rebuild Redpill Loader

Mount your USB:

bash

CopyEdit

mount ls /mnt/ cd /mnt/sdX1 # replace with correct mount point

 

[Peter Suh]

The problem of failing to connect to the Internet seems to be unrelated to the loader's function and is affected by the router's environmental settings.

 

One thing to check is whether the BIOS UTC time of your PC is too far from the actual time.

 

Sometimes, these things can interfere with the Internet connection due to security policies.

[hombre]

I got the IP address thing somewhat figured out. What is the process to redo DSM load as I am in limbo? I used Arc Loader and I think the downgrade menu option is what put me in this place? I beleive the above will work but not a Linux expert so do not want to screw it up even more.. Current DSM is .-0. Thanks.

[Peter Suh]

Downgrading can cause unexpected things, as you said.

 

I have used downgrading in the past, but I was not satisfied with it, so I went back to the latest version.

 

Why do I need to downgrade?

[hombre]

Realize now downgrading is not a good path. I am just trying to get BACK to DSM with a loader. 7.2.2 is fine. For some reason due to the download attempt, I cannot install either 7.2.2 or anything else to the disk now. I am looking for step by step instructions via a loader, to get to 7.2.2 without losing any of my data.

 

Is there a way/process to force 7.2.2? Or do I need to do some clean up before any DSM will load to drives in current state?

 

Thank you in advance.

[Peter Suh]

I'm not exactly sure how ARC supports downgrades and upgrades. I'm also not sure if it's safe to update again. I'm the developer of another loader, MSHELL, which is on the other side of ARC, as you may already know. I recommend asking about this feature of ARC directly on the ARC GitHub issues. Or, I think Russian users are familiar with ARC. You can also consider asking on the Russian topics.

Edited July 6 by Peter Suh