Jump to content
XPEnology Community

TinyCore RedPill Loader Build Support Tool ( M-Shell )

Peter Suh

By Peter Suh
in Software Modding

 Share

Recommended Posts

Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted
11 minutes ago, hendry said:

why the file system not known at first boot ? it's on v7.2.0-64570 

xpe1  | LoadingLoadin gLinux... Linux..
.pe1  |
xpe1  | LoadingLoadin ginitramfs... initramfs..
.pe1  |
xpe1  | error: unknown filesystem.
error: unknown filesystemStarting.
xpe1  | Startin gkernel kerne lwith wit hUSB US Bboot boo
xpe1  |
Press any key to continue...t
xpe1  |
xpe1  | Press any key to continue...
[    0.000000] Initializing cgroup subsys cpuset
xpe1  | [    0.000000] Initializing cgroup subsys cpu
xpe1  | [    0.000000] Initializing cgroup subsys cpuacct
xpe1  | [    0.000000] Linux version 4.4.302+ (root@build8) (gcc version 12.2.0 (GCC) ) #64570 SMP Sat Jun 3 00:10:35 C3
xpe1  | [    0.000000] Command line: BOOT_IMAGE=/zImage withefi earlyprintk syno_hw_version=DS3622xs+ console=ttyS0,115p
xpe1  | [    0.000000] KERNEL supported cpus:
xpe1  | [    0.000000]   Intel GenuineIntel
xpe1  | [    0.000000] x86/fpu: Legacy x87 FPU detected.
xpe1  | [    0.000000] e820: BIOS-provided physical RAM map:
xpe1  | [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
xpe1  | [    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
xpe1  | [    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
xpe1  | [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003ffdbfff] usable
xpe1  | [    0.000000] BIOS-e820: [mem 0x000000003ffdc000-0x000000003fffffff] reserved
xpe1  | [    0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
xpe1  | [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
xpe1  | [    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
xpe1  | [    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
xpe1  | [    0.000000] earlycon: Early serial console at I/O port 0x3f8 (options '115200n8')
xpe1  | [    0.000000] bootconsole [uart0] enabled
xpe1  | [    0.000000] NX (Execute Disable) protection: active
xpe1  | [    0.000000] SMBIOS 2.8 present.
xpe1  | [    0.000000] DMI: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
xpe1  | [    0.000000] Kernel/User page tables isolation: disabled
xpe1  | [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
xpe1  | [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
xpe1  | [    0.000000] e820: last_pfn = 0x3ffdc max_arch_pfn = 0x400000000
xpe1  | [    0.000000] MTRR default type: write-back
xpe1  | [    0.000000] MTRR fixed ranges enabled:
xpe1  | [    0.000000]   00000-9FFFF write-back

and ends up with kernel panic  

xpe1  | [    0.592682] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
xpe1  | [    0.592682]
xpe1  | [    0.593626] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
xpe1  | [    0.593626]

 

 

while on 7.1.0-42661 the boot process is okay.. 

xpe  |
xpe  | Loadin gLinux... Linux..
.pe  |
xpe  | LoadingLoadin ginitramfs... initramfs..
.pe  |
xpe  | StartingStartin gkernel kerne lwith wit hUSB US Bboot boo
[    0.000000] Initializing cgroup subsys cpuset
xpe  | [    0.000000] Initializing cgroup subsys cpu
xpe  | [    0.000000] Initializing cgroup subsys cpuacct
xpe  | [    0.000000] Linux version 3.10.108 (root@build13) (gcc version 8.5.0 (GCC) ) #42661 SMP Fri Apr 1 15:31:15 CS2
xpe  | [    0.000000] Command line: BOOT_IMAGE=/zImage withefi earlyprintk syno_hw_version=DS3615xs console=ttyS0,115201
xpe  | [    0.000000] KERNEL supported cpus:
xpe  | [    0.000000]   Intel GenuineIntel
xpe  | [    0.000000] e820: BIOS-provided physical RAM map:
xpe  | [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
xpe  | [    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
xpe  | [    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
xpe  | [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003ffdbfff] usable
xpe  | [    0.000000] BIOS-e820: [mem 0x000000003ffdc000-0x000000003fffffff] reserved
xpe  | [    0.000000] BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
xpe  | [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
xpe  | [    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
xpe  | [    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
xpe  | [    0.000000] Early serial console at I/O port 0x3f8 (options '115200n')
xpe  | [    0.000000] bootconsole [uart0] enabled

 

 

 

 

PROXMOX ?

Link to comment
Share on other sites
hendry Advanced Member

hendry

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

 

 

 

PROXMOX ?

just like that.. 

actually, i run it under docker container on my NAS hardware. 

docker container on debian os running KVM to load xpenology. 

file system not known i think it's missing the driver to be loaded on the boot process. 

Edited by hendry
Link to comment
Share on other sites
hendry Advanced Member

hendry

Posted
Posted
1 hour ago, Peter Suh said:

 

 

Several tests are scheduled for today.
When my time allows, I will try to follow the xpenology docker you are installing.

 

hope you have a time to try installing docker xpenology as the instruction on the link i show u. 

i just think, the module (.ko) is missing in loader img which was need to load the syno os.

Link to comment
Share on other sites
mealan Newbie

mealan

Posted
Posted
On 8/18/2023 at 8:49 PM, mealan said:

having an issue with ESXi and getting drives detected for new install. FRIEND doesn't detect the drive, but the previous method has a format error. I have several using normal tinycore with no issue at 7.0, was looking to update and see what new progress has made, this is the first time i'm trying m-shell. 

it's awesome so far, i'm sure it'll be great once i can get it going.

 

sadly still the same with 9.5, arc works without issue, i'm on ESXi 8.0u1 and vm hardware version 20. DSM can't install says no harddrive found.


Have tried with sas paravirtual which get's loaded correctly and manually edited satamap and diskidxmap with no luck.

seems like m-shell is having an issue. What logs would be useful? Thank you!

 

und SAS Controller : pciid 15add000007c0  Required Extension : Searching for m
Module vmw_pvscsi loaded succesfully

 

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted (edited)
30 minutes ago, mealan said:

sadly still the same with 9.5, arc works without issue, i'm on ESXi 8.0u1 and vm hardware version 20. DSM can't install says no harddrive found.


Have tried with sas paravirtual which get's loaded correctly and manually edited satamap and diskidxmap with no luck.

seems like m-shell is having an issue. What logs would be useful? Thank you!

 

und SAS Controller : pciid 15add000007c0  Required Extension : Searching for m
Module vmw_pvscsi loaded succesfully

 

 

Please let me know for reference which Synology model you are trying and which DSM version is targeted.

Is version 7.0 still the target?

 

The vmw_pvscsi module used by SAS controller 15add000007c0 seems to have a different TCRP version than the version used in ARC.

{
     "name": "vmw_pvscsi",
     "alias": "pci:v000015ADd000007C0sv*sd*bc*sc*i*"
},

 

In fact, this module was compiled yesterday as well.

 

https://github.com/PeterSuh-Q3/arpl-modules

 

What I am trying now is to make the HBA operate in a Device-Tree based model.
The compilation target is actually the mpt3sas module, but this module is being compiled incidentally.

 

This is an attempt to find the disk on the SAS controller.
mpt3sas is still being tested. Please wait a moment.

Edited by Peter Suh
Link to comment
Share on other sites
Vodka2014 Super Member

Vodka2014

Posted
Posted
On 9/1/2023 at 1:59 AM, Peter Suh said:

[notification]

 

Introducing a new add-on "drivedatabase" for unrecognized firmware version issues.

 

It is a shell called Synology_HDD_db created by @007revad,

and with some modifications, it is installed automatically along with the M SHELL for TCRP loader as a service of DSM.
https://github.com/PeterSuh-Q3/tcrp-addons/tree/main/drivedatabase
 
To use this addon you will need to rebuild your loader.

If you are prompted to update the drive database due to a storage manager error as shown below, you can rebuild the loader or run @007revad's Synology_HDD_db directly by connecting to ssh on DSM.

 

2023-08-317_38_07.thumb.png.ca9c2e26c86ea7e0eca1e9abc8d5132a.png.e255762d8e81816e2c122803d4ffb12a.png

 

Execute the command as below.

 

sudo -i
curl -kLO https://raw.githubusercontent.com/007revad/Synology_HDD_db/main/syno_hdd_db.sh
chmod +x syno_hdd_db.sh
./syno_hdd_db.sh

 

Hi @Peter Suh

 

I just rebuild the loader on my server with Update 3 and all the disks now show the below: DS3622xs+ on my LSI 9211

 

WD-Errors.jpg

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted
1 hour ago, Vodka2014 said:

Hi @Peter Suh

 

REQUEST:

 

Are you able to add an Prob to check the Temps of an HBA at all ? 

 

Thanks

 

S.M.A.R.T is used to measure the temperature of the disk,

but this is the first time I have heard of measuring the temperature of the SCSI controller itself.
Have you ever experienced a similar solution?

Link to comment
Share on other sites
Vodka2014 Super Member

Vodka2014

Posted
Posted
40 minutes ago, Peter Suh said:

 

S.M.A.R.T is used to measure the temperature of the disk,

but this is the first time I have heard of measuring the temperature of the SCSI controller itself.
Have you ever experienced a similar solution?

 

I am just asking since the LSI gets a bit warm. Might need to just add small fan :)

Link to comment
Share on other sites
Captainfingerbang Super Member

Captainfingerbang

Posted
Posted
On 7/24/2023 at 11:52 PM, Optiplex_Fan said:

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

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

So glad i found this!    I keep getting this error on 918+ with REAL Serial and Mac Used for YEARS 

 

Did you find a solution??????

 

image.thumb.png.8059c13e82a8e47ca6c474dbb417699a.png

Link to comment
Share on other sites
Vodka2014 Super Member

Vodka2014

Posted
Posted (edited)

Hi @Peter Suh

 

My system had a issues now I think there was an issue with the loader so I rebuilt it / USB issue or something, selected recover and now again my system is stating.

 

System getting ready please log in later. 

 

Any help here please

 

EDIT: When i try and connect to 7681 i get connection closed

 

Since i am using an HBA now and if i want to roll back to 7.1 will this break anything if i remove the HBA and add the disks back to the onboard. I did do an Disk replacement as well and once done all was working 100%. I rebooted and this is when all the issues started. 

Edited by Vodka2014
Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted
8 minutes ago, Vodka2014 said:

Hi @Peter Suh

 

My system had a issues now I think there was an issue with the loader so I rebuilt it / USB issue or something, selected recover and now again my system is stating.

 

System getting ready please log in later. 

 

Any help here please

 

EDIT: When i try and connect to 7681 i get connection closed

 

 

Usually in these cases a few minutes of waiting time is really necessary.
Have you tried re-entering port 5000 after about 5 minutes?
Are the phenomena the same?

Link to comment
Share on other sites
Vodka2014 Super Member

Vodka2014

Posted
Posted
1 minute ago, Peter Suh said:

 

 

Usually in these cases a few minutes of waiting time is really necessary.
Have you tried re-entering port 5000 after about 5 minutes?
Are the phenomena the same?

 

Yes i get re-directed to 5001 and the same thing. I do hear the disks. When i log in via Putty that works and i look at my volumes everything is blank. Seems like all the services are just dead.

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted
4 minutes ago, Vodka2014 said:

 

Yes i get re-directed to 5001 and the same thing. I do hear the disks. When i log in via Putty that works and i look at my volumes everything is blank. Seems like all the services are just dead.

 

Wasn't the problem of disks being mixed up in the last HBA still ongoing?
The phenomenon of only some disks being identified in RAID can be fatal.
Did you just rebuild the loader to fix this issue?

Link to comment
Share on other sites
Vodka2014 Super Member

Vodka2014

Posted
Posted
Just now, Peter Suh said:

 

Wasn't the problem of disks being mixed up in the last HBA still ongoing?
The phenomenon of only some disks being identified in RAID can be fatal.
Did you just rebuild the loader to fix this issue?

 

All my disks was found on the HBA and they all showed in DSM no issues with this. It was just the Order in DSM So if it was Drive 9 in DSM it was Port 4 on the server that was the issue but i could live with that for now.

 

When i login via SSH i look for the Partions it seems the Storage Pool is no longer there and the disks are no long there as well. Looks like this all dropped out

 

Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/md0         2385528 1430156    836588  64% /
devtmpfs         2994244       0   2994244   0% /dev
tmpfs            3048436       4   3048432   1% /dev/shm
tmpfs            3048436    8120   3040316   1% /run
tmpfs            3048436       0   3048436   0% /sys/fs/cgroup
tmpfs            3048436     280   3048156   1% /tmp

 

If this is the case then the only option is to rebuild again remove the new disk leave the 3 in the RAID 5 as Degraded. remove the HBA and add the disks back to the onboard and hope and pray.

 

Would you agree ?

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted

Please describe the system environment you are installing and using.
Please provide an example as below, which is my first NAS.

 

1) Xpenology RedPill DS918+ FRIEND DSM 7.2.0-64570 Update 2, 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

 

Additionally, please let me know the type of HBA.
Do you have both Dell Perc H310 / H200?
Recently, it has been reported that the disk disappears intermittently on the H310.

 

 

Link to comment
Share on other sites
Peter Suh Guru Master

Peter Suh

Posted
  • Author
Posted (edited)
6 minutes ago, Vodka2014 said:

DS3622xs+ / HP Microserver GEN8 / Latest IMG / Latest Friend / RAID 5

 

LSI 9211-4i

 

 

 

 

 

I checked your last post.
I also have a 9211-4i with 4 ports supported.
The specifications of this HBA are known to be 6GB/s.
I think You flashed the LSI 9211-8i to use a 12GB/s SAS disk.
Is this method proven?

 

Edited by Peter Suh
Link to comment
Share on other sites
Vodka2014 Super Member

Vodka2014

Posted
Posted
1 minute ago, Peter Suh said:

 

 

I checked your last post.
I also have a 9211-4i with 4 ports supported.
The specifications of this HBA are known to be 6GB/s.
I think I flashed the LSI 9211-8i to use a 12GB/s SAS disk.
Is this method proven?

 

 

I got the card as LSI 9211-8i and then had to re-flash it and flashed it back to LSI 9211-8i. I checked all the info as per all the guides and it flashed 100% if there was an issue it would not boot and the card would be bricked

 

Yes 12GB/s SAS Drives work on this card but at 6gb/s as i had it running on my other system for over a few weeks tons of reboots and never an issue with the same disks

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.   Restore formatting

  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
Go to topic listing
×
×
  • Create New...