TinyCore RedPill Loader Build Support Tool ( M-Shell )

[Trabalhador Anonimo]

28 minutes ago, Peter Suh said:

 

I don't quite understand what you mean by risky,
but if this is the only server you have,
and you already have rr stabilized, then you wouldn't bother trying anything else.

 

I could not stabilize RR. It keeps freezing over and over, so I got back to m-shell.

by risky, I mean to lose data. I cannot handle 7tb backup yet.

[Peter Suh]

38 minutes ago, Trabalhador Anonimo said:

 

I could not stabilize RR. It keeps freezing over and over, so I got back to m-shell.

by risky, I mean to lose data. I cannot handle 7tb backup yet.

 

To estimate the risk variables,

The data partition area of the disks originally used by DSM is not affected by the loader replacement operation.
The system partition is used in the front part of each disk that occupies 2G+8G capacity, and the OS of DSM is installed on each disk.

 

However, it is best to have a backup to prepare for all risks.
And, as another insurance, I recommend securing one of the 1GB speed Intel NICs (igb, e1000, e1000e) rather than the Realtek series NIC.

 

What RAID are the disks using?

[Trabalhador Anonimo]

RAID: SHR

NIC 1: Onboard realtek GB Lan - not working

NIC 2: Realtek RL81xx - not working

NIC 3: TP-link TG3468 - working

NIC 4: Lan Rede Gigabit Usb 3.0 Ethernet 10/100/1000, do not know chipset - working.

 

My system is Xeon E3 1240L V3 (LGA1150), 32GB ram DDR3, 10x 1TB HDD + 1x 2TB.

3622xs+: 1x poll, 2x volumes, 1x LUN (vol 1) and 1x virtual Machine: (does it all work in SA6400?)

System information on DSM says the USB NIC is RTL8153 Gigabit Ethernet Adapter.

Is there a way to see what is the NIC´s chipset without open the case (like some linux command line? I´m not that friend of linux)?

Edited November 2 by Trabalhador Anonimo
Input more informatiun

[midiman007]

On 8/31/2024 at 11:17 AM, Peter Suh said:

@Peter Suh Thanks for the info.

This version will support DSM 7.2.2. upgrade my current build is requesting that I update it to Version: 7.2.2-72806.

You can use the new version that is automatically updated.
The latest version after 1.0.4.2 is the required version for using DSM 7.2.2.

 

 

[midiman007]

12 hours ago, Peter Suh said:

 

I am not a native English speaker. I don't understand your metaphorical expressions.

 

What does auto REDPILL mean?

@Peter Suh

Sorry for my bad post. I had an issue yesterday and didn't have time to do a complete post.

I am currently running a few version back of you tineycore-redpill.

The box is asking that I upgrade my current build  to Version: 7.2.2-72806.

Is it safe. I have to much to hose the box or should I just stay on the current version.

 

 

 

[Peter Suh]

5 hours ago, Trabalhador Anonimo said:

RAID: SHR

NIC 1: Onboard realtek GB Lan - not working

NIC 2: Realtek RL81xx - not working

NIC 3: TP-link TG3468 - working

NIC 4: Lan Rede Gigabit Usb 3.0 Ethernet 10/100/1000, do not know chipset - working.

 

My system is Xeon E3 1240L V3 (LGA1150), 32GB ram DDR3, 10x 1TB HDD + 1x 2TB.

3622xs+: 1x poll, 2x volumes, 1x LUN (vol 1) and 1x virtual Machine: (does it all work in SA6400?)

System information on DSM says the USB NIC is RTL8153 Gigabit Ethernet Adapter.

Is there a way to see what is the NIC´s chipset without open the case (like some linux command line? I´m not that friend of linux)?

 

tc@box:~$ ll /sys/class/net/eth*/device/driver
lrwxrwxrwx 1 root root 0 Nov  2 14:36 /sys/class/net/eth0/device/driver -> ../../../../bus/pci/drivers/e1000

 

However, the NIC modules (Drivers) supported by Tinycore may be limited.
If it does not appear in the Driver list above,
You can rely on the FRIEND kernel screen.
In fact, mshell also detects the NIC and displays the type of chipset in the upper right screen of the four loader build windows.

[Peter Suh]

1 hour ago, midiman007 said:

@Peter Suh

Sorry for my bad post. I had an issue yesterday and didn't have time to do a complete post.

I am currently running a few version back of you tineycore-redpill.

The box is asking that I upgrade my current build  to Version: 7.2.2-72806.

Is it safe. I have to much to hose the box or should I just stay on the current version.

 

 

 

 

 

I already answered a similar question today, so here's the link:

 

 

 

[Trabalhador Anonimo]

1 hour ago, Peter Suh said:

 

tc@box:~$ ll /sys/class/net/eth*/device/driver
lrwxrwxrwx 1 root root 0 Nov  2 14:36 /sys/class/net/eth0/device/driver -> ../../../../bus/pci/drivers/e1000

 

However, the NIC modules (Drivers) supported by Tinycore may be limited.
If it does not appear in the Driver list above,
You can rely on the FRIEND kernel screen.
In fact, mshell also detects the NIC and displays the type of chipset in the upper right screen of the four loader build windows.

 

I went to SA6400 on my main server. All NICs were found and are up and running. No data loss.

[midiman007]

2 hours ago, Peter Suh said:

@Peter Suh I rebooted my box with the original tiny core installed I did not appy the update from Sysology.

 

Tinycore updated and rebooted now the box will not boot and I am getting error invalid cluster 0.

 

what did I do wrong?

 

How can I recover the BOX with the data.

 

Please Help.

 

I already answered a similar question today, so here's the link:

 

 

 

 

[Peter Suh]

8 hours ago, midiman007 said:

 

 

This is what I checked by contacting chatgpt. The problem may occur for the following reasons.

 

[fishton]

On 11/2/2024 at 1:12 AM, Peter Suh said:

 

The TinyCore friend's updates are managed and operated independently from TCRP-mshell (Tinycore loader builder), so you don't have to worry about this part.

 

In the case of TCRP, unlike ARPL(rr), you must rebuild the loader when the micro of DSM changes from 7.2.1 to 7.2.2.

 

A micro means a situation where the third number of ${major}.${minor}.${micro} changes from micro 1 to 2, etc.

 

After rebuilding the mshell loader, DSM will request migration to version 7.2.2 at the next reboot.

 

At that time, just follow the request.

 

thanks Peter

 

is there any tutorial on that ?

 

should I use your "auto config" from git to get a new loader image (version v1.0.5.0 I guess) with the same config as current (same serial, mac) to ensure it does not break ?

 

thanks a lot and sorry for the thumb questions :p

 

[Peter Suh]

3 hours ago, fishton said:

 

thanks Peter

 

is there any tutorial on that ?

 

should I use your "auto config" from git to get a new loader image (version v1.0.5.0 I guess) with the same config as current (same serial, mac) to ensure it does not break ?

 

thanks a lot and sorry for the thumb questions 😛

 

 

There is no separate tutorial or manual prepared for preparing a new DSM version in mshell.
It is too easy to make a separate tutorial.
I don't make a tutorial for something that can be explained in one line.

 

There is no need to create a new version of the loader from scratch.
In the case of TCRP mshell, you need to quickly change to the second menu of the Grub boot menu, "Tiny Core Image Build" and re-enter.
Rebuild the loader for DSM 7.2.2 in this menu.
All previously set information will remain as is.

[midiman007]

11 hours ago, Peter Suh said:

 

This is what I checked by contacting chatgpt. The problem may occur for the following reasons.

 

Thanks for the reply  I have another USB drive I can try. I didn't change anything on the box. Just rebooted it and your tinycore redpill updated..

if I hit the key on the first screen to boot the box start to load with a blinking cursor the thumb drive flashes a little then stops. I do not get the

normal text on the screen. it is just a white cursor blinking. How can I get my config from the original USB to the new one?

 

I do not want to have to reformat the data partitions and lose the data.

 

TIA

 

[fishton]

1 hour ago, Peter Suh said:

 

There is no separate tutorial or manual prepared for preparing a new DSM version in mshell.
It is too easy to make a separate tutorial.
I don't make a tutorial for something that can be explained in one line.

 

There is no need to create a new version of the loader from scratch.
In the case of TCRP mshell, you need to quickly change to the second menu of the Grub boot menu, "Tiny Core Image Build" and re-enter.
Rebuild the loader for DSM 7.2.2 in this menu.
All previously set information will remain as is.

 

Thanks a lot !

 

When I enter in grub menu "Tiny Core Image Build", I do not see the original menu I got when I initially created the loader, but only all different linux command prompts windows so I do not know what to do next  

 

 

[Peter Suh]

1 hour ago, midiman007 said:

Thanks for the reply  I have another USB drive I can try. I didn't change anything on the box. Just rebooted it and your tinycore redpill updated..

if I hit the key on the first screen to boot the box start to load with a blinking cursor the thumb drive flashes a little then stops. I do not get the

normal text on the screen. it is just a white cursor blinking. How can I get my config from the original USB to the new one?

 

I do not want to have to reformat the data partitions and lose the data.

 

TIA

 

 

The parts to note in the original configuration are the Synology SN and MAC address.
If you were using the genuine SN or MAC address, you can just copy and paste them.

Sometimes, when entering the FRIEND kernel loading, the response is slow.

You can try rebooting again, and if you wait a little longer, the loading response will come.

[Peter Suh]

53 minutes ago, fishton said:

 

Thanks a lot !

 

When I enter in grub menu "Tiny Core Image Build", I do not see the original menu I got when I initially created the loader, but only all different linux command prompts windows so I do not know what to do next  

 

 

 

If you don't see the original 4 windows after entering the loader build, your loader may have been damaged for some reason.
It seems that you will have no choice but to rebuild the loader from GitHub.
The only things you need to use as they are from the existing DSM are the SN and MAC address.
This part may also be different depending on which SN and MAC address you were using.
If you used a genuine Synology SN, you should use it as is.
Otherwise, if you are using an arbitrarily GEN-processed SN and plan to use the REAL MAC address, you can ignore the existing one.

[midiman007]

7 minutes ago, Peter Suh said:

 

If you don't see the original 4 windows after entering the loader build, your loader may have been damaged for some reason.
It seems that you will have no choice but to rebuild the loader from GitHub.
The only things you need to use as they are from the existing DSM are the SN and MAC address.
This part may also be different depending on which SN and MAC address you were using.
If you used a genuine Synology SN, you should use it as is.
Otherwise, if you are using an arbitrarily GEN-processed SN and plan to use the REAL MAC address, you can ignore the existing one.

Again thanks for your assistance it is greatly appreciated.

 

No it's a i7 MSI MB box. I just tried a different port with the current USB still nothing. Also I tried to re-install DSM ds1621+ DDSML , USB from the menu screen.

 

It loads the initramfs and seems to be working but is taking a long time to finish, Is that normal?

 

How to I rebuild and keep my current vols. Not worried about shares since they are easy to setup.

When I built it I used gen serial and default settings.

 

One vol is a 2 disk mirror the other is a raid 5 4 disk.

 

[fishton]

1 hour ago, Peter Suh said:

 

If you don't see the original 4 windows after entering the loader build, your loader may have been damaged for some reason.
It seems that you will have no choice but to rebuild the loader from GitHub.
The only things you need to use as they are from the existing DSM are the SN and MAC address.
This part may also be different depending on which SN and MAC address you were using.
If you used a genuine Synology SN, you should use it as is.
Otherwise, if you are using an arbitrarily GEN-processed SN and plan to use the REAL MAC address, you can ignore the existing one.

 

Hi

 

I do see the 4 windows, just do not have the "menu" that I used initially to build the loader.

 

what prompt and commndn to use to rebuild ?  sorry for being so dumb

 

 

[Peter Suh]

1 hour ago, midiman007 said:

Again thanks for your assistance it is greatly appreciated.

 

No it's a i7 MSI MB box. I just tried a different port with the current USB still nothing. Also I tried to re-install DSM ds1621+ DDSML , USB from the menu screen.

 

It loads the initramfs and seems to be working but is taking a long time to finish, Is that normal?

 

How to I rebuild and keep my current vols. Not worried about shares since they are easy to setup.

When I built it I used gen serial and default settings.

 

One vol is a 2 disk mirror the other is a raid 5 4 disk.

 

 

Unfortunately for MSI MB, XPE is a lot more prone to MB compatibility.
MSI is the worst of them all.
People say it's because MSI likes to use a special BIOS that is not standard.

It's more likely that the kernel panics in the middle of the process than it is taking forever to complete.

To prove that the kernel has really stopped, monitoring the kernel log through the Serial Com1 port should be done, but this Serial Port has been removed on recent boards.

So, it seems that on MSI boards, people often choose VMs like Proxmox over baremetal.

While you may have lucked out with getting the MSI to work in 7.2.1, it may be the case that things go the other way in 7.2.2.

Edited November 3 by Peter Suh

[Peter Suh]

29 minutes ago, fishton said:

 

Hi

 

I do see the 4 windows, just do not have the "menu" that I used initially to build the loader.

 

what prompt and commndn to use to rebuild ?  sorry for being so dumb

 

 

 

Previous versions used commands directly, but commands are no longer needed.
You can use the menu on the top left in sequence.
There are some differences from the final version, but please refer to the guide in the link below.
https://github.com/PeterSuh-Q3/tinycore-redpill?tab=readme-ov-file#m-shell-for-tinycore-redpill

[midiman007]

6 minutes ago, Peter Suh said:

 

Unfortunately for MSI MB, XPE is a lot more prone to MB compatibility.
MSI is the worst of them all.
People say it's because MSI likes to use a special BIOS that is not standard.

It's more likely that the kernel panics in the middle of the process than it is taking forever to complete.

To prove that the kernel has really stopped, monitoring the kernel log through the Serial Com1 port should be done, but this Serial Port has been removed on recent boards.

So, it seems that on MSI boards, people often choose VMs like Proxmox over baremetal.

While you may have lucked out with getting the MSI to work in 7.2.1, it may be the case that things go the other way in 7.2.2.

Everything was working perfectly.

 

Well I tell tell you exactly what I did.

 

I rebooted the box, I did not install any firmware update to 7.2.2 from sysology.

 

upon reboot Tiny-Core redpill friend did an update  and everything went well with the update.

 

After the tinycore-redpill friend updated theupdate the box will not boot anymore.

 

can you please help me boot a distro to reassemble the raid so I can move the data to a different storage unit.

 

I am not saying MSI is not the worst but it was working fine and I did not update to firmware 7.2.2 only update was to Tiny-core friend via the reboot.

 

[Peter Suh]

8 hours ago, midiman007 said:

Everything was working perfectly.

 

Well I tell tell you exactly what I did.

 

I rebooted the box, I did not install any firmware update to 7.2.2 from sysology.

 

upon reboot Tiny-Core redpill friend did an update  and everything went well with the update.

 

After the tinycore-redpill friend updated theupdate the box will not boot anymore.

 

can you please help me boot a distro to reassemble the raid so I can move the data to a different storage unit.

 

I am not saying MSI is not the worst but it was working fine and I did not update to firmware 7.2.2 only update was to Tiny-core friend via the reboot.

 

 

I think I misunderstood your requirement.

 

I understand that there was no manipulation for DSM 7.2.2.

 

DSM 7.2.1 was maintained, and only the FRIEND kernel was automatically updated to the final version 0.1.1k, which seems to have become KP.

 

https://github.com/PeterSuh-Q3/tcrpfriend/releases

 

This 0.1.1k is a new version that rebuilds the buildroot kernel to support mmc.

 

I will prepare a script that can revert to the previous version 0.1.1j and let you know today.

 

Your case is the first error report since 0.1.1k FRIEND kernel was released 3 weeks ago.

 

What is the exact model of MSI MB you are using?

 

I would like to investigate what part is affected.

[Peter Suh]

8 hours ago, midiman007 said:

Everything was working perfectly.

 

Well I tell tell you exactly what I did.

 

I rebooted the box, I did not install any firmware update to 7.2.2 from sysology.

 

upon reboot Tiny-Core redpill friend did an update  and everything went well with the update.

 

After the tinycore-redpill friend updated theupdate the box will not boot anymore.

 

can you please help me boot a distro to reassemble the raid so I can move the data to a different storage unit.

 

I am not saying MSI is not the worst but it was working fine and I did not update to firmware 7.2.2 only update was to Tiny-core friend via the reboot.

 

 

I have one more question.

 

After selecting the first menu from the four Grub boot menus shown last time,

 

Are you not able to see the Friend kernel loading screen at all?

 

Is the phenomenon that loading seems to have stopped happening in this state?

 

If so, can you stop the loading process with Ctrl+C in this console screen?

 

What does the prompt look like after stopping with Ctrl+C?

 

If you can capture it, please upload it.

[Peter Suh]

12 hours ago, midiman007 said:

Everything was working perfectly.

 

Well I tell tell you exactly what I did.

 

I rebooted the box, I did not install any firmware update to 7.2.2 from sysology.

 

upon reboot Tiny-Core redpill friend did an update  and everything went well with the update.

 

After the tinycore-redpill friend updated theupdate the box will not boot anymore.

 

can you please help me boot a distro to reassemble the raid so I can move the data to a different storage unit.

 

I am not saying MSI is not the worst but it was working fine and I did not update to firmware 7.2.2 only update was to Tiny-core friend via the reboot.

 

 

If Friend kernel loading is normally interrupted by Ctrl+c,
please try the following two commands:

./down.sh
./boot.sh update v0.1.1j

 

I have just released the manual update feature for previous versions as promised above.

Edited November 4 by Peter Suh

[fishton]

Hi Peter

 

I finally got the menu showing. it was just that it had to download multiple things, then multiple reset to finally get the menu showing.

 

from there I did rebuild the loader and DSM was showing as "ready for migrating" 

 

Problem is that, when I gave him the pat file, it first said file is corrupted, then space is not enough ....

 

I found out on this page https://gugucomputing.wordpress.com/2023/12/13/how-to-escape-from-failed-to-install-dsm-available-system-space-is-insufficient-or-similar-messages/ a way to remove files via telnet (I had only 285MB free)

 

I did remove an old pat file, as well as root/XPOenology_backup not sure what it was and got 5000MB free

 

Updates finally went through. Too much stress for me  

 

thanks for your precious help and work indeed