Jump to content
XPEnology Community

Tutorial: Install/Migrate to DSM 7.x with TinyCore RedPill (TCRP) Loader


flyride

Recommended Posts

Hello all, I am looking to install xpenology on a proxmox VM, ryzen 5 4650g, 32gb ram, HBA card, 4x18tb hdd, 2x nvme for cache, 2x ssd for VMs/other. 

 

Which model do I choose as there are new ones available that are not in the DSM 7.X tutorial info. 423+, 923+, 1621+, 1821+ 1823xs+ 3622xs+ etc?

 

What are the differences between these models in xpenology because in the bootloader you can unlock nvme caching, extra bays etc 

Link to comment
Share on other sites

  • 1 month later...

Hi all.  I'm exploring Xpenology and loving the reviews.  But each time I try to build, I get this same error.  I'm trying to build DVA1622 on a i5 EliteDesk.  

 

Can somebody help me out?

TIA

Aescleal

 

tc@box:~$ ./rploader.sh build geminilake-7.2.1-69057-4 auto
Error : Platform not found :
rploader.sh

Version : 0.10.0.0

Link to comment
Share on other sites

5 hours ago, Aescleal said:

Hi all.  I'm exploring Xpenology and loving the reviews.  But each time I try to build, I get this same error.  I'm trying to build DVA1622 on a i5 EliteDesk.  

 

Can somebody help me out?

TIA

Aescleal

 

tc@box:~$ ./rploader.sh build geminilake-7.2.1-69057-4 auto
Error : Platform not found :
rploader.sh

Version : 0.10.0.0

That's because you are using the old command. The new command would be: ./rploader.sh build dva1622-7.2.1-69057-4 auto. It is mentioned on page 4 of this thread.

But there are easier ways to build such as ARPL and Peter Suh's MShell which is based on TRCP:

 

Link to comment
Share on other sites

6 hours ago, rojoone2 said:

That's because you are using the old command. The new command would be: ./rploader.sh build dva1622-7.2.1-69057-4 auto. It is mentioned on page 4 of this thread.

But there are easier ways to build such as ARPL and Peter Suh's MShell which is based on TRCP:

 

Hi rojoone2.  Thanks for the fast heads up.  I started over using that build example, and I still get the same problem.  I just don't see what I'm doing wrong.

So, I'll check out M-Shell and see if that will have a better result.  If you think of anything else let me know!  Thanks again!
 

tc@box:~$ tc@box:~$ ./rploader.sh build dva1622-7.2.1-69057-4 auto
bspatch does not exist, bringing over from repo
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 10232  100 10232    0     0  66441      0 --:--:-- --:--:-- --:--:-- 66441
Error : Platform not found :
rploader.sh

Version : 0.10.0.0
----------------------------------------------------------------------------------------
Usage: ./rploader.sh <action> <platform version> <static or compile module> [extension manager arguments]

Link to comment
Share on other sites

  • 3 weeks later...
On 3/26/2024 at 8:35 PM, crazyazz said:

I setup my NAS and lost the USB boot device, to I have to do the complete process again?

If you did not make a backup, then yes. You could also try Peter Suh's M-Shell which is based on TCRP, but with a build process like ARPL.

Link to comment
Share on other sites

  • 1 month later...

Hi,

I did follow the tutorial and used both RedPill & ARL options.

I tried multiple times installing  DS918+/DS920+/DS3622xs+ and everytime installig DSM via IP::5000/web_index.html succeded.

However. after rebooting - I could not boot the machine.

Are there any additional steps I need to do or is there a way to check/correct the DSM bootloader from disk?

Regards

Link to comment
Share on other sites

additiona info - I have booted from debian live cd and checked using efibootmgr

- I dont see any DSM-related boot entry

 

with this its unable to load althouth the DSM installation finished succesfully.

 

Question - how to correct the boot now?

Link to comment
Share on other sites

  • 3 weeks later...
Posted (edited)

Hello,

I think I made a mistake updating ARC Loader: I use the update menu in ARC Loader, and now Im' well on 24.5.20 version but... ARC still booting on it and not into DSM. How may i do a DSM Force reinstall ??

image.thumb.png.b310b35b24b3e0b1361be9f4279c2a12.png

 

And I can't insert the entire URL tof DSM Pat file

 

image.thumb.png.380efc4fa652faedf9f2f2f93bc7104b.png

 

I tried to put the pat file on a server with a smaller URL but no chance for now...

 

Edited by waazdakka
Link to comment
Share on other sites

Posted (edited)
18 hours ago, waazdakka said:

Hello,

I think I made a mistake updating ARC Loader: I use the update menu in ARC Loader, and now Im' well on 24.5.20 version but... ARC still booting on it and not into DSM. How may i do a DSM Force reinstall ??

image.thumb.png.b310b35b24b3e0b1361be9f4279c2a12.png

 

And I can't insert the entire URL tof DSM Pat file

 

image.thumb.png.380efc4fa652faedf9f2f2f93bc7104b.png

 

I tried to put the pat file on a server with a smaller URL but no chance for now...

 

 

sshot-1.thumb.png.344d355262795192b4ecfc5d29bdd71c.png

 

Try doing a fresh install from an USB pendrive with new version 24.5.20, not doing an update from a pendrive with a previous version < 24.5.x of ARC Loader like you did, then maybe you'll need to use "DSM Reinstall Mode" after first boot.

Edited by jacqlittle
Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...

First of all thank you all for the great effort in putting this loader together. 

 

I followed the guide (came from a DS3615xs, JUN's 1.03b loader DSM 6.2.2-24922 Update 4)

To a DS918+ DSM 7.2-64570 (I first backupped all my data)

 

In the Synology Assistant it said Migrate so I went ahead. When the system was finished migrating I logged in to find a notice that the volume has crashed and that it detected only 1 drive.

During the build of the loader the ./rploader.sh satamap  part said it detected 4 drives.

 

So I did a check in the BIOS and saw that the SATA mode was on RAID instead of AHCI.
I wasn't aware of that I really thought it was AHCI... but OK I went ahead to change that.
It was not detecting the other drives still in DSM.

 

So I booted back into the Tinycore and did ./rploader.sh satamap and saved it into the config.

 

Then I did ./rploader.sh backup again

And I tried to do ./rploader.sh backuploader but it said that there was not enough diskspace (probably from the previous time I used it). So I went ahead and rebooted. After that it showed up as 'Recoverable' in Synology Assistant. So I went ahead  and recovered it.

 

Then I logged into DSM and saw all my data again, but a warning with 3 other drives 'System Partition Failed'. I did a repair and that fixed it.

So do I need to do the ./rploader.sh backuploader command in a different way or should I delete a 'file' somewhere so that I can do this command? I would really like to backup the loader just in case. Or is the loader already backupped and changing the 'satamap' makes no difference?

 

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