Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

On 6/22/2022 at 6:32 AM, cferra said:

That card should be supported in dsm I believe according to the compatibility list.  Try removing the detected extension before you build. 
 

you make also have to remove the line in the xml “disable 10g nic” to get it to work

Hi Cferra, may I know the command to remove detected extension before building the image? thanks very much for your help in advance.🙏

Link to comment
Share on other sites

3 minutes ago, Rebutia said:

Hi Cferra, may I know the command to remove detected extension before building the image? thanks very much for your help in advance.🙏

I'm having a similar problem to yours and I don't want it to build certain drivers

Link to comment
Share on other sites

TC now extends the DTC support model to the full model.

 

5 Models Known as Non-DTC Supported Models
Also on DS918+, DS3615xs, DS3617xs, DS3622xs+, DVA3221
When only the model.dtb file is copied to the /etc.defaults/ and /var/run/ directories,
The sataport starts working in the device tree.

 

Please refer to the topic below for details.

 

 

Link to comment
Share on other sites

On 6/17/2022 at 10:35 AM, Bose321 said:

I've added these to my Unraid setup, and everything works great, except for the shutdown/reboot commands etc. They're not doing anything I'm afraid.

 

Any idea what's missing here?

as dodo-dk says, his acpid is working correctly with 3622. The one on pocopico is not working 

 

On 6/17/2022 at 11:11 AM, dodo-dk said:

@Bose321 test this one

https://raw.githubusercontent.com/dodo-dk/rp-ext/main/acpid/rpext-index.json

 

I think the dodo-dk code should be imported to pocopino code to avoid confusions

Link to comment
Share on other sites

Running a baremetal , trying to install 7.1

Had DS918 6.2 before no problems with jun's loader

If I run the satamap now i get  the following:

Found "00:1f.2 Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)"
Detected 6 ports/4 drives. Bad ports: 3 4. Override # of ports or ENTER to accept <6> 4

Computed settings:
SataPortMap=4
DiskIdxMap=00

WARNING: Bad ports are mapped. The DSM installation will fail!

Should i update the user_config.json with these values ? [Yy/Nn] y
Done.

The DSM will not install because it keeps detecting some error on drives 3 and 4 saying that it has disabled them and wants me to remove the faulty drives ( they are fine btw)  and im stuck

If i go bac to TC i run the satamap command and pick "=2", I recompile 7.1 and  it installs fine but DSM will not show the other 2 HDDs, BIOS detection is fine for all 4 HDDs

What exactly are those "Bad ports" ?

I think I might be getting back to 6.2 but I would love to have 7.1 as main.

Edited by SayonaRrRa
Link to comment
Share on other sites

3 hours ago, SayonaRrRa said:

Running a baremetal , trying to install 7.1

Had DS918 6.2 before no problems with jun's loader

If I run the satamap now i get  the following:

Found "00:1f.2 Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)"
Detected 6 ports/4 drives. Bad ports: 3 4. Override # of ports or ENTER to accept <6> 4

Computed settings:
SataPortMap=4
DiskIdxMap=00

WARNING: Bad ports are mapped. The DSM installation will fail!

Should i update the user_config.json with these values ? [Yy/Nn] y
Done.

The DSM will not install because it keeps detecting some error on drives 3 and 4 saying that it has disabled them and wants me to remove the faulty drives ( they are fine btw)  and im stuck

If i go bac to TC i run the satamap command and pick "=2", I recompile 7.1 and  it installs fine but DSM will not show the other 2 HDDs, BIOS detection is fine for all 4 HDDs

What exactly are those "Bad ports" ?

I think I might be getting back to 6.2 but I would love to have 7.1 as main.

 

H81 chipset, right? Both Intel's H61 and H81 had 2 ports hardcoded as disabled. But the disabled ports were still exposed on software side, this can make DSM complain about internal disks being broken.

 

Fortunately they are positioned after the first 2 ports so you can use SataPortMap=1 or 2 to install DSM, then rebuild the loader with SataPortMap=6(should be 6, if not then try 4) and remap the latter 2 working ports into drive 3 and 4.(use sata_remap=4\>2:5\>3 ) There were some motherboards where the first ports are disabled(usually mapped into M.2 ports), making it almost impossible to get baremetal working, unless you use Device Tree platforms.

 

Method from @ikky_phoenix:

 

 

 

  • Thanks 1
Link to comment
Share on other sites

On 6/21/2022 at 6:11 PM, neonflx said:

I just tried on my supermicro X10SDV-6C+-TLN4F which has been running 3622 7.0.1 for a while built back about 3 months ago, not using TCRP, wanted to upgrade to 7.1 and used TCRP but can't find 10gb network card using 3622 so I used 3617 with that I can find network but can't find any drives , so I just plug back my old usb and still running 7.0.1

any suggestions

 

 

Same issue for me with a Supermicro X10SDV-TLN4F except mine is currently on DSM 6.2.3. What loader did you use for 7.0.1?

Link to comment
Share on other sites

9 hours ago, vbz14216 said:

 

H81 chipset, right? Both Intel's H61 and H81 had 2 ports hardcoded as disabled. But the disabled ports were still exposed on software side, this can make DSM complain about internal disks being broken.

 

Fortunately they are positioned after the first 2 ports so you can use SataPortMap=1 or 2 to install DSM, then rebuild the loader with SataPortMap=6(should be 6, if not then try 4) and remap the latter 2 working ports into drive 3 and 4.(use sata_remap=4\>2:5\>3 ) There were some motherboards where the first ports are disabled(usually mapped into M.2 ports), making it almost impossible to get baremetal working, unless you use Device Tree platforms.

 

Method from @ikky_phoenix:

 

 

 

Thank you so much, I will post about the results. I wonder, now that I got it working back to 6.2, raid 1 (2x drives),and hot spare for the raid, ssd cache with 1x drive , will it play nice if I try to upgrade and migrate. I could easily just wipe the drives, I wonder if it was a stable viable solution given the alternative and having to jump through the remapping hoops.

Link to comment
Share on other sites

After 100 days of issueless operations (yayyy!!), I saw these from dmesg in quick succession from my ds918+ running DSM 7.0.1-42218 Update 2 on Proxmox:

 

kern  :warn  : [Mon Jun 27 13:02:38 2022] No such hdd enable pin. Index: 5
kern  :warn  : [Mon Jun 27 13:02:38 2022] ------------[ cut here ]------------
kern  :warn  : [Mon Jun 27 13:02:38 2022] WARNING: CPU: 1 PID: 4086 at drivers/ata/libata-core.c:453 SYNO_CTRL_HDD_POWERON+0x4f/0x60()
kern  :warn  : [Mon Jun 27 13:02:38 2022] Modules linked in: cmac cifs tun nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE xt_REDIRECT nf_nat_masquerade_ipv4 xt_nat iptable_nat nf_nat_ipv4 nf_nat_redirect nf_nat xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter ip_tables x_tables fuse 8021q vfat fat udf isofs loop vhost_scsi(O) vhost(O) tcm_loop(O) iscsi_target_mod(O) target_core_user(O) target_core_ep(O) target_core_multi_file(O) target_core_file(O) target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) synoacl_vfs(PO) raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx nfsd btrfs ecryptfs zstd_decompress zstd_compress xxhash xor raid6_pq lockd grace rpcsec_gss_krb5 auth_rpcgss sunrpc aesni_intel
kern  :warn  : [Mon Jun 27 13:02:38 2022]  glue_helper lrw gf128mul ablk_helper apollolake_synobios(PO) hid_generic usbhid hid usblp i915 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cfbfillrect cfbcopyarea cfbimgblt drm drm_panel_orientation_quirks iosf_mbi fb fbdev video backlight button uhci_hcd ehci_pci ehci_hcd r8168(O) i2c_algo_bit zram igb(O) e1000e(O) sg dm_snapshot dm_bufio crc_itu_t crc_ccitt psnap p8022 llc hfsplus md4 hmac sit tunnel4 ipv6 flashcache_syno(O) flashcache(O) syno_flashcache_control(O) dm_mod arc4 crc32c_intel cryptd sha256_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_powersave cpufreq_performance processor cpufreq_stats vxlan ip6_udp_tunnel udp_tunnel ip_tunnel etxhci_hcd virtio_scsi(OE) virtio_net(OE) virtio_blk(OE) virtio_pci(OE) virtio_mmio(OE) virtio_ring(OE)
kern  :warn  : [Mon Jun 27 13:02:38 2022]  virtio(OE) usb_storage xhci_pci xhci_hcd usbcore usb_common [last unloaded: apollolake_synobios]
kern  :warn  : [Mon Jun 27 13:02:38 2022] CPU: 1 PID: 4086 Comm: scsi_eh_10 Tainted: P        W  OE   4.4.180+ #42218
kern  :warn  : [Mon Jun 27 13:02:38 2022] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
kern  :warn  : [Mon Jun 27 13:02:38 2022]  0000000000000000 ffff88017830bcb0 ffffffff812ef89d 0000000000000009
kern  :warn  : [Mon Jun 27 13:02:38 2022]  0000000000000000 ffff88017830bce8 ffffffff8105255f 0000000000000bb8
kern  :warn  : [Mon Jun 27 13:02:38 2022]  0000000000000000 0000000000000001 ffff880178978000 0000000000000000
kern  :warn  : [Mon Jun 27 13:02:38 2022] Call Trace:
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff812ef89d>] dump_stack+0x4d/0x70
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff8105255f>] warn_slowpath_common+0x7f/0xb0
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff81052646>] warn_slowpath_null+0x16/0x20
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff8141dcdf>] SYNO_CTRL_HDD_POWERON+0x4f/0x60
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff8142e825>] syno_libata_port_power_ctl+0xc5/0x1a0
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff8142f7c7>] syno_libata_set_deep_sleep+0x2b7/0x9c0
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff81436ee3>] ata_scsi_port_error_handler+0x133/0x1a30
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff8106b0fe>] ? cancel_delayed_work_sync+0xe/0x10
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff81432868>] ? ata_scsi_cmd_error_handler+0x118/0x190
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff8143887b>] ata_scsi_error+0x9b/0xe0
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff813f86f5>] scsi_error_handler+0xa5/0x530
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff81575bcf>] ? __schedule+0x2ef/0x820
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff813f8650>] ? scsi_eh_get_sense+0x170/0x170
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff810700f5>] kthread+0xd5/0xf0
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff81070020>] ? kthread_worker_fn+0x160/0x160
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff81579fef>] ret_from_fork+0x3f/0x80
kern  :warn  : [Mon Jun 27 13:02:38 2022]  [<ffffffff81070020>] ? kthread_worker_fn+0x160/0x160
kern  :warn  : [Mon Jun 27 13:02:39 2022] ---[ end trace 4d3f8f657722e7be ]---
kern  :err   : [Mon Jun 27 13:02:42 2022] ata11: wake up successful, the reset fail can be ignored
kern  :err   : [Mon Jun 27 13:02:45 2022] ata10: wake up from deepsleep, reset link now
kern  :err   : [Mon Jun 27 13:02:48 2022] ata10: wake up successful, the reset fail can be ignore

 

Link to comment
Share on other sites

I'm trying to get my Microserver Gen 8, with a i3-3220T to work, on bare metal DSM 7.1, but I can't seen to manage it.

 

I've configured the onboard B120i RAID adapter to SATA ACHI only, used TCRP 0.8, ds3622xs+ as loader, used the script from @Peter Suh, but everytime I install the .pat from the Synology website, after the reboot, it comes back to the initial UI, so I have to upload the .pat again, and so on, and so on...

 

What am I missing?

Edited by Polyphemus
Link to comment
Share on other sites

On 6/4/2022 at 2:17 PM, rok1 said:

Can this be done from a different computer? My server is headless and is a bit difficult to get a monitor attached. But it's easy to power down the server and boot a laptop to get these postupdates run?

 

On 6/4/2022 at 4:13 PM, pocopico said:

 

Yes. 

Hi Pocopico,

 

I create two VM, VM1 and VM2

 

VM1 run TCRP to build image and extract for VM2

 

After setup in VM2.

downloaded from synology the 7.1.0-42661 update 2

then do manual update inside DSM

After the next reboot I got the page "Welcome back: Click here to migrate your diskstation".

I shutdown VM2

 

And then use VM1 boot into TCRP and run

 

./rploader.sh update now

./rploader.sh fullupgrade now

./rploader.sh backup

./rploader.sh postupdate apollolake-7.1.0-42661

extract image and replace the image in VM2

 

Reboot VM2 

After the next reboot I got the page  "Welcome back: Click here to migrate your diskstation".

confirm migration and reboot.  I got the page  "Welcome back: Click here to migrate your diskstation". again.

 

What step is wrong ?


Thanks

 

Link to comment
Share on other sites

Hello everyone,

 

I need some help with TCRP (0.8.0.3 downloaded yerterday) when i'm supposed to run .rploader.sh postupdate broadwell-7.1.0-42661 (see red part in screenshot "error")

 

I tried with sudo, same result. It seems TCRP doesn't find SDB2 but a fdisk /l prove sdb2 is well mounted.

 

 

Is possible the problem come from SATAMAP configuration ? (Hp microserver Gen10 plus, 4 sata locations, 1 hdd in first location)

 

Thank you for your help.

 

David

error.jpg

disks.jpg

Link to comment
Share on other sites

I was unable to get a 920+ build to detect hard drives beyond the first one on an H270 based motherboard that has 6 ports after install.

 

Without changing a thing in the bios (drives hotplug enabled) a 918+ build was flawless.

Link to comment
Share on other sites

11 hours ago, Pandadoo said:

Hello everyone,

 

I need some help with TCRP (0.8.0.3 downloaded yerterday) when i'm supposed to run .rploader.sh postupdate broadwell-7.1.0-42661 (see red part in screenshot "error")

 

I tried with sudo, same result. It seems TCRP doesn't find SDB2 but a fdisk /l prove sdb2 is well mounted.

 

 

Is possible the problem come from SATAMAP configuration ? (Hp microserver Gen10 plus, 4 sata locations, 1 hdd in first location)

 

Thank you for your help.

 

David

error.jpg

disks.jpg

 

Postupdate is meant to run after you have performed an upgrade from DSM GUI. 

 

 

Link to comment
Share on other sites

@pocopico I have Unraid which is using KVM for Virtual Machines. With Unraid's version 6.9.2 the virtual SATA controller which I passthrough my drives has the PCI address 00.1f.2 it was working fine to me. I updated to Unraid 6.10.3 recently and now when I use the satamap command I am getting the message "Mapping KVM q35 bogus controller after maxdisks".

 

I do not know why this check does not fire when I am on 6.9.2 but is there a specific reason why we flag the 1st controller as bogus?

Link to comment
Share on other sites

3 minutes ago, gadreel said:

@pocopico I have Unraid which is using KVM for Virtual Machines. With Unraid's version 6.9.2 the virtual SATA controller which I passthrough my drives has the PCI address 00.1f.2 it was working fine to me. I updated to Unraid 6.10.3 recently and now when I use the satamap command I am getting the message "Mapping KVM q35 bogus controller after maxdisks".

 

I do not know why this check does not fire when I am on 6.9.2 but is there a specific reason why we flag the 1st controller as bogus?

 

Well actually if i remember correctly the first controller is not the one that KVM is attaching the drives.

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