TinyCore RedPill Loader Build Support Tool ( M-Shell )

[Peter Suh]

11 minutes ago, dmankl said:

As requested 

 

Among the 4 windows shown just before, select “edit user config file manually” from the menu of the first window, add “SasIdxMap”: “0”, and rebuild the loader. Accurately edited state is also displayed in the third window. Please show me a screenshot of this edited screen and tell me the number of disks in DSM or the mapping scheme.

[dmankl]

1 hour ago, Peter Suh said:

 

On Tinycore linux I checked the existence of 8 disks fine from sdb to sdi except for sda. Finally, I want to confirm more. In FRIEND, initialize with Ctrl+C within 7 seconds and let me know the result of the command below once more.

 

ll /sys/block | grep sd

Also should DSM be able to see the smart data of the drives? 
The smart data is all identical is why I ask

[dmankl]

2 hours ago, Peter Suh said:

 

Among the 4 windows shown just before, select “edit user config file manually” from the menu of the first window, add “SasIdxMap”: “0”, and rebuild the loader. Accurately edited state is also displayed in the third window. Please show me a screenshot of this edited screen and tell me the number of disks in DSM or the mapping scheme.

 

 

 

 I tested with a "" and "0" because the other maps had "" and they both had the same outcome. Same disks are showing up and numbered "incase its relevant" the same way.

 

 

Edited July 23, 2023 by dmankl
Clarity and troubleshooting steps

[dimakv2014]

2 hours ago, Peter Suh said:

 

I'm not sure since you didn't mention which Synology modal you're using, but I'd expect it to be different for each model. My case is with the recently added model DS1823xs+. I don't think such a difference occurs because the environment file is configured separately for each model. Tell us your model and we will retest you too.

I did mention in first message #540 that im using dva1622. However, just installed dva3221 and everything works on 7.2

Edited July 23, 2023 by dimakv2014

[Peter Suh]

5 hours ago, dmankl said:

 

 

 

 I tested with a "" and "0" because the other maps had "" and they both had the same outcome. Same disks are showing up and numbered "incase its relevant" the same way.

 

 

 

In HBA, SataPortmap and DiskIdxMap are not used. That's why I used blanks. SasIdxMap specifies that the HBA uses the disks from mapping number 1, but I don't know if Esxi doesn't affect it. I will test whether the AMD CPU is a variable or has other influences under the same conditions. In the past, there was a similar inquiry in Bare Metal, but there was an issue in which only 6 out of 8 disks were recognized. I'm also going to take an exam after work, so it will take time. After 12 hours?

[Peter Suh]

9 hours ago, dmankl said:

 

 

 

 I tested with a "" and "0" because the other maps had "" and they both had the same outcome. Same disks are showing up and numbered "incase its relevant" the same way.

 

 

 

There is one thing I'm missing.

There was a result of a Korean user connecting many disks to the HBA and testing the M-SHELL.
At the time, the test reported that EUDEV did not favor the HBA's disk recognition.
You seem to be holding on to EUDEV.

Would you like to switch to DDSML Only?

 

[dmankl]

6 minutes ago, Peter Suh said:

 

There is one thing I'm missing.

There was a result of a Korean user connecting many disks to the HBA and testing the M-SHELL.
At the time, the test reported that EUDEV did not favor the HBA's disk recognition.
You seem to be holding on to EUDEV.

Would you like to switch to DDSML Only?

 

No new drives visible, Think this has all the settings that were changed..

 

[Peter Suh]

10 minutes ago, dmankl said:

No new drives visible, Think this has all the settings that were changed..

 

 

 

This Korean user shares the results of testing the HBA.

Two HBA controllers were used.
SasIdxMap=0 is the default applied state.

 

Case 1 ~ Case 7 Summary

C1) TCRP DDSML , DS3622xs+, max=32 : Disk recognition 16+2/18 , DISK format failure during DSM installation

C2) TCRP DDSML , DS3622xs+ , max=24 : disk recognition 16+2/18 , DSM installation complete, normal operation

C3) TCRP DDSML , RS4021xs+, max=32 : Disk recognized 0+2/18 -- HBA DISK not recognized

C4) TCRP DDSML , RS4021xs+, max=24 : Disk recognized 0+2/18 -- HBA DISK not recognized

C5) TCRP DDSML , RS4021xs+, max=24 : DS3622xs+ final successful extra_cmdline setting, disk recognition 0+2/18 (HBA DISK not recognized)

C6) TCRP EUDEV, RS4021xs+, max=24 : Disk recognized 16+2/18 , unable to initialize

C7) TCRP EUDEV, DS3617+, max=24 : Disk recognition 16+2/18 , DISK format failure during DSM installation

 

Cn) ......... Testing models other than DS3622xs+ ... will stop.

 

Even though DS3622xs+ and RS4021xs+ are on the same Broadwell nk platform, they showed different aspects within them.

 

 

Edited July 24, 2023 by Peter Suh

[Peter Suh]

9 hours ago, dimakv2014 said:

I did mention in first message #540 that im using dva1622. However, just installed dva3221 and everything works on 7.2

 

I also installed DVA1622 7.2-64570 U1 and tried again.
On my DVA1622 "Edit" responds.
I tested with two web browsers: CHROME for macos / SAFARI.

 

[dmankl]

33 minutes ago, Peter Suh said:

 

 

This Korean user shares the results of testing the HBA.

Two HBA controllers were used.
SasIdxMap=0 is the default applied state.

 

Case 1 ~ Case 7 Summary

C1) TCRP DDSML , DS3622xs+, max=32 : Disk recognition 16+2/18 , DISK format failure during DSM installation

C2) TCRP DDSML , DS3622xs+ , max=24 : disk recognition 16+2/18 , DSM installation complete, normal operation

C3) TCRP DDSML , RS4021xs+, max=32 : Disk recognized 0+2/18 -- HBA DISK not recognized

C4) TCRP DDSML , RS4021xs+, max=24 : Disk recognized 0+2/18 -- HBA DISK not recognized

C5) TCRP DDSML , RS4021xs+, max=24 : DS3622xs+ final successful extra_cmdline setting, disk recognition 0+2/18 (HBA DISK not recognized)

C6) TCRP EUDEV, RS4021xs+, max=24 : Disk recognized 16+2/18 , unable to initialize

C7) TCRP EUDEV, DS3617+, max=24 : Disk recognition 16+2/18 , DISK format failure during DSM installation

 

Cn) ......... Testing models other than DS3622xs+ ... will stop.

 

Even though DS3622xs+ and RS4021xs+ are on the same Broadwell nk platform, they showed different aspects within them.

 

 

Same as before

Edited July 24, 2023 by dmankl

[Peter Suh]

Same as before

I guess I'll have to do a test for you. As I mentioned before, I will do it after work. 5 hours left.


Sent from my iPhone using Tapatalk

[Peter Suh]

Same as before

I guess I'll have to do a test for you. As I mentioned before, I will do it after work. 5 hours left.


Sent from my iPhone using Tapatalk

[dmankl]

10 minutes ago, Peter Suh said:

 

I guess I'll have to do a test for you. As I mentioned before, I will do it after work. 5 hours left.


Sent from my iPhone using Tapatalk

 

No problem, Thank you for your amazing tool!

[Peter Suh]

12 hours ago, dimakv2014 said:

I did mention in first message #540 that im using dva1622. However, just installed dva3221 and everything works on 7.2

 

Just added the missing setting withefi for DVA1622 7.2-64570 only.

https://github.com/PeterSuh-Q3/redpill-load/commit/bf2900e9008ce67680d4008e2b53bb438961919a

I don't know if there is a direct connection to the phenomenon you reported.

[Peter Suh]

7 hours ago, dmankl said:

No problem, Thank you for your amazing tool!

 

SasIdxMap=0

TCRP DDSML , DS3622xs+ , max=24 : disk recognition 16+2/18 , DSM installation complete, normal operation

 

At the request of a Korean user a while ago, bare metal HBA completed 8 disk recognition tests.
I followed the same settings as mentioned above.
Maxdisks fixed it from 16 to 24 exactly.

 

The result is success.

8 disks filled all 8, starting with slot two.

 

My Esxi settings are not working well, so it will take some time now.
Would you please test this Maxdisks only once again after modifying and rebuilding through the edit window where you put SasIdxMap on the loader build menu?

[dmankl]

1 hour ago, Peter Suh said:

 

SasIdxMap=0

TCRP DDSML , DS3622xs+ , max=24 : disk recognition 16+2/18 , DSM installation complete, normal operation

 

At the request of a Korean user a while ago, bare metal HBA completed 8 disk recognition tests.
I followed the same settings as mentioned above.
Maxdisks fixed it from 16 to 24 exactly.

 

The result is success.

8 disks filled all 8, starting with slot two.

 

My Esxi settings are not working well, so it will take some time now.
Would you please test this Maxdisks only once again after modifying and rebuilding through the edit window where you put SasIdxMap on the loader build menu?

I looked for references for the maxdisks in the settings but i couldnt find it and I know they can be particular.

Do I put one of the following or something else?
"max": "24"

"MaxDisks": "24"

 

I will be heading to work so I will test with your guidance when I come home

 

Edited July 24, 2023 by dmankl

[Peter Suh]

4 minutes ago, dmankl said:

I looked for references for the maxdisks in the settings but i couldnt find it and I know they can be particular.

Do I put one of the following or something else?
"max": "24"

"MaxDisks": "24"

 

 

Sorry, You only need to modify "MaxDisks" : "24".
However, I also ran into the problem of only seeing 6 disks.
Try to remove all unnecessary disk controllers to ESXI and map only SATA controllers.
But the controllers of the additional hardware in this miscellaneous item are not deleted so I am looking for a way.

 

 

[dmankl]

21 minutes ago, Peter Suh said:

 

Sorry, You only need to modify "MaxDisks" : "24".
However, I also ran into the problem of only seeing 6 disks.
Try to remove all unnecessary disk controllers to ESXI and map only SATA controllers.
But the controllers of the additional hardware in this miscellaneous item are not deleted so I am looking for a way.

 

 

I only have one sata controller and that is connected to the mshell vmdk, Would satamap possibly be able to help in this case because of the sata controller I do have?

[Peter Suh]

7 minutes ago, dmankl said:

I only have one sata controller and that is connected to the mshell vmdk, Would satamap possibly be able to help in this case because of the sata controller I do have?

 

 

 

 

I'm going to follow these instructions from flyride.

SataPortMap=12 DiskIdxMap=1000
It is difficult to apply the above settings in a general way.

I'll let you know if I'm successful after I finish the exam.

[Peter Suh]

21 minutes ago, dmankl said:

I only have one sata controller and that is connected to the mshell vmdk, Would satamap possibly be able to help in this case because of the sata controller I do have?

 

 

Flyride's instructions should work.
All 8 disks of the pass-through HBA were recognized!!

I got the result like below.

 

 

 

 

 

 

and,
DiskIdxMap=1000 SataPortMap=12
For setting, you need to use the following method.
Editing user_config.json on the loader build is pointless.
Initialize this value of M SHELL.

 

How to fix sata cmdline.

 

 

 

[dmankl]

39 minutes ago, Peter Suh said:

 

 

Flyride's instructions should work.
All 8 disks of the pass-through HBA were recognized!!

I got the result like below.

 

 

 

 

 

 

and,
DiskIdxMap=1000 SataPortMap=12
For setting, you need to use the following method.
Editing user_config.json on the loader build is pointless.
Initialize this value of M SHELL.

 

How to fix sata cmdline.

 

 

 

You are a Gentleman and a Scholar!, by any chance do you have a donation system set up?

I was able to get it working with your instructions! and the drives are reporting the correct info(temps, sn, and such)

[dimakv2014]

18 hours ago, Peter Suh said:

 

I also installed DVA1622 7.2-64570 U1 and tried again.
On my DVA1622 "Edit" responds.
I tested with two web browsers: CHROME for macos / SAFARI.

 

Very strange, tested on 2 different VMs on 4 different browsers including mobile chrome and opera, even restart didn't help, links didn't open. Maybe temporary bug, well thanks for testing anyway. I already found other solution, used trcp 0.9.2.9 with your ./my.sh which has latest update from repository, no automated menu but works like a charm

[Optiplex_Fan]

I'm using this loader, mostly because it has the CPU is speed throttled, I want my PC to be the most power efficient 

Though, even though I use my old DS1515+ serial number and 4 MACs (and netif_num=4 since this NAS has 4 ethernet), I can login to my Synology Account, but cannot activate DDNS or QuickConnect or get the codecs:

• QuickCOnnect, I get a message asking me to re-try in 5 minutes because of server overload
• DDNS, I get a generic error telling me it fails to register my IP to the Synology DNS.
• Codec pack doesn't work without patching, "contact support" ...

What could I look for to get this to work ? maybe remove some files for the configuration to be rewritten ?

Not a major big deal, but it would be nice to have it work... thanks

[Peter Suh]

 

[notification]

 

DT based DS920+ (Gemini Lake), DS1621+ (v1000), ds923+ (r1000)
Please refrain from updating to 7.2-64570 U2 for your platform.

 

An issue has been identified where M.2 NVMe caches are not recognized as DT devices.
If you are not using M.2 NVMe cache, this issue is irrelevant.
As soon as the cause is confirmed, related fixes will be distributed and announced.

 

[maqros]

В 25.07.2023 в 08:50, Peter Suh сказал:

 

[notification]

 

DT based DS920+ (Gemini Lake), DS1621+ (v1000), ds923+ (r1000)
Please refrain from updating to 7.2-64570 U2 for your platform.

 

An issue has been identified where M.2 NVMe caches are not recognized as DT devices.
If you are not using M.2 NVMe cache, this issue is irrelevant.
As soon as the cause is confirmed, related fixes will be distributed and announced.

 

Hi guys. Is there any way to roll back or recover, if I trapped into this)? I've got DS920+ with M.2 NVMe cache