Automated RedPill Loader (ARPL)

[idaanx]

18 hours ago, gaitken said:

Tried both ways now , tried downloading the bigger file, also tried automatic, both come up with the same error. at 57%

 

 

I just had the same error at the same spot in a VM. Tried to reuse the loader for a fresh install for testing, resetting the loader and trying again worked for me. So try to reflash the loader to your USB drive, configure it and try to install again. 

[vasiliy_gr]

So is it possible to install beta7 in DS3622xs+ mode? I ask because I want make some experiments with hibernation, but beta8 and beta9 both make kernel panic in DSM (and I do not know why - may be because of Proxmox, may be because of i5-12400 or may be because of something else). I can't install beta7 from downloaded image (because size error while making DSM kernel). And as for beta3 - there I can't use hibernation at all.

The question is - can I download beta7 image, make some settings, try to make DSM kernel - obtain error, exit, some commands in command-line, again menu.sh and build kernel without error?..

[idaanx]

19 minutes ago, vasiliy_gr said:

So is it possible to install beta7 in DS3622xs+ mode? I ask because I want make some experiments with hibernation, but beta8 and beta9 both make kernel panic in DSM (and I do not know why - may be because of Proxmox, may be because of i5-12400 or may be because of something else). I can't install beta7 from downloaded image (because size error while making DSM kernel). And as for beta3 - there I can't use hibernation at all.

The question is - can I download beta7 image, make some settings, try to make DSM kernel - obtain error, exit, some commands in command-line, again menu.sh and build kernel without error?..

 

There was a version of ARPL that gave me issues building the loader too, can't remember if it was b7. Fixed it by changing to a different model first and build that, then changing the model back and build it again.

[kaku]

So is it possible to install beta7 in DS3622xs+ mode? I ask because I want make some experiments with hibernation, but beta8 and beta9 both make kernel panic in DSM (and I do not know why - may be because of Proxmox, may be because of i5-12400 or may be because of something else). I can't install beta7 from downloaded image (because size error while making DSM kernel). And as for beta3 - there I can't use hibernation at all.
The question is - can I download beta7 image, make some settings, try to make DSM kernel - obtain error, exit, some commands in command-line, again menu.sh and build kernel without error?..

Hey, just out of curiosity. Did you try a fresh install ? Preferably with no volumes. I also dont get ip (but port leds do blink) when i have multiple raid volumes)

It works with a fresh install or in an existing raid0 single volume.

[royeiror]

2 hours ago, idaanx said:

 

I don't know about serial port, just use a screen and keyboard on the M600. If there is nothing important on the disk just wipe it first before trying to install so you don't get the migratable message.

I do always keep a monitor plugged in. It looks normal as the boot screen should, it has on some occasion gone completely blank after a while.

[idaanx]

23 minutes ago, royeiror said:

I do always keep a monitor plugged in. It looks normal as the boot screen should, it has on some occasion gone completely blank after a while.

 

I'm a bit lost at where it goes wrong can you tell me step by step what you did and where it stops working. Also is this an upgrade from a previous version or a new install?

[royeiror]

31 minutes ago, idaanx said:

 

I'm a bit lost at where it goes wrong can you tell me step by step what you did and where it stops working. Also is this an upgrade from a previous version or a new install?

This is a new baremetal install with wiped HDD.

 

I have a bunch of the ARPL zips downloaded, I have flashed most of them on a 16 GB USB drive I have tried with CSM and UEFI modes as well.

* I boot to USB 

* Configure Loader.

* Normally choose 920+ but I've run through all the models.

* Choose Build, I've gone through the 3 of them for multiple models.

* Generate random SN

* Generate MAC (where able)

* Add add-ons like the dbutils and such (I can't seem to find the logs anywhere).

* Build the loader

* Boot the loader

* I have a CMD prompt pinging the device permanently so while on the loader it's always accessible

* Connection is lost while booting, monitor goes through all the steps of booting kernel and then DSM, sometimes goes completely blank after a while.

* Sometimes the device will not respond to ping any further, sometimes it will, but will only be reachable through port 7681.

* The times when Synology Assistant finds the device, it sends me to the IP:5000 page, I've tried uploading the.pat file al also letting it do it automatically, in any case, I wait the 10 minutes, it lets me know something has gone wrong and if I refresh, it gives me another 10 minutes.

* At the moment, the screen looks like it's booting DSM, the IP:7681 is reachable and shows BusyBox.

 

 

 

[blindspot]

1 hour ago, royeiror said:

I have a bunch of the ARPL zips downloaded, I have flashed most of them on a 16 GB USB drive I have tried with CSM and UEFI modes as well.

Maybe try with different usb stick and/or different usb port. I have a mb that will boot arpl on all usb ports but couldnt boot dsm on some specific usb ports.

[royeiror]

2 minutes ago, blindspot said:

Maybe try with different usb stick and/or different usb port. I have a mb that will boot arpl on all usb ports but couldnt boot dsm on some specific usb ports.

Never thought of that, and I have been booting from a single specific port, I'll try that. In any case, could anyone walk me through taking a look at the logs?

[vasiliy_gr]

3 hours ago, idaanx said:

There was a version of ARPL that gave me issues building the loader too, can't remember if it was b7. Fixed it by changing to a different model first and build that, then changing the model back and build it again.

Thank you, it helps. But finally I got on beta6 kernel panic also... I will write about it later.

[vasiliy_gr]

3 hours ago, kaku said:

Hey, just out of curiosity. Did you try a fresh install ? Preferably with no volumes. I also dont get ip (but port leds do blink) when i have multiple raid volumes)

It works with a fresh install or in an existing raid0 single volume.

I do not have spare hdd-s now. So I can't make 'fresh install' or use raid0. But I don't have multiple raid volumes.

[vasiliy_gr]

New investigation. Sorry - without pictures.

Lets start with history. I installed beta3 (previously was tcrp). No problems except hibernation. And on beta3 I can't force my hdd-s hibernate at all.

So later I installed from internal arpl upgrade menu version beta6. There were some issues with kernel panic, but they could be solved by DSM reboot. Soon I got beta7, so I don't know much on beta6. I installed beta7 from beta6 (that was installed from beta3) internally through menu.

And all above I did on four NAS-es wih very similar characteristics. All of them have Proxmox, 12th generation of Intel CPU-s and Z690 m/b-s from Asus with 64 or 128 GB of RAM (minus something for Proxmox), disabled SATA controller, 9300 or 9400 SAS HBA instead. Also all of them are DS3622xs+ with the latest DSM. And historicaly they had finally beta7. The new part is only about one NAS.

 

At first I tried to install new versions internally. After bad results with upgrade procedure, I downloaded images from github, made some settings and tried DSM. My settings: 9p, lsutil - in Addon menu, SataPortMap=18 and DiskIdxMap=1B00 in Cmdline menu. And of course previously - DS3622xs+, latest/upper DSM, random SN. Then - build loader - boot.

 

beta3 - no problems at all. But no hibernation at all.

beta4 - no network, only localhost available.

beta5 - no "Boot" item in menu.sh after building DSM kernel. So I did exit and reboot manually. I saw grub menu but it refused to boot beyond red lines. So no DSM here too.

beta6 - it was the second best result after beta3... It loaded DSM as restore session. I did restore. It rebooted. And - kernel panic...

beta7 - kernel panic.

beta8 - kernel panic.

beta9 - kernel panic.

 

To some up: the last working loader in my configuration is beta3. All loaders above produce unbootable DSM. There may be some way to produce good ARPL above beta3 - using upgrade menu. For example, I managed to do upgade from beta3 to beta6 and later to beta7. But i can't reproduce it, as upgrade menu only upgrades to latest version. And beta8/beta9 produce kernel panic after upgade from beta3 and beta6.

So now I have beta3 on only one NAS where I can study hibernate problem (as I have SAS hdd-s there with inverted led logic). And I have beta7 on other NAS-es - but I can't reproduce the way I got this version.

[idaanx]

2 hours ago, royeiror said:

This is a new baremetal install with wiped HDD.

 

I have a bunch of the ARPL zips downloaded, I have flashed most of them on a 16 GB USB drive I have tried with CSM and UEFI modes as well.

* I boot to USB 

* Configure Loader.

* Normally choose 920+ but I've run through all the models.

* Choose Build, I've gone through the 3 of them for multiple models.

* Generate random SN

* Generate MAC (where able)

* Add add-ons like the dbutils and such (I can't seem to find the logs anywhere).

* Build the loader

* Boot the loader

* I have a CMD prompt pinging the device permanently so while on the loader it's always accessible

* Connection is lost while booting, monitor goes through all the steps of booting kernel and then DSM, sometimes goes completely blank after a while.

* Sometimes the device will not respond to ping any further, sometimes it will, but will only be reachable through port 7681.

* The times when Synology Assistant finds the device, it sends me to the IP:5000 page, I've tried uploading the.pat file al also letting it do it automatically, in any case, I wait the 10 minutes, it lets me know something has gone wrong and if I refresh, it gives me another 10 minutes.

* At the moment, the screen looks like it's booting DSM, the IP:7681 is reachable and shows BusyBox.

 

How do you generate a mac address? Just leave the mac address as the real one from the NIC. If you change it your router will give that mac address a different ip, that's probably why it's not working with the old ip. Also like I said before, once the loader is booted the 7681 port shouldn't work any longer, since it still works for you I'm pretty sure you got a different ip for the loader.

 

Check your routers DHCP to see if you got any new devices connected and use the search button on Synology Assistant.

[royeiror]

34 minutes ago, idaanx said:

 

How do you generate a mac address? Just leave the mac address as the real one from the NIC. If you change it your router will give that mac address a different ip, that's probably why it's not working with the old ip. Also like I said before, once the loader is booted the 7681 port shouldn't work any longer, since it still works for you I'm pretty sure you got a different ip for the loader.

 

Check your routers DHCP to see if you got any new devices connected and use the search button on Synology Assistant.

I didn't think of the MAC detail, will skip the step and see if it fixes anything. I constantly use the ping IP -t and the assistant, it doesn't always show up, but when it does, and I get the drive detected, it goes through the motions and ends up with an error message that something went wrong. in any case I'll check to leave the MAC blank and see if that fixes anything, also checking if a device with the modified MAC shows up in the DHCP lease list.

[idaanx]

Again, how do you generate a mac address?

 

Also don't leave it blank, won't work without one. Easiest to start with a fresh ARPL which populates everything for you.

[royeiror]

4 minutes ago, idaanx said:

Again, how do you generate a mac address?

 

Also don't leave it blank, won't work without one. Easiest to start with a fresh ARPL which populates everything for you.

Right, the newer betas do that stuff automagically when generating the SN.

[soyoscar]

Hi. I am using the v1-beta1 and in the part of the process when I need to install DSM, the system can't see de HD. What can I do?

 

Regards:   Óscar

 

Edited December 17, 2022 by soyoscar
imagge add

[idaanx]

5 hours ago, royeiror said:

Right, the newer betas do that stuff automagically when generating the SN.

 

Still not an answer to the question...

[idaanx]

11 minutes ago, soyoscar said:

Hi. I am using the v1-beta1 and in the part of the process when I need to install DSM, the system can't see de HD. What can I do?

 

Try a different model like 918 or 3622, take a look at the device tree info. Updating the loader can be done within the configurator.

[vasiliy_gr]

...And finally I found a way how to revert my test NAS back to beta7. I will not repeat again all this long story... Only outline. At first stage I installed successfully beta3 on four NAS-es. On second stage I upgraded all of them internally in ARPL from beta3 to beta6 and from beta6 to beta7. And the third stage was a disaster: I upgraded from beta7 to beta8, also beta9, also tried direct image download from github - and I received kernel panic (or other way of unworking DSM) on all the beta-s above beta3. And beta3 has absolutely unworking hibernation. And the only one NAS where I can study hibernation was stuck on beta3...

 

But I have other NAS-es with beta7! So I copied good image of beta7 from one of the other NAS-es, copied it over the network and run instead of beta3.

 

At least you should change in this variant two things - SN and MAC. New SN can be generated randomly. MAC i took from the previous value of MAC on this NAS. More than that ARPL starts even in "configure" variant not with hardware MAC but DSM MAC. So two NAS-es have the same MAC... It is not good for network activity on both of them. So it is better not to run NAS-donor before reconfiguring NAS-patient (at least new/old MAC should be entered). After these two changes (SN and MAC) make other changes if needed (I changed maxdisks). Build loader, boot loader. And everything is working...

 

It take me a lot of time because at first I forgot about MAC. Then it was surprise for me that ARPL starts "configure" with MAC of the other NAS - so I had two NAS-es with equal MAC-s on network. And after understanding and solving this problem - everything was fine.

 

Anyway... Now I have again beta7 on four NAS-es. But I tried previously beta7 on the same NAS - it was kernel panic... So these two beta7 are different.

[soyoscar]

9 hours ago, idaanx said:

 

Try a different model like 918 or 3622, take a look at the device tree info. Updating the loader can be done within the configurator.

Thanks for your answer. I I have seen in the menu of the configurator that the the ARPL can see 0 DRIVES in "SATA ports and drives" and when the final boot starts I can see that sinology find 0 HDs.

 

How can I add mine? 

 

I don't understand what do you men whith this: 

 

Quote

take a look at the device tree info

Can anybody help me?

Regards:   Oscar

Edited December 17, 2022 by soyoscar

[rojoone2]

13 minutes ago, soyoscar said:

Thanks for your answer. I I have seen in the menu of the configurator that the the ARPL can see 0 DRIVES in "SATA ports and drives"   How can I add mine? 

 

I don't understand what do you men whith this: 

 

Can anybody help me?

Regards:   Oscar

Can you give information about your hardware?

 

[soyoscar]

12 minutes ago, rojoone2 said:

Can you give information about your hardware?

 

yes, here you can see the hardwere info of my minipc:
https://drive.google.com/file/d/1Epls8pZk_GBqMjcZoarc_Unl1MRnQMRI/view?usp=sharing

[rojoone2]

Can you try the DS3622xs+ instead of the DS920+?.. because the DS920+ needs a newer processor than the DS3622xs+

Edited December 17, 2022 by rojoone2

[idaanx]

Are you sure you have a SATA drive in your minipc? Can you type 'fdisk -l' (without the quotes and small L) into the terminal of ARPL. You should see sda and sdb, one should be the USB device and the other should be your HDD.

 

Read this page about the different platforms and device tree, link was already in my first replay