Jump to content
XPEnology Community

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


Recommended Posts


@Peter Suh


Is it safe to update the loader?

Do I just reboot and the loader will auto update?


Or should I wait until you guys sort out the version display issue?




Please clarify... It's my understanding that we SHOULD NOT update the nas beyond what the loader supports? e.g. If loader image is DS3622 version 1 then we do NOT install UPDATE 2 from Synology.

Even though I was able to do it, does NOT mean we do it.

Is my understanding correct?


If my understanding is correct, then perhaps you guys can post a warning in the loader or directions in red something such as DO NOT UPDATE DSM beyond what RPL supports (what we see to download when building the loader, the .pat files listed in the loader)

Edited by droiduser22
Link to comment
Share on other sites

On 5/23/2022 at 8:47 AM, flyride said:

Loader Information and Background


RedPill is the core technology that enables DSM 7.x to run on non-Synology hardware. This post is intended to serve as a definitive tutorial/reference for configuring @pocopico's TinyCore RedPill (TCRP) loader. It explains how to install TCRP on baremetal, i.e. with DSM as the only operating system on your NAS hardware. A tutorial to install TCRP using the ESXi hypervisor is located here. There are other hypervisor tutorials in the Tutorials and Guides forum.


TCRP uses a two step-process. First, a Linux OS (TinyCore) boots and evaluates the NAS hardware configuration. Therefore, it is best to have the hardware you plan to use (disk controllers and network cards in particular) installed prior to starting the TCRP setup.


Then, an individualized loader (RedPill) is created. This loader is used to install and run DSM. After that, you can switch between starting DSM with RedPill, and booting back into TinyCore to adjust and rebuild the loader as needed.


Basic Linux command line skills are needed to complete the installation. The tutorial provides examples of the commands that are needed, but exact syntax and capitalization are critical. If unfamiliar, research and review the following minimal list of commands:


ls show the files in the current directory
cat <file> show the contents of the specified file
pwd show the current directory name
cd <directory path> change to the specified directory (same rules as Windows, except with forward slashes instead of backslashes). With no argument, it returns to the “home” TCRP directory
vi <file> a file editor, for manual editing of configuration files if required


Ongoing Development


This tutorial is maintained for consistency with the pocopico stable repository. Since TCRP is completely open-sourced, anyone can fork their own repo and contribute to development, and pocopico now maintains a separate development repo. As the best features and ideas are fully vetted and tested, they may be incorporated into the stable repo over time. 


If you use a repo, script or shell other than the pocopico stable repo, the loader may behave quite differently and the instructions and troubleshooting steps in this tutorial might no longer apply. In an open-source community, you can use any development resource you want, but you add the additional responsibility of understanding, vetting and testing that code on your system.




  Reveal hidden contents

DSM 6.x (with Jun’s loader) can be migrated to DSM 7.x using TCRP.

Do not attempt to upgrade from 6.x to 7.x using the Control Panel.


Complete the following tasks prior to migration:

  1. Read through this reference thoroughly
  2. Remove the 6.x loader USB and array disks (making sure to mark their order)
  3. Build a TCRP loader on a new USB to practice and confirm the build process
    (with all the same NAS hardware that will be used for the upgrade)
  4. Trial install DSM 7.x to a test HDD/SDD
  5. Verify DSM is working perfectly with all the NAS hardware
  6. Remove the test USB and HDD/SDD, and restore the 6.x loader USB and array disks
  7. VERIFY BACKUP of all data saved elsewhere before attempting an in-place upgrade

The actual migration process is simple:

  1. Remove any existing SSD cache configuration (strongly recommended)
  2. Shut down the NAS
  3. Replace the existing 6.x USB loader with the TCRP 7.x USB loader from the process above
  4. Boot the NAS and complete the DSM Migration when prompted
  5. Restore SSD cache configuration as desired

NOTE: Depending on which DSM version was previously installed, the migration process may override the manual option for DSM updates and set it to automatic. Restore the manual option from Control Panel as soon as possible - it might be necessary to shutdown the Internet connection until that is complete.


Step 1. Choose a DSM Platform/Architecture


Evaluate your intended NAS hardware and your the intended use of DSM, and select a platform that best meets your needs. Reference information here: https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/


Write down the selected platform (e.g. DS918+), the corresponding architecture (e.g. apollolake) and whether the platform uses SataPortMap/DiskIdxMap or Device Tree for slot mapping. This information will be needed later.

Now, make sure the NAS hardware is compatible, and prepare it correctly:

  • x86-64-compatible CPU with two cores or more
    • Each platform have maximum threads support! Any threads in excess will be ignored
    • For certain platforms, Intel CPUs must be 4th generation “Haswell” or newer with FMA3 instruction set
      The corresponding AMD CPU architecture is “Piledriver” or newer
    • AMD-based systems may require deactivation of the C1E option in the BIOS
  • 2GB of RAM or more
  • 2GB or larger USB flash drive
    • Configure the BIOS to boot from the USB flash drive ONLY
  • SATA disk controllers are preferred, but SCSI/SAS are compatible
    • IMPORTANT: All SATA controllers must be configured to AHCI mode
    • SATA controllers with port multipliers are not compatible
    • ATA controllers are not compatible (disable embedded ATA in BIOS if possible)
  • At least one SATA/SCSI/SAS drive (HDD or SSD), minimum size 21GB
    • IMPORTANT: Enable SATA port hotplug on each disk port, if hotplug is supported by the BIOS/controller
    • IMPORTANT: Disable M.2 SATA ports that are not in use, if supported by the BIOS/controller
    • NVMe drives are not usable except as dedicated cache devices
    • Host Bus Adapters are not currently compatible with Device Tree platforms
  • Install any NVMe drives intended as cache devices
    • On Device Tree platforms, NVMe drives must be installed prior to loader installation in order for them to be recognized

Step 2. Download TCRP and Write Image to the USB Flash Drive


The latest pocopico stable loader code is always linked here: https://xpenology.com/forum/topic/7848-links-to-loaders/

Download the tinycore-redpill 7.x loader and save it to your personal computer. Then, open it with a zip manager to show the boot images:


tinycore-redpill.vX.X.X.img.gz                    (for BIOS/CSM/Legacy boot from USB flash drive)
tinycore-redpill-uefi.vX.X.X.img.gz            (for UEFI/EFI boot from USB flash drive)
tinycore-redpill.vX.X.X.vmdk.gz                 (for virtual machine SATABOOT from disk image)


Select the boot image that matches the boot capability of the NAS motherboard. If unsure, choose BIOS/CSM/Legacy boot. Save the gzip file to your personal computer, then open it with a zip archive manager and save the uncompressed version.


Write the uncompressed image to the USB flash drive using Win32DiskImager or other appropriate tool.

The USB flash drive is used to store TinyCore and the RedPill loader that it generates. It is a permanent component of an operational XPEnology system. Do not remove it, even after the DSM installation is complete and the NAS is fully up and running.


Step 3. Boot into TinyCore and Complete Pre-Configuration Updates


Start your NAS with the USB flash drive installed and TinyCore will boot. Then, launch a command-line session with either of these methods:

  • Click the Terminal icon at the bottom right of the TinyCore desktop to launch a console window
  • Use a ssh client (e.g. PuTTY) on your computer to connect a network-based console
    • Consult your DHCP server/router for the IP address assignment (TinyCore's host name is "box")
    • Login credentials: tc/P@ssw0rd

When the Linux command line prompt ($) is displayed, update the TCRP script

./rploader.sh update
Checking Internet Access -> OK
Checking if a newer version exists -> There is a newer version on the repo should we use that ? [yY/nN] Y
OK, updating, please re-run after updating
Updating tinycore loader with latest updates
Backing up files to /mnt/sda3//mydata.tgz


Then, update the TCRP support files

./rploader.sh fullupgrade
<downloads snipped>
Current /home/tc size is 114M , try to keep it less than 1GB as it might not fit into your image
Should i update the sda with your current files [Yy/Nn] Y
Backing up home files to sda : Backing up files to /mnt/sda3//mydata.tgz


Finally, choose a DSM release number

Each DSM build as provided by Synology has a release number.  You can display the combinations of platforms and releases supported by TCRP by just running the script with no arguments

<command help snipped>
Available platform versions:


Step 4. Configure System-Specific Parameters


Custom system parameters are stored in the user_config.json file. This can be manually edited, or TCRP can help determine appropriate values for the hardware.

  1. USB flash drive VID/PID: TCRP can query the USB flash drive for the hardware vid/pid values that DSM uses to identify the loader during bootup
    ./rploader.sh identifyusb
    Found: Superdisk Flash SerialNumber: 123456
    Vendor ID: 0x1234 Product ID: 0x0001
    Should i update the user_config.json with these values ? [Yy/Nn] Y
  2. Serial number/MAC: TCRP can automatically generate a serial number for the platform selected in step 1. Additionally, it will generate a random MAC address for the NAS network card. If you prefer to use the actual hardware MAC address instead, append "realmac" to the command.

    Example 1: random MAC address
    ./rploader.sh serialgen DS3622xs+
    Serial Number for Model : 20C0SQRLR47QM
    Mac Address for Model DS3622xs+ : 00:11:32:80:B2:36
    Should i update the user_config.json with these values ? [Yy/Nn] Y

    Example 2: real MAC address

    ./rploader.sh serialgen DS3622xs+ realmac
    Serial Number for Model : 2150SQRGS7N5T
    Mac Address for Model DS3622xs+ : 00:11:32:57:3A:9B
    Real Mac Address : 00:0C:24:62:3E:3D
    Notice : realmac option is requested, real mac will be used
    Should i update the user_config.json with these values ? [Yy/Nn] Y


  3. Drive Slot Mapping: TCRP can try to determine how to map the NAS disk controller ports to DSM slots. If the chosen platform uses SataPortMap/DiskIdxMap for port mapping, the command below will do this. If it uses Device Tree for slot mapping, the command may be skipped, as the Device Tree is configured automatically during the loader build.
    ./rploader.sh satamap
    Found "02:02.0 SATA AHCI controller"
    Detected 4 ports/2 drives. Override # of ports or ENTER to accept: <4>
    Recommended settings:
    Should I update the user_config with these values ? [Yy/Nn] Y

    If the port count is not what you expect, it may be due to the motherboard design servicing physical ports with multiple controllers, or because of M.2 SATA slot support. If necessary, the port count can be overridden with whatever you like. NOTE: If you see a WARNING message, it is certain that either some of your drives are inaccessible or the DSM install will encounter problems. Evaluate and investigate the issue.  The satamap command can be rerun as many times as needed to understand the system.

  4. Manual Review: With prior loaders (such as Jun's), the configuration of these parameters was completely manual. There is no single setup that works for all hardware. Even after using the tools above, please review and verify the parameters, understand what they do, and manually edit if needed.

    Whatever changes rploader.sh makes to the user_config.json file can be reviewed by displaying the file contents

    cat user_config.json

    and overridden by editing the file

    vi user_config.json

    You can also add a simpler editor, nano

    tce-load -iw nano
    nano user_config.json

    And there is also a graphical editor accessible from the TinyCore desktopimage.thumb.png.41b953c551a688a06aa217702b82d315.png

Step 5. Optional: Manually Add Driver Extensions


While TCRP can automatically add drivers based on the detected NAS hardware, it isn’t foolproof. You might want to build a loader for a device you don’t actually have yet. And there are features that are "opt-in" only.  So, a process exists to manually add drivers and other functionality. Extensions are stored in repositories hosted on the web. All the extensions in the main repository are viewable here: https://github.com/pocopico/rp-ext


To list all the extensions recommended by TCRP's hardware detection algorithm, use
./rploader.sh listmods <architecture>-<version>-<DSMreleasenumber>

./rploader.sh listmods apollolake-7.1.0-42661


To add a specific extension, choose from the list and reference the architecture from Step 1.
./rploader.sh ext <architecture>-<version>-<DSMreleasenumber> <extensionurl>

./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill-acpid/rpext-index.json
./rploader.sh ext denverton-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json

The examples illustrate adding ACPI and VIRTIO support. These are often chosen enhancements to a basic installation.

Step 6. Build the Loader


When all preparation steps are complete, build the loader using the command structure
./rploader.sh build <architecture>-<version>-<DSMreleasenumber>

Example #1: DS3622xs+, auto detect hardware

./rploader.sh build broadwellnk-7.1.0-42661

Example #2: DS918+, use preselected drivers

./rploader.sh build apollolake-7.1.0-42661 manual


TCRP will download resources from the Internet to complete the complex process of the loader build. When finished, it will write it to the USB flash drive and add new items to the GRUB boot menu. Review the output for any errors and make corrections if necessary.

Step 7. Optional Backup Tasks


Save the TinyCore configuration state as the default, so that the next boot of TInyCore starts with all your settings

./rploader.sh backup


Back up the generated RedPill loader partition to available space on the USB flash drive

./rploader.sh backuploader


Step 8: Restart and Boot DSM Using the Grub USB Option


Cleanly shutdown and reboot with the TinyCore command

exitcheck.sh reboot


First, the GRUB Menu is displayed. If necessary, use the arrow keys to ensure that USB is selected and press ENTER.



The loader will show some initialization information and silently boot DSM. Nothing else will be displayed unless a serial console is attached (see the Troubleshooting section below). Wait a few minutes, then launch either https://find.synology.com or the Synology Assistant desktop utility. If the loader is working properly, a new "SynologyNAS" will be displayed as Not installed (for a new build) or the name of your existing Migratable NAS (if upgrading from a previous version).




Use your browser to connect to the NAS.




 If "Something went wrong" is displayed, jump to the Basic Troubleshooting section below. 


Otherwise, browse to the Synology Download Center and download the DSM install PAT file that matches the platform and release number specified in the loader build.  Do not use the PAT file stored in TinyCore. It has modifications that are incompatible with DSM installation. However, its name may help identify the correct PAT file to download below.


There can be several files that appear to be candidates. PAT files marked VirtualDSM will not work. Also there can be patch PAT files with the same numbering. These will not work and will usually be smaller than 50MB. The correct PAT file is 300MB or larger.



Once the correct DSM PAT file is saved to your personal computer, upload it to the NAS.  Follow the prompts to complete the installation.


FOR UPGRADES ONLY: If Synology Assistant shows Not installed, or if prompted to erase the disks during the upgrade, STOP!  Some or all of your array disks are not visible to DSM. This must be resolved via troubleshooting and reconfiguration before installing DSM 7.x.


IMPORTANT: During the install, always select DSM manual updates. If a new install completes normally, but then fails after the reboot, it may be that DSM has attempted to auto-update itself with incompatible code.




Basic Troubleshooting


  Reveal hidden contents

Typical Problems:

  • If the DSM installation reports something went wrong/SATA ports disabled, or if WARNING: Bad port is returned by the TCRP configuration tools, there are three primary causes:
    1. hotplug not enabled for all ports on controllers that support hotplug
    2. ports supported by the chipset but omitted from the motherboard physical implementation
    3. M.2 SATA-capable ports that have no hotplug option enabled
  • Consider these workarounds/solutions:
    • enable hotplug on all ports
    • install SATA drives on all ports (including M.2 SATA ports)
    • disable M.2 SATA ports in the BIOS (if the option exists)
    • reduce SataPortMap port count to exclude unimplemented or M.2 SATA ports
      (this only works IF they are not the first ports on the controller)
    • install a different SATA controller and disable the onboard one
    • virtualize the DSM installation, possibly in concert with one of the above options
    • change the DSM platform to one that uses Device Tree (which can address only the good ports, leaving out the bad)
    • choose another motherboard which does not exhibit the causal issues

      A loader or SATA controller configuration that disables valid ports in order to install DSM can be updated to enable those ports once the DSM installation is complete.
  • If the DSM installation reports that no drives are available, use the serial or TCRP console described below to help investigate the problem
  • If unable to locate the new SynologyNAS using Synology Assistant, either the loader has kernel panicked, or the network is not functioning (usually because of a missing or incompatible network driver, or no accessible DHCP server). The only way to verify the specific cause is to use a serial console. 

Using the Serial Console for Troubleshooting


This involves configuring a physical serial port from the NAS hardware to your personal computer and using a terminal emulation program for access. The serial console is also mirrored to a special TCRP network console. If the network is functioning (i.e. you can see the IP in Synology Assistant), it can be accessed via a browser at https://<DSM IP>:7681 


If DSM has not been installed, "SynologyNAS login:" will be displayed. If DSM has been installed but cannot start, "DiskStation login:" will be displayed. This is Junior mode. You can log in with root (you won't be prompted for a password).


If desired, the reason that Junior mode was started can be displayed with

cat /var/log/junior_mode


Disk port shutdown errors and missing disks are usually a SataPortMap/DiskIdxMap/Device Tree problem, but can be a driver issue if using SCSI or SAS host bus adapters. If SATA disks are missing, investigate DSM’s view of SataPortMap/DiskIdxMap and some other user_config.json parameters by typing

cat /proc/cmdline


If the loader device "/dev/synoboot" is not returned by the following command, the identifyusb step of the install may have been skipped

ls /dev/synoboot


Inspect DSM's view of the accessible disk devices with

ls –la /sys/block


If using a Device Tree platform, display the contents of the device tree with

dtc –I dtb -O dts /var/run/model.dtb


Where to Post for Help


It’s easy for requests for installation help to get lost in various unrelated forum threads. Post requests for help as a new topic in the DSM Installation Forum.


At a minimum, state the hardware configuration, selected platform, DSM version, user_config.json information (delete or redact the serial number and configured MAC address) and any information from debugging analysis that you have done.


DON’T post general requests for help on this thread.

Please DON’T post general requests for help on TCRP or RedPill development threads unless providing feedback on a dev issue.


  Revision info (Reveal hidden contents)

2022-Jun-03 added disabled SATA port troubleshooting, removed some satamap complex description

2022-May-31 added restoresession argument



Hey :)


What is the current status about hibernation?

supported? broken?


Link to comment
Share on other sites

Hello everyone, sorry if I intrude, I usually never do it but given what is happening in this forum I think it is appropriate, some users have published requests for help on installation (the last three pages are practically dedicated to this), I wanted to remind that this is a tutorial, for the problems concerning the installation, as indicated on page 1 by Fliryde, they are to be done in the DSM installation forum, I also see that some developers also follow them, I repeat that a 20/30 and more pages is equivalent to no longer being usable, already in this forum there is a lot of confusion in the topics (with topics of 150/200 pages are they usable??? I think not) please don't continue to create even more. Thank you

Link to comment
Share on other sites

On 1/2/2023 at 3:09 PM, PincoPalla said:

Hello everyone, sorry if I intrude, I usually never do it but given what is happening in this forum I think it is appropriate, some users have published requests for help on installation (the last three pages are practically dedicated to this), I wanted to remind that this is a tutorial, for the problems concerning the installation, as indicated on page 1 by Fliryde, they are to be done in the DSM installation forum, I also see that some developers also follow them, I repeat that a 20/30 and more pages is equivalent to no longer being usable, already in this forum there is a lot of confusion in the topics (with topics of 150/200 pages are they usable??? I think not) please don't continue to create even more. Thank you

If you are referring to me since you were not specific...I think if you read what the problem I encountered actually revealed some minor issues with TCRP to which Peter and Poco have solved and still investigating at the time of this post.


If this occurred with me then it can easily happen to others and having this info reduces the future post and most importantly "stress" new or upgrading members might encounter. The mods here are very capable to sort the info. TCRP and Friend are really awesome pieces of tech and it seems they are fine tuning this thing to be that much better. Please remember, not everyone starts as an advanced/expert user. The info shared with me from other senior members here has allowed me to help other new users.

My account is new but I am not new to this forum.


Happy New Year Everyone!!!


  • Like 1
Link to comment
Share on other sites

Just to share some experience with the DS3622xs+ loader and how to get a SAS HBA controller to work:


I use a Xeon based server (32GB Ram) with SAS Controller in HBA mode, connecting 4x 3GB SAS Hds. The 4 HDs were configured in DSM6.2 as 1 Volume in RAID10. The Forum here says that in DSM7 HBA adapters are not yet supported but I got it to work as follows:

- when configuring the Redpill loader I had to run the satamap command and despite the reported errors, the loader found my HDs after a few trials. Te loader does not detect any HDs if I omit running the satamap command so this is the essential step although it creates an error message stating that "there will be problems". 

- after booting, DSM7 immediately detected my old Volume-1 but reported 2 out of 4 disks inside the RAID10 as defect

- nevertheless, all data on Volume 1 was available and accessible, even while the 2 HDs were reported as defect.

- I integrated the 2 ("defect") HDs via the DSM Storage Manager normal procedure to rebuild a RAID Volume

- This took 5-6h to rebuild and showed no errors. All 4 HDs are live as RAID10 again

- Since then the RAID10 runs under DSM7 without any issues


  • Like 1
Link to comment
Share on other sites

18 hours ago, anno said:

Can't install dsm, get error that the pat file is broken. Did a power off to restart but now the hole vm isn't working anymore, stuck at cursor.

Did  try it a second time, this time with ds3622 but also, some error. It will not install, file is broken.......

Link to comment
Share on other sites

On 5/23/2022 at 7:47 AM, flyride said:


The latest pocopico stable loader code is always linked here: https://xpenology.com/forum/topic/7848-links-to-loaders/


tinycore-redpill.vX.X.X.img.gz                    (for BIOS/CSM/Legacy boot from USB flash drive)
tinycore-redpill-uefi.vX.X.X.img.gz            (for UEFI/EFI boot from USB flash drive)
tinycore-redpill.vX.X.X.vmdk.gz                 (for virtual machine SATABOOT from disk image)


Hi, I have gone to the following link to download the latest loader however the 3 img.gz files are not present so I can't mount them to a USB flash drive. Is someone please able to help with what I am doing wrong? The file I am downloading is full of .json files etc. See screenshot below.





Edited by craig_t
Link to comment
Share on other sites

  • 2 weeks later...


I just want to ask the fellow user to advise me for my scenario.

I am currently running DSM 6.2.3-25426 Update 3 (Jun 1.04b / DS918+) on Lenovo V520 tower PC which has i5 7400 cpu and 8GB ram and 2x4TB disks (because  the mobo only supports 2 disks via SATA)


I want to update to DSM 7 as well as replace existing hdds with 2x 8TB Hdds. Ideally I would like to preserve my volumes, shares and data.


Given my scenario is it better to update from Jun 1.04b DS918+ to RedPill 1a (DS918+) in place or clean install?

I have read the Migration section of the guide but it only talks about updating the DSM and not the new disks so I am bit confused how to go about doing it.


BTW, a fellow xpenology user suggested the following on reddit. I was going to follow that process until I read about DRIVE SLOT MAPPING in the first post. Which got me confused if the below process will work for me or not. Any advise will be much appreciated.




Step 1: install DSM with 1 disk, to be on the safe side, do not plug any disk with data. Just a disk for OS.

Step 2: after OS installed and you can login to DSM7, plug in data disk direct to SATA connector or USB dock - it’s up to you.

Go to storage manager and you will see your data disk there ready to be adopted. Follow the instructions by just clicking next and next. As long as there is no warning like the disk will be deleted or anything like that - no data will be gone.






Link to comment
Share on other sites

  • 1 month later...
В 1/28/2023 в 6:49 PM, peter_pan сказал:

I just want to ask the fellow user to advise me for my scenario...

In your case (assuming two HDDs work as RAID/SHR?) I can offer this scenario:

1.       Checking DSM7

 1.1.    Write down the currently used Serial number/MAC

 1.2.    Disconnect both HDD 4TB, disconnect USB flash Jun 1.04b - put them aside

 1.3.    Connect any free HDD for experiments, from which you can delete all data (you can also use a new 8TB HDD, but after checking you will have to erase it).

 1.4.    Download TCRP and Write Image to the new USB Flash Drive (Step 2 in this Tutorial)

 1.5.    Follow the remaining steps of the Tutorial. In Step 4 point 4 – manually enter your SN/MAC into user_config.json

 1.6.    Download the "clean" DSM7, check how it works

2.       DSM6 to DSM7 upgrade

 2.1.    Disconnect the experimental HDD (from clause 1.3), do not disconnect the flash drive TCRP

 2.2.   Connect one active HDD 4TB with DSM6 (let the second HDD 4TB lie as a backup data source) 

 2.3.   Start the DSM. A recover/upgrade will be offered. If everything goes well, then DSM7 will boot successfully, but it will swear at the critical state of the storage pool (one disk is missing in the RAID).

 2.4.    We need to make sure that the data (and some of the settings, packages) are preserved. If everything is fine, then:

 2.5.    Turn off the DSM, connect one new 8TB HDD, turn on and restore the storage pool. Be prepared – this will take several hours to complete. Now you will already have a fully working DSM7, only with a storage size of 4TB.

3.       Final upgrade HDD

 3.1.    Turn off DSM 7, disconnect the old HDD 4TB, connect the second new HDD 8TB, turn on DSM

 3.2.    Restore and expand the storage pool. It will also last a few hours, but this is already your updated DSM7 + 2x8TB HDD.


4.       If something went wrong after point 2.2 (returning to the DSM6 + 2x4TB HD):

 4.1.    Disconnect the first HDD 4TB, connect instead only one second HDD 4TB (deferred in clause 2.2)

 4.2.    Disconnect the TCRP USB-flash drive, connect Jun 1.04b, start and check DSM 6

 4.3.    Clear the first HDD 4TB (Erase the Drive)

 4.4.    Connect a erased first HDD 4TB to the DSM 6, start, restore the storage pool. Now you are completely back to the original state.


In such a scenario, you have a backup copy of your data on one of the HDD at every step.

  • Like 1
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.

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