Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

Hello everyone. I have successfully got DS3622xs+ running. Then I got a weird problem that I can't get the DSM update information. It keeps saying " Connection failed, check your internet connection". Although the package center is functioning well.

Any suggestion is much appreciated~~

Screen Shot 2022-05-26 at 07.23.48.png

Link to comment
Share on other sites

5 hours ago, flyride said:

 

@leang521 I was able to compile and boot DVA3221 with r8169 instead of virtio for network.  But without virtio the scsi data disk won't be accessible. 

 

So unless you want to rebuild for USB/sata0 data disk, we need to wait and see if there is another repo with virtio current platform updates, or the new platforms added to the pocopico fork of redpill-load/virtio.

Okay, I will make another V9FS driver.
But I have a question.
I see you just built a DENVERTON-7.1.0-42661.
And I need to build Denverton-7.0.1-42218, and then build Denverton-7.1.0-42661.
Otherwise, an error will be reported. Is this my special case?

Link to comment
Share on other sites

1 hour ago, vikikang said:

Hello everyone. I have successfully got DS3622xs+ running. Then I got a weird problem that I can't get the DSM update information. It keeps saying " Connection failed, check your internet connection". Although the package center is functioning well.

Any suggestion is much appreciated~~

Screen Shot 2022-05-26 at 07.23.48.png

This is only from the DSM update screen.  RedPill blocks that so that you don't update by accident.  The consequence is that it gives you that error message.

 

In summary, it's by design and nothing is wrong.

Link to comment
Share on other sites

3 minutes ago, flyride said:

You do not need to build them in sequence. You can just build 42661

 

Very frustrated and failed again. The V9FS driver work is good, the NIC work is good, and there is no error in the build.

 

But the disk is not found on installing the webpage.
 

root@x99pve:/etc/pve/qemu-server# cat 108.conf
balloon: 0
bios: ovmf
boot: order=ide2;sata0
cores: 4
cpu: host
ide2: none,media=cdrom
machine: q35
memory: 4096
meta: creation-qemu=6.1.0,ctime=1653357922
name: DVA3221
net0: virtio=00:11:32:7E:6D:DA,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: data-zfs:vm-108-disk-1,backup=0,size=1G
scsi0: data-zfs:vm-108-disk-0,backup=0,size=1200G
serial0: socket
smbios1: uuid=7fb25a1e-5f14-4a3d-9242-5aa88b0ca99a
sockets: 1
vmgenid: 6f42693e-62e8-4b59-a859-840f57244b93

 

 

 

tc@box:~$ ./rploader.sh satamap now
Machine is VIRTUAL Hypervisor=KVM

Found "00:1f.2 Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)"
Detected 6 ports/0 drives. Reserving and disabling KVM q35 bogus controller

Found "06:07.0 Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)"
Detected 6 ports/1 drives. SATABOOT detected. Mapping loader dev after maxdisks
No SATA ports mapped. Setup for compatibility with SCSI/SAS controller mapping.

Recommended settings:
SataPortMap=11
DiskIdxMap=101000

 

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

 

 

 

tc@box:~$ cat user_config.json
{
  "extra_cmdline": {
    "pid": "0xa4a5",
    "vid": "0x0525",
    "sn": "2040SJRVF0Y9J",
    "mac1": "0011329886DD",
    "SataPortMap": "11",
    "DiskIdxMap": "101000"
  },
  "synoinfo": {
    "internalportcfg": "0xffff",
    "maxdisks": "16",
    "support_bde_internal_10g": "no",
    "support_disk_compatibility": "no",
    "support_memory_compatibility": "no"
  },
  "ramdisk_copy": {}
}

 

 

 

SynologyNVR> ifconfig
eth0      Link encap:Ethernet  HWaddr 00:11:32:98:86:DD
          inet addr:192.168.50.129  Bcast:192.168.50.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:294 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:41666 (40.6 KiB)  TX bytes:4906 (4.7 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:300 (300.0 B)  TX bytes:300 (300.0 B)

 

Link to comment
Share on other sites

3 minutes ago, leang521 said:

Very frustrated and failed again. The V9FS driver work is good, the NIC work is good, and there is no error in the build.

 

But the disk is not found on installing the webpage.

I'm sorry you are frustrated.  You did get caught up in some broken repos that took a day or two to get fixed.  You also have done some things in a strange way that would have been avoided if there were better documentation.  I am happy to say that is about to improve.

 

I have exactly replicated your build and it is working fine.

 

You may want to attach a serial console to the VM, reboot and launch.  The serial console will show "SynologyLogin: " and you can use root to access the system as DSM sees it.

 

Then post ls -la /sys/block and we will learn what is happening with your SCSI disk.

 

Link to comment
Share on other sites

16 minutes ago, flyride said:

I'm sorry you are frustrated.  You did get caught up in some broken repos that took a day or two to get fixed.  You also have done some things in a strange way that would have been avoided if there were better documentation.  I am happy to say that is about to improve.

 

I have exactly replicated your build and it is working fine.

 

You may want to attach a serial console to the VM, reboot and launch.  The serial console will show "SynologyLogin: " and you can use root to access the system as DSM sees it.

 

Then post ls -la /sys/block and we will learn what is happening with your SCSI disk.

 

 

 

SynologyNVR> ls -la /sys/block
drwxr-xr-x    2 root     root             0 May 26 01:53 .
dr-xr-xr-x   12 root     root             0 May 26 01:53 ..
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 May 26 01:54 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 May 26 01:54 synoboot -> ../devices/pci0000:00/0000:00:1e.0/0000:05:01.0/0000:06:07.0/ata2/host1/target1:0:0/1:0:0:0/block/synoboot
 

 

 

It is hoped that these tests can provide some help for the improvement of the project. But I have prepared to obey your previous suggestions and use USB to guide.

Link to comment
Share on other sites

34 minutes ago, flyride said:

Ok try ls -la /sys/block/scsi_host

 

Also cat /proc/cmdline

SynologyNVR> ls -la /sys/block
drwxr-xr-x    2 root     root             0 May 26 02:31 .
dr-xr-xr-x   12 root     root             0 May 26 02:31 ..
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram0 -> ../devices/virtual/block/ram0
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram1 -> ../devices/virtual/block/ram1
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram10 -> ../devices/virtual/block/ram10
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram11 -> ../devices/virtual/block/ram11
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram12 -> ../devices/virtual/block/ram12
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram13 -> ../devices/virtual/block/ram13
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram14 -> ../devices/virtual/block/ram14
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram15 -> ../devices/virtual/block/ram15
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram2 -> ../devices/virtual/block/ram2
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram3 -> ../devices/virtual/block/ram3
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram4 -> ../devices/virtual/block/ram4
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram5 -> ../devices/virtual/block/ram5
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram6 -> ../devices/virtual/block/ram6
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram7 -> ../devices/virtual/block/ram7
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram8 -> ../devices/virtual/block/ram8
lrwxrwxrwx    1 root     root             0 May 26 02:32 ram9 -> ../devices/virtual/block/ram9
lrwxrwxrwx    1 root     root             0 May 26 02:32 synoboot -> ../devices/pci0000:00/0000:00:1e.0/0000:05:01.0/0000:06:07.0/ata2/host1/target1:0:0/1:0:0:0/block/synoboot

 


SynologyNVR> ls -la /sys/block/scsi_host
ls: /sys/block/scsi_host: No such file or directory

 


SynologyNVR> cat /proc/cmdline
BOOT_IMAGE=/zImage withefi syno_hw_version=DVA3221 console=ttyS0,115200n8 netif_num=4 earlycon=uart8250,io,0x3f8,115200n8 mac1=0011324C321D sn=2150SJRHX6DRY HddHotplug=0 DiskIdxMap=101000 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 root=/dev/md0 SataPortMap=11

 

Edited by leang521
Link to comment
Share on other sites

3 hours ago, flyride said:

This is only from the DSM update screen.  RedPill blocks that so that you don't update by accident.  The consequence is that it gives you that error message.

 

In summary, it's by design and nothing is wrong.

Much appreciate my friend!

 

All the best!

Link to comment
Share on other sites

@flyride

 

I try to configure according to your suggestion. Building successfully. But the following information appears during the web installation process:

 

        Unable to install DSM
        Unable to install this file, the file may have been damaged.

 

 

root@x99pve:/etc/pve/qemu-server# cat 108.conf
args: -device 'nec-usb-xhci,id=usb-bus0,multifunction=on' -drive 'file=/var/lib/vz/images/108/tinycore-redpill.img,media=disk,format=raw,if=none,id=drive-disk-bootloader' -device 'usb-storage,bus=usb-bus0.0,port=1,drive=drive-disk-bootloader,id=usb-disk-bootloader,bootindex=999,removable=on'
balloon: 0
bios: ovmf
boot: order=ide2
cores: 4
cpu: host
ide2: none,media=cdrom
machine: q35
memory: 4096
meta: creation-qemu=6.1.0,ctime=1653357922
name: DVA3221
net0: rtl8139=00:11:32:0A:F8:DD,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: data-zfs:vm-108-disk-0,backup=0,size=1200G
serial0: socket
smbios1: uuid=7fb25a1e-5f14-4a3d-9242-5aa88b0ca99a
sockets: 1
vmgenid: 6f42693e-62e8-4b59-a859-840f57244b93

 

 

tc@box:~$ ./rploader.sh identifyusb now
Machine is VIRTUAL Hypervisor=KVM
Found QEMU QEMU SerialNumber: 1-0000:00:02.0-1
Vendor ID : 0x46f4 Product ID : 0x0001
Should i update the user_config.json with these values ? [Yy/Nn]
Y
tc@box:~$ ./rploader.sh serialgen DVA3221
Serial Number for Model : 20C0SJRQBS8SN
Mac Address for Model DVA3221 : 00:11:32:0A:F8:DD
Should i update the user_config.json with these values ? [Yy/Nn]
Y
tc@box:~$ ./rploader.sh satamap now
Machine is VIRTUAL Hypervisor=KVM

Found "00:1f.2 Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)"
Detected 6 ports/0 drives. Reserving and disabling KVM q35 bogus controller

Found "06:07.0 Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)"
Detected 6 ports/1 drives. Override # of ports or ENTER to accept <6>

Recommended settings:
SataPortMap=16
DiskIdxMap=1000

Should i update the user_config.json with these values ? [Yy/Nn] Y
Done.
tc@box:~$ cat user_config.json
{
  "extra_cmdline": {
    "pid": "0x0001",
    "vid": "0x46f4",
    "sn": "20C0SJRQBS8SN",
    "mac1": "0011320AF8DD",
    "SataPortMap": "16",
    "DiskIdxMap": "1000"
  },
  "synoinfo": {
    "internalportcfg": "0xffff",
    "maxdisks": "16",
    "support_bde_internal_10g": "no",
    "support_disk_compatibility": "no",
    "support_memory_compatibility": "no"
  },
  "ramdisk_copy": {}
}

 

Edited by leang521
Link to comment
Share on other sites

1 hour ago, leang521 said:

@flyride

 

I try to configure according to your suggestion. Building successfully. But the following information appears during the web installation process:

 

        Unable to install DSM
        Unable to install this file, the file may have been damaged.

 

 

root@x99pve:/etc/pve/qemu-server# cat 108.conf
args: -device 'nec-usb-xhci,id=usb-bus0,multifunction=on' -drive 'file=/var/lib/vz/images/108/tinycore-redpill.img,media=disk,format=raw,if=none,id=drive-disk-bootloader' -device 'usb-storage,bus=usb-bus0.0,port=1,drive=drive-disk-bootloader,id=usb-disk-bootloader,bootindex=999,removable=on'
balloon: 0
bios: ovmf
boot: order=ide2
cores: 4
cpu: host
ide2: none,media=cdrom
machine: q35
memory: 4096
meta: creation-qemu=6.1.0,ctime=1653357922
name: DVA3221
net0: rtl8139=00:11:32:0A:F8:DD,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: data-zfs:vm-108-disk-0,backup=0,size=1200G
serial0: socket
smbios1: uuid=7fb25a1e-5f14-4a3d-9242-5aa88b0ca99a
sockets: 1
vmgenid: 6f42693e-62e8-4b59-a859-840f57244b93

 

 

tc@box:~$ ./rploader.sh identifyusb now
Machine is VIRTUAL Hypervisor=KVM
Found QEMU QEMU SerialNumber: 1-0000:00:02.0-1
Vendor ID : 0x46f4 Product ID : 0x0001
Should i update the user_config.json with these values ? [Yy/Nn]
Y
tc@box:~$ ./rploader.sh serialgen DVA3221
Serial Number for Model : 20C0SJRQBS8SN
Mac Address for Model DVA3221 : 00:11:32:0A:F8:DD
Should i update the user_config.json with these values ? [Yy/Nn]
Y
tc@box:~$ ./rploader.sh satamap now
Machine is VIRTUAL Hypervisor=KVM

Found "00:1f.2 Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)"
Detected 6 ports/0 drives. Reserving and disabling KVM q35 bogus controller

Found "06:07.0 Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)"
Detected 6 ports/1 drives. Override # of ports or ENTER to accept <6>

Recommended settings:
SataPortMap=16
DiskIdxMap=1000

Should i update the user_config.json with these values ? [Yy/Nn] Y
Done.
tc@box:~$ cat user_config.json
{
  "extra_cmdline": {
    "pid": "0x0001",
    "vid": "0x46f4",
    "sn": "20C0SJRQBS8SN",
    "mac1": "0011320AF8DD",
    "SataPortMap": "16",
    "DiskIdxMap": "1000"
  },
  "synoinfo": {
    "internalportcfg": "0xffff",
    "maxdisks": "16",
    "support_bde_internal_10g": "no",
    "support_disk_compatibility": "no",
    "support_memory_compatibility": "no"
  },
  "ramdisk_copy": {}
}

 

 

So far, in my experience, the file corruption message has nothing to do with the actual pat file corruption or the USB PID/VID setting, and it seems to have occurred when the junior did not recognize the disk correctly due to missing or incorrect mapping of SataPortMap or DTC Internal_slot. .

A migration message is expected from a disk with DSM already installed.

Link to comment
Share on other sites

38 minutes ago, Peter Suh said:

 

So far, in my experience, the file corruption message has nothing to do with the actual pat file corruption or the USB PID/VID setting, and it seems to have occurred when the junior did not recognize the disk correctly due to missing or incorrect mapping of SataPortMap or DTC Internal_slot. .

A migration message is expected from a disk with DSM already installed.

I use the new KVM.

Link to comment
Share on other sites

In @pocopico's 0.4.6 img for legacy, the first partition is increased from 48mb to 96mb to secure space for the dtc utility to be copied, and it is an image that has been fully upgraded to the latest version 0.7.1.7.
Download it from the Google link below, decompress the gz and record it on a new USB stick.
And rploader.sh on my Github repo blocks the patchdtc function so that there are no errors like the log above, and also blocks the update of rploader.sh itself.

 

It's for the use of the new dtb util of jumkey

 

[tinycore-redpill.v0.7.1.7.img]

https://drive.google.com/file/d/1Jxr0znrDxkqIhcbFPTyll44VwdvuPBu-/view?usp=sharing

 

tc@box:~$ curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/rploader.sh" --output rploader.sh

 

mkdir /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles; sudo ln -s /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles /home/tc/custom-module;

 

./rploader.sh build geminilake-7.1.0-42661

 

./rploader.sh backup now

 

And

 

Share the tincore-redfill.v0.7.1.7.vmdk file.

For the use of the new dtb util of jumkey

This is a file that increased the first partition from 48MB to 96MB, as shown above in img for legacy.

 

[tinycore-redpill.v0.7.1.7.vmdk]

https://drive.google.com/file/d/1UCOzK1LTjLy3-bD2u5feeGblhqYN5UH_/view?usp=sharing

Link to comment
Share on other sites

12 hours ago, leang521 said:

root@x99pve:/etc/pve/qemu-server# cat 108.conf
balloon: 0
bios: ovmf
boot: order=ide2;sata0
cores: 4
cpu: host
ide2: none,media=cdrom
machine: q35
memory: 4096
meta: creation-qemu=6.1.0,ctime=1653357922
name: DVA3221
net0: virtio=00:11:32:7E:6D:DA,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: data-zfs:vm-108-disk-1,backup=0,size=1G
scsi0: data-zfs:vm-108-disk-0,backup=0,size=1200G
serial0: socket
smbios1: uuid=7fb25a1e-5f14-4a3d-9242-5aa88b0ca99a
sockets: 1
vmgenid: 6f42693e-62e8-4b59-a859-840f57244b93

 

I have repeated your install in both configurations (USB/SATA and SATABOOT/SCSI) on my equipment with no issue.

I did notice one difference back in your SATABOOT/SCSI test, and since you seem to be missing SCSI disk, maybe it is relevant.

 

My VM conf file has "scsihw: virtio-scsi-pci" and yours did not.  I am not a Proxmox expert so I do not know if it matters.

Link to comment
Share on other sites

5 hours ago, Peter Suh said:

In @pocopico's 0.4.6 img for legacy, the first partition is increased from 48mb to 96mb to secure space for the dtc utility to be copied, and it is an image that has been fully upgraded to the latest version 0.7.1.7.
Download it from the Google link below, decompress the gz and record it on a new USB stick.
And rploader.sh on my Github repo blocks the patchdtc function so that there are no errors like the log above, and also blocks the update of rploader.sh itself.

 

It's for the use of the new dtb util of jumkey

 

[tinycore-redpill.v0.7.1.7.img]

https://drive.google.com/file/d/1Jxr0znrDxkqIhcbFPTyll44VwdvuPBu-/view?usp=sharing

 

tc@box:~$ curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/rploader.sh" --output rploader.sh

 

mkdir /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles; sudo ln -s /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles /home/tc/custom-module;

 

./rploader.sh build geminilake-7.1.0-42661

 

./rploader.sh backup now

 

And

 

Share the tincore-redfill.v0.7.1.7.vmdk file.

For the use of the new dtb util of jumkey

This is a file that increased the first partition from 48MB to 96MB, as shown above in img for legacy.

 

[tinycore-redpill.v0.7.1.7.vmdk]

https://drive.google.com/file/d/1UCOzK1LTjLy3-bD2u5feeGblhqYN5UH_/view?usp=sharing

Thank you.👋

 

I used your script and was able to setup DS920+ on VMWare

the steps I used for the setup are as follows:

 

./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS920+

curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/rploader.sh" --output rploader.sh

the next step is for e1000 driver:

./rploader.sh ext geminilake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/e1000/rpext-index.json

 

./rploader.sh build geminilake-7.1.0-42661

 

749835518_Screenshot(14).thumb.png.41933de113cd85c072653b6faefa1edb.png

 

30017253_Screenshot(15).thumb.png.8b2b8aba9d8bb51361b04bcdeda623dc.png

 

1320256190_Screenshot(16).thumb.png.4e78bed8b268443d3ce5d655399028bf.png

 

 

Edited by techfriend63
  • Like 2
Link to comment
Share on other sites

4 hours ago, flyride said:

 

I have repeated your install in both configurations (USB/SATA and SATABOOT/SCSI) on my equipment with no issue.

I did notice one difference back in your SATABOOT/SCSI test, and since you seem to be missing SCSI disk, maybe it is relevant.

 

My VM conf file has "scsihw: virtio-scsi-pci" and yours did not.  I am not a Proxmox expert so I do not know if it matters.

 

Can you send me your configuration file and the constructive mirror file and test it on my machine. The mailbox address has been sent to you through the message.

Link to comment
Share on other sites

15 hours ago, Peter Suh said:

In @pocopico's 0.4.6 img for legacy, the first partition is increased from 48mb to 96mb to secure space for the dtc utility to be copied, and it is an image that has been fully upgraded to the latest version 0.7.1.7.
Download it from the Google link below, decompress the gz and record it on a new USB stick.
And rploader.sh on my Github repo blocks the patchdtc function so that there are no errors like the log above, and also blocks the update of rploader.sh itself.

 

It's for the use of the new dtb util of jumkey

 

[tinycore-redpill.v0.7.1.7.img]

https://drive.google.com/file/d/1Jxr0znrDxkqIhcbFPTyll44VwdvuPBu-/view?usp=sharing

 

tc@box:~$ curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/rploader.sh" --output rploader.sh

 

mkdir /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles; sudo ln -s /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles /home/tc/custom-module;

 

./rploader.sh build geminilake-7.1.0-42661

 

./rploader.sh backup now

 

And

 

Share the tincore-redfill.v0.7.1.7.vmdk file.

For the use of the new dtb util of jumkey

This is a file that increased the first partition from 48MB to 96MB, as shown above in img for legacy.

 

[tinycore-redpill.v0.7.1.7.vmdk]

https://drive.google.com/file/d/1UCOzK1LTjLy3-bD2u5feeGblhqYN5UH_/view?usp=sharing


I would not change sizes of the loader partitions. You don’t know if that is critical to DSM or not  

Link to comment
Share on other sites

6 hours ago, pocopico said:


I would not change sizes of the loader partitions. You don’t know if that is critical to DSM or not  

 

I heard that Synology is based on the debian fork.
The hint below may not be 100% reliable information, but wouldn't it be helpful?
This hint says that up to 256MB or 512MB is allowed.

 

https://linuxhint.com/boot-partition-size-debian/?nowprocket=1

 

You may find this information useful as well.

 

https://serverfault.com/questions/334663/what-is-the-recommended-size-for-a-linux-boot-partition

 

https://unix.stackexchange.com/questions/628711/whats-the-maximum-disk-size-grub-can-use

Edited by Peter Suh
Link to comment
Share on other sites

4 hours ago, Peter Suh said:

 

I heard that Synology is based on the debian fork.
The hint below may not be 100% reliable information, but wouldn't it be helpful?
This hint says that up to 256MB or 512MB is allowed.

 

https://linuxhint.com/boot-partition-size-debian/?nowprocket=1

 

You may find this information useful as well.

 

https://serverfault.com/questions/334663/what-is-the-recommended-size-for-a-linux-boot-partition

 

https://unix.stackexchange.com/questions/628711/whats-the-maximum-disk-size-grub-can-use


I am sorry but, that’s totally irrelevant to what syno is expecting to find and is probably hardcoded. I would not change the sizes of the first two partitions and that is why we decided with Jumkey to move buildroot to the second partition 

 

EDIT The idea was always to immitate the hardware in order to match as much as possible the original HW and avoid counter measures (there were some in the past). Even redpill module is already able to hide itself and run in stealth mode, for that purpose. The scope of all the above, is to limit the posibilities for your box to be identified as alien HW.

 

 

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

An extensive end-user installation tutorial has been posted here:

https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/

 

It should answer many of the questions often posed on this development site.  Please start directing general installation questions to the Help forums unless you know you are contributing to a dev issue.

  • Like 3
  • Thanks 2
Link to comment
Share on other sites

3 hours ago, neonflx said:

Would this run on AMD RYZEN setup???

 

For AMD Ryzen, DS1621+ is recommended.
If you plan to install on bare metal,
At the Tinycore Linux prompt, download and install the following m shell (my.sh)
 

tc@box:~$ wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz; tar -zxvf my.sh.gz;

 

And then all you need to do is simply run ./my.sh DS1621+

  • Like 1
Link to comment
Share on other sites

Hello,

 

I have some problems with my installation. I have a working installation with Proxmox v7.1 with q35 VM and virtio nic DS3615 with DSM 7.0.1-42218, it works until now that I have make rpload update and fullupgrade. I have decided to make a new virtual usb installation, this time only with rploader update, all seems to work ok, but DMS is not detected on lan. I've made a network scan without success. 

 

Someone with the same problem or any help?

 

Regards

Link to comment
Share on other sites

Hello,
 
I have some problems with my installation. I have a working installation with Proxmox v7.1 with q35 VM and virtio nic DS3615 with DSM 7.0.1-42218, it works until now that I have make rpload update and fullupgrade. I have decided to make a new virtual usb installation, this time only with rploader update, all seems to work ok, but DMS is not detected on lan. I've made a network scan without success. 
 
Someone with the same problem or any help?
 
Regards

Can I see your loader build log? If it possible, use spoiler icon for log attachment.


Sent from my iPhone using Tapatalk
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...