Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

Seems your browser is not able to validate the chain of trust. Though, it's a client problem, not a server problem. The build-in LE client in DSM7 should create valid certifcates using the recent issuers. Not sure if this applies to DSM6.2.x as well.

 

Another explanaition is you access you Box, by ip or hostname that doesn't match any of the "Subject Alternative Names". As you surely already know the request URL must match one of the domains in the list of SANs of the certificate.

 

If the above is not the problem, then an outdated browser or ca-certifactes bundle on the client machine might be the issue.

With linux command line clients an outdated openssl version (<1.1.0) can cause the issues. 

 

Edited by haydibe
Link to comment
Share on other sites

Thanks all great masters, that make this easy way to run modern xpenology possible!

 

I successfully run bromolow-7.0.1-42218 on Proxmox 7.1, but have one trouble with dsm vm shutdown. Before I build loader in tinycore I add extention with command "sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://github.com/jum
key/redpill-load/raw/develop/redpill-acpid/rpext-index.json". Everything run fine, but I can't shutdown dsm vm in Proxmox, always get timeout error. Then I was at 6.2.4 with redpill loader and powerbutton 6.2.0002 spk installed shutdown in Proxmox was working. Where should I search to see what's wrong and fix it, if it's possible? Googling this with no luck: powerbutton spk for DSM 7 is absent :(

Link to comment
Share on other sites

2 hours ago, scoobdriver said:

HI Guys , great work . 

 

When I build with @haydibe proxmox method DS918+ 7.0.1 I get the following message during boot (Failed and Depend) . 

Is this normal ? I don't seem to get it when using Esxi ? 

DSM comes up and I am able to log in .

 

474997387_Screenshot2022-01-22at13_07_43.thumb.png.397ba2709ec3a14296b81a3e64362807.png

Had this entries in the logs with Proxmox 7.1.x since day one with apollolake dsm7.x. Regardless if rp-helper or rploader was used. Are you sure those log entries do not exist on EXSi?  

Edited by haydibe
fix typo
Link to comment
Share on other sites

After sussing the full process out this week, and many thanks of course to the OP and contributors, i decided to do a Video of the whole process today for those unsure on how to get this running on Proxmox. Mine is not a complex setup at all so YMMV however the video shows all the steps, which i do slightly differently i think by not using the vmdk image and converting it but using the normal image to boot from. However i have repeated the process many times and it's success each time!. I have not made the video public out of respect to the OP, however any one wanting the link, just message me and i will send.

 

Thanks again, this is absolute top work!

Edited by CassTG
  • Like 1
Link to comment
Share on other sites

2 hours ago, haydibe said:

Had this entries in the logs with Proxmox 7.1.x since day one with apollolake dsm7.x. Regardless if rp-helper or rploader was used. Are you sure those log entries do not exist on EXSi?  

@haydibe yes apologies your correct . I was looking at the output of dmesg for the ESXi build, when I look at the serial output I see the same messages . (Is this written to any of the logs in /var/log/ ? ) 

 

So both appear to be working ok , I am having difficulty with Face recognise in Photos, Iv'e tried the suggestions I have read, to passthrough the GPU as 0000:00:02.0 , that does not seem to work (unless real serial is still needed) , i915 hw transcode is working for Video's, Plex , conversion in Photos etc. so the quicksync aspects are working correctly .  (I'm using mediated passthrough of the integrated GPU which is a coffeelake UHD 630 . ) 

 

Iv'e seen there Is a patch to make face recognition work on the DS918+ using just the cpu , however Iv'e been unable to get that to work also ,  (again not sure if real serial is needed ) . 

That's the only thing that's stopping me running this as a parallel daily driver. 

 

Appeciate All you guys effort, Iv'e been experimenting , and trialing since your docker redpill, and can't thank you guys enough . 

 

I've also got a Gen 8 Microserver with LSI HBA card which I may try some builds on also (Doesn't support HW encoding) and I know another member had some issues kernel panics , so it's still running Juns at the moment , and I need to schedule some down time, in case I need to rollback :)

 

Edit : Oh I can't seem to get Esxi to passthrough the gpu as 0000:00:02.0 , it just seems to revert back when I change pciPassthru0.pciSlotNumber = "2" . With Proxmox I can but only under machine type i440 not q35 for some reason. 

 

 

Edited by scoobdriver
Link to comment
Share on other sites

1 hour ago, Kaneske said:

@haydibe interesting, because I noticed mine sends messages, that Protocolls are above set threshold and gives me a warning. In System Log (GUI) is nothing to read about it.

I should have been more precise: in the serial boot log or what you see in dmesg.

 

I have no idea what the Syno Systems Logs show, I don't look at them at all.

Though, I wouldn't be surprised if Syno filtered out (as in dumbed down) the output to not confuse its users. 

Link to comment
Share on other sites

I've seen this happening to a few users but wasn't able to zero in on a fix. Any tips?

 

880538581_Screenshot2022-01-23at08_33_13.thumb.png.79cb99f1f71c04dc7c1feb1f53ee55c6.png

I've just one HDD connected to the SATA port of my Intel NUC 10iFNH motherboard. Following installation details:

 

tc@box:~$ cat user_config.json 
{
  "extra_cmdline": {
    "pid": "0x5581",
    "vid": "0x0781",
    "sn": "1230LWN027216",
    "mac1": "001132BFE351",
    "SataPortMap": "3",
    "DiskIdxMap": "00"
  },
  "synoinfo": {

          "internalportcfg" : "0xffff",
          "maxdisks" : "16"

},
  "ramdisk_copy": {

    
}

}
tc@box:~$ lsscsi -Hv
[0]    ahci          
  dir: /sys/class/scsi_host//host0
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata1/host0
[1]    ahci          
  dir: /sys/class/scsi_host//host1
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata2/host1
[2]    ahci          
  dir: /sys/class/scsi_host//host2
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata3/host2
[3]    usb-storage   
  dir: /sys/class/scsi_host//host3
  device dir: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/host3

 

 

Telnet output from the Diskstation:

DiskStation> fdisk -l

Disk /dev/sdc: 149 GB, 160041885696 bytes, 312581808 sectors

19457 cylinders, 255 heads, 63 sectors/track

Units: sectors of 1 * 512 = 512 bytes



Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type

/dev/sdc1 *  0,1,1       1023,254,63         63   48676949   48676887 23.2G  7 HPFS/NTFS

/dev/sdc3    1023,0,2    1023,254,63   48676951  312576704  263899754  125G  7 HPFS/NTFS

Disk /dev/sdu: 29 GB, 30752000000 bytes, 60062500 sectors

29327 cylinders, 64 heads, 32 sectors/track

Units: sectors of 1 * 512 = 512 bytes



Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type

/dev/sdu1 *  0,32,33     6,62,56           2048     100351      98304 48.0M 83 Linux

/dev/sdu2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux

/dev/sdu3    15,205,63   130,138,8       253952    2097151    1843200  900M 83 Linux

 

Edited by synoxpe
formatting
Link to comment
Share on other sites

Hello everyone, today finally after some failed attempts (because I was wrong with the procedure) I was able to install a new diskstation 918+ vers. DSM 7.0.1 in vm mode on virtualbox to test it (I need to install it in baremetal mode on a special server) with an image downloaded from the network, unfortunately I am not able to build it myself and everything is ok, it seems to work correctly and I will test it for a few days with installation tests of the applications I need. I needed to know something for those who have already done it or are aware of it and it is this; having the need to install DSM 7.0.1 on a special machine in baremetal mode where a DSM 6.2.3 up3 version already runs, must a new installation be made or can you do a migration? The migration obviously (as long as everything goes well) is much faster and less expensive in terms of time, obviously for safety I would back up the whole machine but if it were possible to do the migration it would be much better. Does anyone know if it is possible and possibly how ??? Thank you

  • Thanks 1
Link to comment
Share on other sites

Hi all

 

Is there Something special with this loader when you have Intel 10Gb 520 Networkcard ?

Because i have tested all Model with this loader but i cant found my Gen8 with this network card in the network?

With the 1.02 or 1.03b loader all is working without drivberpacks etc.

thank you very much

Edited by nemesis122
Link to comment
Share on other sites

5 hours ago, synoxpe said:

I've seen this happening to a few users but wasn't able to zero in on a fix. Any tips?

 

After seeing the output of lsscsi, I would have used the same user_config.

 

From what I remember NUC's have a single sata connector. I have no idea why the other ports are detected but not functional. As you won't be able to use those ports anyway, I would consider this a cosmetic issue. Though, you probably want to add "sata_remap": "0>2:2>0" as additional entry in "extra_cmdline", to remap your only drive to be detected as drive1 instead of drive3.

 

 

Edited by haydibe
Link to comment
Share on other sites

45 minutes ago, haydibe said:

"sata_remap": "0>2:2>0"

Thanks for trying to help out.

So the user_config now looks like:

{
  "extra_cmdline": {
    "pid": "0x5581",
    "vid": "0x0781",
    "sn": "1330LWN008584",
    "mac1": "001132450C15",
    "sata_remap": "0>2:2>0",
    "SataPortMap": "3",    
    "DiskIdxMap": "00"     
  },                       
  "synoinfo": {
               
          "internalportcfg" : "0xffff",
          "maxdisks" : "16"            
                           
},
  "ramdisk_copy": {
                   

}
 
}

This addition however reduces the GRUB menu to only one option: "Tiny Core Image Build". The RedPill boot entries from USB or SATA are gone.

Link to comment
Share on other sites

Огромное спасибо pocopico за его работу. Благодаря ему, я смог обновить свой древний <Atom D2500> до версии 7.0.1 со второй попытки. Я использовал <sudo ./rploader.sh satamap now>, в первый раз я ничего не исправлял. SataPortMap=4 и это было неверно. Я заменил на число 2, так как у меня 2 диска JBOD array, и всё запустилось! Ещё раз спасибо.

Many thanks to pocopico for his work. Thanks to him, I was able to upgrade my ancient <Atom D2500> to version 7.0.1 on the second attempt. I used <sudo./rploader.sh satamap now>, I didn't fix anything the first time. SataPortMap=4 and it was incorrect. I replaced it with the number 2, since I have 2 JBOD array disks, and everything started! Thanks again.

Edited by ser-40in
mistake
Link to comment
Share on other sites

 

11 minutes ago, synoxpe said:

This addition however reduces the GRUB menu to only one option: "Tiny Core Image Build". The RedPill boot entries from USB or SATA are gone.

 

Pitty seems the paramter (even though it should be a correct one accoring https://gugucomputing.wordpress.com/2018/11/11/experiment-on-sata_args-in-grub-cfg/) is not handled by rp-load. Remove it again a rebuild. Seems there is no "sata_remap" for us in the cards.

 

I am pretty sure rp-load threw an error while building that indicates the error. 

 

 

 

Link to comment
Share on other sites

10 hours ago, synoxpe said:

I've seen this happening to a few users but wasn't able to zero in on a fix. Any tips?

 

880538581_Screenshot2022-01-23at08_33_13.thumb.png.79cb99f1f71c04dc7c1feb1f53ee55c6.png

I've just one HDD connected to the SATA port of my Intel NUC 10iFNH motherboard. Following installation details:

 



tc@box:~$ cat user_config.json 
{
  "extra_cmdline": {
    "pid": "0x5581",
    "vid": "0x0781",
    "sn": "1230LWN027216",
    "mac1": "001132BFE351",
    "SataPortMap": "3",
    "DiskIdxMap": "00"
  },
  "synoinfo": {

          "internalportcfg" : "0xffff",
          "maxdisks" : "16"

},
  "ramdisk_copy": {

    
}

}


tc@box:~$ lsscsi -Hv
[0]    ahci          
  dir: /sys/class/scsi_host//host0
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata1/host0
[1]    ahci          
  dir: /sys/class/scsi_host//host1
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata2/host1
[2]    ahci          
  dir: /sys/class/scsi_host//host2
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata3/host2
[3]    usb-storage   
  dir: /sys/class/scsi_host//host3
  device dir: /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/host3

 

 

Telnet output from the Diskstation:



DiskStation> fdisk -l

Disk /dev/sdc: 149 GB, 160041885696 bytes, 312581808 sectors

19457 cylinders, 255 heads, 63 sectors/track

Units: sectors of 1 * 512 = 512 bytes



Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type

/dev/sdc1 *  0,1,1       1023,254,63         63   48676949   48676887 23.2G  7 HPFS/NTFS

/dev/sdc3    1023,0,2    1023,254,63   48676951  312576704  263899754  125G  7 HPFS/NTFS

Disk /dev/sdu: 29 GB, 30752000000 bytes, 60062500 sectors

29327 cylinders, 64 heads, 32 sectors/track

Units: sectors of 1 * 512 = 512 bytes



Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type

/dev/sdu1 *  0,32,33     6,62,56           2048     100351      98304 48.0M 83 Linux

/dev/sdu2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux

/dev/sdu3    15,205,63   130,138,8       253952    2097151    1843200  900M 83 Linux

 

Try SataPortMap 1 and drop the sataremap

Edited by chickey
Link to comment
Share on other sites

9 hours ago, PincoPalla said:

must a new installation be made or can you do a migration?

I am still testing on a N54L. I have created a 6.2.3 system on a spare disk and then migrated it to 7.0.1. There were a number of packages that wouldn't upgrade but that is nothing to do with Xpenology.

Everything else seemed to work. But I haven't run it for long.

And yes. When/if I do it, I will have a full backup and I will keep that up to date in case I have to fall back later.

Link to comment
Share on other sites

@synoxpe so the tinycore bootloader entry disapeared as well? I understood it still exist and you can still start tinycore. What error does it give you when you try to build after sata_remap is removed?

 

@Kaneske I have no idea. I don't use ESXi since I switched to Proxmox. Actualy I am surprised that no one created a rp-extension for the open-vm-tools so far. I assume it's the way to go.

 

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