TinyCore RedPill Loader Build Support Tool ( M-Shell )

[Peter Suh]

2 hours ago, shibby said:

I came to terms with the thought that I have to install Synology again. Now the questions are:

- use M-shell, RR or Arc as loader? I propably leave iGPU for now to SA6400 is not a priority. Must be 100% stable

- 7.2.1 or 7.2.2?

 

 

 

Today, I also applied DSM 7.2.2 to my main Xpenology, not the test system.
Since I am using SataDOM, it works with SATA-type bootloader.
However, I confirmed that KP continues as you experienced.
Most platforms except SA6400 are KP.
USB-type bootloader works stably without KP.

SATA-type was originally an experimental bootloader, and it started with a warning when Redpill was first born, but it has been stabilized a lot now.
However, it seems that KP continues again in special cases in 7.2.2.
I think I need to build various VMs or SATA-type bootloaders to collect more diverse data and stabilize it.
There is also a way to make USB-type bootloader instead of SATA in Proxmox.
Please switch to this and use it for the time being.

 

1) Xpenology RedPill DS918+ FRIEND DSM 7.2.2-72803 Update 0, ASUS IOT H310i-IM-A R2.0 G5500 / Intel I211, I219-V / 16GB  /  ASM1166 M.2 NVME PCIE 6 Port Sata / 3x4TB + 1x3TB SHR, 1x8TB / Jonsbo N1 For NAS

 

[Peter Suh]

18 minutes ago, gericb said:

Hey there @Peter Suh when you are saying "At the stage where DSM can be installed, you can access TTYD 7681 port instead of 5000 port through a web browser." are you referring to this boot-up screen?  I have tried a few times via my browser to go to this address (as seeing the image), while I see this screen, but there is never a response.  Is this accessibility persistent, or only for a short duration?

 

Since you guys are leveraging off one another, do you think it would be possible for you to add this additional functionality shown on option Z, "Force Enable Telnet & SSH"?

 

Thank You

 

 

 

Something seems wrong.
This accessibility is permanent unless you proceed with DSM installation or intentionally reboot / poweroff.

RR's TTYD is a bit different.
I'm telling you based on TCRP.

 

If you are sure that the NIC is responding to the corresponding IP with a ping,
and the page http://192.168.1.129:5000 is loaded,
then the page http://192.168.1.129:7681 should also appear.

As below...

 

 

 

[Peter Suh]

3 hours ago, shibby said:

I came to terms with the thought that I have to install Synology again. Now the questions are:

- use M-shell, RR or Arc as loader? I propably leave iGPU for now to SA6400 is not a priority. Must be 100% stable

- 7.2.1 or 7.2.2?

 

 

 

I think I made one mistake building lkm 24.8.29.
The lkm 24.6.4 was a trial pre-release form of the sata bootloader, and I don't know if rr applied it, but mshell has been holding off on applying it right away, more conservatively. However, reflecting this 24.8.29, it was unintentionally included. Not all mobos seem to have kp on the sata loader, and it seems that you and my case are the only ones with no luck. I will build 24.9.4 lkm tomorrow and distribute it to a version that excludes the lkm 24.6.4 content.

[gericb]

3 hours ago, Peter Suh said:

 

Something seems wrong.
This accessibility is permanent unless you proceed with DSM installation or intentionally reboot / poweroff.

RR's TTYD is a bit different.
I'm telling you based on TCRP.

 

If you are sure that the NIC is responding to the corresponding IP with a ping,
and the page http://192.168.1.129:5000 is loaded,
then the page http://192.168.1.129:7681 should also appear.

As below...

 

 

 

I have a 2 port ethernet card, and you can see in the attached image from earlier, (bonded together in DSM) that eth0 gets IP 192.168.1.245

                                                                                                                                                                                              eth1  gets IP 192.168.1.129

 

So I was blindly following "To check the problem..." which directed me to (eth1) 192.168.1.129 location, which did nothing and failed.  So I tried eth0:7681 and I do get a gray screen with a white block cursor in the upper left corner, and in the middle of the screen is flashing alternatively 186x43, Connection Closed.  Would I be better served using something other than a Web Browser?

 

At least that's progress! 

Edited September 3 by gericb
Added additional info

[djvas335]

@gericb TTYD and port 7681 is only active while the DSM is loaded in install mode and waiting for your input.

 

7 hours ago, gericb said:

I have a 2 port ethernet card, and you can see in the attached image from earlier, (bonded together in DSM) that eth0 gets IP 192.168.1.245

                                                                                                                                                                                              eth1  gets IP 192.168.1.129

 

So I was blindly following "To check the problem..." which directed me to (eth1) 192.168.1.129 location, which did nothing and failed.  So I tried eth0:7681 and I do get a gray screen with a white block cursor in the upper left corner, and in the middle of the screen is flashing alternatively 186x43, Connection Closed.  Would I be better served using something other than a Web Browser?

 

At least that's progress! 

 

[Peter Suh]

14 hours ago, shibby said:

 

Well... i messed up and now i have a huge problem. Yesterday i moved to Arc Next loader and migrated DS423+ (7.2.1) to SA6400 7.2.2 (sata mode). All worked fine and i was happy to be prepare to change hardware to 13gen. Morning my NAS was dead - i had kernel panic and one drive got "critical" state - it was fine in proxmox. My biggest mistake was try back to DS423+... After migration i cannot run few services: san manager, container manager and file manager wont repair. I tried move to other models like ds923+, dva3221, even once again sa6400. Every time is the same problem with those packages.

 

But there is more: i cannot back to M-Shell loader. Every time i`ve got lernel panic. I tried lots of model and always is the same. Here for example DS423+

 

 

 

On RR and Arc i can run Xpenology but with packages issue.

 

Is there any possibility back to 7.2.1??
😕

 

 

 

I have configured Proxmox with the most similar environment to you for the lkm rebuild that I promised you.
I use Proxmox 8.2.4.

 

In the first capture, I applied the same machine type q35 as you.
As expected, I also got KP.

 

 

In the second capture, I used the default i440FX of Proxmox instead of the machine type q35.
In the case of i440FX, it does not fall into KP.

 

 

However, since I have not had KP in any situation regardless of q35/i440FX, I will proceed with the lkm modification that I promised.

Edited September 4 by Peter Suh

[Peter Suh]

13 hours ago, shibby said:

I came to terms with the thought that I have to install Synology again. Now the questions are:

- use M-shell, RR or Arc as loader? I propably leave iGPU for now to SA6400 is not a priority. Must be 100% stable

- 7.2.1 or 7.2.2?

 

 

 

I tried several lkm versions in q35 environment.
Only lkm 24.4.11 + DSM 7.2.1 boots q35 without any problem.
The BIOS processing part of lkm 24.8.29 needs to be reviewed with @wjz304.

 

 

 

 

 

 

 

[shibby]

 

14 hours ago, Peter Suh said:

There is also a way to make USB-type bootloader instead of SATA in Proxmox.

 

Can you tell more about it? How attach img file as usb to VM under proxmox? Or maybe just burn img to flashdrive, plug do USB port and passtrough to VM?

 

I`m already on 13400T... if i will try SA6400 7.2.1, so how should i configure VM and bootloader? Or just give up and run DS423+/DS920+ as previously...

 

I always used vmdk as sata0 and i don`t know any other way to run bootloader on VM.

Edited September 4 by shibby

[Peter Suh]

1 hour ago, shibby said:

 

 

Can you tell more about it? How attach img file as usb to VM under proxmox? Or maybe just burn img to flashdrive, plug do USB port and passtrough to VM?

 

I`m already on 13400T... if i will try SA6400 7.2.1, so how should i configure VM and bootloader? Or just give up and run DS423+/DS920+ as previously...

 

I always used vmdk as sata0 and i don`t know any other way to run bootloader on VM.

 

If so, I'd recommend taking a simpler approach.
Change the machine type to i440FX instead of q35.
You can modify it like this in the hardware section.

 

 

Edited September 4 by Peter Suh

[Orphée]

3 hours ago, shibby said:

Can you tell more about it? How attach img file as usb to VM under proxmox? Or maybe just burn img to flashdrive, plug do USB port and passtrough to VM?

 

To be put inside your /etc/pve/qemu-server/<vm id>.conf

 

args: -device 'nec-usb-xhci,id=usb-bus0,multifunction=on' -drive 'file=/var/lib/vz/dump/rr.img,media=disk,format=raw,if=none,id=drive-disk-bootloader' -device 'usb-s
torage,bus=usb-bus0.0,port=1,drive=drive-disk-bootloader,id=usb-disk-bootloader,bootindex=999,removable=on'

 

With no boot disk selected in VM option.

 

Of your you have to adapt file where you put the img file, mine is just an example. (/var/lib/vz/dump/rr.img)

[shibby]

I finally have that i want. My configuration (q35 is required to select PCI-Express on iGPU Passtrough). One drive at the moment because i have to move all my datas from "broken" NAS. USB0 is my UPS.

 

 

 

I used Arc Loader Next as USB Mode using @Orphée advice and installed SA6400 7.2.2

 

 

 

I hope it will be rock stable Nothing more i need.

[gericb]

10 hours ago, djvas335 said:

@gericb TTYD and port 7681 is only active while the DSM is loaded in install mode and waiting for your input.

 

 

Yes, I understand this general idea.  Isn't that the screen that I shared earlier and marked with the red arrow pointing to the line do exactly login to that port using a Web Browser?  Am I missing that I should be hitting some key to pause it or something?  Clearly it's responding to the designated port, but flashing that info in the middle of the screen....maybe an issue with Safari or I need re-size it?  Sorry to be so thick, clearly I must be misunderstanding something or not moving fast enough and it isn't persistent, but rather only a limited amount of time.  I'll try it again... Thanks

[Peter Suh]

20 minutes ago, shibby said:

I finally have that i want. My configuration (q35 is required to select PCI-Express on iGPU Passtrough). One drive at the moment because i have to move all my datas from "broken" NAS. USB0 is my UPS.

 

 

 

I used Arc Loader Next as USB Mode using @Orphée advice and installed SA6400 7.2.2

 

 

 

I hope it will be rock stable Nothing more i need.

 

 

A stable loader cannot be provided consistently all the time.
If so, you will have to stay on the old version of DSM.
When a new version of DSM is released, the loader will move accordingly and find stability again.

The process is still ongoing.
This is inevitable.

Edited September 4 by Peter Suh

[Orphée]

18 minutes ago, shibby said:

I finally have that i want. My configuration (q35 is required to select PCI-Express on iGPU Passtrough). One drive at the moment because i have to move all my datas from "broken" NAS. USB0 is my UPS.

 

 

 

I used Arc Loader Next as USB Mode using @Orphée advice and installed SA6400 7.2.2

 

 

 

I hope it will be rock stable Nothing more i need.

You should switch to UEFI bios. (and disable SECURE BOOT in BIOS settings). It better match genuine Synology.

[gericb]

1 hour ago, gericb said:

Yes, I understand this general idea.  Isn't that the screen that I shared earlier and marked with the red arrow pointing to the line do exactly login to that port using a Web Browser?  Am I missing that I should be hitting some key to pause it or something?  Clearly it's responding to the designated port, but flashing that info in the middle of the screen....maybe an issue with Safari or I need re-size it?  Sorry to be so thick, clearly I must be misunderstanding something or not moving fast enough and it isn't persistent, but rather only a limited amount of time.  I'll try it again... Thanks

 

So @djvas335 setting up a computer in the same room, opening a browser to my primary IP:7681 what I see is basically the same screen that I see on the booting USB DSM loader screen, I did see an option to CTRL-C to interrupt the boot process.  So some addtional progress...  What I am not seeing is that Peter indicated, where I could then mount /dev/md0

[djvas335]

You mount it right there, on this command line, just to clarify, this access only works when the DSM is in install mode, ie waiting for the upload of the DSM installation file, else called junior mode, if the DSM is already fully loaded, the access does not work and you need to into SSH, send me a PM if you need additional help.

 

 

3 hours ago, gericb said:

 

So @djvas335 setting up a computer in the same room, opening a browser to my primary IP:7681 what I see is basically the same screen that I see on the booting USB DSM loader screen, I did see an option to CTRL-C to interrupt the boot process.  So some addtional progress...  What I am not seeing is that Peter indicated, where I could then mount /dev/md0

 

Edited September 4 by djvas335

[shibby]

23 hours ago, Orphée said:

You should switch to UEFI bios. (and disable SECURE BOOT in BIOS settings). It better match genuine Synology.

 

Maybe next time. I dont want to touch it for a long time

[gericb]

On 9/4/2024 at 12:31 PM, djvas335 said:

You mount it right there, on this command line, just to clarify, this access only works when the DSM is in install mode, ie waiting for the upload of the DSM installation file, else called junior mode, if the DSM is already fully loaded, the access does not work and you need to into SSH, send me a PM if you need additional help.

 

 

 

BINGO!  That was the MISSING key to the whole puzzle!  Though I'd like to say I keep up with things here pretty regularly, it still doesn't mean in the stream of wonderful developments that goes on to make all this magic happen, that I caught every minutia of detail in what does what, why, how you might use it.  "Junior Mode" at the very start of my query would have been all I needed, so not super well conveyed at first, thus I appreciate you're supplying the missing puzzle piece @djvas335.

 

Since becoming enlightened, I have very successfully on numerous occasions restarted my box along the way, still trying to upgrade to 7.2.2 and failing every time and then downgrading the 7.2.1 during my weeknights when my brain is already not really in the mood to dig too deeply and ponder the meaning of life.

 

Today however, I went off the deep end...researching, cleaning, purging, researching, repeating...and finally SUCCESS! I had double tight 🤞🏼's going, watching from the corner of my eye, as the 7.2.2 was downloaded from Synology and the % sloooooowly started, then advancing at a painfully slow increment, until for the first time it passed the previous failure points and kept on going. 🥳

 

Interestingly, after the 7.2.2 upload, and went through the full 10min countdown, it finished indicating a similar looking migration looking screen that "Something went wrong" (No clue what if anything was really an issue) but then came up perfectly to the LOGIN and no issue getting logged in, lo and behold, everything worked!  Got a message about the AME being upgraded/repaired, and sure enough a much newer version/codec.  I also had to download a newer version of Plex Media Server specifically for 7.2.2. It's NOTICEABLY more responsive now too, don't know if that's due to the freed space or changes in 7.2.2.

 

In the end, the error "Failed to install the file. The file is probably corrupted." was only partially true, it was caused by a lack of free space on the System Partition and only copious and meticulous cleaning was the total solution to solve all my woes.  I got in DEEP and gutted a ton of things @Peter Suh and learned along the way how much residual crap gets left behind in a ton of places, Déjà vu WinWoes.  Also likey some things that could use cleaned periodically, before calamity strikes again...maybe a loader pre-boot script. 🤣

 

I confess I have no firm notion of how much I eradicated, but I'm sure it was all viable candidates for the digital afterlife...probably ~80MB give or take.  I'm just relieved to get this off my already burgeoning TO DO list and move on!

 

Having said all that - this begs the greater question - how to prevent this in the future?!  Wondering if there is any way those of us that started out with DSM 6 and upgraded to DSM 7 with the whole /dev/md0 2.3G vs 7.9G different sizes respectively, to resize the System Partition, without having to do a full backup, re-install DSM, restore backup. 🫣

[djvas335]

I just backed up and restored all my NAS one by one,  this increased my system partition size, I think it's better to do it like this as the data stays safe while I mess with the NAS and you can loose data due to bad repartition/resize.

 

17 minutes ago, gericb said:

BINGO!  That was the MISSING key to the whole puzzle!  Though I'd like to say I keep up with things here pretty regularly, it still doesn't mean in the stream of wonderful developments that goes on to make all this magic happen, that I caught every minutia of detail in what does what, why, how you might use it.  "Junior Mode" at the very start of my query would have been all I needed, so not super well conveyed at first, thus I appreciate you're supplying the missing puzzle piece @djvas335.

 

Since becoming enlightened, I have very successfully on numerous occasions restarted my box along the way, still trying to upgrade to 7.2.2 and failing every time and then downgrading the 7.2.1 during my weeknights when my brain is already not really in the mood to dig too deeply and ponder the meaning of life.

 

Today however, I went off the deep end...researching, cleaning, purging, researching, repeating...and finally SUCCESS! I had double tight 🤞🏼's going, watching from the corner of my eye, as the 7.2.2 was downloaded from Synology and the % sloooooowly started, then advancing at a painfully slow increment, until for the first time it passed the previous failure points and kept on going. 🥳

 

Interestingly, after the 7.2.2 upload, and went through the full 10min countdown, it finished indicating a similar looking migration looking screen that "Something went wrong" (No clue what if anything was really an issue) but then came up perfectly to the LOGIN and no issue getting logged in, lo and behold, everything worked!  Got a message about the AME being upgraded/repaired, and sure enough a much newer version/codec.  I also had to download a newer version of Plex Media Server specifically for 7.2.2. It's NOTICEABLY more responsive now too, don't know if that's due to the freed space or changes in 7.2.2.

 

In the end, the error "Failed to install the file. The file is probably corrupted." was only partially true, it was caused by a lack of free space on the System Partition and only copious and meticulous cleaning was the total solution to solve all my woes.  I got in DEEP and gutted a ton of things @Peter Suh and learned along the way how much residual crap gets left behind in a ton of places, Déjà vu WinWoes.  Also likey some things that could use cleaned periodically, before calamity strikes again...maybe a loader pre-boot script. 🤣

 

I confess I have no firm notion of how much I eradicated, but I'm sure it was all viable candidates for the digital afterlife...probably ~80MB give or take.  I'm just relieved to get this off my already burgeoning TO DO list and move on!

 

Having said all that - this begs the greater question - how to prevent this in the future?!  Wondering if there is any way those of us that started out with DSM 6 and upgraded to DSM 7 with the whole /dev/md0 2.3G vs 7.9G different sizes respectively, to resize the System Partition, without having to do a full backup, re-install DSM, restore backup. 🫣

 

Edited September 8 by djvas335

[Trabalhador Anonimo]

Let me understand this:

DSM 6 -> /dev/md0 -> 2.3G

DSM 7 -> /dev/md0 -> 7.9G

 

If you start in DSM 7.0 you will get 7.9G in /dev/md0 ?

I have a DS414J, that came with DS 6.x. Now it has 7.1.1-42962 Update 6 - last for this DS. The upgrade was as easily as possible following Synology sequence:

Is this mean that during the process the system partition was resized? I did not lost any data. Or this just for xpenology?

Edited September 8 by Trabalhador Anonimo

[djvas335]

It does not resize system partition automatically, to resize you need to format the NAS and reinstall the DSM, the DSM installer will create the new partition layout for you.

 

44 minutes ago, Trabalhador Anonimo said:

Let me understand this:

DSM 6 -> /dev/md0 -> 2.3G

DSM 7 -> /dev/md0 -> 7.9G

 

If you start in DSM 7.0 you will get 7.9G in /dev/md0 ?

I have a DS414J, that came with DS 6.x. Now it has 7.1.1-42962 Update 6 - last for this DS. The upgrade was as easily as possible following Synology sequence:

Is this mean that during the process the system partition was resized? I did not lost any data. Or this just for xpenology?

 

[djvas335]

Hi @Peter Suh please note that while trying to upgrade to DSM_72806, after the loader rebuild and system upgrade, the system shuts down, happening with JOT and Friend modes on different devices

[Peter Suh]

7 hours ago, djvas335 said:

Hi @Peter Suh please note that while trying to upgrade to DSM_72806, after the loader rebuild and system upgrade, the system shuts down, happening with JOT and Friend modes on different devices

 

I patched this issue about 2 hours ago.
Thanks to @wjz304's help, the patch was done as below,
and now the phenomenon of immediate shutdown when connecting to DSM 5000 port is gone.
https://github.com/PeterSuh-Q3/tcrp-addons/commit/44a9cd3f96b5228368f765b739946c5d283c2f55

Please try rebuilding the loader again.
Sorry for the inconvenience.

[dasbooter]

Is sanmanager-repair script on boot still a requirement for a  stable running system? I only marginally understand that it fixes sanmanager that somehow gets broken on reboot. I am trying to educate myself on the scripts installed using M Shell tcrp but I havent found but a few pieces of info I have google fooed. I am little reluctant to reboot lol after a marathon day of installing yesterday

 

By the way m shell was the only way I could update a HP EliteDesk 800 G2 SFF Desktop PC: Intel Core i5-6500 Quad-Core 3.2GHz with jmb585 sata controller using DS918+ version from 7.1 update 6 to 7.2 latest. Others( ARC,RR) all froze at booting the loader. Thanks so much to Peter Suh after 5 or 6 hours of trying different things m shell worked.

Edited September 15 by dasbooter

[Peter Suh]

21 hours ago, dasbooter said:

Is sanmanager-repair script on boot still a requirement for a  stable running system? I only marginally understand that it fixes sanmanager that somehow gets broken on reboot. I am trying to educate myself on the scripts installed using M Shell tcrp but I havent found but a few pieces of info I have google fooed. I am little reluctant to reboot lol after a marathon day of installing yesterday

 

By the way m shell was the only way I could update a HP EliteDesk 800 G2 SFF Desktop PC: Intel Core i5-6500 Quad-Core 3.2GHz with jmb585 sata controller using DS918+ version from 7.1 update 6 to 7.2 latest. Others( ARC,RR) all froze at booting the loader. Thanks so much to Peter Suh after 5 or 6 hours of trying different things m shell worked.

 

I don't know if you understand the script of this sanmanager-repair Addon, but if you look closely,

you can see that it loads the relevant modules only when an error occurs.
It is prepared, but if there is no error, it doesn't run at all, so don't worry.
https://github.com/PeterSuh-Q3/tcrp-addons/blob/main/sanmanager-repair/src/sanrepair.sh