TinyCore RedPill Loader Build Support Tool ( M-Shell )

[midiman007]

13 hours ago, Peter Suh said:

 

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.

Yes that is correct.

DSM 7.2.2 was not updated DSM 7.2.1 was maintained.

 

I will get you a pict later today for the model MSI motherboard.

 

[midiman007]

13 hours ago, Peter Suh said:

 

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.

I completely understand and here is the Motherboard and the CPU.

ASUS ROG STRIX Z490-F GAMING LGA 1200

with Intel Core i7-10700KA Comet Lake 8-Core 3.8 GHz LGA1200

also G.SKILL Ripjaws V Series 32GB

It has 32 gig of ram also

 

[midiman007]

13 hours ago, Peter Suh said:

 

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.

All I see is a white cursor on the left screen after the first menu item is selected to boot.

 

Please see the screen shot.

[midiman007]

On 11/2/2024 at 1:17 PM, midiman007 said:

 

After the second screen shown all I get is a white cursor on left side top of the screen.

I tried the the third option to reinstall DSML to usb it loaded then went to reboot and just stays there.

I am using a USB thumb drive as my boot.

 

I will look at your other posts to see what you recommend.

 

This info is for others who might have an issue with wanting to get data off there Xen box.

 

Right now I am using https://community.synology.com/enu/forum/1/post/41691?reply=163369

I see all of my data and I am in the process of rsying it off to another storage device.

 

 

Create Ubuntu bootable USB flash stick.
We will start Ubuntu from USB stick, so no OS installation is needed and no changes will be made. Download Ubuntu desktop ISO file and USB installer from url's below:
http://www.ubuntu.com/download/desktop
http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
Set some persistent file size for storing changes (at least 400 MB). edit: eik's post

Boot Ubuntu from USB stick.
Connect NAS HDD and USB stick to computer, then turn it on. Select boot from USB stick (press Esc or F12, depends on computer, for boot menu and select your USB device. In first menu, select first option 'Run Ubuntu from this USB'.

Check HDD drive.
When desktop boots, press Windows key (it's funny, I know, but it works) and type Disk. You should see Disk Utility icon. Double click it. You should see an Extended Partition and RAID component.

Install RAID drivers.
Now we need to install Linux RAID driver. Press Win key, search for Terminal and run it. Type this and press enter: It will require Postfix installation, install it and select 'No configuration' in installation menu. sudo apt-get install mdadm Now we will search and assemble RAID arrays. sudo mdadm --assemble --scan Open Disk Utility again and you should see RAID array components. See picture:

Install LVM2 driver. sudo apt-get install lvm2 sudo vgscan --mknodes Now run Disk Utility, select "vg1" in "Multi-disk Devices" option. Select "Start Volume Group". Now you should be able to see new device in list - "1.41.3-1167" for me.

Here are all your files.

Now you can copy and backup your files.

 

 

[midiman007]

13 hours ago, Peter Suh said:

 

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.

Thanks for your reply and help!

I will do that later since I am in the prepossess of copying data off via a bookable Linux distro and need to get my stuff off of this box.

If it take me a few days I am not ignoring you just need to finish the data copy.

 

[Peter Suh]

44 minutes ago, midiman007 said:

After the second screen shown all I get is a white cursor on left side top of the screen.

I tried the the third option to reinstall DSML to usb it loaded then went to reboot and just stays there.

I am using a USB thumb drive as my boot.

 

I will look at your other posts to see what you recommend.

 

This info is for others who might have an issue with wanting to get data off there Xen box.

 

Right now I am using https://community.synology.com/enu/forum/1/post/41691?reply=163369

I see all of my data and I am in the process of rsying it off to another storage device.

 

 

Create Ubuntu bootable USB flash stick.
We will start Ubuntu from USB stick, so no OS installation is needed and no changes will be made. Download Ubuntu desktop ISO file and USB installer from url's below:
http://www.ubuntu.com/download/desktop
http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/
Set some persistent file size for storing changes (at least 400 MB). edit: eik's post

Boot Ubuntu from USB stick.
Connect NAS HDD and USB stick to computer, then turn it on. Select boot from USB stick (press Esc or F12, depends on computer, for boot menu and select your USB device. In first menu, select first option 'Run Ubuntu from this USB'.

Check HDD drive.
When desktop boots, press Windows key (it's funny, I know, but it works) and type Disk. You should see Disk Utility icon. Double click it. You should see an Extended Partition and RAID component.

Install RAID drivers.
Now we need to install Linux RAID driver. Press Win key, search for Terminal and run it. Type this and press enter: It will require Postfix installation, install it and select 'No configuration' in installation menu. sudo apt-get install mdadm Now we will search and assemble RAID arrays. sudo mdadm --assemble --scan Open Disk Utility again and you should see RAID array components. See picture:

Install LVM2 driver. sudo apt-get install lvm2 sudo vgscan --mknodes Now run Disk Utility, select "vg1" in "Multi-disk Devices" option. Select "Start Volume Group". Now you should be able to see new device in list - "1.41.3-1167" for me.

Here are all your files.

Now you can copy and backup your files.

 

 

 

Are you still getting the "invalid cluster 0" message even if you use a different USB stick?

[Peter Suh]

19 minutes ago, midiman007 said:

Thanks for your reply and help!

I will do that later since I am in the prepossess of copying data off via a bookable Linux distro and need to get my stuff off of this box.

If it take me a few days I am not ignoring you just need to finish the data copy.

 

 

In case you can't handle ./boot.sh inside the Friend kernel,
I've added one more thing.
Go back to the 4 windows of the Tinycore Linux menu.
You need to select "Tiny Core Image Build".

 

If you see that the version of mshell has changed to 1.0.5.1,
Enter the command below in the lower right window.
You can revert to the stable version you want, FRIEND 0.1.1j.

 

./functions.sh update v0.1.1j

[midiman007]

3 hours ago, Peter Suh said:

 

Are you still getting the "invalid cluster 0" message even if you use a different USB stick?

I have not tried to a new USB since I want to get the data off of the box first.

Also Here is a screen shot of what I get after trying to boot with the first option.

Just a dot. nothing else. I killed the transfer of the file with the Linux Distro just so I could get you this.

I can edit the first menu item before booting if you have a command you want me to add in.

I tried the ctl C at you said but it just sits are that screen.

 

 

[Peter Suh]

6 hours ago, midiman007 said:

I have not tried to a new USB since I want to get the data off of the box first.

Also Here is a screen shot of what I get after trying to boot with the first option.

Just a dot. nothing else. I killed the transfer of the file with the Linux Distro just so I could get you this.

I can edit the first menu item before booting if you have a command you want me to add in.

I tried the ctl C at you said but it just sits are that screen.

 

 

 

What direction do you want to go?
You're not just trying to get your data out through a separate Linux Distro, are you?
Please make sure to back up any data you have with the Linux Distro.
If you want to use TCRP-mshell normally, it looks like rebuilding the USB is the only way to go as of now.
You said your MB is ASUS, not MSI, and I suspect it's more about the instability of the USB stick than the instability of the Friend kernel.

[midiman007]

12 hours ago, Peter Suh said:

 

What direction do you want to go?
You're not just trying to get your data out through a separate Linux Distro, are you?
Please make sure to back up any data you have with the Linux Distro.
If you want to use TCRP-mshell normally, it looks like rebuilding the USB is the only way to go as of now.
You said your MB is ASUS, not MSI, and I suspect it's more about the instability of the USB stick than the instability of the Friend kernel.

@Peter Suh

Hi peter I am so sorry about the miss info in this posting. I was going nuts trying to get my data copied off and miss posted.

 

This is the Motherboard, CPU and Memory.This was my old PC.

 

MSI Z97-GD65 Gaming LGA 1150 Intel Z97 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard

 

Intel Core i7-4790K - Core i7 4th Gen Devil's Canyon Quad-Core 4.0 GHz LGA 1150 88W Intel HD Graphics 4600 Desktop ...

 

G.SKILL Ripjaws X Series 16GB (2 x 8GB) 240-Pin PC RAM DDR3 1600.

 

I am still in the process of copying data off.

 

TCRP-mshell I am using Tinycore-Redpill Friend. After the data has copied off should I try the second option in the Tinycore-redpill friend menu?

 

Kind regards,

 

 

 

 

 

 

[midiman007]

On 11/4/2024 at 7:50 PM, Peter Suh said:

 

What direction do you want to go?
You're not just trying to get your data out through a separate Linux Distro, are you?
Please make sure to back up any data you have with the Linux Distro.
If you want to use TCRP-mshell normally, it looks like rebuilding the USB is the only way to go as of now.
You said your MB is ASUS, not MSI, and I suspect it's more about the instability of the USB stick than the instability of the Friend kernel.

Ok I got what I could off the drives.

what do you recommend as the next steps to try and recover the box to a bookable state?

I am wondering if Tinycore Friend update messed something up,

Is there anyway of rolling back to the older version and not receiving the update on boot?

 

 

 

[Peter Suh]

12 hours ago, midiman007 said:

Ok I got what I could off the drives.

what do you recommend as the next steps to try and recover the box to a bookable state?

I am wondering if Tinycore Friend update messed something up,

Is there anyway of rolling back to the older version and not receiving the update on boot?

 

 

 

 

 

Have you got a new USB stick?
I feel like the story keeps going around in circles.
And I don't understand this second question at all.

[shibby]

15 hours ago, midiman007 said:

Is there anyway of rolling back to the older version and not receiving the update on boot?

 

Not easy but there is a possibility to do it. You have to manualy change m-shell script to pull specific tag from git instead of the latest version. If you don`t know "bash" then answer for your question is "no, it`s not possible".

 

But @Peter Suh i admit it will be nice feature to have a possibility switch to specific version of m-shell. Not always "the latest" is "the best". Or maybe add a simple question "Do you want update M-shell scripts?" instead of do this automatically?

 

Best Regards

[Peter Suh]

1 hour ago, shibby said:

 

Not easy but there is a possibility to do it. You have to manualy change m-shell script to pull specific tag from git instead of the latest version. If you don`t know "bash" then answer for your question is "no, it`s not possible".

 

But @Peter Suh i admit it will be nice feature to have a possibility switch to specific version of m-shell. Not always "the latest" is "the best". Or maybe add a simple question "Do you want update M-shell scripts?" instead of do this automatically?

 

Best Regards

 

rr's version management is a bit different from tcrp (mshell).
rr seems to use versions for not only the main script, but also addon packs, module packs, etc., and track their version history.
There are also quite a few helpers supporting this.
mshell doesn't have the resources to expand its scope as much as rr does.

 

So the way mshell pursues is to pursue the latest version rather than reverting to the past version, and if a problem occurs here,

it is immediately supplemented to bring stability that everyone can use.

 

tcrp (mshell) does not make major changes to lkm, load, addon, or module.
Issues can occur in the version upgrade of mshell menu.sh script or boot.sh of friend kernel.

 

By the way, has there ever been a case where a revert to the past version was necessary?
As far as I remember, there hasn't been one.

 

To @midiman007, I prepared a function to install the past version of friend kernel, but it seems likely that this process will not be necessary due to miscommunication.

[midiman007]

9 hours ago, Peter Suh said:

 

 

Have you got a new USB stick?
I feel like the story keeps going around in circles.
And I don't understand this second question at all.

@Peter Suh

Yes I have a brand new 32 GB stick.

What I meant on the second question is how would you try and rebuild the box and try and keep everything?

 

Please Note : Everything was running fine until I rebooted and tiny core friend updated. That is when the issue happened.

I am not saying it's the issue but it might be.

 

 

[Peter Suh]

15 hours ago, midiman007 said:

@Peter Suh

Yes I have a brand new 32 GB stick.

What I meant on the second question is how would you try and rebuild the box and try and keep everything?

 

Please Note : Everything was running fine until I rebooted and tiny core friend updated. That is when the issue happened.

I am not saying it's the issue but it might be.

 

 

 

If you change to new stick and have the same problem, your assumption may be correct.

 

The only things you need to refer to in the existing settings are SN and MAC.

 

If you were using REAL MAC, you don't need to refer to MAC.

 

The SN also depends on which type (genuine or randomly generated) you have been using, whether you need to get the same value or not.

[midiman007]

4 hours ago, Peter Suh said:

 

If you change to new stick and have the same problem, your assumption may be correct.

 

The only things you need to refer to in the existing settings are SN and MAC.

 

If you were using REAL MAC, you don't need to refer to MAC.

 

The SN also depends on which type (genuine or randomly generated) you have been using, whether you need to get the same value or not.

Is there anyway I can get that info from the box as it is now with out is being bookable into the Xenology os?

[Peter Suh]

3 minutes ago, midiman007 said:

Is there anyway I can get that info from the box as it is now with out is being bookable into the Xenology os?

 

Mount that damaged USB stick on MS Windows and check the user_config.json file on the 3rd partition.

If the 3rd partition on MS Windows does not have a volume letter assigned, try assigning it with the help of a separate partition utility.

[midiman007]

5 hours ago, Peter Suh said:

 

Mount that damaged USB stick on MS Windows and check the user_config.json file on the 3rd partition.

If the 3rd partition on MS Windows does not have a volume letter assigned, try assigning it with the help of a separate partition utility.

Sorry if this question sounds dumb.

So I should just burn your new version to a new USB or is there a way to copy the original USB to the new USB?

[Peter Suh]

6 hours ago, midiman007 said:

Sorry if this question sounds dumb.

So I should just burn your new version to a new USB or is there a way to copy the original USB to the new USB?

 

I think it meant to look into user_config.json in the 3rd partition of the original usb and find the SN/MAC in it,
I didn't know it would be such a difficult problem for you.

 

In fact, I was asking if there was a possibility to do it without having to find these two values,
but you didn't answer my question.

How did you get the Synology SN that was already used in the original USB?
Is it difficult to answer?

[midiman007]

13 hours ago, Peter Suh said:

 

I think it meant to look into user_config.json in the 3rd partition of the original usb and find the SN/MAC in it,
I didn't know it would be such a difficult problem for you.

 

In fact, I was asking if there was a possibility to do it without having to find these two values,
but you didn't answer my question.

How did you get the Synology SN that was already used in the original USB?
Is it difficult to answer?

@Peter Suh  It will not be that hard to get it from the old USB. 

 

I generated it the last time.

 

My question is do I just burn the new boot loader .img file and run through the setup again and just enter the info from the old  .json file?

 

 

 

 

[Peter Suh]

2 hours ago, midiman007 said:

@Peter Suh  It will not be that hard to get it from the old USB. 

 

I generated it the last time.

 

My question is do I just burn the new boot loader .img file and run through the setup again and just enter the info from the old  .json file?

 

 

 

 

 

The information from the .json file should be input during the process of building the loader in the top left menu of the mshell screen where the 4 windows appear.

[midiman007]

1 minute ago, Peter Suh said:

 

The information from the .json file should be input during the process of building the loader in the top left menu of the mshell screen where the 4 windows appear.

Got it. Thanks so much for your help.

[midiman007]

21 hours ago, midiman007 said:

Got it. Thanks so much for your help.

@Peter Suh

 

Ok I got it back up.

The USB drive would not mount under windows had to use Linux.

I used the tinycore-redpill.v1.0.5.0.m-shell.img not the newest one since I thought that might be the issue.

 

After thinking about it I remembered I used a generated the serial number and used the real mac.

So I built the loader with that and the same previous model.

All went well and the box is back up.

 

Thanks you so much for your help again.

I am just posting this info to help others that might have this issue.

 

 

Edited November 10 by midiman007

[Trabalhador Anonimo]

Is it safe to go to 7.2.2-72806-1?