Jump to content
XPEnology Community

Automated RedPill Loader (ARPL)


fbelavenuto

Recommended Posts

On 7/12/2022 at 4:21 PM, pigr8 said:

@fbelavenuto i'm trying the same on a ESXi test enviroment, it detects the mpt3sas but on reboot and dsm boot it shows disk 34 35 36 37 (with sdae sdaj disk numbering) ecc ecc, i tried adding cmdline such as sataportmap and diskidxmap but does not seem to work.

 

any idea?

Try add only SataPortMap=1

  • Like 1
Link to comment
Share on other sites

suggested driver to add (often asked/used)

 

-aqc111 - usb adapter 2.5/5 GBbit

-mlx_compat mlx4_core mlx4_en mlx5_core

-aacraid

-tn40xx - tehuti 10G nic's (can be tricky to have all firmware files integrated for all phy's, i do have as source that usually works  for all cards as i added from different sources)

-9p for virtio drivers  (9pnet 9pnet_virtio 9p virtio)

-ixgbevf, igbvf,,i40evf for virtio

 

  • Like 1
Link to comment
Share on other sites

2 часа назад, fbelavenuto сказал:

ls -la /sys/devices/system/cpu/cpufreq/

 ls -la /sys/devices/system/cpu/cpufreq/
total 0
drwxr-xr-x  6 root root    0 Jul 13 20:43 .
drwxr-xr-x 10 root root    0 Jul 13 20:42 ..
-rw-r--r--  1 root root 4096 Jul 14 11:19 boost
drwxr-xr-x  3 root root    0 Jul 13 20:43 policy0
drwxr-xr-x  3 root root    0 Jul 13 20:43 policy1
drwxr-xr-x  3 root root    0 Jul 13 20:43 policy2
drwxr-xr-x  3 root root    0 Jul 13 20:43 policy3

Link to comment
Share on other sites

Using this I was finally able to get DSM booted up... only for it to say there were no disks. I believe this describes why I am not seeing disks:

Quote
For LSI SAS2008 cards, depending on the actual model, you might need mpt2sas (MPT Fusion SAS 2.0)
or a specific megaraid extension. I'm not 100% sure about this, but the mpt3sas extension should 
work with MPT Fusion SAS 3.0 cards (like a LSI SAS3008 card). I don't know why it defaults to it.

sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json

I am seeing errors when DSM starts about it not finding certain properties of the hard drives. This topic describes what I was seeing 


Is there a way for me to load mpt2sas as an addon through arpl? I saw that it the url needs to point to an .addon - would you be able to generate this for me?

Link to comment
Share on other sites

6 hours ago, use-nas said:

 ls -la /sys/devices/system/cpu/cpufreq/
total 0
drwxr-xr-x  6 root root    0 Jul 13 20:43 .
drwxr-xr-x 10 root root    0 Jul 13 20:42 ..
-rw-r--r--  1 root root 4096 Jul 14 11:19 boost
drwxr-xr-x  3 root root    0 Jul 13 20:43 policy0
drwxr-xr-x  3 root root    0 Jul 13 20:43 policy1
drwxr-xr-x  3 root root    0 Jul 13 20:43 policy2
drwxr-xr-x  3 root root    0 Jul 13 20:43 policy3

Thanks!! There are some bug in my adaptation of misc ext/addon.

Link to comment
Share on other sites

6 hours ago, jrac86 said:

Using this I was finally able to get DSM booted up... only for it to say there were no disks. I believe this describes why I am not seeing disks:

I am seeing errors when DSM starts about it not finding certain properties of the hard drives. This topic describes what I was seeing 


Is there a way for me to load mpt2sas as an addon through arpl? I saw that it the url needs to point to an .addon - would you be able to generate this for me?

For the DS3615xs model, the addon doesn't really exist yet. For the other models there is mpt3sas. Try adding it manually by going to the addon/drivers menu, add an addon, mpt3sas.

 

Link to comment
Share on other sites

15 hours ago, fbelavenuto said:

Try add only SataPortMap=1

 

nope, does not work.

 

i can see the disk using "fdisk -l" (sda sdb sdc sdd sde sdf) but dsm wont install, sais no disk attached.

 

i tried using a usb pendrive as boot disk instead of the vmdk, same thing.

Link to comment
Share on other sites

5 minutes ago, pigr8 said:

 

nope, does not work.

 

i can see the disk using "fdisk -l" (sda sdb sdc sdd sde sdf) but dsm wont install, sais no disk attached.

 

i tried using a usb pendrive as boot disk instead of the vmdk, same thing.

Thanks for the test. Which model are you testing?

Link to comment
Share on other sites

8 hours ago, jrac86 said:

Using this I was finally able to get DSM booted up... only for it to say there were no disks. I believe this describes why I am not seeing disks:

I am seeing errors when DSM starts about it not finding certain properties of the hard drives. This topic describes what I was seeing 


Is there a way for me to load mpt2sas as an addon through arpl? I saw that it the url needs to point to an .addon - would you be able to generate this for me?

 

On kernel versions > 3.x the module for mpt2sas and mpt3sas are merged into one module with a module alias for mpt2sas. 

 

In Bromolow which is the only platform left behind with no kernel upgrade, you can still use mpt2sas. You can try if this solves your issues.

 

Are the disks identified as SAS or SATA inside DSM ? Redpill included a shim for SAS disks. Does this actually work for you ? 

 

 

Link to comment
Share on other sites

49 minutes ago, pocopico said:

 

On kernel versions > 3.x the module for mpt2sas and mpt3sas are merged into one module with a module alias for mpt2sas. 

 

In Bromolow which is the only platform left behind with no kernel upgrade, you can still use mpt2sas. You can try if this solves your issues.

 

Are the disks identified as SAS or SATA inside DSM ? Redpill included a shim for SAS disks. Does this actually work for you ? 

 

 

 

How can I tell if DSM is seeing them as SAS or SATA? Sorry, I am not sure what you mean by a shim for SAS disks... I am new to xpenology and learning as I go along.

 

Let me provide a little more info... I am creating the bootloader with the model DS2422+ and build 42218 during creation. It also detects to download the mpt3sas automatically. However, when it boots, I am seeing the below in the output (which admittedly I am not sure is the root cause, but seems like there is some issue with that addon for the SAS card). DSM boots up fine, but reports that there are no drives detected - it does not see any of the disks from the SAS HBA card. When I did more digging, I came across that other thread that made it seem like my specific card may actually need the mpt2sas instead of mpt3sas. (If I add a virtual disk, DSM sees that, so seems like everything will work once it recognizes the drives from the SAS card)

 

Installing module for LSI MPT Fusion SAS 3.0 Device adapter
[    1.569639] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.569980] mpt3sas: Unknown symbol raid_class_release (err 0)
[    1.574235] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.574586] mpt3sas: Unknown symbol raid_class_release (err 0)
insmod: can't insert '/modules/mpt3sas.ko': unknown symbol in module, or unknown parameter
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory

 

I had been trying to setup using Redpill prior to your utility, but that was as a DS3622xs and I couldnt get DSM to start at all - I believe it was related to the satamap being incorrect and I just did not know enough to get it to work. Will give that a go again as well, but your utility has gotten me closest.

Edited by jrac86
Provided incorrect code - fixed
Link to comment
Share on other sites

11 minutes ago, jrac86 said:

 

How can I tell if DSM is seeing them as SAS or SATA? Sorry, I am not sure what you mean by a shim for SAS disks... I am new to xpenology and learning as I go along.

 

Let me provide a little more info... I am creating the bootloader with the model DS2422+ and build 42218 during creation. It also detects to download the mpt3sas automatically. However, when it boots, I am seeing the below in the output (which admittedly I am not sure is the root cause, but seems like there is some issue with that addon for the SAS card). DSM boots up fine, but reports that there are no drives detected - it does not see any of the disks from the SAS HBA card. When I did more digging, I came across that other thread that made it seem like my specific card may actually need the mpt2sas instead of mpt3sas. (If I add a virtual disk, DSM sees that, so seems like everything will work once it recognizes the drives from the SAS card)

 

Installing module for ACPI bu[    1.568567] mpt3sas: Unknown symbol sas_enable_tlr (err 0)
t[    1.568969] mpt3sas: Unknown symbol sas_port_alloc_num (err 0)
[    1.569391] mpt3sas: Unknown symbol sas_remove_host (err 0)
t[    1.569727] mpt3sas: Unknown symbol sas_phy_alloc (err 0)
[    1.570131] mpt3sas: Unknown symbol sas_phy_free (err 0)
o[    1.570477] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.570876] mpt3sas: Unknown symbol sas_port_add (err 0)
n[    1.571276] mpt3sas: Unknown symbol sas_end_device_alloc (err 0)
[    1.571663] mpt3sas: Unknown symbol sas_read_port_mode_page (err 0)
[    1.572114] mpt3sas: Unknown symbol sas_expander_alloc (err 0)

[    1.572475] mpt3sas: Unknown symbol sas_attach_transport (err 0)
[    1.572856] mpt3sas: Unknown symbol raid_class_release (err 0)
I[    1.573255] mpt3sas: Unknown symbol sas_port_delete (err 0)
[    1.573612] mpt3sas: Unknown symbol sas_rphy_add (err 0)
n[    1.573946] mpt3sas: Unknown symbol sas_port_delete_phy (err 0)
[    1.574382] mpt3sas: Unknown symbol sas_port_add_phy (err 0)
s[    1.574722] mpt3sas: Unknown symbol sas_disable_tlr (err 0)
[    1.575116] mpt3sas: Unknown symbol sas_phy_add (err 0)
t[    1.575442] mpt3sas: Unknown symbol sas_is_tlr_enabled (err 0)
[    1.575804] mpt3sas: Unknown symbol sas_release_transport (err 0)
alling module for LSI MPT Fusion SAS 3.0 Device adapter
[    1.581207] mpt3sas: Unknown symbol sas_enable_tlr (err 0)
[    1.581532] mpt3sas: Unknown symbol sas_port_alloc_num (err 0)
[    1.581857] mpt3sas: Unknown symbol sas_remove_host (err 0)
[    1.582239] mpt3sas: Unknown symbol sas_phy_alloc (err 0)
[    1.582552] mpt3sas: Unknown symbol sas_phy_free (err 0)
[    1.582859] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.583286] mpt3sas: Unknown symbol sas_port_add (err 0)
[    1.583600] mpt3sas: Unknown symbol sas_end_device_alloc (err 0)
[    1.583951] mpt3sas: Unknown symbol sas_read_port_mode_page (err 0)
[    1.584440] mpt3sas: Unknown symbol sas_expander_alloc (err 0)
[    1.584779] mpt3sas: Unknown symbol sas_attach_transport (err 0)
[    1.585200] mpt3sas: Unknown symbol raid_class_release (err 0)
[    1.585545] mpt3sas: Unknown symbol sas_port_delete (err 0)
[    1.585863] mpt3sas: Unknown symbol sas_rphy_add (err 0)
[    1.586259] mpt3sas: Unknown symbol sas_port_delete_phy (err 0)
[    1.586610] mpt3sas: Unknown symbol sas_port_add_phy (err 0)
[    1.586945] mpt3sas: Unknown symbol sas_disable_tlr (err 0)
[    1.587323] mpt3sas: Unknown symbol sas_phy_add (err 0)
[    1.587636] mpt3sas: Unknown symbol sas_is_tlr_enabled (err 0)
[    1.587973] mpt3sas: Unknown symbol sas_release_transport (err 0)
insmod: can't insert '/modules/mpt3sas.ko': unknown symbol in module, or unknown parameter
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory

 

I had been trying to setup using Redpill prior to your utility, but that was as a DS3622xs and I couldnt get DSM to start at all - I believe it was related to the satamap being incorrect and I just did not know enough to get it to work. Will give that a go again as well, but your utility has gotten me closest.

Please update addons and rebuild the loader.

 

Link to comment
Share on other sites

3 minutes ago, fbelavenuto said:

Please update addons and rebuild the loader.

 

I had to fix my previous post.. gave the incorrect output for the LSI SAS Card:

Installing module for LSI MPT Fusion SAS 3.0 Device adapter
[    1.569639] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.569980] mpt3sas: Unknown symbol raid_class_release (err 0)
[    1.574235] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.574586] mpt3sas: Unknown symbol raid_class_release (err 0)
insmod: can't insert '/modules/mpt3sas.ko': unknown symbol in module, or unknown parameter
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory

 

I am going to rebuild now and let you know.

Link to comment
Share on other sites

I did 2 rebuilds, one with just the detected hardware that the utility found (mpt3sas). That gave these errors.

Installing module for LSI MPT Fusion SAS 3.0 Device adapter
[    1.563495] mpt3sas: Unknown symbol sas_enable_tlr (err 0)
[    1.563825] mpt3sas: Unknown symbol sas_port_alloc_num (err 0)
[    1.564240] mpt3sas: Unknown symbol sas_remove_host (err 0)
[    1.564552] mpt3sas: Unknown symbol sas_phy_alloc (err 0)
[    1.564861] mpt3sas: Unknown symbol sas_phy_free (err 0)
[    1.565246] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.565567] mpt3sas: Unknown symbol sas_port_add (err 0)
[    1.565869] mpt3sas: Unknown symbol sas_end_device_alloc (err 0)
[    1.566301] mpt3sas: Unknown symbol sas_read_port_mode_page (err 0)
[    1.566651] mpt3sas: Unknown symbol sas_expander_alloc (err 0)
[    1.566987] mpt3sas: Unknown symbol sas_attach_transport (err 0)
[    1.567373] mpt3sas: Unknown symbol raid_class_release (err 0)
[    1.567702] mpt3sas: Unknown symbol sas_port_delete (err 0)
[    1.568046] mpt3sas: Unknown symbol sas_rphy_add (err 0)
[    1.568361] mpt3sas: Unknown symbol sas_port_delete_phy (err 0)
[    1.568696] mpt3sas: Unknown symbol sas_port_add_phy (err 0)
[    1.569074] mpt3sas: Unknown symbol sas_disable_tlr (err 0)
[    1.569390] mpt3sas: Unknown symbol sas_phy_add (err 0)
[    1.569682] mpt3sas: Unknown symbol sas_is_tlr_enabled (err 0)
[    1.570042] mpt3sas: Unknown symbol sas_release_transport (err 0)
[    1.575209] mpt3sas: Unknown symbol sas_enable_tlr (err 0)
[    1.575591] mpt3sas: Unknown symbol sas_port_alloc_num (err 0)
[    1.575984] mpt3sas: Unknown symbol sas_remove_host (err 0)
[    1.576371] mpt3sas: Unknown symbol sas_phy_alloc (err 0)
[    1.576679] mpt3sas: Unknown symbol sas_phy_free (err 0)
[    1.576979] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.577383] mpt3sas: Unknown symbol sas_port_add (err 0)
[    1.577687] mpt3sas: Unknown symbol sas_end_device_alloc (err 0)
[    1.578062] mpt3sas: Unknown symbol sas_read_port_mode_page (err 0)
[    1.578426] mpt3sas: Unknown symbol sas_expander_alloc (err 0)
[    1.578754] mpt3sas: Unknown symbol sas_attach_transport (err 0)
[    1.579134] mpt3sas: Unknown symbol raid_class_release (err 0)
[    1.579476] mpt3sas: Unknown symbol sas_port_delete (err 0)
[    1.579789] mpt3sas: Unknown symbol sas_rphy_add (err 0)
[    1.580134] mpt3sas: Unknown symbol sas_port_delete_phy (err 0)
[    1.580487] mpt3sas: Unknown symbol sas_port_add_phy (err 0)
[    1.580805] mpt3sas: Unknown symbol sas_disable_tlr (err 0)
[    1.581163] mpt3sas: Unknown symbol sas_phy_add (err 0)
[    1.581457] mpt3sas: Unknown symbol sas_is_tlr_enabled (err 0)
[    1.581784] mpt3sas: Unknown symbol sas_release_transport (err 0)
insmod: can't insert '/modules/mpt3sas.ko': unknown symbol in module, or unknown parameter
insmod: can't insert '/lib/modules/etxhci-hcd.ko'[    1.591787] v1000_synobios: module license '

 

The second build I did (which is from my previous post) was with a few more addons that I manually added (megaraid_sas and mptsas). I got way less errors, but seems like it is looking for etxhci-hcd.ko. Can this be added manually?

 

Installing module for LSI MPT Fusion SAS 3.0 Device adapter
[    1.596302] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.596705] mpt3sas: Unknown symbol raid_class_release (err 0)
[    1.602254] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.602612] mpt3sas: Unknown symbol raid_class_release (err 0)
insmod: can't insert '/modules/mpt3sas.ko': unknown symbol in module, or unknown parameter
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory

 

Link to comment
Share on other sites

1 hour ago, jrac86 said:

I did 2 rebuilds, one with just the detected hardware that the utility found (mpt3sas). That gave these errors.

Installing module for LSI MPT Fusion SAS 3.0 Device adapter
[    1.563495] mpt3sas: Unknown symbol sas_enable_tlr (err 0)
[    1.563825] mpt3sas: Unknown symbol sas_port_alloc_num (err 0)
[    1.564240] mpt3sas: Unknown symbol sas_remove_host (err 0)
[    1.564552] mpt3sas: Unknown symbol sas_phy_alloc (err 0)
[    1.564861] mpt3sas: Unknown symbol sas_phy_free (err 0)
[    1.565246] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.565567] mpt3sas: Unknown symbol sas_port_add (err 0)
[    1.565869] mpt3sas: Unknown symbol sas_end_device_alloc (err 0)
[    1.566301] mpt3sas: Unknown symbol sas_read_port_mode_page (err 0)
[    1.566651] mpt3sas: Unknown symbol sas_expander_alloc (err 0)
[    1.566987] mpt3sas: Unknown symbol sas_attach_transport (err 0)
[    1.567373] mpt3sas: Unknown symbol raid_class_release (err 0)
[    1.567702] mpt3sas: Unknown symbol sas_port_delete (err 0)
[    1.568046] mpt3sas: Unknown symbol sas_rphy_add (err 0)
[    1.568361] mpt3sas: Unknown symbol sas_port_delete_phy (err 0)
[    1.568696] mpt3sas: Unknown symbol sas_port_add_phy (err 0)
[    1.569074] mpt3sas: Unknown symbol sas_disable_tlr (err 0)
[    1.569390] mpt3sas: Unknown symbol sas_phy_add (err 0)
[    1.569682] mpt3sas: Unknown symbol sas_is_tlr_enabled (err 0)
[    1.570042] mpt3sas: Unknown symbol sas_release_transport (err 0)
[    1.575209] mpt3sas: Unknown symbol sas_enable_tlr (err 0)
[    1.575591] mpt3sas: Unknown symbol sas_port_alloc_num (err 0)
[    1.575984] mpt3sas: Unknown symbol sas_remove_host (err 0)
[    1.576371] mpt3sas: Unknown symbol sas_phy_alloc (err 0)
[    1.576679] mpt3sas: Unknown symbol sas_phy_free (err 0)
[    1.576979] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.577383] mpt3sas: Unknown symbol sas_port_add (err 0)
[    1.577687] mpt3sas: Unknown symbol sas_end_device_alloc (err 0)
[    1.578062] mpt3sas: Unknown symbol sas_read_port_mode_page (err 0)
[    1.578426] mpt3sas: Unknown symbol sas_expander_alloc (err 0)
[    1.578754] mpt3sas: Unknown symbol sas_attach_transport (err 0)
[    1.579134] mpt3sas: Unknown symbol raid_class_release (err 0)
[    1.579476] mpt3sas: Unknown symbol sas_port_delete (err 0)
[    1.579789] mpt3sas: Unknown symbol sas_rphy_add (err 0)
[    1.580134] mpt3sas: Unknown symbol sas_port_delete_phy (err 0)
[    1.580487] mpt3sas: Unknown symbol sas_port_add_phy (err 0)
[    1.580805] mpt3sas: Unknown symbol sas_disable_tlr (err 0)
[    1.581163] mpt3sas: Unknown symbol sas_phy_add (err 0)
[    1.581457] mpt3sas: Unknown symbol sas_is_tlr_enabled (err 0)
[    1.581784] mpt3sas: Unknown symbol sas_release_transport (err 0)
insmod: can't insert '/modules/mpt3sas.ko': unknown symbol in module, or unknown parameter
insmod: can't insert '/lib/modules/etxhci-hcd.ko'[    1.591787] v1000_synobios: module license '

 

The second build I did (which is from my previous post) was with a few more addons that I manually added (megaraid_sas and mptsas). I got way less errors, but seems like it is looking for etxhci-hcd.ko. Can this be added manually?

 

Installing module for LSI MPT Fusion SAS 3.0 Device adapter
[    1.596302] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.596705] mpt3sas: Unknown symbol raid_class_release (err 0)
[    1.602254] mpt3sas: Unknown symbol raid_class_attach (err 0)
[    1.602612] mpt3sas: Unknown symbol raid_class_release (err 0)
insmod: can't insert '/modules/mpt3sas.ko': unknown symbol in module, or unknown parameter
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory

 

Please try new alpha release:

https://github.com/fbelavenuto/arpl/releases/tag/v0.2-alpha4

 

Link to comment
Share on other sites

36 minutes ago, fbelavenuto said:

 

I do not see the errors from before, however it is saying there is a recursive fault at the end of loading. I tried rebooting, but same errors

 

    1.984215] CPU: 3 PID: 4051 Comm: kworker/u8:10 Tainted: G      D W  OE   4.4.180+ #42218
[    1.984215] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
[    1.984215] task: ffff88007ba71700 ti: ffff880079f6c000 task.ti: ffff880079f6c000
[    1.984215] RIP: 0010:[<ffffffff81074a2b>]  [<ffffffff81074a2b>] kthread_data+0xb/0x20
[    1.984215] RSP: 0018:ffff880079f6f988  EFLAGS: 00010002
[    1.984215] RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000003
[    1.984215] RDX: ffff88017d005000 RSI: 0000000000000003 RDI: ffff88007ba71700
[    1.984215] RBP: ffff880079f6f988 R08: ffff88017dd963a8 R09: 0000000076357728
[    1.984215] R10: 0000000000000000 R11: 000000000000001a R12: ffff88007ba71700
[    1.984215] R13: ffff88017dd96340 R14: ffff88017dd96340 R15: 0000000000000003
[    1.984215] FS:  0000000000000000(0000) GS:ffff88017dd80000(0000) knlGS:0000000000000000
[    1.984215] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    1.984215] CR2: 0000000000000028 CR3: 000000017ca0a000 CR4: 00000000000006f0
[    1.984215] Stack:
[    1.984215]  ffff880079f6f9a0 ffffffff810709cc 0000000000016340 ffff880079f6f9f0
[    1.984215]  ffffffff815687ab 000000007ba2f078 ffff880079f6f9e8 ffff88007ba71700
[    1.984215]  ffff88007ba71700 ffff880079f6fa40 ffff880079f6f5f0 ffff88017d118000
[    1.984215] Call Trace:
[    1.984215]  [<ffffffff810709cc>] wq_worker_sleeping+0xc/0x90
[    1.984215]  [<ffffffff815687ab>] __schedule+0x36b/0x7a0
[    1.984215]  [<ffffffff81568c06>] schedule+0x26/0x70
[    1.984215]  [<ffffffff8105a096>] do_exit+0x686/0xa60
[    1.984215]  [<ffffffff810081f4>] oops_end+0x84/0xb0
[    1.984215]  [<ffffffff810085c6>] die+0x46/0x60
[    1.984215]  [<ffffffff81005b67>] do_trap+0x137/0x150
[    1.984215]  [<ffffffff81005d42>] do_error_trap+0x72/0xe0
[    1.984215]  [<ffffffff812088ac>] ? internal_create_group+0x2bc/0x2e0
[    1.984215]  [<ffffffff81207e9d>] ? sysfs_warn_dup+0x5d/0x70
[    1.984215]  [<ffffffff810a37ba>] ? vprintk+0x1a/0x20
[    1.984215]  [<ffffffff810a37c9>] ? vprintk_default+0x9/0x10
[    1.984215]  [<ffffffff8112fbb3>] ? printk+0x46/0x4e
[    1.984215]  [<ffffffff8100628b>] do_invalid_op+0x1b/0x20
[    1.984215]  [<ffffffff8156e1f8>] invalid_op+0x18/0x20
[    1.984215]  [<ffffffff812088ac>] ? internal_create_group+0x2bc/0x2e0
[    1.984215]  [<ffffffff812088de>] sysfs_create_group+0xe/0x10
[    1.984215]  [<ffffffff810fc5d4>] blk_trace_init_sysfs+0x14/0x20
[    1.984215]  [<ffffffff812c3192>] blk_register_queue+0x42/0x150
[    1.984215]  [<ffffffff812d0eef>] add_disk+0x1bf/0x460
[    1.984215]  [<ffffffff813c941a>] ? update_autosuspend+0x4a/0x50
[    1.984215]  [<ffffffff813c94ba>] ? __pm_runtime_use_autosuspend+0x4a/0x60
[    1.984215]  [<ffffffff814013a0>] sd_probe_async+0x110/0x1c0
[    1.984215]  [<ffffffff81076be8>] async_run_entry_fn+0x38/0xe0
[    1.984215]  [<ffffffff810781aa>] worker_run_work+0x9a/0xe0
[    1.984215]  [<ffffffff81076bb0>] ? lowest_in_progress+0x70/0x70
[    1.984215]  [<ffffffff8106f99b>] process_one_work+0x1db/0x4e0
[    1.984215]  [<ffffffff8106fccd>] worker_thread+0x2d/0x4a0
[    1.984215]  [<ffffffff8106fca0>] ? process_one_work+0x4e0/0x4e0
[    1.984215]  [<ffffffff81074573>] kthread+0xd3/0xf0
[    1.984215]  [<ffffffff810744a0>] ? kthread_worker_fn+0x160/0x160
[    1.984215]  [<ffffffff8156c92f>] ret_from_fork+0x3f/0x80
[    1.984215]  [<ffffffff810744a0>] ? kthread_worker_fn+0x160/0x160
[    1.984215] Code: c4 4f 00 49 8b 04 24 48 85 c0 75 e6 e9 07 ff ff ff 0f 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 8b 87 c8 04 00 00 55 48 89 e5 <48> 8b 40 d8 5d c3 0f 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 
[    1.984215] RIP  [<ffffffff81074a2b>] kthread_data+0xb/0x20
[    1.984215]  RSP <ffff880079f6f988>
[    1.984215] CR2: ffffffffffffffd8
[    1.984215] ---[ end trace 5c51a3c6de9c3b49 ]---
[    1.984215] Fixing recursive fault but reboot is needed!

 

When I go to find.synology.com, it now is showing a bunch of them, but I cannot connect to any (see attached image). 

 

 

Screenshot 2022-07-14 125932.jpg

Link to comment
Share on other sites

I tried some more and it seems like the recursion error only happens when I have my SAS card attached. If I remove it and just add a virtual disk, find.synology sees one DS2422. I did the DSM install with that one disk and got into DSM. I then shut down and re-added the SAS card, but when I booted up, it gave the recursive error again and find.synology showed several DSMs that did not work (like my previous post). Is this now triggering a DSM instance for each of the attached disks from the HBA card? 

 

I really appreciate the assistance so far and hope that this can be figured out. 

  • Like 1
Link to comment
Share on other sites

This is a nice project unfortunately I can't get it to work on my HP Microserver Gen8. The HP refuses to recognise the USB key as bootable. I used arpl 0.2alpha4 img and tried Rufus, Win32DiskImager, 2 different USB keys and two different ports on the Gen8. 

I then created tcrp img to one of the usb keys using rufus, and the HP boots into tcrp no problems...

 

Any suggestions?

  • Like 1
  • Thanks 1
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.

×
×
  • Create New...