Automated RedPill Loader (ARPL)

[use-nas]

[Green]

10 minutes ago, use-nas said:

 fbelavenuto said:
I've changed the update system, then is necessary to burn the image again, the upload menu do not work from alpha to beta!

[use-nas]

Ok

[vinhnguyen]

12 hours ago, fbelavenuto said:

Finally the beta version!

 

https://github.com/fbelavenuto/arpl/releases/tag/v1.0-beta2

 

I've changed the update system, then is necessary to burn the image again, the upload menu do not work from alpha to beta!

 

Thank you. My Intel I225-LM worked at this new version.
But Network Status does not show parameters... My home network is 1Gbps and it has received enough. I don't have a 2.5Gbps switch see if it gets enough...

[pocopico]

On 10/26/2022 at 4:31 AM, Peter Suh said:

 

Ah, I misunderstood the PM of pocopico.
The permanent solution was provided by you
Is pocopico thinking about multi-reservation?
Sorry. ^^

 

The powersched extension that includes the rtc-cmos module and fabios powersched command and execution scheduling has been created under my rp-ext repo. I have tested that but need more testing if you can help with that.

[RedwinX]

@IG-88 🤣🤣 you have to work for Synology support, you know more about DSM than Synology 😅😅

[Peter Suh]

1 hour ago, pocopico said:

 

The powersched extension that includes the rtc-cmos module and fabios powersched command and execution scheduling has been created under my rp-ext repo. I have tested that but need more testing if you can help with that.

 

Does rtc-cmos and powersched always make sense to build together?
Is powersched's core function for scheduling multi-power startup?

 

Or should I just use powersched instead of rtc-cmos?

Edited October 27, 2022 by Peter Suh

[Peter Suh]

@pocopico, @fbelavenuto

 

APRL is of course also relevant, but is it okay to keep referring to the test for power reservation here?

Maybe fabio will follow us up?

 

Replaced rtc-cmos with powersched and set up multi-schedule.
However,
The value that initially set 18:55 minutes was changed to 1666864500.
However, the setting value of 18:50 minutes earlier than that is not changed.
please check.

 

I'll check if it boots up at 18:55.

 

And this is a script that converts the epoch to my time zone and shows it. Take advantage of it.

 

while true;  do echo $(date -d @`cat /sys/class/rtc/rtc0/wakealarm`);  sleep 3;  done

 

 

 

Edited October 27, 2022 by Peter Suh

[pocopico]

1 hour ago, Peter Suh said:

 

Does rtc-cmos and powersched always make sense to build together?
Is powersched's core function for scheduling multi-power startup?

 

Or should I just use powersched instead of rtc-cmos?

 

Well its either the one or the other. Powersched extension though looks more solid. Lets move this discussion though to the power up schedule thread 

Edited October 27, 2022 by pocopico

[Peter Suh]

2 minutes ago, pocopico said:

 

Well its either the one or the other. Powersched extension though looks more solid. 

 

Did you see the reporting right above?
powersched is not behaving as expected.
Is it possible to make multiple reservations?

[fbelavenuto]

58 minutes ago, Peter Suh said:

 

Did you see the reporting right above?
powersched is not behaving as expected.
Is it possible to make multiple reservations?

Thanks for the tests, I did it quickly to help @pocopico but it will definitely need tweaking. The software was made with multiple reservations in mind.

[pocopico]

6 minutes ago, fbelavenuto said:

Thanks for the tests, I did it quickly to help @pocopico but it will definitely need tweaking. The software was made with multiple reservations in mind.

 

@Peter Suh The powersched is scheduled to run every 60 seconds and set the wake alarm. You wll have to wait maximum one minute before checking the value of wakealarm. 

[Peter Suh]

15 minutes ago, pocopico said:

 

@Peter Suh The powersched is scheduled to run every 60 seconds and set the wake alarm. You wll have to wait maximum one minute before checking the value of wakealarm. 

 

Ok, I'll test again.

[Peter Suh]

34 minutes ago, pocopico said:

 

@Peter Suh The powersched is scheduled to run every 60 seconds and set the wake alarm. You wll have to wait maximum one minute before checking the value of wakealarm. 

 

@pocopico

 

It always reacts only to the first PowerOn Task 0 scheduler.
The second, PowerOn Task 1, changed the time and waited for more than 1 minute, but there was no change.

 

[RedwinX]

 

6 hours ago, RedwinX said:

@IG-88 🤣🤣 you have to work for Synology support, you know more about DSM than Synology 😅😅

 

Edited October 27, 2022 by RedwinX

[Peter Suh]

2 hours ago, pocopico said:

 

@Peter Suh The powersched is scheduled to run every 60 seconds and set the wake alarm. You wll have to wait maximum one minute before checking the value of wakealarm. 

 

I finally succeeded in multi-booking.
I changed "task 1" to 23:13 minutes
Again I changed "task 0" to 23:02 minutes, both work.

 

[Peter Suh]

30 minutes ago, Peter Suh said:

 

I finally succeeded in multi-booking.
I changed "task 1" to 23:13 minutes
Again I changed "task 0" to 23:02 minutes, both work.

 

 

The time setting seems to be normal.
But, why doesn't it start at 23:13?
What should I check again?

 

Sorry. The power was turned off at 23:03.
I'll try again.^^

Edited October 27, 2022 by Peter Suh

[Peter Suh]

26 minutes ago, Peter Suh said:

 

The time setting seems to be normal.
But, why doesn't it start at 23:13?
What should I check again?

 

Sorry. The power was turned off at 23:03.
I'll try again.^^

 

@pocopico

 

23:47 Power On
23:50 Power Off
23:53 Power On
23:56 Power Off

 

I tested it like this.

The first boot came up,
There is no news on the 2nd boot.

Is it because it shuts down in too short a time after the first boot?

[Peter Suh]

23 minutes ago, Peter Suh said:

 

@pocopico

 

23:47 Power On
23:50 Power Off
23:53 Power On
23:56 Power Off

 

I tested it like this.

The first boot came up,
There is no news on the 2nd boot.

Is it because it shuts down in too short a time after the first boot?

 

@pocopico

 

At around 4 minutes, powersched searches for the next schedule and sets it.

I tested it every 5 minutes, and it was confirmed that the time of the second schedule changed after the first boot.

 

00:05 Power On
00:10 Power Off
00:15 Power On
00:20 Power Off

 

However, the first boot is also
The second boot did not boot at the expected 00:15.

 

 

Edited October 27, 2022 by Peter Suh

[jetca]

Hi , I am updating DSM6  (Jun's loader) to DSM7 ( ARPL ) runing in ESXi 7. The problem I have is the disk order. The disk order works pretty well with DSM6 loader, but not good with DSM7 loader. 

 

my setting:

Dell R730xd, with 12x 3.5" drives, and 2x 2.5" drives.  

H730 flashed to HBA330, passthrough all drive to DSM virtual machine.

ESXi: 7.0 update 3

 

DSM 6.2.3 (25426):

synoboot drive at sata0 (0:0)

synodata drive at sata1 (1:0)

all hard drives: passthrough by HBA330

grub.cfg setting:

sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=1819 SataPortMap=1 SasIdxMap=0'

 

With this DiskIdxMap=1819 SataPortMap=1 SasIdxMap=0 setting,

Everything works pretty well, the disk number in DSM6 starting from 1 to 12 for 3.5", 13 and 14 for 2.5" drive. and synoboot and synodata drives are hidden.

Empty bay will not be taken by the other drives. for example, I put disks in 3.5" bay #1,#2,#3,#12, and #1, #2 in 2.5" bay,  then the disk numbers in DSM6 are shown as disk 1,2,3,12,13, 14 

but when I booted with DSM7 (update 42962)  with ARPL loader (v0.5-alpha1), 

ARPL boot drive at sata0 (0:0)

synodata drive at sata1 (1:0)

all hard drives: passthrough by HBA330

 

the old DiskIdxMap=1819 SataPortMap=1 SasIdxMap=0 setting cannot work. system cannot detect any drive.

i changed to following setting suggested by running tool in tinycore load  "rpload.sh satamap now" 

SataPortMap: 18

DiskIdxMap: 1000

SasIdxMap: 0

then the drives are listed with wrong order. the empty bays are ignored. 

for example, I put disks in bay #1,#2,#3,#12,#13,#14,  then the disk numbers in DSM6  are 10,11,12,13,14,15, with disk 1 for the syno data drive. 

anyone know how to fix it? Thanks.

 

 

 

Edited October 27, 2022 by jetca

[pocopico]

59 minutes ago, jetca said:

Hi , I am updating DSM6  (Jun's loader) to DSM7 ( ARPL ) runing in ESXi 7. The problem I have is the disk order. The disk order works pretty well with DSM6 loader, but not good with DSM7 loader. 

 

my setting:

Dell R730xd, with 12x 3.5" drives, and 2x 2.5" drives.  

H730 flashed to HBA330, passthrough all drive to DSM virtual machine.

ESXi: 7.0 update 3

 

DSM 6.2.3 (25426):

synoboot drive at sata0 (0:0)

synodata drive at sata1 (1:0)

all hard drives: passthrough by HBA330

grub.cfg setting:

sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=1819 SataPortMap=1 SasIdxMap=0'

 

With this DiskIdxMap=1819 SataPortMap=1 SasIdxMap=0 setting,

Everything works pretty well, the disk number in DSM6 starting from 1 to 12 for 3.5", 13 and 14 for 2.5" drive. and synoboot and synodata drives are hidden.

Empty bay will not be taken by the other drives. for example, I put disks in 3.5" bay #1,#2,#3,#12, and #1, #2 in 2.5" bay,  then the disk numbers in DSM6 are shown as disk 1,2,3,12,13, 14 

but when I booted with DSM7 (update 42962)  with ARPL loader (v0.5-alpha1), 

ARPL boot drive at sata0 (0:0)

synodata drive at sata1 (1:0)

all hard drives: passthrough by HBA330

 

the old DiskIdxMap=1819 SataPortMap=1 SasIdxMap=0 setting cannot work. system cannot detect any drive.

i changed to following setting suggested by running tool in tinycore load  "rpload.sh satamap now" 

SataPortMap: 18

DiskIdxMap: 1000

SasIdxMap: 0

then the drives are listed with wrong order. the empty bays are ignored. 

for example, I put disks in bay #1,#2,#3,#12,#13,#14,  then the disk numbers in DSM6  are 10,11,12,13,14,15, with disk 1 for the syno data drive. 

anyone know how to fix it? Thanks.

 

 

 

 

 

Did you try changing the command line option HddHotplug=0 to HddHotplug=1 ? 

 

 

 

[SanKen]

I have updated 0.5alpha to version 1.0beta2. After booting, I got Recovery ... but this is not Recovery loop. I clicked Recovery and DSM started up properly.

 

I have a question. I have built-in eMMC 32GB memory in Intel NUC. How to use it for ARPL. i was thinking about using dd from linux.

[Mincemeat]

15 hours ago, RedwinX said:

 

 

 

Thanks for bringing that to out attention. We will get right on it, making loaders harder to work and whatever

 

Why u in their dms, you got a legit unit?

[jurgenautt]

Hello, I report that the beta version does not work with my hardware, instead the alpha version v0.5-alpha1 does work correctly (removing some errors that I had previously reported)
  the version i try rs4021xs+
If you need to carry out any additional tests, tell me fbelavenuto, thank you very much for the work

.I proceed in the same way, I format a new USB, I install the image, I carry out the configuration process, everything seems correct, I restart to be able to install the dsm, on the screen everything appears correct, (search ip etc, booting etc)
but the windows explorer gives it the ip, but it does nothing, i search with an ip scanner program, but that ip that the loader gives me is not there, as if it did not give the ip or that the drivers of the network cards did not they were fine...

[jetca]

Thanks, Pocopico. 

I tried HddHotplug=1, and the disk numbers are still the same as HddHotplug=0 .