Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

9 hours ago, Amrit86 said:

Hi all

 

I’ve upgraded to 7.0.1 using the RedPill Tinycore loader and it’s all working fine. It installed 7.0.1-42218 but I’ve seem some people here have Update 2 which fixes some security vulns. The Tinycore loader didn’t give this as an option, can I upgrade from the Synology website or have I missed something?


Hi all

 

Sorry to ask again but wanted to check if I had made a mistake in the install process or there is an upgrade path that I can follow. 
 

Thanks

Link to comment
Share on other sites

Stil can't install DS3617xs from tinycore, even if i'm disconnected from internet, stuck at 56% 

repeated many times 

 

[ 2284.795163] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 2284.866132] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2284.905686] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2290.733149] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[ 2290.795457] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 2290.866347] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2290.906283] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2296.739614] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[ 2296.804086] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 2296.875278] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2296.914771] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2302.732568] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[ 2302.796048] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 2302.859247] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2302.899032] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2308.738253] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[ 2308.804680] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 2308.875702] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2308.915130] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2314.731867] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[ 2314.796642] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 2314.867649] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2314.907231] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2320.744865] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[ 2320.805276] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[ 2320.877221] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[ 2320.916905] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop

 

Edited by Aigor
Link to comment
Share on other sites

Just now, pocopico said:

Whats the issue ? can you try to telnet and list disks with

 

fdisk -l |grep -i disk

DiskStation> fdisk -l |grep -i disk
Disk /dev/sda: 233 GB, 250059350016 bytes, 488397168 sectors
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
Disk /dev/md1 doesn't contain a valid partition table

 

Link to comment
Share on other sites

Just now, Aigor said:

DiskStation> fdisk -l |grep -i disk
Disk /dev/sda: 233 GB, 250059350016 bytes, 488397168 sectors
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
Disk /dev/md1 doesn't contain a valid partition table

 

 

Where is the usb ? If its VM, did you use SATA for the loader ?

Link to comment
Share on other sites

3 minutes ago, pocopico said:

 

Where is the usb ? If its VM, did you use SATA for the loader ?

USB is in the microsd reader on Gen8, is baremetal installatation, VID and PID comes from tinycore 

previous version, for DS3617xs 6.2.3 works flawless 

 

Edited by Aigor
Link to comment
Share on other sites

5 minutes ago, Dvalin21 said:

He is having the same issue as myself and a few others. I've tried different usbs and still got the same issue. @Aigor

yes, same issue even with usb stick and without internet connection, it stucks at 55% 
Log 

DiskStation> [  185.605393] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  185.642065] random: synodiskport: uninitialized urandom read (4 bytes read, 114 bits of entropy available)
[  185.690522] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  190.271359] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  190.308305] random: synodiskport: uninitialized urandom read (4 bytes read, 127 bits of entropy available)
[  190.356976] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  192.745822] random: nonblocking pool is initialized
[  195.490071] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  195.529812] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  200.675626] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  200.715272] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  201.788556] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  201.828359] <redpill/smart_shim.c:352> ATA_CMD_ID_ATA confirmed SMART support - noop
[  205.006192] md: bind<sda1>
[  205.019065] md/raid1:md0: active with 1 out of 16 mirrors
[  205.047743] md0: detected capacity change from 0 to 2549940224
[  208.105764] md: bind<sda2>
[  208.118642] md/raid1:md1: active with 1 out of 16 mirrors
[  208.147295] md1: detected capacity change from 0 to 2147418112
[  208.929517] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[  208.988758] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  209.239664] <redpill/pmu_shim.c:310> Got 1 bytes from PMU: reason=1 hex={2d} ascii="-"
[  209.389670] <redpill/pmu_shim.c:310> Got 1 bytes from PMU: reason=1 hex={72} ascii="r"
[  209.393033] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[  209.430323] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  209.498678] <redpill/pmu_shim.c:239> Executing cmd OUT_SCHED_UP_OFF handler cmd_shim_noop+0x0/0x30 [redpill]
[  209.545692] <redpill/pmu_shim.c:45> vPMU received OUT_SCHED_UP_OFF using 1 bytes - NOOP
[  209.607995] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[  209.647026] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
^C
DiskStation>

 

Link to comment
Share on other sites

Im happy to say that DS3622xs+ is now installed on my Dell Poweredge T320 Perc 3 H310. I did notice that when the device was suppose to restart after it finished being installed, it didn't. I had to remote restart. (FYI the H310 is not in IT Mode, but will be flashing it at first chance).  Also, I left the default satamap and Diskxid in the user_config.json file. 

@pocopico @IG-88 @hendry @Aigor

Edited by Dvalin21
  • Like 2
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...