TinyCore RedPill Loader (TCRP)

synoxpe · February 2, 2022

3 hours ago, renxpe said:

Hi Synoxpe, I am using newer hardware mainly the cpu is 10thgen i7 - my understanding is 3617 can fully utilize all the cores with hyperthreading - is this the case for DS918+ as well? Also, i'm using 10 drives 6 spinning and 4 ssd's - the 918 has 4 drive limit - can this be increased through configuration file?

appreciate the suggestion!

Ren

Yes! All loaders are set to 16 drives by default so that shouldn’t be a problem.

I too have a i7 10th gen and the 918+ is a quadcore device (just like the 3617).

renxpe · February 2, 2022

@ngsupbit worked! I pulled the drives, formatted to ext in linux, popped them back in. Blocked the test machine at the router level so it can't go out the network and do its update - install proceeded and reboot came back with "services starting" in syno assistant - awesome!

for reference this is for 3617xs using tinycore on

i7 10700 with asus z490 strix mobo

Orphée · February 2, 2022

Hello @pocopico ! Thanks for your work

For info, but I bet it is expected (not fixed since ThorGroup disappeared)

I tried to build loader for bromolow with my LSI 2308 SAS card with 4x4To disks

I added mpt3sas ext module but disks not found.

I relaunched the build adding mpt2sas ext module too.

DSM install found the disks and told I could migrated old version.

But looking on telnet serial console

Quote

DiskStation> fdisk -l
Disk /dev/synoboot: 1024 MB, 1073741824 bytes, 2097152 sectors
130 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device       Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors Size Id Type
/dev/synoboot1 * 0,32,33     6,62,56           2048     100351      98304 48.0M 83 Linux
/dev/synoboot2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux
/dev/synoboot3    15,205,63   130,138,8       253952    2097151    1843200 900M 83 Linux

fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sdb: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors Size Id Type
/dev/sdb1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sdc: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 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,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sdd: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors Size Id Type
/dev/sdd1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sde: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors Size Id Type
/dev/sde1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT

Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
622544 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
524272 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md1 doesn't contain a valid partition table

Disks shown are only 2To. So I won't try the migration and still stick to 6.2.3

But still thank you, really easy to use this tool

Edit : I guess I could mount disks as RDM, it would probably work, but I would loose Smart Data.

Edited February 3, 2022 by Orphée

superma87 · February 3, 2022

Hi, I got the setup working on a Zotac CI323 mini box with just 1 disk

Now I'm trying to get it to work on a more powerful bare-metal system

motherboard is a ASUS P11C-I, it has intel C242 chipset and has 1 mini-SAS connector to 4 SATA disks and 2 more SATA ports, one of them got disabled if i connect an NVMe disk on the 2242 onboard connector.

2x intel GB ports

Nothing fancy, it should work no problem and I found a couple of success reports around the forum

the satamap function however does not works as expected

./rploader.sh satamap now
HBA: 00:17.0 Disks : 6
ls: cannot access '/sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0/port*': No such file or directory
HBA: 00:1d.2 Disks : 0
ls: cannot access '/sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0/port*': No such file or directory
SataPortMap=60
DiskIdxMap=0001

some one has hints on that? even configuring it manually would be ok for me!

mode info on lsscsi command that satamap uses, that should be the 5(4 used) disks + 1 nvme setup that i have now:

lsscsi -Hv |grep pci |grep -v usb
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata1/host0
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata2/host1
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata3/host2
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata4/host3
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata5/host4
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata6/host5
  device dir: /sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0

Edited February 3, 2022 by superma87

ozef · February 3, 2022

Exactly same prob

il y a 23 minutes, superma87 a dit :
Hi, I got the setup working on a Zotac CI323 mini box with just 1 disk

Now I'm trying to get it to work on a more powerful bare-metal system

motherboard is a ASUS P11C-I, it has intel C242 chipset and has 1 mini-SAS connector to 4 SATA disks and 2 more SATA ports, one of them got disabled if i connect an NVMe disk on the 2242 onboard connector.

2x intel GB ports

Nothing fancy, it should work no problem and I found a couple of success reports around the forum

the satamap function however does not works as expected
./rploader.sh satamap now
HBA: 00:17.0 Disks : 6
ls: cannot access '/sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0/port*': No such file or directory
HBA: 00:1d.2 Disks : 0
ls: cannot access '/sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0/port*': No such file or directory
SataPortMap=60
DiskIdxMap=0001
some one has hints on that? even configuring it manually would be ok for me!

mode info on lsscsi command that satamap uses, that should be the 5(4 used) disks + 1 nvme setup that i have now:
lsscsi -Hv |grep pci |grep -v usb
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata1/host0
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata2/host1
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata3/host2
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata4/host3
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata5/host4
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata6/host5
  device dir: /sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0

Exactly same problem with 4 ports SATA controller + 1 NVME disk...

satamap does not see nvme but fdisk -l on tinycore see it.

superma87 · February 3, 2022

1 hour ago, ozef said:

Exactly same prob

Exactly same problem with 4 ports SATA controller + 1 NVME disk...

satamap does not see nvme but fdisk -l on tinycore see it.

I'm still learning how this stuff work but i think tat nvme disk are not detected since they are not attached to a sata controller of any type but to the pci express

marigo · February 3, 2022

I have tried to update my VM on Proxmox from 6.2.3 to 7.0.1 (apollolake-7.0.1-42218) but no IP is given from DHCP.

My setup is to boot from Juns loader 1.04B and have one bootdisk on SATA0 and a datadisk on SATA1:

vm-xxx-disk-0.raw <- bootdisk
vm-xxx-disk1.qcow2 <- datadisk

I deleted the bootdisk (detach and remove drive) and added a new (raw) bootdisk with 2GB capacity. Changed the NIC from "E1000" to "Virtio", loaded Tinycore loader on this disk and booted. Everything is looking fine, Update the user_config.json and backup this configuration.

After the reboot (booted in grub menu from SATA) there is no connectivity and no IP address has been given out by DHCP.

If I stop this VM and detach my datadisk (which was previous om dsm6.2.3) and boot again, I get an IP address from DHCP and find.synology.com finds this "Diskstation".

But there are no disks found to install DSM.

Am I missing something here? I thought it could be the "satamap" so I applied "./rploader satamap now" and this will find the disks in KVM and added to user_config.json

But that didn't do the trick.

When I create a new VM with Tinycore loader, I can add a second disk with no problem and install DSM7 normally. So greenfield works, but upgrade not yet.

Hope someone can point me in the right direction.

Edited February 3, 2022 by marigo

Invaliduser · February 3, 2022

19 minutes ago, marigo said:

I have tried to update my VM on Proxmox from 6.2.3 to 7.0.1 (apollolake-7.0.1-42218) but no IP is given from DHCP.

My setup is to boot from Juns loader 1.04B and have one bootdisk on SATA0 and a datadisk on SATA1:

vm-xxx-disk-0.raw <- bootdisk

vm-xxx-disk1.qcow2 <- datadisk

I deleted the bootdisk (detach and remove drive) and added a new (raw) bootdisk with 2GB capacity. Changed the NIC from "E1000" to "Virtio", loaded Tinycore loader on this disk and booted. Everything is looking fine, Update the user_config.json and backup this configuration.

After the reboot (booted in grub menu from SATA) there is no connectivity and no IP address has been given out by DHCP.

If I stop this VM and detach my datadisk (which was previous om dsm6.2.3) and boot again, I get an IP address from DHCP and find.synology.com finds this "Diskstation".

But there are no disks found to install DSM.

Am I missing something here? I thought it could be the "satamap" so I applied "./rploader satamap now" and this will find the disks in KVM and added to user_config.json

But that didn't do the trick.

When I create a new VM with Tinycore loader, I can add a second disk with no problem and install DSM7 normally. So greenfield works, but upgrade not yet.

Hope someone can point me in the right direction.

Are you generating a new mac address for the 7.0.1 build? If so, you will need to assign that mac address to the VM's network device.

marigo · February 3, 2022

40 minutes ago, Invaliduser said:

Are you generating a new mac address for the 7.0.1 build? If so, you will need to assign that mac address to the VM's network device.

Hi Invaliduser, I have used a new MAC address, so I will try that. (could it be that simple) thx for quick reply.

EDIT: This works to update the MAC address of the VM with the one used in "user_config.json" (no workaround needed) THX!!

In the meanwhile I discovered a workaround, to detach the "old" disk and add a new one. After boot the diskstation is visible and I can install DSM7.

After install I shutdown the machine and added the datadisk again, so together with the new disk and booted. Now the diskstation sees the datadisk again and I can migrate to DSM7. After migration I deleted the new disk en rebooted. Everything seems te work.

Edited February 3, 2022 by marigo

matlow · February 3, 2022

Hi to all,

Motherboard: Asus P8H61-I LX - 1x controller SATA, 4x SATA ports

2x 1TB SATA disks

Tinycore is on bootable usb connected to motherboard

Build Bromolow 6.2.4-25556

Problem with SataPortMap... I have tried a lot of combinations and the effect is the same. All time I have error with not connected disks ( 3 and 4 ) or system installation loop.

script: ./rploader satamap now give me this:

2.png.00de1d94c590d4278647d930a6cd0fbb.png

after boot i have error 3 and 4 disk ( i have only 2 hard drives connected )

2) SataPortMap =2

DiskIdxMap=00

NO DISK ERROR but DSM installation loop

3) SataPortMap = 188

DiskIdxMap = 0A0008

NO DISK ERROR but DSM installation loop

4) SataPortMap = 42

DiskIdxMap = 0004

ERROR DISKS

and many combinations don't help because the problems are like mentioned above.

1.png.576ec9c972804ae1c0aafcbf10bd2b66.png

416547379_Zrzutekranuz2022-02-0312-53-25.png.0cf9d093c9b6d90705a303214d96ea59.png

could I ask for support and help?

NooL · February 3, 2022

On 1/30/2022 at 11:16 PM, synoxpe said:
Proxmox SATA HDD Passthrough to DSM 7. Anyone able to achieve this?

I just added a few SATA Disks manually to the DSM VM with id 100:
qm set 100 -sata1 /dev/disk/by-id/<id>
but they're showing on DSM Storage Manager as QEMU Harddisks missing SMART info.

@haydibe @pocopico

I believe if you want the full smart info etc you have to pass through the controller, not the drive.

superma87 · February 3, 2022

9 hours ago, superma87 said:
Hi, I got the setup working on a Zotac CI323 mini box with just 1 disk

Now I'm trying to get it to work on a more powerful bare-metal system

motherboard is a ASUS P11C-I, it has intel C242 chipset and has 1 mini-SAS connector to 4 SATA disks and 2 more SATA ports, one of them got disabled if i connect an NVMe disk on the 2242 onboard connector.

2x intel GB ports

Nothing fancy, it should work no problem and I found a couple of success reports around the forum

the satamap function however does not works as expected
./rploader.sh satamap now
HBA: 00:17.0 Disks : 6
ls: cannot access '/sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0/port*': No such file or directory
HBA: 00:1d.2 Disks : 0
ls: cannot access '/sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0/port*': No such file or directory
SataPortMap=60
DiskIdxMap=0001
some one has hints on that? even configuring it manually would be ok for me!

mode info on lsscsi command that satamap uses, that should be the 5(4 used) disks + 1 nvme setup that i have now:
lsscsi -Hv |grep pci |grep -v usb
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata1/host0
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata2/host1
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata3/host2
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata4/host3
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata5/host4
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata6/host5
  device dir: /sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0

removing the nvme drive fixes the satamap recognition, however i got it working even without removing the nvme drive, the config should always be the same that the working satamap generates

superma87 · February 3, 2022

8 hours ago, ozef said:

Exactly same prob

Exactly same problem with 4 ports SATA controller + 1 NVME disk...

satamap does not see nvme but fdisk -l on tinycore see it.

this thread has a lot of redundad information:

someone there got cache working too on dsm 7

short answer is patch the libnvme library with you pci id and copy it back to your system

another Chinese post with "detailed" instructions, just translate it

https://wp.gxnas.com/10930.html

(feel free to test it before messing your system and/or your data)

recoco · February 4, 2022

I have built the loader, follow these commands:

sudo ./rploader.sh update now
sudo ./rploader.sh serialgen DS3615xs now
sudo ./rploader.sh identifyusb now
sudo ./rploader.sh satamap now
sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json # for the SAS HBA card
sudo ./rploader.sh build bromolow-7.0.1-42218

The loader can boot. Anything looks fine. But after booting, the installation can not recognize networks cards. Both are e1000 and one of these is signed the MAC generated by tinyloader.

The e1000e module is loaded successfully.

DiskStation> lsmod
Module                  Size  Used by    Tainted: P  
usbhid                 26271  0 
hid                    88234  1 usbhid
etxhci_hcd             84851  0 
apollolake_synobios    70938  0 
nfsv3                  24512  0 
nfs                   181543  1 nfsv3
lockd                  73280  2 nfsv3,nfs
grace                   2114  1 lockd
sunrpc                245230  3 nfsv3,nfs,lockd
r8168                 527330  0 
igb                   175987  0 
i2c_algo_bit            5456  0 
e1000e                173807  0 
vxlan                  32623  0 
ip6_udp_tunnel          1967  1 vxlan
udp_tunnel              2419  1 vxlan
vfat                   10479  0 
fat                    54532  1 vfat
usb_storage            49529  0 
xhci_pci                4650  0 
xhci_hcd              111928  1 xhci_pci
usbcore               201223  5 usbhid,etxhci_hcd,usb_storage,xhci_pci,xhci_hcd
usb_common              2286  1 usbcore

DiskStation> ifconfig -a
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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

DiskStation> more /etc/synoinfo.conf |grep eth
AppleTalk="eth0"
eth0_mtu="1500"
eth0_wol_options="d"
eth1_mtu="1500"
eth1_wol_options="d"

What is wrong with these? Thanks in advance!

Edited February 4, 2022 by recoco

painkiller895 · February 4, 2022

4 hours ago, recoco said:

I have built the loader, follow these commands:


sudo ./rploader.sh update now
sudo ./rploader.sh serialgen DS3615xs now
sudo ./rploader.sh identifyusb now
sudo ./rploader.sh satamap now
sudo ./rploader.sh ext bromolow-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json # for the SAS HBA card
sudo ./rploader.sh build bromolow-7.0.1-42218

The loader can boot. Anything looks fine. But after booting, the installation can not recognize networks cards. Both are e1000 and one of these is signed the MAC generated by tinyloader.

The e1000e module is loaded successfully.


DiskStation> lsmod
Module                  Size  Used by    Tainted: P  
usbhid                 26271  0 
hid                    88234  1 usbhid
etxhci_hcd             84851  0 
apollolake_synobios    70938  0 
nfsv3                  24512  0 
nfs                   181543  1 nfsv3
lockd                  73280  2 nfsv3,nfs
grace                   2114  1 lockd
sunrpc                245230  3 nfsv3,nfs,lockd
r8168                 527330  0 
igb                   175987  0 
i2c_algo_bit            5456  0 
e1000e                173807  0 
vxlan                  32623  0 
ip6_udp_tunnel          1967  1 vxlan
udp_tunnel              2419  1 vxlan
vfat                   10479  0 
fat                    54532  1 vfat
usb_storage            49529  0 
xhci_pci                4650  0 
xhci_hcd              111928  1 xhci_pci
usbcore               201223  5 usbhid,etxhci_hcd,usb_storage,xhci_pci,xhci_hcd
usb_common              2286  1 usbcore


DiskStation> ifconfig -a
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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


DiskStation> more /etc/synoinfo.conf |grep eth
AppleTalk="eth0"
eth0_mtu="1500"
eth0_wol_options="d"
eth1_mtu="1500"
eth1_wol_options="d"

What is wrong with these? Thanks in advance!

Test it using a Intel nic card...

synoxpe · February 4, 2022

19 hours ago, NooL said:

I believe if you want the full smart info etc you have to pass through the controller, not the drive.

Yes! That did it!! Sometimes you miss the obvious

So now this is starting to look like the real deal!

matlow · February 4, 2022

23 hours ago, matlow said:

Hi to all,

Motherboard: Asus P8H61-I LX - 1x controller SATA, 4x SATA ports

2x 1TB SATA disks

Tinycore is on bootable usb connected to motherboard

Build Bromolow 6.2.4-25556

Problem with SataPortMap... I have tried a lot of combinations and the effect is the same. All time I have error with not connected disks ( 3 and 4 ) or system installation loop.

script: ./rploader satamap now give me this:

after boot i have error 3 and 4 disk ( i have only 2 hard drives connected )

2) SataPortMap =2

    DiskIdxMap=00

NO DISK ERROR but DSM installation loop

3) SataPortMap = 188

    DiskIdxMap = 0A0008

NO DISK ERROR but DSM installation loop

4) SataPortMap = 42

    DiskIdxMap = 0004

ERROR DISKS

and many combinations don't help because the problems are like mentioned above.

could I ask for support and help?

I tried to do a build for bromolow 7.0.1 with SataPortMap 2 and DiskIdxMap 00 and everything works fine!!!. No disk errors and the system installed successfully. Clearly the problem is with build bromolow 6.2.4-25556 on the same sataport and diskidx after which the system installs in a loop. @pocopico could you check this? Thanks a lot

Edited February 4, 2022 by matlow

tmolinos · February 4, 2022

On 2/2/2022 at 6:17 PM, tmolinos said:

Hello everyone!

I'm trying to run this tool on VmWare 6.5. I downloaded the vmdk and converted it to be usable by ESX using vmfstools.

I can get into tinycore, configure and start building, but then it stops at “Creating loader image at loader.img…”.

I googled a bit and found another user with the same exact issue.

Any help would be appreciated.

Thanks!

I'm stuck at this... any suggestion?

chickey · February 4, 2022

On 2/3/2022 at 12:01 PM, superma87 said:
Hi, I got the setup working on a Zotac CI323 mini box with just 1 disk

Now I'm trying to get it to work on a more powerful bare-metal system

motherboard is a ASUS P11C-I, it has intel C242 chipset and has 1 mini-SAS connector to 4 SATA disks and 2 more SATA ports, one of them got disabled if i connect an NVMe disk on the 2242 onboard connector.

2x intel GB ports

Nothing fancy, it should work no problem and I found a couple of success reports around the forum

the satamap function however does not works as expected
./rploader.sh satamap now
HBA: 00:17.0 Disks : 6
ls: cannot access '/sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0/port*': No such file or directory
HBA: 00:1d.2 Disks : 0
ls: cannot access '/sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0/port*': No such file or directory
SataPortMap=60
DiskIdxMap=0001
some one has hints on that? even configuring it manually would be ok for me!

mode info on lsscsi command that satamap uses, that should be the 5(4 used) disks + 1 nvme setup that i have now:
lsscsi -Hv |grep pci |grep -v usb
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata1/host0
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata2/host1
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata3/host2
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata4/host3
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata5/host4
  device dir: /sys/devices/pci0000:00/0000:00:17.0/ata6/host5
  device dir: /sys/devices/pci0000:00/0000:00:1d.2/0000:05:00.0

how did you get around the no such file or directory error? or was it by patching in the file so it recognised your nvme drive that cured that issue?

superma87 · February 4, 2022

43 minutes ago, chickey said:

how did you get around the no such file or directory error? or was it by patching in the file so it recognised your nvme drive that cured that issue?

that's just and error from the script, it's very basic it fails very easily

if you know you system just put the sata mappings inside the file and you are good

nvme disk recognition has nothing in common with that part of the script

just connect it and if you happen to boot to a working system, follow my last post to get info on how to use nvme on dsm

Aigor · February 4, 2022

Hp Gen8
Tinycore last version
DS3617xs

Usb boot, VID PID from tinycore, fresh installation hangs at 55% from webiterface

 266.582276] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[  266.635087] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  267.588008] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  267.627474] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  275.573270] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[  275.626550] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  276.654628] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  276.694231] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop

danellis12561 · February 4, 2022

I'm so close, yet so far. I'm able to use the Tiny Core image to generate the serial/MAC, get the SATA port map and also get the PID/VID for the flash drive. I get to the point where it's installing the .pat file I upload to it and it fails at about 56% and says the image may be corrupt. I have verified multiple times via multiple tools that the flash drive PID and VID are correct. I've tried the 3615xs and 3617xs loaders and neither work. I've also tried different USB ports. Details for my system are below. Any help would be appreciated.

Bare metal install

Dell Poweredge t420

Intel Xeon E5-2420v2

64GB RAM

PERC h710 RAID controller flashed to IT mode

4x1TB SATA hard drives

3617xs fails around 56% saying the file may be corrupt.

3615xs finds no drives at all

***EDIT - After re-reading some of the older posts, I think the bootloader may have been booting into SATA mode instead of USB. I'll check that this evening and give it another shot.

Edited February 4, 2022 by danellis12561
Actually read stuff lol

vbz14216 · February 4, 2022

Just wanted to say thank you for such an amazing project, your automated script is a lifesaver! No need to be a Linux guru to build the RedPill as the automated process made everything a walk in the park. (I had experiences with vanilla hackintosh but building RedPill from scratch is next level stuff.)

My setup runs on an ancient Intel Atom D510(i915 driver+e1000 driver, no HBA installed), 1HDD and 2GB of RAM, I originally wanted to have 6.2.4 running on bromolow w/ Legacy boot on baremetal as DSM6 is more mature. Got into 6.2.4 DSM desktop but updating to 6.2.4 update-4 always fails(recovery loop), not sure what the culprit was.

Bit the bullet, kept the user_config.json, built bromolow-7.0.1-42218 and update to 42218-2 worked without problem(s).

Small tip for anyone encountering "missing files error" when building the bootloader, use "./rploader.sh clean now" and build the bootloader again so all assets can be re-downloaded.

Edited February 4, 2022 by vbz14216
fix errors

plarkass · February 4, 2022

I'm stuck at this... any suggestion?

Default vmdk is working like that on esxi.
You just need to put controller as idea for the tiny core loader vmdk

Envoyé de mon KB2003 en utilisant Tapatalk

recoco · February 5, 2022

On 2/4/2022 at 12:44 PM, painkiller895 said:

Test it using a Intel nic card...

Thanks!

I'm using vm in Proxmox. NIC is e1000.

TinyCore RedPill Loader (TCRP)

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation