RedPill Tinycore loader


Recommended Posts

5 hours ago, howudodat said:

Trying to isntall 3622xs+ on proxmox using the below steps:

 

create the guest:


# set vm id
id=930
ver=0.4.6

# create image directory, download and uncomporess
mkdir -p /var/lib/vz/images/${id}
curl --location https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v${ver}.img.gz --output /var/lib/vz/images/${id}/tinycore-redpill.img.gz
gzip --decompress /var/lib/vz/images/${id}/tinycore-redpill.img.gz --keep

# create disk for sata0
pvesm alloc local-lvm ${id} vm-${id}-disk-0 100G

# create vm
qm create ${id} \
  --args "-drive 'if=none,id=synoboot,format=raw,file=/var/lib/vz/images/${id}/tinycore-redpill.img' -device 'qemu-xhci,addr=0x18' -device 'usb-storage,drive=synoboot,bootindex=5'" \
  --cores 2 \
  --cpu host \
  --machine q35 \
  --memory 2048 \
  --name DSM \


  
install tcrp:


./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS3622xs+
./rploader.sh identifyusb now
./rploader.sh satamap now
./rploader.sh build broadwellnk-7.0.1-42218
./rploader.sh clean now
./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/develop/redpill-virtio/rpext-index.json
./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/develop/redpill-acpid/rpext-index.json
./rploader.sh build broadwellnk-7.1.0-42661

 

GRUB shows:


    RedPill DS3622xs v7.1.0-42661 Beta (USB, Verbose)
*    RedPill DS3622xs v7.1.0-42661 Beta (SATA, Verbose)
    TinyCore ...


    
Afterwards when I go to the web page I see:
Welcome!
Set up your Synology DS3622xs+ now
I click on Install and it prompts me for a pat file
So I select and install the pat downloaded from synology and I get error: Failed to install the file is probably corrupt

 

Questions:
1. What is the difference in GRUB between the USB and SATA entries?
2. Are these the right steps to install on proxmox?
3. Why is it asking to install a pat file when it seems that tcrp is downloading that file already for me?

4. and of course, how to fix the error
 

 

4 hours ago, flyride said:

 

- Grub USB is to support a USB key for boot, or an emulated USB key image if desired when virtualized.

- SATA USB is a disk image specifically for VMware as there is no way to emulate a USB key or boot from it.  I don't know if it works on Proxmox.

- PAT file needs to be downloaded by the loader in order to create the loader.  DSM install also needs to use the PAT file.  You can download the necessary pat files and host locally, and push to TCRP install if you don't like pulling it from the internet repeatedly.

- See answer #2, you probably need to emulate or use a physical USB key.  Look for folks that have installed on proxmox.

 

Documentation on this will improve.  I'm working on a general installation document and a VMware addendum. Typically others pitch in with variants for the other hypervisors.

I just posted a tutorial guide with step by step instructions and pictures on how to setup and install on Proxmox. The thread is waiting for approval from the moderators.

I actually did it side by side as I wrote it to verify each and every step. And it all worked 100%.. I will post the link, however I dont know how long it will be until its approved.

 

 

  • Like 2
Link to post
Share on other sites

hi, any try to add more than 16HDD?

i successful install 3615 and add 17HDD - 1 on MB sata and 16 on LSI9201-16i

edit user_config.json

    "SataPortMap": "616",
    "DiskIdxMap": "0001"

          "internalportcfg" : "0x3FFFFFFFF",
          "maxdisks" : "36",

but USB HDDs connecting as internal

Link to post
Share on other sites

 

13 hours ago, Itay1778 said:

Hi, everyone.
I am trying to install DSM 7.1 on bare metal with the help of this guide:


But I seem to be stuck on this screen:

893549598_.thumb.png.595bb0556658da24151709770ab12c42.png
Don't really know what to do... I tried to figure out how to maybe fix it through the previous pages here, but without success
Motherboard model: asrock h91m-plus
The SATA controller supports up to 6 ports but the board has 4 ports and all ports are connected with HDDs
What to do?
And another question when I make a change in user_config.json I need to do build again to save it?

Try This. Build a loader with SataPortMap 1, install with only one hdd on port0, When you install build loader again with sataportmap 4 and connect other drives.

23 hours ago, facelessone said:

 

Thanks you guys. You are great.

I have decided to give DS918+ another try, or more like 10 tries to be correct.

 

I finally manged to install DS918 with "SataPortMap": "1" and only one disk inside. I made a fresh install on a cleaned drive and will move my data around and configure stuff later on.

Later I build a loader again with "SataPortMap": "4" and it boots now and detects other drives. I moved back the drive from DS920+ install with data on and it recovered the pool with no problems.

Still one drive to move from DS3615xs later but I belive it will go without problems.

Link to post
Share on other sites
1 minute ago, facelessone said:

 

Try This. Build a loader with SataPortMap 1, install with only one hdd on port0, When you install build loader again with sataportmap 4 and connect other drives.

Ok, I'll try but just to be sure what to do:
I do the build loader with SataPortMap 1 if it works then continue installing DSM with only one drive then after installation and everything works with one drive then to try to build again with SataPortMap 4? And if I build again then it will not ask me to install DSM again?

Link to post
Share on other sites
Posted (edited)

Exactly. If you manage to install it with one drive, when you build loader again again with sataportmap 4 it will still boot from 1st drive into DSM, but you will see other drives. Make sure the other data in user_config.json stay the same.

 

That's how I got it to work, hope you will to :)

Edited by facelessone
Link to post
Share on other sites
Posted (edited)
33 minutes ago, facelessone said:

Exactly. If you manage to install it with one drive, when you build loader again again with sataportmap 4 it will still boot from 1st drive into DSM, but you will see other drives. Make sure the other data in user_config.json stay the same.

 

That's how I got it to work, hope you will to :)

Thank you!! I succeeded! Everything works, all disks are recognized.
I need to set sataportmap to 6 because this motherboard defines disks 0,1,4,5 so in DSM it shows me Disk 1, DIsk 2, Disk 5, Disk 6
But it doesn't matter to me because I still know who is what.

Edited by Itay1778
Link to post
Share on other sites
Posted (edited)

[Notice]

 

As TC is re-versioned, the method of copying and using modified dts files has changed a little.

 

The modified dts file need to copy it to this folder.

 

custom-module -> /mnt/sdb3/auxfiles

 

If you do that

 

./my.sh DS920+ manual

 

instead

 

./my.sh DS920+

 

It doesn't matter if you remove the manual like this.

 

The reason for using the original manual is to prevent automatic dts mapping in TC like that.

 

Now, if a file copied to a separate directory is found, dtc auto-mapping will stop automatically.

Edited by Peter Suh
Link to post
Share on other sites
Posted (edited)
18 hours ago, Peter Suh said:

[Notice]

 

As TC is re-versioned, the method of copying and using modified dts files has changed a little.

 

The modified dts file need to copy it to this folder.

 

custom-module -> /mnt/sdb3/auxfiles

 

If you do that

 

./my.sh DS920+ manual

 

instead

 

./my.sh DS920+

 

It doesn't matter if you remove the manual like this.

 

The reason for using the original manual is to prevent automatic dts mapping in TC like that.

 

Now, if a file copied to a separate directory is found, dtc auto-mapping will stop automatically.

 

@pocopico

 

I think it's a new feature from version 0.7.0.8.
If I just copy the dts file, which is a text file,
I mistook it as a line that compiles and generates dtb with dtc.
The echo log says they found dts.
Can TC compile it to dtb if we just copy dts?
Wouldn't it be difficult for users to compile with dtc?

Are there any technical difficulties?

 

-------------------------------------------------------------

 

    if [ -f /home/tc/custom-module/${dtbfile}.dtb ]; then

        echo "Fould locally cached dts file"
        read -p "Should i use that file ? [Yy/Nn]" answer
        if [ -n "$answer" ] && [ "$answer" = "Y" ] || [ "$answer" = "y" ]; then
            echo "OK copying over the cached dtb file"

            dtbextfile="$(find /home/tc/redpill-load/custom -name model_${dtbfile}.dtb)"
            if [ ! -z ${dtbextfile} ] && [ -f ${dtbextfile} ]; then
                echo -n "Copying patched dtb file ${dtbfile}.dtb to ${dtbextfile} -> "
                sudo cp /home/tc/custom-module/${dtbfile}.dtb ${dtbextfile}
                if [ $(sha256sum /home/tc/custom-module/${dtbfile}.dtb | awk '{print $1}') = $(sha256sum ${dtbextfile} | awk '{print $1}') ]; then
                    echo -e "OK ! File copied and verified !"
                    return
                else
                    echo -e "ERROR !\nFile has not been copied succesfully, you will need to copy it yourself"
                    return
                fi
            else
                [ -z ${dtbextfile} ] && echo "dtb extension is not loaded and its required for DSM to find disks on ${SYNOMODEL}"
                echo "Copy of the DTB file ${dtbfile}.dtb to ${dtbextfile} was not succesfull."
                echo "Please remember to replace the dtb extension model file ..."
                echo "execute manually : cp ${dtbfile}.dtb ${dtbextfile} and re-run"
                exit 99
            fi
        else
            echo "OK lets continue patching"
        fi
    else
        echo "No cached dtb file found in /home/tc/custom-module/${dtbfile}.dtb"
    fi
 

 

 

Edited by Peter Suh
Link to post
Share on other sites
18 minutes ago, Peter Suh said:

 

@pocopico

 

I think it's a new feature from version 0.7.0.8.
If I just copy the dts file, which is a text file,
I mistook it as a line that compiles and generates dtb with dtc.
The echo log says they found dts.
Can TC compile it to dtb if we just copy dts?
Wouldn't it be difficult for users to compile with dtc?

Are there any technical difficulties?

 

-------------------------------------------------------------

 

    if [ -f /home/tc/custom-module/${dtbfile}.dtb ]; then

        echo "Fould locally cached dts file"
        read -p "Should i use that file ? [Yy/Nn]" answer
        if [ -n "$answer" ] && [ "$answer" = "Y" ] || [ "$answer" = "y" ]; then
            echo "OK copying over the cached dtb file"

            dtbextfile="$(find /home/tc/redpill-load/custom -name model_${dtbfile}.dtb)"
            if [ ! -z ${dtbextfile} ] && [ -f ${dtbextfile} ]; then
                echo -n "Copying patched dtb file ${dtbfile}.dtb to ${dtbextfile} -> "
                sudo cp /home/tc/custom-module/${dtbfile}.dtb ${dtbextfile}
                if [ $(sha256sum /home/tc/custom-module/${dtbfile}.dtb | awk '{print $1}') = $(sha256sum ${dtbextfile} | awk '{print $1}') ]; then
                    echo -e "OK ! File copied and verified !"
                    return
                else
                    echo -e "ERROR !\nFile has not been copied succesfully, you will need to copy it yourself"
                    return
                fi
            else
                [ -z ${dtbextfile} ] && echo "dtb extension is not loaded and its required for DSM to find disks on ${SYNOMODEL}"
                echo "Copy of the DTB file ${dtbfile}.dtb to ${dtbextfile} was not succesfull."
                echo "Please remember to replace the dtb extension model file ..."
                echo "execute manually : cp ${dtbfile}.dtb ${dtbextfile} and re-run"
                exit 99
            fi
        else
            echo "OK lets continue patching"
        fi
    else
        echo "No cached dtb file found in /home/tc/custom-module/${dtbfile}.dtb"
    fi
 

 

 


No it just gives you more control. I can of course add the dts conversion as well. Thanks for the recommendations  

  • Thanks 1
Link to post
Share on other sites
Posted (edited)

Hi guys,

 

I'm having NO luck with redpill on proxmox. I've tried a number of methods:

- qm importdisk the vmdk and assigning it to SATA0

- both the bios and uefi IMG files as virtual usb devices like in this post

- with and without the virtio modules

- different versions and models (ie 918+, DS3622xs+, 7.0.1, 7.1 etc)

 

The TinyCore Image Builder loads up fine. I can go through the update/generate process. Once I reboot out of TinyCore and attempt to load the appropriate RedPill option from the boot menu - it always panics in the exact same spot when loading ahci:

 

[    2.117175] ahci 0000:00:1f.2: version 3.0
[    2.118230] ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode
[    2.119318] ahci 0000:00:1f.2: flags: 64bit ncq only 
[    2.119953] BUG: unable to handle kernel NULL pointer dereference at 0000000000000120
[    2.120301] IP: [<ffffffff813ffefe>] ata_host_start.part.37+0x18e/0x1b0
[    2.121399] PGD 0 
[    2.121399] Oops: 0000 [#1] SMP 
[    2.121399] Modules linked in: redpill(OE)
[    2.121399] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G           OE   4.4.180+ #42661
[    2.121399] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
[    2.125182] task: ffff88007b108000 ti: ffff88007b110000 task.ti: ffff88007b110000
[    2.125182] RIP: 0010:[<ffffffff813ffefe>]  [<ffffffff813ffefe>] ata_host_start.part.37+0x18e/0x1b0
[    2.125182] RSP: 0018:ffff88007b113be8  EFLAGS: 00010246
[    2.125182] RAX: 0000000000000000 RBX: ffff8800351d23d8 RCX: 0000000000000080
[    2.125182] RDX: 0000000000000000 RSI: 000000000000001c RDI: 0000000000000000
[    2.125182] RBP: ffff88007b113c10 R08: ffffffff818a9c60 R09: 0000000000000040
[    2.125182] R10: 00000000000000fa R11: ffffffff81a056ad R12: ffff8800351d23d8
[    2.131324] R13: 000000000000001c R14: ffffffff81428cf0 R15: ffffffff818a9c60
[    2.131324] FS:  0000000000000000(0000) GS:ffff88007dd00000(0000) knlGS:0000000000000000
[    2.131324] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    2.131324] CR2: 0000000000000120 CR3: 00000000357c0000 CR4: 00000000001606f0
[    2.131324] Stack:
[    2.131324]  ffff8800351d23d8 ffff8800351d23d8 000000000000001c ffffffff81428cf0
[    2.131324]  ffffffff818a9c60 ffff88007b113c58 ffffffff81406176 0000000000000202
[    2.131324]  0000000000000080 ffff8800351d23d8 ffff8800351d23d8 000000000000001c
[    2.131324] Call Trace:
[    2.131324]  [<ffffffff81428cf0>] ? ahci_handle_port_intr+0x90/0x90
[    2.131324]  [<ffffffff81406176>] ata_host_activate+0xb6/0x110
[    2.131324]  [<ffffffff81428dfd>] ahci_host_activate+0x4d/0x180
[    2.131324]  [<ffffffff81313a5a>] ? pcibios_set_master+0x5a/0x80
[    2.131324]  [<ffffffff81425ef9>] ahci_init_one+0x9a9/0xdf0
[    2.131324]  [<ffffffff81315d50>] pci_device_probe+0x90/0x100
[    2.131324]  [<ffffffff8139d50a>] driver_probe_device+0xba/0x260
[    2.131324]  [<ffffffff8139d729>] __driver_attach+0x79/0x80
[    2.131324]  [<ffffffff8139d6b0>] ? driver_probe_device+0x260/0x260
[    2.131324]  [<ffffffff8139b7e9>] bus_for_each_dev+0x69/0xa0
[    2.131324]  [<ffffffff8139cf59>] driver_attach+0x19/0x20
[    2.131324]  [<ffffffff8139cbac>] bus_add_driver+0x19c/0x1e0
[    2.131324]  [<ffffffff81932b91>] ? ata_sff_init+0x31/0x31
[    2.131324]  [<ffffffff8139decb>] driver_register+0x6b/0xc0
[    2.131324]  [<ffffffff813147f1>] __pci_register_driver+0x41/0x50
[    2.131324]  [<ffffffff81932baa>] ahci_pci_driver_init+0x19/0x1b
[    2.131324]  [<ffffffff81000340>] do_one_initcall+0x80/0x130
[    2.131324]  [<ffffffff818f56e7>] ? do_early_param+0x90/0x90
[    2.131324]  [<ffffffff818f5faf>] kernel_init_freeable+0x14d/0x1de
[    2.131324]  [<ffffffff8155e50d>] ? rest_init+0x74/0x74
[    2.131324]  [<ffffffff8155e516>] kernel_init+0x9/0xd3
[    2.131324]  [<ffffffff81563baf>] ret_from_fork+0x3f/0x80
[    2.131324]  [<ffffffff8155e50d>] ? rest_init+0x74/0x74
[    2.131324] Code: 39 80 16 00 48 83 eb 08 41 83 ec 01 45 85 e4 79 db 4c 89 f7 e8 c4 10 fa ff 44 89 f8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 48 8b 43 28 <48> 83 b8 20 01 00 00 00 0f 85 f4 fe ff ff e9 67 ff ff ff 41 bf 
[    2.131324] RIP  [<ffffffff813ffefe>] ata_host_start.part.37+0x18e/0x1b0
[    2.131324]  RSP <ffff88007b113be8>
[    2.131324] CR2: 0000000000000120
[    2.131324] ---[ end trace b4d1009b2d916780 ]---
[    2.160499] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
[    2.160499] 
[    2.161484] Kernel Offset: disabled
[    2.161484] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
[    2.161484] 

 

I believe the ahci controller at 0000:00:1f.2 is the default KVM sata controller which doesn't have an option to remove. I've tried attaching the loader to SATA0. Tried passing through 2 different types of physical AHCI controllers but it always panics here.

 

I had no troubles going through the process on ESXi on this exact same hardware, as well as baremetal on this same hardware.

 

Does anyone have any ideas what I might be missing?

Edited by ideasman69
Link to post
Share on other sites

Is there a good guide or post that explains creating a loader for DS920? I would like to try it.

All I know (remember) is having to edit the dts file to point each slot to a individual sata port, and same for any NVME drives for cache...

Link to post
Share on other sites
2 hours ago, ideasman69 said:

Hi guys,

 

I'm having NO luck with redpill on proxmox. I've tried a number of methods:

- qm importdisk the vmdk and assigning it to SATA0

- both the bios and uefi IMG files as virtual usb devices like in this post

- with and without the virtio modules

- different versions and models (ie 918+, DS3622xs+, 7.0.1, 7.1 etc)

 

The TinyCore Image Builder loads up fine. I can go through the update/generate process. Once I reboot out of TinyCore and attempt to load the appropriate RedPill option from the boot menu - it always panics in the exact same spot when loading ahci:

 


[    2.117175] ahci 0000:00:1f.2: version 3.0
[    2.118230] ahci 0000:00:1f.2: AHCI 0001.0000 32 slots 6 ports 1.5 Gbps 0x3f impl SATA mode
[    2.119318] ahci 0000:00:1f.2: flags: 64bit ncq only 
[    2.119953] BUG: unable to handle kernel NULL pointer dereference at 0000000000000120
[    2.120301] IP: [<ffffffff813ffefe>] ata_host_start.part.37+0x18e/0x1b0
[    2.121399] PGD 0 
[    2.121399] Oops: 0000 [#1] SMP 
[    2.121399] Modules linked in: redpill(OE)
[    2.121399] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G           OE   4.4.180+ #42661
[    2.121399] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014
[    2.125182] task: ffff88007b108000 ti: ffff88007b110000 task.ti: ffff88007b110000
[    2.125182] RIP: 0010:[<ffffffff813ffefe>]  [<ffffffff813ffefe>] ata_host_start.part.37+0x18e/0x1b0
[    2.125182] RSP: 0018:ffff88007b113be8  EFLAGS: 00010246
[    2.125182] RAX: 0000000000000000 RBX: ffff8800351d23d8 RCX: 0000000000000080
[    2.125182] RDX: 0000000000000000 RSI: 000000000000001c RDI: 0000000000000000
[    2.125182] RBP: ffff88007b113c10 R08: ffffffff818a9c60 R09: 0000000000000040
[    2.125182] R10: 00000000000000fa R11: ffffffff81a056ad R12: ffff8800351d23d8
[    2.131324] R13: 000000000000001c R14: ffffffff81428cf0 R15: ffffffff818a9c60
[    2.131324] FS:  0000000000000000(0000) GS:ffff88007dd00000(0000) knlGS:0000000000000000
[    2.131324] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    2.131324] CR2: 0000000000000120 CR3: 00000000357c0000 CR4: 00000000001606f0
[    2.131324] Stack:
[    2.131324]  ffff8800351d23d8 ffff8800351d23d8 000000000000001c ffffffff81428cf0
[    2.131324]  ffffffff818a9c60 ffff88007b113c58 ffffffff81406176 0000000000000202
[    2.131324]  0000000000000080 ffff8800351d23d8 ffff8800351d23d8 000000000000001c
[    2.131324] Call Trace:
[    2.131324]  [<ffffffff81428cf0>] ? ahci_handle_port_intr+0x90/0x90
[    2.131324]  [<ffffffff81406176>] ata_host_activate+0xb6/0x110
[    2.131324]  [<ffffffff81428dfd>] ahci_host_activate+0x4d/0x180
[    2.131324]  [<ffffffff81313a5a>] ? pcibios_set_master+0x5a/0x80
[    2.131324]  [<ffffffff81425ef9>] ahci_init_one+0x9a9/0xdf0
[    2.131324]  [<ffffffff81315d50>] pci_device_probe+0x90/0x100
[    2.131324]  [<ffffffff8139d50a>] driver_probe_device+0xba/0x260
[    2.131324]  [<ffffffff8139d729>] __driver_attach+0x79/0x80
[    2.131324]  [<ffffffff8139d6b0>] ? driver_probe_device+0x260/0x260
[    2.131324]  [<ffffffff8139b7e9>] bus_for_each_dev+0x69/0xa0
[    2.131324]  [<ffffffff8139cf59>] driver_attach+0x19/0x20
[    2.131324]  [<ffffffff8139cbac>] bus_add_driver+0x19c/0x1e0
[    2.131324]  [<ffffffff81932b91>] ? ata_sff_init+0x31/0x31
[    2.131324]  [<ffffffff8139decb>] driver_register+0x6b/0xc0
[    2.131324]  [<ffffffff813147f1>] __pci_register_driver+0x41/0x50
[    2.131324]  [<ffffffff81932baa>] ahci_pci_driver_init+0x19/0x1b
[    2.131324]  [<ffffffff81000340>] do_one_initcall+0x80/0x130
[    2.131324]  [<ffffffff818f56e7>] ? do_early_param+0x90/0x90
[    2.131324]  [<ffffffff818f5faf>] kernel_init_freeable+0x14d/0x1de
[    2.131324]  [<ffffffff8155e50d>] ? rest_init+0x74/0x74
[    2.131324]  [<ffffffff8155e516>] kernel_init+0x9/0xd3
[    2.131324]  [<ffffffff81563baf>] ret_from_fork+0x3f/0x80
[    2.131324]  [<ffffffff8155e50d>] ? rest_init+0x74/0x74
[    2.131324] Code: 39 80 16 00 48 83 eb 08 41 83 ec 01 45 85 e4 79 db 4c 89 f7 e8 c4 10 fa ff 44 89 f8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 48 8b 43 28 <48> 83 b8 20 01 00 00 00 0f 85 f4 fe ff ff e9 67 ff ff ff 41 bf 
[    2.131324] RIP  [<ffffffff813ffefe>] ata_host_start.part.37+0x18e/0x1b0
[    2.131324]  RSP <ffff88007b113be8>
[    2.131324] CR2: 0000000000000120
[    2.131324] ---[ end trace b4d1009b2d916780 ]---
[    2.160499] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
[    2.160499] 
[    2.161484] Kernel Offset: disabled
[    2.161484] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
[    2.161484] 

 

I believe the ahci controller at 0000:00:1f.2 is the default KVM sata controller which doesn't have an option to remove. I've tried attaching the loader to SATA0. Tried passing through 2 different types of physical AHCI controllers but it always panics here.

 

I had no troubles going through the process on ESXi on this exact same hardware, as well as baremetal on this same hardware.

 

Does anyone have any ideas what I might be missing?

 

It looks to me like CPU emulation issue. Please follow @haydibeguide. You may find it in his signature.

Link to post
Share on other sites

 

[Notice]

 

M-SHELL's guide has been registered as a separate topic below.

 

For inquiries about use of M-SHELL or request for improvement, please request it in the new topic below.

 

 

 

Link to post
Share on other sites

For DS920+ and DS1621+, TC currently patches the DTS/DTSB for the USB port to which the loader image is connected.  However, the Syno hardware appears to have all physically accessible USB ports defined in the DTS.  Has anyone checked to see if their other USB ports are usable on installs of DS920+ and DS1621+?

 

I'm trying to determine if we need to actively patch all USB ports, not just the loader port (and if so, do we need device connected to each port, or can we just trace out the USB hubs and patch that way).

 

This could also be meaningful for both virtual and passthrough USB ports, not just baremetal.

 

Any practical observations are appreciated.

Link to post
Share on other sites

problem with last rploader.sh

curl: (60) SSL certificate problem: certificate is not yet valid
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
chown: cannot access 'custom_config.json': No such file or directory
chown: cannot access 'global_config.json': No such file or directory
chown: cannot access 'modules.alias.3.json.gz': No such file or directory
chown: cannot access 'modules.alias.4.json.gz': No such file or directory
chown: cannot access 'rpext-index.json': No such file or directory
chown: cannot access 'user_config.json': No such file or directory
chown: cannot access 'dtc': No such file or directory
chown: cannot access 'rploader.sh': No such file or directory
chown: cannot access 'ds1621p.dts': No such file or directory
chown: cannot access 'ds920p.dts': No such file or directory
gzip: modules.alias.*.gz: No such file or directory
chmod: cannot access 'rploader.sh': No such file or directory
Please make sure you are using the latest 1GB img before using backup option
Current /home/tc size is 3.6M , try to keep it less than 1GB as it might not fit into your image
Should i update the sdf with your current files [Yy/Nn]

 

Link to post
Share on other sites
On 5/14/2022 at 2:45 AM, -iliya- said:

hi, any try to add more than 16HDD?

i successful install 3615 and add 17HDD - 1 on MB sata and 16 on LSI9201-16i

edit user_config.json

    "SataPortMap": "616",
    "DiskIdxMap": "0001"

          "internalportcfg" : "0x3FFFFFFFF",
          "maxdisks" : "36",

but USB HDDs connecting as internal

 

The "16" in 616 is invalid.  SataPortMap is only one digit with a maximum of "9"

 

This is not good for LSI9201-16i obviously.  However, SataPortMap = "1" should probably work for you to use 17 HDD. Specifically, if the last PCI controller (must be actually the highest PCI slot) has >9 ports, you can leave that entry on SataPortMap blank and it should use all the ports.

 

I would advise maxdisks of 24 instead of 36 (internalportcfg must be modified accordingly).

  • Confused 1
Link to post
Share on other sites
Posted (edited)
1 hour ago, flyride said:

 

The "16" in 616 is invalid.  SataPortMap is only one digit with a maximum of "9"

 

This is not good for LSI9201-16i obviously.  However, SataPortMap = "1" should probably work for you to use 17 HDD. Specifically, if the last PCI controller (must be actually the highest PCI slot) has >9 ports, you can leave that entry on SataPortMap blank and it should use all the ports.

 

I would advise maxdisks of 24 instead of 36 (internalportcfg must be modified accordingly).

Which one is the "Last" and "Highest" ?  If there are 2, lets say doing lspci and they are listed as 01:00 and 02:00 which is last/highest? or 00:00 and 01:00 ?

(sorry, just trying to fully understand)

Edited by phone guy
Link to post
Share on other sites
2 minutes ago, phone guy said:

Which one is the "Last" and "Highest" ?  If there are 2, lets say doing lspci and they are listed as 01:00 and 02:00 which is last/highest? or 00:00 and 01:00 ?

(sorry, just trying to fully understand)

 

It must be the last controller listed in lspci (top to bottom).

  • Thanks 1
Link to post
Share on other sites
1 час назад, flyride сказал:

The "16" in 616 is invalid.  SataPortMap is only one digit with a maximum of "9"

 

This is not good for LSI9201-16i obviously.  However, SataPortMap = "1" should probably work for you to use 17 HDD. Specifically, if the last PCI controller (must be actually the highest PCI slot) has >9 ports, you can leave that entry on SataPortMap blank and it should use all the ports.

 

I would advise maxdisks of 24 instead of 36 (internalportcfg must be modified accordingly).

616 received after command ./rploader.sh satamap now
with sata enabled on MoBo 6 ports and 16  on 9201-16i

Link to post
Share on other sites
1 minute ago, -iliya- said:

616 received after command ./rploader.sh satamap now
with sata enabled on MoBo 6 ports and 16  on 9201-16i

 

Yes. satamap reported controllers with cards >9 ports incorrectly until very recently.

 

If you ./rploader.sh update now and repeat you will get a different result. 

Link to post
Share on other sites
2 minutes ago, flyride said:

 

It must be the last controller listed in lspci (top to bottom).

So do not add any sataportmap for the last listed pci sata controller and it should use all available ports. Good to have that confirmed. I did exactly that in a vm build using a HBA (8 port) adapter in proxmox. However the disk ordering started at 2, I could never get the disk ordering to start at 1, even though the hba card is the only available sata controller which is being pci pass thru.  It listed all the hdd but starting at 2 (not at 1)

Link to post
Share on other sites
Posted (edited)
7 минут назад, flyride сказал:

If you ./rploader.sh update now and repeat you will get a different result. 

today i have problem with

./rploader.sh update now
Checking Internet Access -> OK
Checking if a newer version exists on the repo -> gzip: modules.alias.3.json.gz: No such file or directory
gzip: modules.alias.4.json.gz: No such file or directory
sha256sum: latestrploader.sh: No such file or directory
There is a newer version of the script on the repo should we use that ? [yY/nN]y
OK, updating, please re-run after updating
cp: cannot stat '/home/tc/latestrploader.sh': No such file or directory
Updating tinycore loader with latest updates
Backing up files to /mnt/sdf3//mydata.tgz

 

13 минуты назад, flyride сказал:

It must be the last controller listed in lspci (top to bottom).

Скрытый текст

00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] (rev 02)
02:00.0 RAID bus controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
04:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41)

9201-16i + 9240-8i in IT mode firmware

Edited by -iliya-
Link to post
Share on other sites
4 minutes ago, phone guy said:

So do not add any sataportmap for the last listed pci sata controller and it should use all available ports

 

Generally you should add a sataportmap entry for each controller.  The current TCRP code will recommend this.

The only case not to do so is the >9 port card as you have described.

 

3 minutes ago, phone guy said:

However the disk ordering started at 2, I could never get the disk ordering to start at 1, even though the hba card is the only available sata controller which is being pci pass thru.  It listed all the hdd but starting at 2 (not at 1)

 

This is dependent on a lot of factors, whether you are trying to use SATABOOT etc.  Script enhancement should help folks move their configurations to a more predictable space.  Testing across the various hypervisors is inconsistent, so there may be some work to do there.

Link to post
Share on other sites
2 minutes ago, -iliya- said:

01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] (rev 02)
02:00.0 RAID bus controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

 

If possible, you need to exchange the slots on these cards if you want to use all the ports on the 9201.  If one of them is embedded, look in BIOS to see if it can be assigned a different PCI slot.

 

Alternatively, you can build using DS1621+ and manually assign each of the slots using DTS/DTB.  This will be automated soon, but not yet.

Link to post
Share on other sites
5 minutes ago, -iliya- said:

today i have problem with

./rploader.sh update now
Checking Internet Access -> OK
Checking if a newer version exists on the repo -> gzip: modules.alias.3.json.gz: No such file or directory
gzip: modules.alias.4.json.gz: No such file or directory
sha256sum: latestrploader.sh: No such file or directory
There is a newer version of the script on the repo should we use that ? [yY/nN]y
OK, updating, please re-run after updating
cp: cannot stat '/home/tc/latestrploader.sh': No such file or directory
Updating tinycore loader with latest updates
Backing up files to /mnt/sdf3//mydata.tgz

 

  lspci (Hide contents)

00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:01.1 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x8 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
01:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2116 PCI-Express Fusion-MPT SAS-2 [Meteor] (rev 02)
02:00.0 RAID bus controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
04:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41)

9201-16i + 9240-8i in IT mode firmware

Based on what @flyride said, I would suggest switching pci slots with your 2 HBA cards, so the 16 port ends up at position 02:00 (where your 8 port card is now)

Link to post
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.