petersuh-q3 / tinycore-redpill

M Shell for tinycore-redpill

Please note that minimum recommended memory size for configuring the loader is 2GB

Instructions

A typical build process starts with:

1. Burn images

   A. To burn physical gunzip and img files to a USB stick

   B. For virtual gunzip use the provided vmdk file

2. Boot Tinycore

3. Loader Building

    A. Choose one of the Synology models.

    B. Create a virtual serial number or enter a prepared serial number.

    C. Select the real mac address of the nic or create a virtual mac address or 
       input the prepared mac address. 
       (If there are 2 nics, you can enter up to the 2nd mac address)

    D. Build the loader.

6. Reboot

< Version History >

1.0.1.1 Fix monitor fuction about ethernet infomation
1.0.1.2 Fix for SA6400
1.0.2.0 Remove restrictions on use of DT-based models when using HBA (apply mpt3sas blacklist instead)
1.0.2.1 Changed extension file organization method
1.0.2.2 Recycle initrd-dsm instead of custom.gz (extract /exts), The priority starts from custom.gz
1.0.2.3 Added RedPill bootloader hard disk porting function
1.0.2.4 Added NVMe bootloader support

tinycore-redpill's Issues

iGPU support for N6005

Hi Peter,

First of all, thank you very much for all the great work you've done.
I'm trying to use a bare metal Intel N6005 board to run a plex host and I can't get HW Transcoding to work.

The /dev/dri device is not found.

Is this a missing driver issue ? and if so is there a way to package the drivers and enable the iGPU ?

I'm a complete new comer to this and would like some help to get pointed in the right direction.

everything else about the system is super stable and DSM 7.2 runs very well on it, so it would be superb if I can get the iGPU enabled.

no internet after booting up

Hi PeterSuh-Q3,

Firstly i really appreciate the work thank you for that!

I have an issue with the loader. Once it loads i see a purple line rops_handle_POLLIN: DELADDR and then the UTP link from the back goes off and i dont have any connection to the IP anymore. Attached a screenshot. Thanks again for the support.

Kind regards

My nic:MT27710 Family [ConnectX-4 Lx] on model:918+ OS:7.2.1 is not working

NIC ConnectX-4 Lx is not working

missing the /dev/dri system drivers folder?

Hello. When I try to locate the /dev/dri system drivers folder in the installed DSM, it cannot be found. I am not sure if this is supposed to be part of the loader install, but if these directories are not present, it seems like it is impossible to use transcoding in Jellyfin. I have tried using both the DS920+ and the DS1520+, both of which are supposed to be able to do transcoding, but both of them do not contain the /dev/dri folder which is required by Jellyfin. Is this something that should be in the loader? Sorry, I am not very knowledgeable with all the technical stuff here, was just hoping I could find a solution to this issue.

Select the Extension

Hi Peter thank you very much for your work :-)
Small Question is there a possibilty to select the extension because you already know on a Gen8 the CPU Scaller Extension is not correct working or is this already fixed ?

g7400cpu cannot load core display normally

Sorry, my English is not very good, use Google Translate to carry on the conversation.
Problem: The hardware is g7400cpu. After installation, nothing can be obtained through dmesg | grep i915. The cpu model is the default epyc, I don’t know if it is affected.

add virtio driver

hi, I know it seem ridiculous.
but please add virtio driver so the installer can read disk from vultr block storage.
it can installed, but cant read vultr drive

thank you

Cannot add ext driver

After install, I'm unable to use the network.
Basically I need to add below driver. However, after I ssh in and add it, after installed and rebooted, I still unable to connect to the NAS due to no network driver after it booting into synology.
./rploader.sh ext ds3615xs-7.1.1-42962 add https://github.com/pocopico/redpill-load/raw/master/redpill-misc/rpext-index.json

DVA3221 GPU GTX1650

no detection of the gtx1650 board

Recent Update caused DSM to reboot randomly

i just notice my DSM7.2 rebooted randomly after a recent update few days ago.

so far i switched to ARPL and seems ok, i believe the recent update with TCRP got some glitch which i dont get any useful log, it just completed reboot itself.

mvsas9485 sub device id is 0x8635 and not 0x9485

Sorry, my controller sub device id is 0x8635 and not 0x9485. Can DSM not load properly solve this problem? thanks

Slot: 01:00.0
Class: Class 0104
Vendor: Vendor 1b4b
Device: Device 9485
SVendor: Unknown vendor 1043
SDevice: Device 8635
Rev: c3

Slot: 02:00.0
Class: Class 0104
Vendor: Vendor 1b4b
Device: Device 9485
SVendor: Unknown vendor 1043
SDevice: Device 8635

Manually modifying the satamap and rebuild does not take effect

The currently set satamap is not read during build execution

i915 issue

After boot kernel panic and can't install DSM due to i915 issue. Is the i915 built into this latest build?

long boot time

Hi,

Thanks for your m-shell, it's very convenient to build a usable loader.

Everytime when I boot the loader, it stay on this status about 5 minutes and then the "boot timeout exceeded, booting...." appears. Is there any way to make the timeout shorter?

[DS918+] iSCSI 관련 이슈입니다.

서버포럼에도 문의글을 올렸었고, 동일증상 문의를 올리신 분이 한분 더 계시긴 합니다만, 혹시나 싶어 이슈 남겨봅니다.
제가 작성한 게시글
다른분의 동일증상 게시글

장비는 오드로이드 H2 (J4105 / RTL8111G Dual) 입니다.
현재 최신 TCRP로 부트로더가 구성되어있고, DS918+ 7.2.1 DSM을 설치해두었습니다.

11월 TCRP 버전으로 구성하여 사용하던 중, 1월 초에 부트로더 업데이트를 위해 재부팅을 실시했고,
이후 부팅이 되지 않는 문제가 발생하였습니다.
그래서 부트로더와 HDD전체를 포맷하고 재설치 후 복원하여 사용하고 있는데요,
이 시점부터 iSCSI의 사용이 불가한 문제가 있습니다.

SAN Manager 상에서는 정상이라고 나오나, 외부에서 NAS 장비에 포트스캔을 해보면 3260포트 자체가 열려있지 않다고 감지되며, 실제로도 윈도우/리눅스/ESXi 모두에서 iSCSI를 검색하지 못합니다.
SAN Manager에서 LUN과 ISCSI를 모두 삭제한 뒤 다시 셋업해보기도 하였고,
최근 서버포럼 게시글에 따라 SAN Manager 자체를 제거한 뒤 재설치해보기도 하였으나, 증상이 동일합니다.

부트로더 자체를 재설치해보아도 문제가 동일한걸 보면, 현재 TCRP 버전에 문제가 있는건가 싶은데,
여기저기 로그를 확인해보아도 별다른 분석이 되지를 않네요.

혹시 확인해볼 부분이나 도움드릴 수 있는 분석파트가 있을까요?

DSM not loading on reboot

Hi,

I tried out your fantastic work. Basically I was using TCRP until 7.1, then I upgraded in the Synology UI to 7.2 U3, then my loader wouldn't boot anymore.

So I went and used ARPL and tried to recreate the loader for 7.2.0-64570 (FRIEND), rebooted, but no DSM loads onto the network.

Any idea?

Thanks!

Build with mpt3sas rather then automaticly found megaraid_sas module

Hi

I want to override megaraid_sas to mpt3sas module.

Some background.
Im using ESXi 8.0u2 with xeon brodwell cpus.
Im choosing the broadwell platform because of the underlying host cpu matches.
Probably unnessecary but its nice to my eyes.
Passthrough LSI 3008 card to the host. ( In IR mode, i can flash it to IT mode but that is tedious :( )

I have tried to get LSI 3008 card working with compiling xpenology with redpill.
The automatic prober wants to use the megaraid_sas module.
But that does not work at all, i need to

rmmod megaraid_sas
insmod megaraid_sas

to get the system to want to install.
And then when rebooted im meet with no disks avalible.
And im in a loop.

SO:

Im trying to add the mpt3sas module and the system will not compile.
./redpill-load/ext-manager.sh add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/mpt3sas/rpext-index.json
OR
./rploader.sh ext rs3618xs-7.1.1-42962 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/mpt3sas/rpext-index.json
It is the same

I see in the repo that there is a module for 4.4.180+ kernel, so anything above DSM-7.1.1 uses a newer kernel, i understand that.
So, trying to add and build 7.1.1 ( i have tried almost every system in the list.... ) the mpt3sas modules spits out the same error.

Now i tested PeterSuh's extentions but it is the same as pocopico, i get the same errors:

tc@box:~$ ./rploader.sh build rs3618xs-7.1.1-42962 static
platform_selected={
  "id": "rs3618xs-7.1.1-42962",
  "platform_name": "broadwell",
  "downloads": {
    "os": {
      "sha256": "2ccd7dc0c33cb133476bce8cdd29db6a164669c0e0caf6fb2daad17202525ec5"
    }
  },
  "add_extensions": [
    {
      "all-modules": "https://raw.githubusercontent.com/PeterSuh-Q3/tcrp-modules/master/all-modules/rpext-index.json",
      "storagepanel": "https://raw.githubusercontent.com/PeterSuh-Q3/tcrp-addons/master/storagepanel/rpext-index.json"
    }
  ]
}
Rploader Version  : 1.0.0.5
Extensions        :   all-modules
  storagepanel
Extensions URL    : "https://raw.githubusercontent.com/PeterSuh-Q3/tcrp-modules/master/all-modules/rpext-index.json",
"https://raw.githubusercontent.com/PeterSuh-Q3/tcrp-addons/master/storagepanel/rpext-index.json"
TARGET_PLATFORM   : rs3618xs
TARGET_VERSION    : 7.1.1
TARGET_REVISION   : 42962
KERNEL_MAJOR      : 4
MODULE_ALIAS_FILE : modules.alias.4.json
SYNOMODEL         : rs3618xs_42962
MODEL             : RS3618xs
KERNEL VERSION    : 4.4.180
Local Cache Folder : /mnt/sda3/auxfiles
DATE Internet     : 09122023 Local : 09122023
Checking Internet Access -> OK
KERNEL VERSION of getredpillko() is 4.4.180, DSMVER is 7.1
Downloading broadwell 4.4.180+ redpill.ko ...
TAG is 23.6.0
'/tmp/rp-broadwell-4.4.180-prod.ko' -> '/home/tc/custom-module/redpill.ko'
static

No extra build option or static specified, using default <static>
Using static compiled redpill extension
'/home/tc/custom-module/redpill.ko' -> '/home/tc/redpill-load/ext/rp-lkm/redpill-linux-v4.4.180+.ko'
Got redpill-linux-v4.4.180+.ko
Testing modules.alias.4.json -> File OK
------------------------------------------------------------------------------------------------
It looks that you will need the following modules :


Ethernet Interface : Required Extension :
Ethernet Interface : Required Extension : vmxnet3
RAID bus Controller : Required Extension : megaraid_sas
LSI Logic / Symbios Logic MegaRAID SAS-3 3008 [Fury]  (rev 02)
------------------------------------------------------------------------------------------------

[#] Updating broadwell_44180 platforms extensions...
[-] The extension PeterSuh-Q3.mpt3sas was found. However, the extension index has no recipe for broadwell_44180 platform. It may not be
[-] supported on that platform, or author didn't updated it for that platform yet. You can try running
[-] "ext-manager.sh update" to refresh indexes for all extensions manually. Below are the currently known information about
[-] the extension stored locally:
[#] ========================================== PeterSuh-Q3.mpt3sas ==========================================
[#] Extension name: mpt3sas
[#] Description: Adds LSI MPT Fusion SAS 3.0 Device Driver Support
[#] To get help visit: <todo>
[#] Extension preparer/packer: https://github.com/PeterSuh-Q3/rp-ext/tree/main/mpt3sas
[#] Software author: https://github.com/PeterSuh-Q3
[#] Update URL: https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/mpt3sas/rpext-index.json
[#] Platforms supported: ds3617xs_42218 dva3221_42962 ds1019p_42218 ds3622xsp_42962 rs3618xs_42962 dva3221_42218 ds3622xsp_42218 rs3413xsp_42218 rs4021xsp_42962 zendofmodel ds3615xs_42962 ds3617xs_42962 rs3618xs_42218 rs4021xsp_42218 dva3219_42962 dva3219_42218 ds1621xsp_42962 ds918p_42962 ds918p_42218 ds1019p_42962 ds1621xsp_42218 rs3413xsp_42962 ds3615xs_42218
[#] =======================================================================================


[-] Failed to update recipe for PeterSuh-Q3.mpt3sas extension for platform broadwell_44180. The script will terminate as you do not
[-] have previously downloaded recipe which can be used if download fails. Try again later. If problem
[-] persists contact the extension packer for support (displayed below)
[#] ========================================== PeterSuh-Q3.mpt3sas ==========================================
[#] Extension name: mpt3sas
[#] Description: Adds LSI MPT Fusion SAS 3.0 Device Driver Support
[#] To get help visit: <todo>
[#] Extension preparer/packer: https://github.com/PeterSuh-Q3/rp-ext/tree/main/mpt3sas
[#] Software author: https://github.com/PeterSuh-Q3
[#] Update URL: https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/mpt3sas/rpext-index.json
[#] Platforms supported: ds3617xs_42218 dva3221_42962 ds1019p_42218 ds3622xsp_42962 rs3618xs_42962 dva3221_42218 ds3622xsp_42218 rs3413xsp_42218 rs4021xsp_42962 zendofmodel ds3615xs_42962 ds3617xs_42962 rs3618xs_42218 rs4021xsp_42218 dva3219_42962 dva3219_42218 ds1621xsp_42962 ds918p_42962 ds918p_42218 ds1019p_42962 ds1621xsp_42218 rs3413xsp_42962 ds3615xs_42218
[#] =======================================================================================

[!] Cannot continue due to previous errors (see above)

*** Process will exit ***
[!] Failed to update all extensions for rs3618xs_42962 platform - see errors above

*** Process will exit ***
FAILED : Loader creation failed check the output for any errors

I have tried to figure out how everyting incorperate with each other but im giving up :)
As the broadwell_44180 specefiy the architecture and 44180 is the kernel.

Everything matches with the info in the mpt3sas repo.

How do i link/add broadwell_44180 with pocopico.mpt3sas/PeterSuh-Q3.mpt3sas to get it to build?
( I got this to work one time after like 6h testing at 4AM but 100 of builds and fiddeling around, i cant replicate it... :( So i need help)

Empty tcrp, can't boot

Thanks for the awesome work!

One week in haven

I managed to install it last week, and was up and running with no Problem. After a power loss when I rebooted it wouldn't boot anymore.

I tried to re-build, re-install the image, different flash drives, etc, but no luck.

Setup

• I'm on bare metal
• flash drive connected another soldered on the Motherboard(unused 1GB)
• Terminal from motherboard

Output

Output on boot

`Loading Linux...
vga=791 is deprecated. Use set gfxpayload=1024x768x16,1024x768 before linux
command instead.
Loading initramfs...
Booting TinyCore Friend
Saving 256 bits of non-creditable seed for next boot
Starting syslogd: OK
Starting acpid: OK
Starting klogd: OK
Running sysctl: OK
Populating /dev using udev: done
Starting system message bus: done
Starting iptables: OK
Starting network: OK
Starting dhcpcd...
dhcpcd-10.0.4 starting
dev: loaded udev
no interfaces have a carrier
Starting connmand: OK
ssh-keygen: generating new host keys: RSA ECDSA ED25519
Starting sshd: OK
Starting SMB services: OK
Starting NMB services: OK

Please press Enter to activate this console. [2024/03/20 20:55:03:0670] N: ttyd 1.7.3 (libwebsockets 4.3.2-2023.08.4)
[2024/03/20 20:55:03:0672] N: tty configuration:
[2024/03/20 20:55:03:0673] N: start command: login -f root
[2024/03/20 20:55:03:0673] N: close signal: SIGHUP (1)
[2024/03/20 20:55:03:0673] N: terminal type: xterm-256color
[2024/03/20 20:55:03:0686] N: /usr/lib/libwebsockets-evlib_uv.so
[2024/03/20 20:55:03:0687] N: lws_create_context: LWS: 4.3.2-2023.08.4, NET CLI SRV H1 H2 WS ConMon IPV6-off
[2024/03/20 20:55:03:0688] N: elops_init_pt_uv: Using foreign event loop...
[2024/03/20 20:55:03:0688] N: __lws_lc_tag: ++ [wsi|0|pipe] (1)
[2024/03/20 20:55:03:0689] N: __lws_lc_tag: ++ [vh|0|netlink] (1)
[2024/03/20 20:55:03:0690] N: __lws_lc_tag: ++ [vh|1|default||7681] (2)
[2024/03/20 20:55:03:0691] N: [vh|1|default||7681]: lws_socket_bind: source ads 0.0.0.0
[2024/03/20 20:55:03:0691] N: __lws_lc_tag: ++ [wsi|1|listen|default||7681] (2)
[2024/03/20 20:55:03:0692] N: Listening on port: 7681`

After boot pressing key / running boot.sh

`root@tcrpfriend:~# ./boot.sh
device node not found
model is not resolved. Please check the /mnt/tcrp/user_config.json file. stopping boot process

!!NOTE: This file is empty!!
root@tcrpfriend:# cat /mnt/tcrp/user_config.json
root@tcrpfriend:#`

Populating user_config.json

At this point I can see the it on the network at \192.168.1.198\tcrpfriend\tcrp
There is an empty user_config.json
I added the same config used at build time.
But both tcrp-p1, and tcrp-p2 are empty observing from the network

Output after config

`root@tcrpfriend:# ./boot.sh device node not found
User config file needs update, updating -> Done
cat: /mnt/tcrp-p1/GRUB_VER: No such file or directory
--------------------------------------={ TinyCore RedPill Friend }=--------------------------------------
TCRP Friend Version : 0.1.0t
0.1.0 friend kernel version up from 5.15.26 to 6.4.16
0.1.0l Modified the kexec option from -a (memory) to -f (file) to accurately load the patched initrd-dsm.
0.1.0m Recycle initrd-dsm instead of custom.gz (extract /exts)
0.1.0n When a loader is inserted into syno disk /dev/sda and /dev/sdb,
change to additionally mount partitions 1,2 and 3 to /dev/sda5,/dev/sda6 and /dev/sdb5.
0.1.0o Added RedPill bootloader hard disk porting function
0.1.0p Added priority search for USB or VMDK bootloader over bootloader injected into HDD
0.1.0q Added support for SHR type to HDD for bootloader injection.
synoboot3 unified to use partition number 4 instead of partition number 5 (1 BASIC + 1 SHR required)
0.1.0r Fix bug of 0.1.0q (Fix typo for partition number 4)
0.1.0s Force the dom_szmax limit of the injected bootloader to be 16GB
0.1.0t Supports bootloader injection with SHR disk only
dom_szmax=32GB (limit size of the injected bootloader)

Model : DS3622xs+, Serial : 20C0SQRTZSWZA, Mac :c1d297c8b765, Build : 7.2.1-69057, Update : 0, LKM : prod
Loader BUS:
CPU,MEM: Intel(R) Atom(TM) CPU D525 @ 1.80GHz [4 Thread(s)], 1.9G Memory
DMI: Iomega Corporation StorCenter Pro xxxx/StorCenter Pro xxxx, BIOS 0122 03/26/2013
SAS/RAID HBAs Count : 0 , NICs Count : 2
System is running in Legacy boot mode
Setting MAC Address from c1:d2:97:c8:b7:65 to c1:d2:97:c8:b7:65 on eth0 (r8169)
Setting MAC Address from c1:d2:97:c8:b7:66 to c1:d2:97:c8:b7:66 on eth1 (r8169)
[2024/03/20 20:59:45:5910] N: rops_handle_POLLIN_netlink: DELADDR
IP Address : 192.168.1.198, Network Interface Card : eth0 [10ec:8168] (r8168
r8169)
IP Address : , Network Interface Card : eth1 [10ec:8168] (r8168
r8169)
ERROR ! /mnt/tcrp-p2/rd.gz file not found, stopping boot process
root@tcrpfriend:#`

Experiments/observations

Honorable mentions in log

When running Re-Install DSM

:: Mounting devtmpfs ... [FAILED]
:: Loading module acpi-cpufreq ... [FAILED]
:: Loading module i40e ... [FAILED]

[ 7.221787] redpill: module verification failed: signature and/or required key missing - tainting kernel

`
Checking ext4 rootfs on /dev/md0
return value: 1
All components of md0 have partition layout above v9.
ForceNewestLayout: Skipped
[ 114.854048] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[ 114.916348] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Mounting /dev/md0 /tmpRoot
[ 115.145681] EXT4-fs (muser_config.json): couldn't mount as ext3 due to feature incompatibilities
[ 115.163855] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: prjquota,rootprjquota,barrier=1
insmod: can't insert '/usr/lib/modu[ 115.209979] eth0: 0xffffc900000ee000, c1:d2:97:c8:b7:6b, IRQ 29
les/r8168.ko': File exists
[ 115.426200] Module [r8168] is removed.
Update OOB FW A success!

Constant error

Some constant warning

I get this every minute or so, but I got it even when the thing was working Maybe from the onboard USB storage

[ 202.162026] usb 8-1: device descriptor read/64, error -110
[ 217.394029] usb 8-1: device descriptor read/64, error -110
[ 217.623029] usb 8-1: new full-speed USB device number 3 using uhci_hcd

Things I tried

• Re-Install DSM of ... to USB and SATA (I'm not sure what is the difference)
• Different Flash Drive
• I had 4 HDDs in RAID 5 I unplugged the others formatted the remaining(from menu.sh), and tried to install it on that(I don't have any more spared)
• Rebuilding with different parameters

Bonus question

Now that I have formatted one of the 4 drives from Raid 5 it should theoretically still be possible to recover the data if I get it working right? Is it complicated?

I've only had a week's worth of data there, but I recovered some old pictures from a failed drive and I'm not sure if it survives an other deep scan

Could someone help me with some guidance, please?
Where should I look for the problem?

user_config.json
When booting Re-install.log

Tiny core friend won't boot without internet access

I have build succesfully the loader. (lastest version)
I can start DSM if the internet connection is allowed on my firewall. But when I disable internet access to the nas and reboot it, tiny core friend is stuck and will not start DSM.

I changed friendautoupdate to false: “friendautoupd”: “false
I tried: “staticboot”: “false” but it is still not booting.
If I enable the internet connection it will boot succesfully.

How can I change this?
It is stuck on:

Press to enter a menu for edit USB/Sata Command Line
Press to enter Junior mode

Pressing e or j is doing nothing.

Strange freezing with MPT3SAS on SA6400

Hi Peter,

Thank you for this awesome loader. I wanted to let you know I've run into some strange freezing and lock ups, while trying to run raid rebuilds and data scrubbing using SA6400.

Is it possible that the MPT3SAS Drivers have some issues still? Below are some of the logs I captured:

2024-01-03T14:46:51+11:00 Beast kernel: [19655.913031] BUG: kernel NULL pointer dereference, address: 0000000000000428
2024-01-03T14:46:51+11:00 Beast kernel: [19655.920157] #PF: supervisor read access in kernel mode
2024-01-03T14:46:51+11:00 Beast kernel: [19655.925382] #PF: error_code(0x0000) - not-present page
2024-01-03T14:46:51+11:00 Beast kernel: [19655.933253] Oops: 0000 [#1] SMP NOPTI
2024-01-03T14:46:51+11:00 Beast kernel: [19655.937018] CPU: 0 PID: 9273 Comm: kworker/u24:3 Tainted: P           OE     5.10.55+ #69057
2024-01-03T14:46:51+11:00 Beast kernel: [19655.945742] Hardware name: System manufacturer System Product Name/ROG STRIX Z370-F GAMING, BIOS 3004 07/12/2021
2024-01-03T14:46:51+11:00 Beast kernel: [19655.956158] Workqueue: raid5wq raid5_do_work [raid456]
2024-01-03T14:46:51+11:00 Beast kernel: [19655.961470] RIP: 0010:handle_stripe_clean_event+0x1ae/0x430 [raid456]
2024-01-03T14:46:51+11:00 Beast kernel: [19655.968129] Code: 87 08 01 00 00 4d 8b b7 30 01 00 00 49 c7 87 30 01 00 00 00 00 00 00 49 89 87 00 01 00 00 4d 85 f6 74 4e 49 8b 87 38 01 00 00 <49> 8b 76 28 48 8b 7b 28 48 8d 50 08 48 39 d6 73 3a 41 8b 46 30 c1
2024-01-03T14:46:51+11:00 Beast kernel: [19655.987458] RSP: 0018:ffffc9000122bbb0 EFLAGS: 00010206
2024-01-03T14:46:51+11:00 Beast kernel: [19655.992837] RAX: 00000003e8c975f0 RBX: ffff88811cdec800 RCX: 0000000000000001
2024-01-03T14:46:51+11:00 Beast kernel: [19656.000027] RDX: 0000000000000002 RSI: ffff88812cc32e80 RDI: ffff88811cdec800
2024-01-03T14:46:51+11:00 Beast kernel: [19656.007331] RBP: ffff88812cc32e80 R08: 0000000000000000 R09: ffff88812cc330f2
2024-01-03T14:46:51+11:00 Beast kernel: [19656.014575] R10: 0000000000000000 R11: 0000000000000000 R12: ffff88812cc32e80
2024-01-03T14:46:51+11:00 Beast kernel: [19656.021877] R13: 0000000000000005 R14: 0000000000000400 R15: ffff88812cc33250
2024-01-03T14:46:51+11:00 Beast kernel: [19656.029158] FS:  0000000000000000(0000) GS:ffff888fe8c00000(0000) knlGS:0000000000000000
2024-01-03T14:46:51+11:00 Beast kernel: [19656.037379] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2024-01-03T14:46:51+11:00 Beast kernel: [19656.043228] CR2: 0000000000000428 CR3: 000000082aa0a003 CR4: 00000000003706f0
2024-01-03T14:46:51+11:00 Beast kernel: [19656.050427] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
2024-01-03T14:46:51+11:00 Beast kernel: [19656.057721] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
2024-01-03T14:46:51+11:00 Beast kernel: [19656.065033] Call Trace:
2024-01-03T14:46:51+11:00 Beast kernel: [19656.067594]  [<ffffffffa1167ec4>] handle_stripe+0xed4/0x2070 [raid456]
2024-01-03T14:46:51+11:00 Beast kernel: [19656.074289]  [<ffffffff810aecb3>] ? __wake_up_common+0x73/0x130
2024-01-03T14:46:51+11:00 Beast kernel: [19656.080280]  [<ffffffffa1169361>] handle_active_stripes.constprop.0+0x301/0x4a0 [raid456]
2024-01-03T14:46:51+11:00 Beast kernel: [19656.088643]  [<ffffffffa116a07c>] raid5_do_work+0x8c/0x1a0 [raid456]
2024-01-03T14:46:51+11:00 Beast kernel: [19656.095149]  [<ffffffff8108e2f8>] worker_run_work+0xb8/0xd0
2024-01-03T14:46:51+11:00 Beast kernel: [19656.100887]  [<ffffffffa1169ff0>] ? raid5d+0xaf0/0xaf0 [raid456]
2024-01-03T14:46:51+11:00 Beast kernel: [19656.107092]  [<ffffffff81080bd3>] process_one_work+0x1d3/0x3c0
2024-01-03T14:46:51+11:00 Beast kernel: [19656.113032]  [<ffffffff81080e0d>] worker_thread+0x4d/0x3e0
2024-01-03T14:46:51+11:00 Beast kernel: [19656.118632]  [<ffffffff81080dc0>] ? process_one_work+0x3c0/0x3c0
2024-01-03T14:46:51+11:00 Beast kernel: [19656.124716]  [<ffffffff8108684d>] kthread+0x12d/0x150
2024-01-03T14:46:51+11:00 Beast kernel: [19656.129879]  [<ffffffff81086720>] ? __kthread_bind_mask+0x60/0x60
2024-01-03T14:46:51+11:00 Beast kernel: [19656.136181]  [<ffffffff8100174f>] ret_from_fork+0x1f/0x30
2024-01-03T14:46:51+11:00 Beast kernel: [19656.141682] Modules linked in: nfnetlink xfrm_user xfrm_algo xt_conntrack xt_addrtype fuse ip6table_filter ip6_tables xt_MASQUERADE xt_REDIRECT xt_nat iptable_nat nf_nat xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter ip_tables x_tables tun nvidia_drm(POE) nvidia_modeset(POE) nvidia_uvm(OE) nvidia(OE) udf isofs cmac cifs synoacl_vfs(O) btrfs adt7475 hwmon_vid raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 8021q vfat fat bonding leds_atmega1608 lrw gf128mul epyc7002_synobios(O) uhci_hcd ehci_pci ehci_hcd be2net bnxt_en(O) bnx2x(O) qede(O) qed(O) mlx5_core(O) mlx4_en(O) mlx4_core(O) atlantic_v2(O) atlantic(O) r8168(O) ixgbe(O) i2c_algo_bit igb(O) dm_crypt essiv sg dm_snapshot dm_bufio crc_itu_t crc_ccitt psnap p8022 llc hfsplus md4 hmac sit tunnel4 ipv6 flashcache_syno(O) syno_flashcache_control(O) dm_mod zstd zstd_compress lzo_rle lzo aesni_intel glue_helper crypto_simd libarc4
2024-01-03T14:46:51+11:00 Beast kernel: [19656.141717]  cryptd ecb authenc des_generic libdes ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance vxlan ip6_udp_tunnel udp_tunnel zram ip_tunnel loop sha256_generic libsha256(OE) synorbd(O) synofsbd(O) mei_pxp(OE) mei_hdcp(OE) uas mei_me(OE) usbhid mei(OE) mpt3sas(OE) hid dmabuf(OE) scsi_transport_sas(OE) e1000e(OE) thermal(OE) usb_storage rtc_cmos(OE) button(OE) xhci_pci xhci_hcd usbcore usb_common [last unloaded: veth]
2024-01-03T14:46:51+11:00 Beast kernel: [19656.269766] CR2: 0000000000000428
2024-01-03T14:46:51+11:00 Beast kernel: [19656.273154] ---[ end trace cbba4ee9d6caaffa ]---
2024-01-03T14:46:51+11:00 Beast kernel: [19656.277855] RIP: 0010:handle_stripe_clean_event+0x1ae/0x430 [raid456]
2024-01-03T14:46:51+11:00 Beast kernel: [19656.284421] Code: 87 08 01 00 00 4d 8b b7 30 01 00 00 49 c7 87 30 01 00 00 00 00 00 00 49 89 87 00 01 00 00 4d 85 f6 74 4e 49 8b 87 38 01 00 00 <49> 8b 76 28 48 8b 7b 28 48 8d 50 08 48 39 d6 73 3a 41 8b 46 30 c1
2024-01-03T14:46:51+11:00 Beast kernel: [19656.303495] RSP: 0018:ffffc9000122bbb0 EFLAGS: 00010206
2024-01-03T14:46:51+11:00 Beast kernel: [19656.308806] RAX: 00000003e8c975f0 RBX: ffff88811cdec800 RCX: 0000000000000001
2024-01-03T14:46:51+11:00 Beast kernel: [19656.316050] RDX: 0000000000000002 RSI: ffff88812cc32e80 RDI: ffff88811cdec800
2024-01-03T14:46:51+11:00 Beast kernel: [19656.323302] RBP: ffff88812cc32e80 R08: 0000000000000000 R09: ffff88812cc330f2
2024-01-03T14:46:51+11:00 Beast kernel: [19656.330578] R10: 0000000000000000 R11: 0000000000000000 R12: ffff88812cc32e80
2024-01-03T14:46:51+11:00 Beast kernel: [19656.337838] R13: 0000000000000005 R14: 0000000000000400 R15: ffff88812cc33250
2024-01-03T14:46:51+11:00 Beast kernel: [19656.345089] FS:  0000000000000000(0000) GS:ffff888fe8c00000(0000) knlGS:0000000000000000
2024-01-03T14:46:51+11:00 Beast kernel: [19656.353328] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2024-01-03T14:46:51+11:00 Beast kernel: [19656.359185] CR2: 0000000000000428 CR3: 000000082aa0a003 CR4: 00000000003706f0
2024-01-03T14:46:51+11:00 Beast kernel: [19656.366434] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
2024-01-03T14:46:51+11:00 Beast kernel: [19656.373704] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
2024-01-03T14:46:51+11:00 Beast kernel: [19656.380967] BUG: sleeping function called from invalid context at include/linux/percpu-rwsem.h:49
2024-01-03T14:46:51+11:00 Beast kernel: [19656.389967] in_atomic(): 0, irqs_disabled(): 1, non_block: 0, pid: 9273, name: kworker/u24:3
2024-01-03T14:46:51+11:00 Beast kernel: [19656.398546] CPU: 0 PID: 9273 Comm: kworker/u24:3 Tainted: P      D    OE     5.10.55+ #69057
2024-01-03T14:46:51+11:00 Beast kernel: [19656.407095] Hardware name: System manufacturer System Product Name/ROG STRIX Z370-F GAMING, BIOS 3004 07/12/2021
2024-01-03T14:46:51+11:00 Beast kernel: [19656.417441] Workqueue: raid5wq raid5_do_work [raid456]
2024-01-03T14:46:51+11:00 Beast kernel: [19656.422668] Call Trace:
2024-01-03T14:46:51+11:00 Beast kernel: [19656.425167]  [<ffffffff81769200>] dump_stack+0x57/0x6a
2024-01-03T14:46:51+11:00 Beast kernel: [19656.430406]  [<ffffffff817597b4>] ___might_sleep.cold+0x8c/0x9d
2024-01-03T14:46:51+11:00 Beast kernel: [19656.436447]  [<ffffffff8107598c>] exit_signals+0x1c/0x1a0
2024-01-03T14:46:51+11:00 Beast kernel: [19656.441948]  [<ffffffff81068628>] do_exit+0xb8/0x9b0
2024-01-03T14:46:51+11:00 Beast kernel: [19656.447008]  [<ffffffff81080dc0>] ? process_one_work+0x3c0/0x3c0
2024-01-03T14:46:51+11:00 Beast kernel: [19656.453125]  [<ffffffff8108684d>] ? kthread+0x12d/0x150
2024-01-03T14:46:51+11:00 Beast kernel: [19656.458445]  [<ffffffff81001777>] rewind_stack_do_exit+0x17/0x20
2024-01-03T14:46:51+11:00 Beast kernel: [19656.464552] RIP: 0000:0x0
2024-01-03T14:46:51+11:00 Beast kernel: [19656.467218] Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
2024-01-03T14:46:51+11:00 Beast kernel: [19656.474209] RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000
2024-01-03T14:46:51+11:00 Beast kernel: [19656.481911] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
2024-01-03T14:46:51+11:00 Beast kernel: [19656.489213] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
2024-01-03T14:46:51+11:00 Beast kernel: [19656.496473] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
2024-01-03T14:46:51+11:00 Beast kernel: [19656.503744] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
2024-01-03T14:46:51+11:00 Beast kernel: [19656.510978] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000

Also captured some other messages:

2024-01-03T15:20:17+11:00 Beast kernel: [  202.204672] synostgd-space[27700]: segfault at 4e46 ip 0000000000004e46 sp 00007fff19310d38 error 14 in synostoraged[55ce72fbd000+6000]
2024-01-03T15:20:17+11:00 Beast kernel: [  202.204676] Code: Unable to access opcode bytes at RIP 0x4e1c.
2024-01-03T15:20:17+11:00 Beast coredump[27711]: Process synostgd-space[27700](/usr/syno/sbin/synostoraged) dumped core on signal [11]. Core file [/volume2/@synostgd-space.synology_epyc7002_sa6400.69057.core.gz]. Cmdline [synostgd-space              ]
2024-01-03T15:20:17+11:00 Beast coredump[27711]: Core file [/volume2/@synostgd-space.synology_epyc7002_sa6400.69057.core.gz] size [804463]
2024-01-03T15:21:53+11:00 Beast kernel: [  298.353449] synostgd-space[29481]: segfault at 4e46 ip 0000000000004e46 sp 00007fff19310d38 error 14 in synostoraged[55ce72fbd000+6000]
2024-01-03T15:21:53+11:00 Beast kernel: [  298.365781] Code: Unable to access opcode bytes at RIP 0x4e1c.
2024-01-03T15:21:53+11:00 Beast coredump[29487]: Process synostgd-space[29481](/usr/syno/sbin/synostoraged) dumped core on signal [11]. Core file [/volume2/@synostgd-space.synology_epyc7002_sa6400.69057.core.gz]. Cmdline [synostgd-space              ]
2024-01-03T15:21:53+11:00 Beast coredump[29487]: Core file [/volume2/@synostgd-space.synology_epyc7002_sa6400.69057.core.gz] size [804658]

I have seen some of the other loaders, RR & ARC, mention they've updated their MPT3SAS Drivers recently due to some issues with the SA6400. Is it possible that there could be a bug with the current ones in your tinycore loader?

Appreciate any help you can provide.

Thank you,

Kills

server rebooted imediate after selecting grub menu 1

friend entry is ok, but for the first 2 entries, the server reboots immediately...

what could be the problem?

DSM 무한재설치 문의드립니다

서버포럼에도 글을 쓰긴 했는데...
여기다가도 올려봅니다.

로그가 길어 별도 첨부파일로 올리겠습니다.

linuxrc.syno.log .txt
messages.txt
messages2.txt
messages3.txt
messages4.txt

cat messages의 경우
각기 여러번 부팅해보며 각각 긁어온 것으로 4회차 분으로 생각하시면 됩니다

설치에 사용한 제품은 인텔 1U서버이고

 

서버 제품명은 R1304RPOSHBN

(https://www.intel.co.kr/content/www/kr/ko/products/sku/71389/intel-server-system-r1304rposhbn/specifications.html)

메인보드는 S1200V3RPO

(https://www.intel.co.kr/content/www/kr/ko/products/sku/71386/intel-server-board-s1200v3rpo/specifications.html)

입니다.

 

CPU는 E3-1240L V3, MEM은 DDR3 2G * 4이며,

장착된 하드디스크는 2TB 4장, 80GB SSD1장 총 5장입니다.

이 중 2TB하드 3장은 proxmox에서 가상화로 돌렸던 헤놀로지에서 RAID5(SHR아님)로 돌렸던 디스크입니다.

별도의 PCI카드는 사용하지 않았으며, 메인보드의 SATA 0,1,2,3에 하드디스크 4개를 꽃았고 SATA5에 SSD를 꽃았습니다.

EUDEV, DDSML, EUDEV + DDSML 모두 시도해보았으며,

모델로는 DS920+, DS918+, DS3622xs+, SA6400을 시도했습니다.

부팅은 USB로 진행했습니다. 

 

증상은,

기존에 DSM에 사용하던 하드디스크임에도 불구하고 마이그레이션을 감지하지 않고 기기를 새로 설정하는 페이지가 뜹니다.
그런데 BTRFS로 이미 포맷되어 있는 디스크라 그런지 초기화를 요구하진 않고, 어쩌다가 한 번 DSM으로 진입하면 내부에 DATA는 모두 살아있음을 확인했습니다.
전원을 내렸다가 올린다던가 하는 식으로 재부팅을 하면 다시 기기설정페이지로 돌아갑니다.
DSM설치 후 재부팅하면 다시 기기설정페이지로 돌아가서 DSM을 무한재설치하게 됩니다.

이것을 계속 반복하고 있습니다.

혹시나 싶어 BIOS에서 AHCI -> Enhanced(Native SATA support)로 변경도 해보았는데.. 효과는 없었습니다.

 

특이사항(?)으로, 맨 처음 로더 빌드 후 DSM설치 -> 재부팅 후 모니터에 출력되는 것 중,

 

Detecting Upgrade : Ramdisk upgrade has been detected and sed : no previous ragexp

zImage upgrade has been detected

 

이렇게 두 줄이 출력됩니다.

신경을 안 썻던거였는진 몰라도.. 제 기억으로 DSM버전이 바뀌거나 하면

Detecting Upgrade : Ramdisk upgrade has been detected 요거 한 줄만 나왔던거같은데...

 

기타 그 외 메모리 오버 없습니다.

 

어떤 정보를 더 드려야 문제 해결이 될지 알려주시면 감사하겠습니다...

Power button and network card sequence

Version: tinycore-redpill.v1.0.0.0.m-shell
Model: DS3622

Power button does not work
The order of network cards cannot be adjusted

Support for DS218+

Can you please add support for DS218+

virtio gpu sa6400 13500 vgpu not work

I build the loader with pve. It can launch successful, but /dev/dri is empty