Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

On 4/12/2022 at 6:57 PM, cpresco said:

@anyone

 

I'm considering migrating from DS918+ to DS3622xs+ for various reasons and recommendations I've seen in this thread.

 

DSM is currently at 7.0.1-42218U3. TCRP is 0.4.5. Hardware is in my sig.

 

Are these the correct steps for migrating an existing DS918+/7.0.1-42218U3 to DS3622xs+/7.0.1-42218U3?

 

1. Backup all data

2. Create a new USB loader with TCRP 0.4.6 from pocopico github

3. Remove existing USB loader and boot with new USB loader

4. Select Tiny Core Image Build during boot

5. Run following commands

 

./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh clean now

./rploader.sh serialgen DS3622xs+
./rploader.sh identifyusb now
./rploader.sh satamap now

./rploader.sh build broadwellnk-7.0.1-42218

 

I'm guessing that DSM will do it's own migration when I access DSM after the reboot.

 

Once I have a successful migration to DS3622xs+/7.0.1-42218U3 I'll be considering the upgrade to DSM7.1 and am guessing that would be the two step update but I'm not sure what the sequence of events/commands would be for that.

You can't downgrade from 7.0.1-42218U3 to 7.0.1-42218! I don't think TC supports the U3 (but it's not necessary either) If I were you, I would first update to DS918 7.1.0-42621 and/or 7.1.0-42661, and only then create a new loader for DS3622-7.1.0-42661, the migration to DS3622 then takes place automatically with the first Boot the newly created loader!

 

Don't forget to back up your HDD data before!!!

Link to comment
Share on other sites

Synology discontinued USB device support from version 7

 

 

4 hours ago, mitch55 said:

On my N54L, it seems to have a problem with USB drivers (or other, I'm not an expert) 

  • the control panel doesn't find my bluetooth. 
  • And it doesn't find my inverter (eaton ellipse pro 650).

image.thumb.png.4addafbdf7fa61737defcfd7ab7c2d33.pngimage.png.df4612e285027d8d4d23dce6b7af34eb.png

image.png.aff38016ac5a3d065a837bcea49b62a0.png

 

Is this working for someone?

 

 

 

  • Thanks 2
Link to comment
Share on other sites

3 hours ago, loveburn said:

Guy's the internal antivirus can't update virus bases always error

 

"Can't update virus base with freshclam (ext code:17 err code 2)"

Anyone have same troubles?

Where do you see that particular error log?  I attempt to update the AV and it says updating, updating successful, however the date code does not change so I assume it is not actually updating.

 

 

Link to comment
Share on other sites

By mistake I deleted the *.img file that I created for a DS1621+ in Proxmox and now the VM doesn't start anymore.

The DS1621+ was running 7.0.1-42218-U3. I have tried several times to rebuild the loader. Last time I did:

./rploader.sh update now

./rploader fullupgrade now

./rploader serialgen DS1621+ (write user_config.json)

./rploader identifusb now (write user_config.json)

./rploader satamap now (write user_config.json)

./rploader build v1000-7.0.1-42218

 

VM starts, gets an IP address, can be connected to but no disks detected.

 

please advise how to (re)build a DS1621+ in Proxmox?

 

By the way using redpill TC v0.4.6

 

Link to comment
Share on other sites

2 hours ago, Brunox said:

You can't downgrade from 7.0.1-42218U3 to 7.0.1-42218! I don't think TC supports the U3 (but it's not necessary either) If I were you, I would first update to DS918 7.1.0-42621 and/or 7.1.0-42661, and only then create a new loader for DS3622-7.1.0-42661, the migration to DS3622 then takes place automatically with the first Boot the newly created loader!

 

Don't forget to back up your HDD data before!!!

 

I believe in an earlier post Peter Suh recommended migrating an exiting DS918+/7.0.1-42218 to DS3622xs+/7.0.1-42218 before upgrading to 7.1.0-42661.

 

I'm going to try these steps on spare hardware with DS918+/7.0.1-42218 that is similar to my in-use DS918+/7.0.1-42218 system.

 

Data backup is #1 on the list of steps before doing this on my in-use DS918+/7.0.1-42218 system. :)

 

Brunox, your reply is appreciated.

 

I'd be interested to know/hear anyone's experience with migrating an existing DS918+/7.0.1-42218 to DS3622xs+/7.0.1-42218.

Link to comment
Share on other sites

On 2022/1/1 at AM3点16分, pocopico said:

 

您通常不必为大多数 SATA 控制器使用扩展,AHCI 包含在 DSM 中。那是一个不同的错误,与 SataPortMap 和 DiskIdxMap 有关。

 

我需要研究自动设置它的正确方法,因为这已成为首次安装中最常出现的问题。

 

同时,您可以在 MacX 下的 user_config.json 上尝试 SataPortMap=188 DiskIdxMap=0A0008

I found a problem. When I installed DSM7.0.1 on the H610 and B660 motherboards, it was prompted that SATA1234 was disabled. After analysis, I came to the conclusion that perhaps the SATA controllers of H610 and B660 were castrated from the 8 SATA of Z690 and disabled. Caused by 4 SATA, so I can't install DSM because it always has 4 non-existing SATA ports disabled, hope H610, B660 are supported

Link to comment
Share on other sites

8 minutes ago, wt19891207 said:

I found a problem. When I installed DSM7.0.1 on the H610 and B660 motherboards, it was prompted that SATA1234 was disabled. After analysis, I came to the conclusion that perhaps the SATA controllers of H610 and B660 were castrated from the 8 SATA of Z690 and disabled. Caused by 4 SATA, so I can't install DSM because it always has 4 non-existing SATA ports disabled, hope H610, B660 are supported

 

Have you ever seen this guide?

Read item 5 here.

 

 

Link to comment
Share on other sites

hello..Its my dream to create  a DSM boot by myself. Your work give a chance to me. But now i was interrupted at this:

#] Adding new extension from https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/rpext-index.json...
[#] Downloading remote file https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/rpext-index.json to /opt/redpill-load/custom/extensions/_new_ext_index.tmp_json
######################################################################### 100.0%
curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused
[!] Failed to download https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/rpext-index.json to /opt/redpill-load/custom/extensions/_new_ext_index.tmp_json

*** Process will exit ***

[!] Failed to add "https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/rpext-index.json" as an extension:

*** Process will exit ***
[!] Failed to install redpill.bootwait bundled extension - see errors above

*** Process will exit ***
make: *** [Makefile:34: build_redpill_load] Error 1

 

A lot of time was cost at this step. I don't know what problem it is.

So, thank you very much if you can help me deal with it.🙂

Link to comment
Share on other sites

3 часа назад, cferra сказал:

date code does not change

 

 

it''s OK... last update by 13 april... 

in our country CISCO blocked the clamav.net domains... and this error because resource is blocked and can't download update...

and AGIN just i am LET YOU KNOW!! - last update of virus defenitions from 13.04.22

Link to comment
Share on other sites

15 hours ago, Hong Kong said:

Hello,

I downloaded and burn tinycore-redpill.v0.4.6 to my USB drive and boot it to my HP Microserver Gen 8 with 4 disks. However, I cannot make it work.

Commands shown below.

 

My questions:

  1. My system is using Intel(R) Celeron(R) CPU G1610T @ 2.30GHz with 2GB RAM. Is the DS3615xsbromolow-7.0.1-42218 a good choice?
  2. There is no modules.alias.3.json.gz  modules.alias.4.json.gz  latestrploader.sh on my drive. Is it normal?
  3. There are SSL certificate problem: certificate is not yet valid errors. Are they expected?
  4. Do I need the pciid 8086d00001c02 and pciid 102bd00000533 extensions? If yes, how can I locate and include them?

Many thanks!

 

tc@box:~$ sudo ./rploader.sh update now

Checking Internet Access -> OK

Checking if a newer version exists on the repo -> gzip: modules.alias.3.json.gz: No such file or directory

gzip: modules.alias.4.json.gz: No such file or directory

sha256sum: latestrploader.sh: No such file or directory

There is a newer version of the script on the repo should we use that ? [yY/nN]Y

OK, updating, please re-run after updating

cp: cannot stat '/home/tc/latestrploader.sh': No such file or directory

Updating tinycore loader with latest updates

Backing up files to /mnt/sde3//mydata.tgz

Done.

tc@box:~$

tc@box:~$ sudo ./rploader.sh serialgen DS3615xs now

Serial Number for Model : 1330LWN027197

Mac Address for Model DS3615xs : 00:11:32:C4:8A:21

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

Y

tc@box:~$

tc@box:~$ sudo ./rploader.sh satamap now

HBA: 00:1f.2 Disks : 6

SataPortMap=6

DiskIdxMap=00

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

Y

tc@box:~$

tc@box:~$ sudo ./rploader.sh identifyusb now

Found USB SanDisk SerialNumber: 00003615093021102742

Vendor ID : 0x0781 Product ID : 0x5583

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

Y

tc@box:~$

tc@box:~$ sudo ./rploader.sh build bromolow-7.0.1-42218 now

Loader source : https://github.com/jumkey/redpill-load.git Loader Branch : develop

Redpill module source : https://github.com/RedPill-TTG/redpill-lkm.git : Redpill module branch : master

Extensions :

Extensions URL :

TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.bromolow-7.0.dev.txz/download

TOOLKIT_SHA : a5fbc3019ae8787988c2e64191549bfc665a5a9a4cdddb5ee44c10a48ff96cdd

SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/25426branch/bromolow-source/linux-3.10.x.txz/download

SYNOKERNEL_SHA : 18aecead760526d652a731121d5b8eae5d6e45087efede0da057413af0b489ed

COMPILE_METHOD : toolkit_dev

TARGET_PLATFORM       : bromolow

TARGET_VERSION    : 7.0.1

TARGET_REVISION : 42218

REDPILL_LKM_MAKE_TARGET : dev-v7

KERNEL_MAJOR : 3

MODULE_ALIAS_FILE= modules.alias.3.json

Checking Internet Access -> OK

Checking if a newer version exists on the repo -> gzip: modules.alias.3.json.gz: No such file or directory

gzip: modules.alias.4.json.gz: No such file or directory

sha256sum: latestrploader.sh: No such file or directory

There is a newer version of the script on the repo should we use that ? [yY/nN]Y

OK, updating, please re-run after updating

cp: cannot stat '/home/tc/latestrploader.sh': No such file or directory

Updating tinycore loader with latest updates

Backing up files to /mnt/sde3//mydata.tgz

Done.

tc@box:~$

tc@box:~$ sudo ./rploader.sh ext bromolow-7.0.1-42218 auto

Loader source : https://github.com/jumkey/redpill-load.git Loader Branch : develop

Redpill module source : https://github.com/RedPill-TTG/redpill-lkm.git : Redpill module branch : master

Extensions :

Extensions URL :

TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.bromolow-7.0.dev.txz/download

TOOLKIT_SHA : a5fbc3019ae8787988c2e64191549bfc665a5a9a4cdddb5ee44c10a48ff96cdd

SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/25426branch/bromolow-source/linux-3.10.x.txz/download

SYNOKERNEL_SHA : 18aecead760526d652a731121d5b8eae5d6e45087efede0da057413af0b489ed

COMPILE_METHOD : toolkit_dev

TARGET_PLATFORM       : bromolow

TARGET_VERSION    : 7.0.1

TARGET_REVISION : 42218

REDPILL_LKM_MAKE_TARGET : dev-v7

KERNEL_MAJOR : 3

MODULE_ALIAS_FILE= modules.alias.3.json

Checking Internet Access -> OK

Cloning into 'redpill-lkm'...

fatal: unable to access 'https://github.com/RedPill-TTG/redpill-lkm.git/': SSL certificate problem: certificate is not yet valid

Cloning into 'redpill-load'...

fatal: unable to access 'https://github.com/jumkey/redpill-load.git/': SSL certificate problem: certificate is not yet valid

Testing modules.alias.3.json -> File OK

------------------------------------------------------------------------------------------------

It looks that you will need the following modules :

 

 

Found SATA Controller : pciid 8086d00001c02  Required Extension :

No matching extension

Found VGA Controller : pciid 102bd00000533  Required Extension :

No matching extension

Found Ethernet Interface : pciid 14e4d0000165f Required Extension : tg3.ko

Searching for matching extension for tg3.ko

Found Ethernet Interface : pciid 14e4d0000165f Required Extension : tg3.ko

Searching for matching extension for tg3.ko

------------------------------------------------------------------------------------------------

tc@box:~$

 

 

Trying to build on another box (Older Dell Duo core) so my kids can play around with it, and I'm getting this same errors.

it seems the sites are down or a chance in the code on how to acess it?

any help would be apreciated 

ps: I have a sucessully installed and updated I7 machine running DS3266xs+ with DSM 7.1.

Link to comment
Share on other sites

22 hours ago, pocopico said:

 

You can change that from within DSM or withing TC by editing grub.cfg which is on the first partition of the loader

I think I found correct settings for my test build. 

I have got in total 6 disks, (3 HDD and 3 SSDs)

2 HDDs I connected to SATA1 and SATA2 ports on my motherboard, (still I have two empty ports) 

3 SSDs and 1 HDD I connected to my SAS controller. 

 

I edited grub.cfg file

 

SataPortMap 48 and  DiskIdxMap 0005

 

and after reboot I can see that everything seems to be in order. 

 

 

 

Diskmap02.thumb.PNG.a0e9fd21bd58641f99b26fff45f33f89.PNGDiskmap01.thumb.PNG.104d2ae09188e82a107ba7d302e6efe0.PNG
 

The only minor problem is with (I think) SAS cable, Each individual disk cable has got own label form P1-P4.  
I am not quite sure why disk which is connected to P1 (I assume should be first) but is 3rd in my Storage Manager.
Instead Drive 5 - SK hynix SH920 (connected to P4) I would expect Samsung 860 Evo (connected to P1) 

Similar situation is with Toshiba MQ001ABF050 and Crucial. 

Everything is swapped. 
I am not quite sure if this is big deal, or maybe controller recognizes disks in own order rather than cable labels. 

 

  

disks order.JPG

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

21 minutes ago, MajkelP said:

I think I found correct settings for my test build. 

I have got in total 6 disks, (3 HDD and 3 SSDs)

2 HDDs I connected to SATA1 and SATA2 ports on my motherboard, (still I have two empty ports) 

3 SSDs and 1 HDD I connected to my SAS controller. 

 

I edited grub.cfg file

 

SataPortMap 48 and  DiskIdxMap 0005

 

and after reboot I can see that everything seems to be in order. 

 

 

 

Diskmap02.thumb.PNG.a0e9fd21bd58641f99b26fff45f33f89.PNGDiskmap01.thumb.PNG.104d2ae09188e82a107ba7d302e6efe0.PNG
 

The only minor problem is with (I think) SAS cable, Each individual disk cable has got own label form P1-P4.  
I am not quite sure why disk which is connected to P1 (I assume should be first) but is 3rd in my Storage Manager.
Instead Drive 5 - SK hynix SH920 (connected to P4) I would expect Samsung 860 Evo (connected to P1) 

Similar situation is with Toshiba MQ001ABF050 and Crucial. 

Everything is swapped. 
I am not quite sure if this is big deal, or maybe controller recognizes disks in own order rather than cable labels. 

 

  

disks order.JPG

This post helped me understand much about SMP and DIM

https://gugucomputing.wordpress.com/2018/11/11/experiment-on-sata_args-in-grub-cfg/

 

try sata_remap=2>4:3>5

or sata_remap=2>4:4>2:3>5:5>3

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

8 hours ago, Brunox said:

You can't downgrade from 7.0.1-42218U3 to 7.0.1-42218! I don't think TC supports the U3 (but it's not necessary either) If I were you, I would first update to DS918 7.1.0-42621 and/or 7.1.0-42661, and only then create a new loader for DS3622-7.1.0-42661, the migration to DS3622 then takes place automatically with the first Boot the newly created loader!

 

Don't forget to back up your HDD data before!!!

As I understand, when installing dsm 7.0.1-42218 (or any version?) the unit goes online and downloads the current updated version, in this case 42218U3. To prevent that, you will have to remove internet connectivity during the process and reboot, and once its up to a desktop you can re-establish internet connection.

Link to comment
Share on other sites

2 hours ago, nemesis122 said:

I have for 3622 the same and i think this is normal / when you need that this is functional you have to try 3615

Are you saying the DS3622 build prevents itself from communicating with synology and discovering dsm updates!? Awesome! Perfect!

Link to comment
Share on other sites

Updates are blocked on purpose at redpill level, first its not good for custom synology to phone home and second and probably most importantly is that some smart users will configure automatic updates and will get their systems bricked.

 

 

5 hours ago, lws8964 said:

I Can download package from package center but can not check update.

Screen Shot 2022-04-15 at 8.23.10 AM.png

 

 

Link to comment
Share on other sites

15 hours ago, cpresco said:

 

I believe in an earlier post Peter Suh recommended migrating an exiting DS918+/7.0.1-42218 to DS3622xs+/7.0.1-42218 before upgrading to 7.1.0-42661.

 

I'm going to try these steps on spare hardware with DS918+/7.0.1-42218 that is similar to my in-use DS918+/7.0.1-42218 system.

 

Data backup is #1 on the list of steps before doing this on my in-use DS918+/7.0.1-42218 system. :)

 

Brunox, your reply is appreciated.

 

I'd be interested to know/hear anyone's experience with migrating an existing DS918+/7.0.1-42218 to DS3622xs+/7.0.1-42218.

That's also correct what Peter wrote, but since you already have U3 installed on your Synology, you can only migrate to DS3622xs+ 7.0.1-42218U3 and that doesn't exist "officially" in TC !! That's your problem and that's why I would first change the firmware in your place that is available in TC on the DS918 and on the DS3622 and that would be either 7.1-42621 or 7.1-42661 and only then migrate the system to DS3622!

 

I hope I was able to explain your little problem in a reasonably understandable way

BR Brunox

Link to comment
Share on other sites

You can upgrade directly to 7.1, I did it and zero issues with current loader state

 

 

3 minutes ago, Brunox said:

That's also correct what Peter wrote, but since you already have U3 installed on your Synology, you can only migrate to DS3622xs+ 7.0.1-42218U3 and that doesn't exist "officially" in TC !! That's your problem and that's why I would first change the firmware in your place that is available in TC on the DS918 and on the DS3622 and that would be either 7.1-42621 or 7.1-42661 and only then migrate the system to DS3622!

 

I hope I was able to explain your little problem in a reasonably understandable way

BR Brunox

 

Link to comment
Share on other sites

13 hours ago, Jizar Stoffel said:

Trying to build on another box (Older Dell Duo core) so my kids can play around with it, and I'm getting this same errors.

it seems the sites are down or a chance in the code on how to acess it?

any help would be apreciated 

ps: I have a sucessully installed and updated I7 machine running DS3266xs+ with DSM 7.1.


Check the system date. SSL certificates are invalid if your system date is out of date

Link to comment
Share on other sites

Posted (edited)
On 4/14/2022 at 5:41 AM, Hong Kong said:

Hello,

I downloaded and burn tinycore-redpill.v0.4.6 to my USB drive and boot it to my HP Microserver Gen 8 with 4 disks. However, I cannot make it work.

Commands shown below.

 

My questions:

  1. My system is using Intel(R) Celeron(R) CPU G1610T @ 2.30GHz with 2GB RAM. Is the DS3615xsbromolow-7.0.1-42218 a good choice?
  2. There is no modules.alias.3.json.gz  modules.alias.4.json.gz  latestrploader.sh on my drive. Is it normal?
  3. There are SSL certificate problem: certificate is not yet valid errors. Are they expected?
  4. Do I need the pciid 8086d00001c02 and pciid 102bd00000533 extensions? If yes, how can I locate and include them?

Many thanks!

 

tc@box:~$ sudo ./rploader.sh update now

Checking Internet Access -> OK

Checking if a newer version exists on the repo -> gzip: modules.alias.3.json.gz: No such file or directory

gzip: modules.alias.4.json.gz: No such file or directory

sha256sum: latestrploader.sh: No such file or directory

There is a newer version of the script on the repo should we use that ? [yY/nN]Y

OK, updating, please re-run after updating

cp: cannot stat '/home/tc/latestrploader.sh': No such file or directory

Updating tinycore loader with latest updates

Backing up files to /mnt/sde3//mydata.tgz

Done.

tc@box:~$

tc@box:~$ sudo ./rploader.sh serialgen DS3615xs now

Serial Number for Model : 1330LWN027197

Mac Address for Model DS3615xs : 00:11:32:C4:8A:21

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

Y

tc@box:~$

tc@box:~$ sudo ./rploader.sh satamap now

HBA: 00:1f.2 Disks : 6

SataPortMap=6

DiskIdxMap=00

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

Y

tc@box:~$

tc@box:~$ sudo ./rploader.sh identifyusb now

Found USB SanDisk SerialNumber: 00003615093021102742

Vendor ID : 0x0781 Product ID : 0x5583

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

Y

tc@box:~$

tc@box:~$ sudo ./rploader.sh build bromolow-7.0.1-42218 now

Loader source : https://github.com/jumkey/redpill-load.git Loader Branch : develop

Redpill module source : https://github.com/RedPill-TTG/redpill-lkm.git : Redpill module branch : master

Extensions :

Extensions URL :

TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.bromolow-7.0.dev.txz/download

TOOLKIT_SHA : a5fbc3019ae8787988c2e64191549bfc665a5a9a4cdddb5ee44c10a48ff96cdd

SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/25426branch/bromolow-source/linux-3.10.x.txz/download

SYNOKERNEL_SHA : 18aecead760526d652a731121d5b8eae5d6e45087efede0da057413af0b489ed

COMPILE_METHOD : toolkit_dev

TARGET_PLATFORM       : bromolow

TARGET_VERSION    : 7.0.1

TARGET_REVISION : 42218

REDPILL_LKM_MAKE_TARGET : dev-v7

KERNEL_MAJOR : 3

MODULE_ALIAS_FILE= modules.alias.3.json

Checking Internet Access -> OK

Checking if a newer version exists on the repo -> gzip: modules.alias.3.json.gz: No such file or directory

gzip: modules.alias.4.json.gz: No such file or directory

sha256sum: latestrploader.sh: No such file or directory

There is a newer version of the script on the repo should we use that ? [yY/nN]Y

OK, updating, please re-run after updating

cp: cannot stat '/home/tc/latestrploader.sh': No such file or directory

Updating tinycore loader with latest updates

Backing up files to /mnt/sde3//mydata.tgz

Done.

tc@box:~$

tc@box:~$ sudo ./rploader.sh ext bromolow-7.0.1-42218 auto

Loader source : https://github.com/jumkey/redpill-load.git Loader Branch : develop

Redpill module source : https://github.com/RedPill-TTG/redpill-lkm.git : Redpill module branch : master

Extensions :

Extensions URL :

TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.bromolow-7.0.dev.txz/download

TOOLKIT_SHA : a5fbc3019ae8787988c2e64191549bfc665a5a9a4cdddb5ee44c10a48ff96cdd

SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/25426branch/bromolow-source/linux-3.10.x.txz/download

SYNOKERNEL_SHA : 18aecead760526d652a731121d5b8eae5d6e45087efede0da057413af0b489ed

COMPILE_METHOD : toolkit_dev

TARGET_PLATFORM       : bromolow

TARGET_VERSION    : 7.0.1

TARGET_REVISION : 42218

REDPILL_LKM_MAKE_TARGET : dev-v7

KERNEL_MAJOR : 3

MODULE_ALIAS_FILE= modules.alias.3.json

Checking Internet Access -> OK

Cloning into 'redpill-lkm'...

fatal: unable to access 'https://github.com/RedPill-TTG/redpill-lkm.git/': SSL certificate problem: certificate is not yet valid

Cloning into 'redpill-load'...

fatal: unable to access 'https://github.com/jumkey/redpill-load.git/': SSL certificate problem: certificate is not yet valid

Testing modules.alias.3.json -> File OK

------------------------------------------------------------------------------------------------

It looks that you will need the following modules :

 

 

Found SATA Controller : pciid 8086d00001c02  Required Extension :

No matching extension

Found VGA Controller : pciid 102bd00000533  Required Extension :

No matching extension

Found Ethernet Interface : pciid 14e4d0000165f Required Extension : tg3.ko

Searching for matching extension for tg3.ko

Found Ethernet Interface : pciid 14e4d0000165f Required Extension : tg3.ko

Searching for matching extension for tg3.ko

------------------------------------------------------------------------------------------------

tc@box:~$

 

 


check and fix your system date. If the date is invalid your system certificates will not be respected 

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

The approval of the new topic has been delayed so much that I share the full version 7.1 guide first.

 

If you are using an existing 7.0.1 after the version of the Synology DSM was updated to 7.1, you may want to update to 7.1

 

or this is a guide for those who want to install 7.1 from the beginning.

 

For those who are new to this article, I will share it with you by adding and subtracting it from the existing 7.0.1 guide.

 

It is a translation from Korean to English using a translator.

 

Please understand if there is a slight misunderstanding.

 

 

 

Existing RedPill, released last year, can generate IMG files directly through the compilation process of the bootloader only if Linux is available separately

 

In the case of tinyCore RedPill, it comes completely with tinyCore Linux in the form of a USB boot image

 

It's much easier without having to install and prepare linux separately.

 

 

 

You can add the drivers you want to build after you select them and add them directly.

 

The latest version of tinycore supports a total of 7 models (DS3622xs+/DS918+/DS3615xs/DS3617xs/DS1621+/DS920+/DVA3221)

 

You can continuously change the boot loader on your own without re-imaging it (model/sn/mac, etc.)

 

Tinycore supports both img for native installation and vmdk for virtual environments.

 

 

 

1.Preparing Bootloader IMG

 

Use the Download button in the middle of the beam link below.Download the gz file

 

In it 0.4.6 version img.You can decompress the gz file one more time and use the img file.

 

(Full File)

 

https://github.com/pocopico/tinycore-redpill

 

(for LEGACY / EFI)

 

https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.4.6.img.gz

 

(for VMWARE)

 

https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.4.6.vmdk.gz

 

 

 

2. Bootloader IMG File USB Recording

 

Use the above tinycore-redfill.v0.4.6.img file to burn it with USB with a convenient image tool such as WinImage or Rufus.

 

You don't need to adjust the configuration file in advance to modify the VID/PID/Serial/MAC/SATAPortMap like the JUN loader.

 

 

 

If you want to create a USB image on a Mac or Linux like me, you can use the DD command below in the terminal.

 

(Assuming that the DEVICE ID of the USB verified by diskutil is disk4)

 

sudo diskutil unmountDisk /dev/disk4

 

sudo dd if=/Users/MyAccount/Downloads/tinycore-redpill.v0.4.5.img of=/dev/disk4 bs=1m

 

sudo diskutil eject /dev/disk4

 

 

 

3.Starting TinyCore Linux

 

USB boot by plugging it into a PC for xpenology (UEFI 1 partition or USB CSM can be booted)

 

The tinyCore Linux (tinyCore Image Build menu) is running and appears.

 

Run the far right icon terminal app here.

 

Check the ip address automatically assigned an en0 LAN card with ifconfig.

 

 

 

[tinyCore Linux Screen]

 

220210_lec_e7397197e78d8a0ccb100073529ff34d3adfbf13.thumb.jpg.c83145a60ed0cdaddd6b58fe54f57085.jpg.f1cda8a9aa409b0324d7559f0367f6be.jpg

4. Adjust CONFIG after SSH connection ( In fact, the command is executed in number 7 below, and this is a preliminary explanation. )

 

Ssh connection with putty etc. from PC other than xpenology. ( id:tc / pass : P@ssw0rd )

 

I'm connecting.

 

 

 

Tinycore Redfill is stabilizing right now

 

PocoPico, the original author of this program, fixes bugs from time to time and announces rebuilding.

 

There's a possibility that this rebuild will happen from time to time

 

Even with the final image version of 0.4.6, changes can still be updated in real time over the Internet.

 

Sometimes the rploader.sh file itself changes if there is a bug.

 

 

 

If you've migrated from JUN xpenology,

 

at tc@box:~$user_config.json

 

Existing grub such as VID/PID/Sn/Mac/SataPortMap in user_config.json file.Refer to the cfg and move it as it is.

 

For new installers, perform serial GEN/USB VID, PID auto-detect, SataPortMap auto-detect, etc. as shown below.

 

For the next process, I will share the command focusing on the platform that I have completed the most normal verification.

 

tc@box:~$./rploader.sh serialgen (select one from DS3622x+/DS918+/DS3615xs/DS3617xs/DS1621+/DS920+/DV3221)

 

tc@box:~$ ./rploader.sh identifyusb now

 

tc@box:~$./rploader.sh satamap now (no HBA card user required)

 

You can see that the contents of user_config.json have been changed automatically.

 

 

 

Finally, the commonality of existing users and new installers is

 

tc@box:~$catuser_config.json If you assume that there are 4 internal Sata ports,

 

SataPortMap = "4",

 

DiskIdxMap = "00"

 

Please check if it's changed to the back.

 

After find.synology.com, you may not be able to find SATA HDDs during DSM installation.

 

The following is an example of a 6-port SATA additional expansion card.

 

SataPortMap = "46",

 

DiskIdxMap = "0000"

 

(Except for those who use H200, H310, H710, etc. cards, you don't have to clear the options for this SataPortMap and DiskIdxMap itself and use it.

 

Please erase the lines of the above two options with the vi editor and organize them well so that there are no Syntex errors. Of course.

 

./rploader.sh satamap now command is not required.)

 

 

 

5.BIOS Internal SATA Port Hot Plug disable -> enable Handling (Important)

 

To avoid temporarily reducing the number of SATA PortMap maps set above by the number of HDDs physically connected by the Sata cable during the DSM installation process:

 

Make sure to turn on the Hot Plug function.

 

This reduces the probability of encountering an error message stating that the above automatically recognizes the number of SATAPortMaps and the HDD is not found.

 

Please refer to the link below for the relevant details highlighted by TheSTREET.

 

http://www.2cpu.co.kr/nas/37891

 

 

6.Add boot loader extension driver after SSH connection (optional)

 

 

7.Build Boot Loader After SSH Connection (Two Step Update - TSU)

 

If you are done adding the above extension drivers, build the bootloader at the end.

 

After 7.0.1 build, check if the custom-module -> /mnt/sdb3/auxfiles directory is created well with the ll command.

 

Without this directory, the second 7.1.0 build will fail.

 

 

If you do not see the custom-module -> /mnt/sdb3/auxfiles directory,

 

Please do the 7.0.1 build again.

 

 

[DS3622xs+]

 

./rploader.sh update now

 

./rploader.sh fullupgrade now

 

 

./rploader.sh serialgen DS3622xs+

 

./rploader.sh identifyusb now

 

./rploader.sh satamap now

 

 

./rploader.sh build broadwellnk-7.0.1-42218

 

(run if custom-module -> /mnt/sdb3/auxfiles is missing)

ll /mnt. (Check the 3rd partition in usb)

sudo ln -s /mnt/sdb3/auxfiles /home/tc/custom-module

 

./rploader.sh clean now

 

./rploader.sh build broadwellnk-7.1.0-42661

 

 

./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now;

 

 

[DS918+]

 

./rploader.sh update now

 

./rploader.sh fullupgrade now

 

 

./rploader.sh serialgen DS918+

 

./rploader.sh identifyusb now

 

./rploader.sh satamap now

 

 

./rploader.sh build apollolake-7.0.1-42218

 

(run if custom-module -> /mnt/sdb3/auxfiles is missing)

ll /mnt. (Check the 3rd partition in usb)

sudo ln -s /mnt/sdb3/auxfiles /home/tc/custom-module

 

./rploader.sh clean now

 

./rploader.sh build apollolake-7.1.0-42661

 

 

./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now;

 

 

[DS3615xs]

 

./rploader.sh update now

 

./rploader.sh fullupgrade now

 

 

./rploader.sh serialgen DS3615xs

 

./rploader.sh identifyusb now

 

./rploader.sh satamap now

 

 

./rploader.sh build bromolow-7.0.1-42218

 

(run if custom-module -> /mnt/sdb3/auxfiles is missing)

ll /mnt. (Check the 3rd partition in usb)

sudo ln -s /mnt/sdb3/auxfiles /home/tc/custom-module

 

./rploader.sh clean now

 

./rploader.sh build bromolow-7.1.0-42661

 

 

./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now;

 

 

[DVA3221]

 

./rploader.sh update now

./rploader.sh fullupgrade now

 

./rploader.sh serialgen DVA3221

./rploader.sh identifyusb now

./rploader.sh satamap now

 

./rploader.sh build denverton-7.0.1-42218

 

(run if custom-module -> /mnt/sdb3/auxfiles is missing)

ll /mnt. (Check the 3rd partition in usb)

sudo ln -s /mnt/sdb3/auxfiles /home/tc/custom-module

 

./rploader.sh clean now

./rploader.sh build denverton-7.1.0-42661

 

./rploader.sh clean now;  rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module;  ./rploader.sh backup now;

 

The last line doesn't get restored even if you reboot later

 

It is the process of organizing the folders where the pat file exists and reducing the capacity and completing the backup.

 

 

 

8-1.Using the bootloader (update user)

 

tc@box:~$ sudo poweroff

 

Place the 7.1 bootloader on the bottom well

 

 

In the existing 7.0.1 henol boot state, obtain the DSM 7.1.0-42661.pat file separately from the Sinology Download Center

 

https://www.synology.com/ko-kr/support/download

 

Click the Control Panel -> Update and Restore -> DSM Update -> Manual DSM Update button and proceed with the update to the prepared pat file above.

 

 

 

If you are asked to wait 10 minutes after the update, use the telnet connection method that appears in the NAS column by searching for the title telnet

 

I'll power off.

 

-> using putty and telnet it using user=root without password.  after you type root then enter, it will goes to linux prompt.

 

 

 

By the way, if there are a lot of actual packages installed, it says that you have to wait 20 minutes.

 

Very few packages appear to wait 10 minutes.

 

If you don't want to let me go to the Wi-Telnet connection process, check the monitor to see if you want to power down when rebooting or when rebooting

 

I think you can change it quickly to enter TC Linux.

 

1512307271_254382882_2022-04-1312_46_09.thumb.png.ff14ce9e8c152ddd189c5e8d987a9f6a(1).png.50b0d36133540c283ba5be895a284d76.png

 

Replace the USB with the 7.1 boot loader prepared above and proceed with the boot

 

You can use it. (There's nothing else I can do for you.)

 

191965412_2022-04-1010_29_22.thumb.png.e8dc4924304ff086e73f8dd68f7eceea.png.549ca4ceddbb9ed9d041736dbe998de7.png

 

If you want to update from 7.0.1 to 7.1,

Process 8-1 in the guide above, and if you're using it, boot from USB and enter Tinycore Linux again

You can start from number 3. Tynicore Linux is the third menu, so you have to switch quickly in 4 seconds.

This is a method that can be carried out without preparing one more USB memory, but the existing 7.0.1 boot loader may be erased

You can use the new functions, backuploader now and restoreloader now action

 

 

 

8-2.Use bootloader (new installer)

 

After successfully completing the build above, reboot the xpenology with USB using the command below.

 

tc@box:~$ sudo reboot

 

 

 

The settings or ext drivers that were backed up remain the same

 

The setting values are restored from the mydata.tgz file and remain intact at the next Tiny Core Image Build boot for modification.

 

(The default setting for automatic entry within 4 seconds is USB, Verbose at the top. If you don't touch it with your keyboard, it will automatically enter USB mode.)

 

191965412_2022-04-1010_29_22.thumb.png.e8dc4924304ff086e73f8dd68f7eceea.png.549ca4ceddbb9ed9d041736dbe998de7.png

 

xpenology On-Screen After PC Boots

 

In the case of the existing RedPill, you will be asked to find it at find.synology.com like the existing Jun loader

 

For this tinyCore,

 

Decompressing Linux... Parsing ELF... done.

 

Booting the kernel.

 

This is the message. There is a delay of 1 to 2 minutes from the IP allocation, so please wait a little bit.

 

In this state, browse to find.synology.com on another PC and you will find the xpenology IP.

 

After that, you can proceed with the installation process of the Synology DSM as you are working on the existing xpenology.

Edited by Peter Suh
  • Like 5
Link to comment
Share on other sites

20 hours ago, loveburn said:

Guy's the internal antivirus can't update virus bases always error

 

"Can't update virus base with freshclam (ext code:17 err code 2)"

Anyone have same troubles?

 

can you ssh to your box and do a cat /etc/hosts ? if you have two syno lines pointing to localhost remove the last one and check

  • Like 1
Link to comment
Share on other sites

4 минуты назад, pocopico сказал:

 

can you ssh to your box and do a cat /etc/hosts ? if you have two syno lines pointing to localhost remove the last one and check

I am already fix it, in our country Cisco blocked clamav.net domain) i edit the freshcalm.conf and add mirror for download updates and it's work) thanks for your thinks)

Edited by loveburn
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...