Jump to content
XPEnology Community

RS4021xs+ loader development thread


Recommended Posts

Posted (edited)

1397149432_2022-07-2110_25_33.thumb.png.a0e4e0b81c9c8875c3cd0f3390052990.png

614167967_2022-07-2110_25_41.png.bd3b0575c2c01393b1b3793e5c64ecc6.png

 

Release to build RS4021xs+ loader using TCRP and M shell.

 

This is RS4021xs+, a 16-bay model.

It is the first model with XPE as an enterprise-class rack station.

There are 2 powers, but it is not so on the PC, so power 1 is an error as in the capture.

 

This model is also a Broadwellnk platform like DS3622xs+ and DS1621xs+.

Release jot mode / jun mode at the same time.

 

Recycled bsp files in pocopico 's config.

https://github.com/PeterSuh-Q3/redpill-load/tree/master/config/RS4021xs%2B/7.1.0-42661

 

jun mode is still being stabilized, so please do not use it yet and wait for a separate notice.
 

To use the m shell below, in TCRP Linux
Download and unzip it with the command below.

 

curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" -O; tar -zxvf my.sh.gz;

 

After building the loader in jot mode and completing DSM installation, be sure to process postupdate with the following command.

 

sudo ./my.sh RS4021xs+ postupdate

 

 

449490328_2022-07-2112_10_39.thumb.png.da0eaa85b547fbbc29d4ba9f09f453cf.png

------------------------------------------------------------ --------------------------------------
Usage: ./my.sh <Synology Model Name> <Options>

Options: postupdate, noconfig, noclean, manual, realmac

- postupdate : Option to patch the restore loop after applying DSM 7.1.0-42661 Update 2, no additional build required.

- noconfig: SKIP automatic detection change processing such as SN/Mac/Vid/Pid/SataPortMap of user_config.json file.

- noclean: SKIP the 💊 RedPill LKM/LOAD directory without clearing it with the Clean command.
           However, delete the Cache directory and loader.img.

- manual: Options for manual extension processing and manual dtc processing in build action (skipping extension auto detection).

- realmac : Option to use the NIC's real address instead of creating a virtual one.

 

Please type Synology Model Name after ./my.sh

- for jot mode

./my.sh DS918+
./my.sh DS3617xs
./my.sh DS3615xs
./my.sh DS3622xs+
./my.sh DVA3221
./my.sh DS920+
./my.sh DS1621+
./my.sh DS2422+
./my.sh DVA1622
./my.sh DS1520+ (Not Suppoted)
./my.sh FS2500 (Not Supported)
./my.sh DS1621xs+
./my.sh RS4021xs+

 

- for jun mode

./my.sh DS918+J
./my.sh DS3617xsJ
./my.sh DS3615xsJ
./my.sh DS3622xs+J
./my.sh DVA3221J
./my.sh DS920+J
./my.sh DS1621+J
./my.sh DS2422+J
./my.sh DVA1622J (Not Supported)
./my.sh DS1520+J
./my.sh FS2500J
./my.sh DS1621xs+J
./my.sh RS4021xs+J

 

653481565_2022-07-2112_19_44.thumb.png.a9c1d59cc3dd831eefd5d5ed6609915b.png

Edited by Peter Suh
  • Like 1
  • Thanks 1
Link to comment
Share on other sites

@Peter Suh I am testing with VMWare the new mod RS4021xs+.

 

  • With VMWare I can´t find any Synology DS. I add e1000e driver but not works.
  • On baremetal with Lenovo ThinkCentre Edge I have issue with disks, only I have one hdd, and I need to put SerialPortMap=1 and DiskIdMap=00 and detect hdd, but with serialmap detect SerialPortMap=4 and DiskIdMap=00 with error hdd.
Link to comment
Share on other sites

Posted (edited)
39 minutes ago, apriliars3 said:

@Peter Suh I am testing with VMWare the new mod RS4021xs+.

 

  • With VMWare I can´t find any Synology DS. I add e1000e driver but not works.
  • On baremetal with Lenovo ThinkCentre Edge I have issue with disks, only I have one hdd, and I need to put SerialPortMap=1 and DiskIdMap=00 and detect hdd, but with serialmap detect SerialPortMap=4 and DiskIdMap=00 with error hdd.

 

First, let's check the bare metal problem that the NIC is recognized.
Please log in as Junior and attach the logs below.
For junior log, log in as TTYD as shown below and check the log below.
 
http://<youripaddr>:7681/
id : root / pw : ( no password )

cat /var/log/*rc*
ls -l /sys/block
ls -la /sys/class/ata_device
ls -l /dev/syno*
 
Please use spoilers to attach the contents of this log.

Edited by Peter Suh
Link to comment
Share on other sites

Posted (edited)
5 hours ago, Peter Suh said:

 

First, let's check the bare metal problem that the NIC is recognized.
Please log in as Junior and attach the logs below.
For junior log, log in as TTYD as shown below and check the log below.
 
http://<youripaddr>:7681/
id : root / pw : ( no password )

cat /var/log/*rc*
ls -l /sys/block
ls -la /sys/class/ata_device
ls -l /dev/syno*
 
Please use spoilers to attach the contents of this log.

 

On baremetal, I can migrate to DVA1622 to RS4021xs+ with SataPortMap=1 DiskIdMap=00

 

Captura de pantalla 2022-07-26 213040.png

 

cat /var/log/*rc*

 

SynologyNAS> cat /var/log/*rc*
START /linuxrc.syno.impl
Insert Marvell 1475 SATA controller driver
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "e1000.ko" for PeterSuh-Q3.e1000 (args: )
Loading kmod #0 "e1000e.ko" for PeterSuh-Q3.e1000e (args: )
Loading kmod #0 "mii.ko" for PeterSuh-Q3.r8169 (args: )
Loading kmod #1 "r8169.ko" for PeterSuh-Q3.r8169 (args: )
Loading kmod #0 "libphy.ko" for PeterSuh-Q3.tg3 (args: )
Loading kmod #1 "tg3.ko" for PeterSuh-Q3.tg3 (args: )
Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script
Checking for VirtIO
*No* VirtIO hypervisor detected
NOT loading kmods for thethorgroup.virtio
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-e1000.sh" for PeterSuh-Q3.e1000->on_boot
Loading module e1000 -> Module e1000 loaded succesfully
Ran "check-e1000.sh" for PeterSuh-Q3.e1000->on_boot - exit=0
Running "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot
Loading module e1000e -> Module e1000e loaded succesfully
Ran "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot - exit=0
Running "check-r8169.sh" for PeterSuh-Q3.r8169->on_boot
Loading module r8169 -> Module r8169 loaded succesfully
Ran "check-r8169.sh" for PeterSuh-Q3.r8169->on_boot - exit=0
Running "check-tg3.sh" for PeterSuh-Q3.tg3->on_boot
Loading module tg3 -> Module tg3 loaded succesfully
Ran "check-tg3.sh" for PeterSuh-Q3.tg3->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot
Still waiting for boot device (waited 1 of 30 seconds)
Still waiting for boot device (waited 2 of 30 seconds)
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
All disk ready or timeout execeed
Assemble args: -u 98df8d83:9a6d9e19:05d949f7:b0bbaec7 /dev/sda1
mdadm: /dev/md0 has been started with 1 drive (out of 16).
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0... 
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_rs4021xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_geminilake_dva1622
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_rs4021xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_geminilake_dva1622
Exit on error [7] root not matched with junior...
Tue Jul 26 20:30:13 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0

 

ls -l /sys/block

 

SynologyNAS> ls -l /sys/block
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 loop0 -> ../devices/virtual/block/loop0
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 loop1 -> ../devices/virtual/block/loop1
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 loop2 -> ../devices/virtual/block/loop2
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 loop3 -> ../devices/virtual/block/loop3
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 loop4 -> ../devices/virtual/block/loop4
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 loop5 -> ../devices/virtual/block/loop5
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 loop6 -> ../devices/virtual/block/loop6
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 loop7 -> ../devices/virtual/block/loop7
lrwxrwxrwx    1 root     root             0 Jul 26 20:30 md0 -> ../devices/virtual/block/md0
lrwxrwxrwx    1 root     root             0 Jul 26 20:30 md1 -> ../devices/virtual/block/md1
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 Jul 26 20:30 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx    1 root     root             0 Jul 26 20:30 sdy -> ../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/host2/target2:0:0/2:0:0:0/block/sdy
lrwxrwxrwx    1 root     root             0 Jul 26 20:32 synoboot -> ../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/host1/target1:0:0/1:0:0:0/block/synoboot

 

ls -la /sys/class/ata_device

 

SynologyNAS> ls -la /sys/class/ata_device
drwxr-xr-x    2 root     root             0 Jul 26 20:35 .
drwxr-xr-x   55 root     root             0 Jul 26 20:30 ..
lrwxrwxrwx    1 root     root             0 Jul 26 20:35 dev1.0 -> ../../devices/pci0000:00/0000:00:1f.2/ata1/link1/dev1.0/ata_device/dev1.0

 

ls -l /dev/syno*

 

SynologyNAS> ls -l /dev/syno*
crw-r--r--    1 root     root      201,   0 Jul 26 20:30 /dev/synobios
brw-------    1 root     root      135, 240 Jul 26 20:30 /dev/synoboot
brw-------    1 root     root      135, 241 Jul 26 20:30 /dev/synoboot1
brw-------    1 root     root      135, 242 Jul 26 20:30 /dev/synoboot2
brw-------    1 root     root      135, 243 Jul 26 20:30 /dev/synoboot3

 

On VMWare with rploader by pocopico find ip but not works hdd with SataPortMap=1 DiskIdMap=10 (satamap). Any differents with my.sh?
 

 

 

 

Edited by apriliars3
Link to comment
Share on other sites

2 hours ago, apriliars3 said:

On VMWare, with rploader by pocopico works. I think for default SataPortMap=58 DiskIdMap=0A00. With my.sh or myv.sh with add drivers e1000e, not find ip. Is very strange.

 

 

Captura de pantalla 2022-07-27 000427.png

 

The reason for the difference between pocopico's TC and my.sh was as follows.

 

at some point for some reason
Inside my.sh, the script was blocked as shown below.
# ./rploader.sh satamap

 

Distinguish between DTC-based and non-DTC-based models.
In the case of a non-DTC-based model, I will activate the above script processing.

 

I will notify you of the release after modifying my.sh.
Thanks for reporting the error.

Link to comment
Share on other sites

1 hour ago, Peter Suh said:

 

The reason for the difference between pocopico's TC and my.sh was as follows.

 

at some point for some reason
Inside my.sh, the script was blocked as shown below.
# ./rploader.sh satamap

 

Distinguish between DTC-based and non-DTC-based models.
In the case of a non-DTC-based model, I will activate the above script processing.

 

I will notify you of the release after modifying my.sh.
Thanks for reporting the error.

 

 

./rploader.sh satamap now works.
my.sh has been modified and released.
Please check if the automatic update is performed only by executing ./my.sh.

 

Also, it is necessary to clarify which virtual NIC device is used in the VM.
Take a screenshot of your VMWARE configuration screen and show it to us.
I want to know which virtual NIC is set up.
TC automatically detects the virtual NIC you have configured.

 

Until recently, there was a problem that TC falsely detected e1000 as e1000e.
This part has been fixed by pocopico and I.

Link to comment
Share on other sites

 
The reason for the difference between pocopico's TC and my.sh was as follows.
 
at some point for some reason
Inside my.sh, the script was blocked as shown below.
# ./rploader.sh satamap
 
Distinguish between DTC-based and non-DTC-based models.
In the case of a non-DTC-based model, I will activate the above script processing.
 
I will notify you of the release after modifying my.sh.
Thanks for reporting the error.
 

I wil Test it later after come back my job, but I add drivers manually with my.sh or add drivers with myv.sh. the modules load satisfully on rd.gz but not find ip.
 
I've been testing all weekend and a few days, and yesterday it seems that it worked with pocopico rploader, but the normal issue was that it won't detect hard drives with low peak either. It's lucky sometimes all this.
Link to comment
Share on other sites

 
 
./rploader.sh satamap now works.
my.sh has been modified and released.
Please check if the automatic update is performed only by executing ./my.sh.
 
Also, it is necessary to clarify which virtual NIC device is used in the VM.
Take a screenshot of your VMWARE configuration screen and show it to us.
I want to know which virtual NIC is set up.
TC automatically detects the virtual NIC you have configured.
 
Until recently, there was a problem that TC falsely detected e1000 as e1000e.
This part has been fixed by pocopico and I.


It is very complicate for me to understand that works satamap, but for me in this model not works.

On baremetal, satamap detect SataPortMap=4 DiskIdMap=00 but need to put SataPortMap=1 DiskIdMap=00 for not error disks

On VMWare or virtual, satamap detect SataPortMap=1 DiskIdMap=10 but need to put SataPortMap=58 DiskIdMap=0A00 for detect disks, but first disk is 12 disk of 16.

Not works allways the same SataPortMap and DiskIdMap with all models, each one is different, I understand because not all there are 16 disks or less, but automatically satamap not works well, I try to explain pocopico because not only I have issues with this.
Link to comment
Share on other sites

1 hour ago, apriliars3 said:

 


It is very complicate for me to understand that works satamap, but for me in this model not works.

On baremetal, satamap detect SataPortMap=4 DiskIdMap=00 but need to put SataPortMap=1 DiskIdMap=00 for not error disks

On VMWare or virtual, satamap detect SataPortMap=1 DiskIdMap=10 but need to put SataPortMap=58 DiskIdMap=0A00 for detect disks, but first disk is 12 disk of 16.

Not works allways the same SataPortMap and DiskIdMap with all models, each one is different, I understand because not all there are 16 disks or less, but automatically satamap not works well, I try to explain pocopico because not only I have issues with this.

 

 

You seem to be quite confused about the mapping of SataPortMap / DiskIdMap values.
The DTC base model doesn't care about either number anymore. (Ignored)
There are two types of DTC base model: GeminiLake and v1000 platform.

 

Sometimes, the SataPortMap value presented by the TC in SataMap Action may not be reliable.
Most of the time it should be adjusted by the number of disks actually mounted to ensure no problems.

 

In my experience, in VMs because of the SataDom disk used for the bootloader.
You need to increase the SataPortMap value by one more.
So SataPortMap=1 DiskIdMap=10 suggested by TC is also not correct.

 

SataPortMap=58 DiskIdMap=0A00 The value is not the intended setting value, but the value initialized by TC in Fullupgrade.
This number is meaningless.
Rather SataPortMap= DiskIdMap=
This seems to have the same effect as not recording the value.

Link to comment
Share on other sites

Posted (edited)
2 hours ago, Peter Suh said:

 

You seem to be quite confused about the mapping of SataPortMap / DiskIdMap values.
The DTC base model doesn't care about either number anymore. (Ignored)
There are two types of DTC base model: GeminiLake and v1000 platform.

 

Sometimes, the SataPortMap value presented by the TC in SataMap Action may not be reliable.
Most of the time it should be adjusted by the number of disks actually mounted to ensure no problems.

 

In my experience, in VMs because of the SataDom disk used for the bootloader.
You need to increase the SataPortMap value by one more.
So SataPortMap=1 DiskIdMap=10 suggested by TC is also not correct.

 

SataPortMap=58 DiskIdMap=0A00 The value is not the intended setting value, but the value initialized by TC in Fullupgrade.
This number is meaningless.
Rather SataPortMap= DiskIdMap=
This seems to have the same effect as not recording the value.

 

On VM, I have 3 forms to virtualice each model. I have test it with all models several times on vm or baremetal.

  • Tinycore SATA 0:0 HDD SATA 0:1. This configuration works with DS4021xs+ build with rploader by pocopico. Later, I need other time test it with your rploader and script my.sh
  • loader.vmdk SATA 0:0 HDD SATA 0:1. Is the same, but tynicore.vmdk is replaced with loader.vmdk build with tinycore (rploader pocopico or script my.sh JUN or not)
  • ARPL.vmdk SATA 0:0 HDD SATA 0:1. New menu.sh for build bootloader, but is not possible to create a .img, that on VM this is the form that I can test.

In all cases, I use NIC e1000e (change on vmx). Sometimes I test it with e1000 and vmxnet3 but I think is more reliable with e1000e. I have NUC J3455 and Ryzen 3900X for test it with VM. I have two pc with Windows and can´t format hdd to test it on baremetal.

 

One I have tested in virtual that everthing is correct, I proceed to test it on baremetal with my HP Microserver Gen8 and Lenovo ThinkCentre Edge 71 i3 2120.

 

I have test with all models available, for me all works except DS1520+ and FS2500 that I can´t boot. Usually the issue is not find NAS ip or not detect any hdd, but I know that models is development yet, althought I can build a loader.img. All the times is the same configuration, only change .vmdk or burn new pendrive with new loader.

 

 

Captura de pantalla 2022-07-27 110137.png

Captura de pantalla 2022-07-27 110444.png

Captura de pantalla 2022-07-27 110748.png

Edited by apriliars3
Link to comment
Share on other sites

Posted (edited)
4 hours ago, apriliars3 said:

 

On VM, I have 3 forms to virtualice each model. I have test it with all models several times on vm or baremetal.

  • Tinycore SATA 0:0 HDD SATA 0:1. This configuration works with DS4021xs+ build with rploader by pocopico. Later, I need other time test it with your rploader and script my.sh
  • loader.vmdk SATA 0:0 HDD SATA 0:1. Is the same, but tynicore.vmdk is replaced with loader.vmdk build with tinycore (rploader pocopico or script my.sh JUN or not)
  • ARPL.vmdk SATA 0:0 HDD SATA 0:1. New menu.sh for build bootloader, but is not possible to create a .img, that on VM this is the form that I can test.

In all cases, I use NIC e1000e (change on vmx). Sometimes I test it with e1000 and vmxnet3 but I think is more reliable with e1000e. I have NUC J3455 and Ryzen 3900X for test it with VM. I have two pc with Windows and can´t format hdd to test it on baremetal.

 

One I have tested in virtual that everthing is correct, I proceed to test it on baremetal with my HP Microserver Gen8 and Lenovo ThinkCentre Edge 71 i3 2120.

 

I have test with all models available, for me all works except DS1520+ and FS2500 that I can´t boot. Usually the issue is not find NAS ip or not detect any hdd, but I know that models is development yet, althought I can build a loader.img. All the times is the same configuration, only change .vmdk or burn new pendrive with new loader.

 

 

Captura de pantalla 2022-07-27 110137.png

Captura de pantalla 2022-07-27 110444.png

Captura de pantalla 2022-07-27 110748.png

 

 

I don't know the point of what you want to talk about.
There is nothing wrong with bare metal,
Is VMWARE the problem?

 

Models based on the GeminiLake and V1000 platforms such as DS1520+, FS2500, DS920+, and DS1621+ are also based on DTC, and at least Haswell or higher is guaranteed to work in the system.
ApolloLake is the same.


If you want to test all models in VMWARE, it would be better to use NUC J3455.

And, as explained in the post below, all models have not yet been tested, so there are parts that are not stable. The FS2500 is not yet available.

 

https://xpenology.com/forum/topic/63946-dva3219-loader-development-thread/

Edited by Peter Suh
Link to comment
Share on other sites

Posted (edited)

@Peter Suh Two things I want to tell:

 

  • First, I test it with your myv.sh or my.sh but not works RS4021xs+. Don´t get me ip and I can´t find the NAS. ./myv.sh RS4021xs+
  • Second, I test it the similar model with rploader by pocopico and works.  ./rploader.sh build rs4021xsp-7.1.0-42661

 

I have added serial port output that give me the two options. If you can revise, all is in VMWARE. Two options have extension e1000e.

 

Serial port rploader pocopico is RS4021xs+ is installed and works well.

Serial port my.sh is RS4021xs+ but not detect ip and can´t install.

 

All is similar, rploader pocopico is get from repository beta and my.sh is all repository your with new updates.

 

I don´t know what do you need for helping, but for me with your script don´t works. I follow to try if I do with the issue or I am able to make it work.

serial port rploader pocopico.txt serial port my.sh.txt

Edited by apriliars3
Link to comment
Share on other sites

Posted (edited)
27 minutes ago, apriliars3 said:

@Peter Suh Two things I want to tell:

 

  • First, I test it with your myv.sh or my.sh but not works RS4021xs+. Don´t get me ip and I can´t find the NAS.
  • Second, I test it the similar model with rploader by pocopico and works. 

 

I have added serial port output that give me the two options. If you can revise, all is in VMWARE.

 

Serial port rploader pocopico is RS4021xs+ is installed and works well.

Serial port my.sh is RS4021xs+ but not detect ip and can´t install.

 

All is similar, rploader pocopico is get from repository beta and my.sh is all repository your with new updates.

 

I don´t know what do you need for helping, but for me with your script don´t works. I follow to try if I do with the issue or I am able to make it work.

serial port rploader pocopico.txt 321.27 kB · 0 downloads serial port my.sh.txt 141.4 kB · 0 downloads

 

I compared the two logs with the compare tool.
Although the two mac addresses are different,
I will assume that you have changed and set the virtual NIC of VMWARE.


If so, the difference is that vmxnet3 is not visible when only rploader is used.
Did you select it separately and add it to myv.sh ?
When my.sh is used, it seems that vmxnet3 is added, causing an error.
There have been reports of cases in which the junior log appears to be a success, but in reality it does not work.
See if there is an effective way to remove vmxnet3.

Edited by Peter Suh
Link to comment
Share on other sites

Posted (edited)
42 minutes ago, Peter Suh said:

 

I compared the two logs with the compare tool.
Although the two mac addresses are different,
I will assume that you have changed and set the virtual NIC of VMWARE.


If so, the difference is that vmxnet3 is not visible when only rploader is used.
Did you select it separately and add it to myv.sh ?
When my.sh is used, it seems that vmxnet3 is added, causing an error.
There have been reports of cases in which the junior log appears to be a success, but in reality it does not work.
See if there is an effective way to remove vmxnet3.

 

Usually, I add several drivers for after use on baremetal. 

 

I am testing only add e1000e with my.sh and add before drivers with ./rploader.sh but not works.

 

There are something that kill VM, sometimes give me this error when boot with your loader.

 

The 2 VM are different mac and s/n, because two VM are on at same time for compare what is the problem.

 

I can try one thing, built 2 loader.img (one rploader and other with script). Boot and install with one that it was possible and test it with the other.

Captura de pantalla 2022-07-27 164358.png

 

 

Is this the issue?

 

Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot
Still waiting for boot device (waited 1 of 30 seconds)

 

 

With loader by pocopico have ip after this

 

Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory

Edited by apriliars3
Link to comment
Share on other sites

2 hours ago, apriliars3 said:

 

Usually, I add several drivers for after use on baremetal. 

 

I am testing only add e1000e with my.sh and add before drivers with ./rploader.sh but not works.

 

There are something that kill VM, sometimes give me this error when boot with your loader.

 

The 2 VM are different mac and s/n, because two VM are on at same time for compare what is the problem.

 

I can try one thing, built 2 loader.img (one rploader and other with script). Boot and install with one that it was possible and test it with the other.

Captura de pantalla 2022-07-27 164358.png

 

 

Is this the issue?

 

Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot
Still waiting for boot device (waited 1 of 30 seconds)

 

 

With loader by pocopico have ip after this

 

Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory

 

It is said that only one e1000e is used, but vmxnet3 is not automatically added through rploader.sh
I don't understand that it was automatically added only in my.sh.
In vmware, it is known that vmxnet3 is added separately and used.

 

I also tried to build by adding vmxnet3 in proxmox,
An error appeared. boot-wait waited more than 30 seconds and no IP was assigned.
And finally, a kernel error occurred and the loader stopped.
I have the same symptoms as you.

 

Anyway, please do not use RS4021xs+ and vmxnet3 together.
I'm also thinking of removing it from rp-ext.
And jumkey said that you don't have to worry too much about the message below.
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory

  • Thanks 1
Link to comment
Share on other sites

8 hours ago, rojoone2 said:

@Peter Suh  Is the power supply warning something we have to live with or would there be a fix for it?

I see there is not much interest in this platform, but this is something I personally have been looking forward to.

Let me know if there is anyway I can help you test on a baremetal install.

 

 

I thought that the alarm that appeared because only one of the dual power of RS4021xs+ could be controlled with the Synology warning setting, but I didn't have time to look into it in detail.
I need to focus more on the stabilization test of the 28 models of the M shell now, so I'll look into it later when I have time.

Link to comment
Share on other sites

21 minutes ago, Rebutia said:

Nice work Peter. By the way, do you know the SATA controller being used in original RS4021x hardware? I am wondering if it RS4021x DSM has native support of LSI 2008 IT mode? or shall we load the driver for it?

 

Every time I add a new model, the first thing I do is prepare all the exts for the new model in my rp-ext repo, which I inherited from pocopico.
Of course, mpt3sas also supports RS4021xs+.

https://github.com/PeterSuh-Q3/rp-ext/blob/main/mpt3sas/rpext-index.json

  • Like 1
Link to comment
Share on other sites

5 hours ago, Peter Suh said:

 

Every time I add a new model, the first thing I do is prepare all the exts for the new model in my rp-ext repo, which I inherited from pocopico.
Of course, mpt3sas also supports RS4021xs+.

https://github.com/PeterSuh-Q3/rp-ext/blob/main/mpt3sas/rpext-index.json

Thank you Peter, sorry my original question misled you. I meant what is the original SATA hardware of RS4021xs+? does it contain LSI 2008 itself? just curious what kind of hardware the RS4021xs+ using.

Link to comment
Share on other sites

Thank you Peter, sorry my original question misled you. I meant what is the original SATA hardware of RS4021xs+? does it contain LSI 2008 itself? just curious what kind of hardware the RS4021xs+ using.

https://www.synology.com/en-us/compatibility?search_by=products&model=RS4021xs%2B&category=fc_host_bus_adapters&p=1&change_log_p=1

For external controllers, the above Marvell chipset controller is supported, and even if it is a built-in SATA, it all depends on the ahci ext built into redpill.


Sent from my iPhone using Tapatalk
  • Like 1
Link to comment
Share on other sites

3 hours ago, Rebutia said:

As an enterprise product, do you find RS4021xs+ strictly implement HDD compatibility check? That is, not listed in their compatibility list means it cannot be used?

 

https://www.synology.com/en-us/compatibility?search_by=products&model=RS4021xs%2B&category=hdds_no_ssd_trim&p=1&change_log_p=1

I would be surprised if its not strictly enforced on that model considering its target audience. There are ways around the compatibility list, but it will revert back after certain upgrades I've been told. Its just modifying the list that contains the compatible drives, you just add your drive to the list. Google it, its posted in several places as people use that trick on real hardware too.

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...