Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

1 час назад, synoxpe сказал:

Can I to ask about UPS connection via usb? I have APC CS-500 that normally worked on my N54L Jun 1.0.3 loader DSM-3615 6.2.3 , but after migration to 7.0.1 redpill loader UPS isn't connect watching into DSM. Have anybody the same problem, and any ideas how to fix?

 

HPx510 UPS.png

  • Like 1
Link to comment
Share on other sites

Hello,

 

Can someone reminds me how to telnet on baremetal BEFORE trying to start install ?

 

I want to check "fdisk -l" to see disk partition size.

 

Can't remember if there is a specific port to pass...

 

Edit : I don't want to break my prod disks... I want to check if there are 4, and if 4To is detected...

But it may not be possible to access to telnet until there is a failure ?

 

Edit 2 : search is my friend, sorry ... http://xxxxx:5000/webman/start_telnet.cgi

Edited by Orphée
Link to comment
Share on other sites

2 minutes ago, Orphée said:

Hello,

 

Can someone reminds me how to telnet on baremetal BEFORE trying to start install ?

 

I want to check "fdisk -l" to see disk partition size.

 

Can't remember if there is a specific port to pass...

http://<your-dsm-ip-address>:5000/webman/start_telnet.cgi

 

  • Like 1
Link to comment
Share on other sites

So it seems I won't be able to install DSM7

 

Quote

DiskStation> fdisk -l
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sda: 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/sda1    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/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
Disk /dev/synoboot: 14 GB, 15376318464 bytes, 30031872 sectors
14664 cylinders, 64 heads, 32 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
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
622544 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

 

On HP N54L with current running DSM 6.2.3

Link to comment
Share on other sites

7 minutes ago, Aigor said:

have you tried to perform installation without internet connection? 

I did not even tried to install. As long as my drives are only detected as 2To instead of 4, I won't start the installation process.

 

Edit :

DSM 6.2.3 fdisk -l

Quote

Disk /dev/sda: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: C8F6C728-968A-4E5A-A4CE-4F9C8088B232

Device       Start        End    Sectors  Size Type
/dev/sda1     2048    4982527    4980480  2.4G Linux RAID
/dev/sda2  4982528    9176831    4194304    2G Linux RAID
/dev/sda3  9437184 7813832351 7804395168  3.6T Linux RAID


Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 14839AC4-2446-4931-A35B-DB75462A7B86

Device       Start        End    Sectors  Size Type
/dev/sdb1     2048    4982527    4980480  2.4G Linux RAID
/dev/sdb2  4982528    9176831    4194304    2G Linux RAID
/dev/sdb3  9437184 7813832351 7804395168  3.6T Linux RAID


Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 2EB2E747-7B6A-4553-BB5F-7FE7F012454E

Device       Start        End    Sectors  Size Type
/dev/sdc1     2048    4982527    4980480  2.4G Linux RAID
/dev/sdc2  4982528    9176831    4194304    2G Linux RAID
/dev/sdc3  9437184 7813832351 7804395168  3.6T Linux RAID


Disk /dev/sdd: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 1737264A-CC18-4ED0-9DFC-6A8B78ECD8D5

Device       Start        End    Sectors  Size Type
/dev/sdd1     2048    4982527    4980480  2.4G Linux RAID
/dev/sdd2  4982528    9176831    4194304    2G Linux RAID
/dev/sdd3  9437184 7813832351 7804395168  3.6T Linux RAID

 

Edit 2 :

 

Looking at error thrown by fdisk on DSM7 install :

 

https://askubuntu.com/questions/694102/cant-get-full-drive-capacity-in-fdisk

 

Don't use MBR on a disk with over 2^32 sectors (2TiB, assuming 512-byte logical sectors)!

MBR uses 32-bit sector pointers, so anything with more than 2^32 sectors is simply incompatible with MBR -- or at least, MBR tops out at 2^32 sectors, so you won't be able to use the full capacity of the disk, as you've discovered. There are hackish workarounds that can be used to get up to about twice that capacity, but they're unreliable, especially if the disk is to be used across multiple OSes. (As a side note, you seem to be confusing TB and TiB; they aren't the same. See this page for details.)

Instead, use the GUID Partition Table to partition the disk. You can do this with GPT fdisk (gdisk, sgdisk, or cgdisk), or with most libparted-based tools (parted, GParted, and others). Recent versions of fdisk also support GPT, but Ubuntu 14.04 doesn't yet provide that version. (I think one of the later non-LTS releases does, but I don't recall when it was introduced, in Ubuntu version terms.) GPT fdisk is a GPT-specific tool modeled after fdisk, and so uses GPT by default. The others require explicit commands to use GPT rather than MBR.

Edited by Orphée
Link to comment
Share on other sites

is it very important to check what CPU Model is used and what Synology NAS we want to compilte?

 

DS3615xs => Bromolow=> Intel Xeon E3-1230 v2

DS3617xs => Broadwell => Intel Xeon D-1527

 

RS3617xs Intel Xeon E3-1230 v2 Quad Core8 Bromolow DDR3 ECC 4 GB

 

so for a HP Gen8 Micro with Xeon E3-1230 v2 the support is only on a DS3616xs or RS3617xs

Link to comment
Share on other sites

i follow the instruction step from this site https://github.com/pocopico/tinycore-redpill 

when i check the img file, it has not valid partition table.

why ?


 

fdisk -l /share/Public/XPE/syst/tinycore-redpill.v0.4.4_20220210_173245.img

Disk /share/Public/XPE/syst/tinycore-redpill.v0.4.4_20220210_173245.img: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /share/Public/XPE/syst/tinycore-redpill.v0.4.4_20220210_173245.img doesn't contain a valid partition table

 

but i can open .img file using 7zip and see the partition table inside.

redpill.png.597a4a509b52a8708c8e0ad1de808cde.png

 

i run the redpill script inside VM. 

 

Edited by hendry
Link to comment
Share on other sites

3 hours ago, cferra said:

@pocopicohey man!  I’m trying to build with TC 3617 and it seems like it’s having trouble downloading extensions from your repo.. any ideas?


maybe the url is incorrect for the files in the repo?

 

thanks for everything!

 

 

3D9F28ED-381A-422F-877F-843FB8E2FF37.jpeg

11EFE133-DD7C-4447-9C61-C909E54E01E4.jpeg

 

So for the first error, i have fixed missing 3617 mlx4_core reference. (These are co-maintained with JimmyGaland).

 

For the second error, it looks that you failed or for some reason you didnt download the redpill loader before executing listmods function.

Link to comment
Share on other sites

16 minutes ago, pocopico said:

 

So for the first error, i have fixed missing 3617 mlx4_core reference. (These are co-maintained with JimmyGaland).

 

For the second error, it looks that you failed or for some reason you didnt download the redpill loader before executing listmods function.

Ok great!  Let me try it out!

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