rojoone2

Skip 6.2.4-25556 altogether. Its a non working update with Xpenology. You will have to rebuild the loader anyway, so get a new USB drive and choose choose ARPL (AuxXxilium) or M-SHELL by Peter Suh: https://github.com/AuxXxilium/arc https://github.com/PeterSuh-Q3/tinycore-redpill/releases You will be presented with a choice to update to either 7.0.1 0r 7.2.1. Any one you choose will cause some apps to be uninstalled because they are no longer supported. Check support on the apps you use before you update.

Try Peter's version that is automated: https://github.com/PeterSuh-Q3/tinycore-redpill/releases You should also build a DS1621+ instead of the DS918 with the Ryzen processor.

That update has not worked for many users and was not recommended for anyone to update to. Is there any reason you are still using DSM6.x.x? Are you using apps that only work on that version? If not, you may want to upgrade to DSM7 which has more security updates.

What loader are you using? What other hardware are you using besides the Supermicro MB? Do you have the BIOS settings correct?

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.

You can use of of the loaders such as TCRP, ARPL or Peter Suh's M-Shell that is based on TCRP: https://xpenology.com/forum/topic/61839-tinycore-redpill-loader-build-support-tool-m-shell/ is the one I use. They all now allow you to build within a web interface that makes the process pretty simple with support for many newer models. The DS3615xs has lost support since it is one of the oldest models, so the DS3622xs+ would be a great upgrade for you. But if you do not have 12 disks in your system, for cosmetic reasons only, you can choose one of the models that hold 2.4 disks. The steps I would use is, get a new thumb drive and a spare hard drive that you can test builds with. Download the PAT file for the model you want to use, you will need it later. Remove you data disks from the system and put them in a safe place until the build is done. I would keep the disks in order for simplicity. Build say the DS920+ and see how you like it. If you are satisfied, power down the system, remove the test disk and install your data disks. Once booted, you will get a prompt to migrate. At this point you will get a prompt to re-install the OS. Choose manual and select the file you downloaded. Enjoy your new NAS.

Why didn't you go to storage manager and select swap drive? You could have replaced them one at a time if you had RAID 1 without loosing any data. Its takes a while to copy things, but it could have been done in a couple days depending on how much data was stored on the original drives. Is there a reason you still use DSM 6.2.1 and have not upgraded to 7.2?

Those hardware specifications are perfect for almost any platform you want to build. There was an issues with 10th generation and above, Intel processors, but you are fine with a 9th gen.

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:

1) Which version of DSM would be compatible? With the hardware you have, most platforms would work for you. The DS918+ or 920+ would be great choices, but you can use others. Read through this post to choose a platform for your build: https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/ Read through this post for a better understanding of how things work with TCRP: https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ If you want to go the easy route without and command line, look at this tread: https://xpenology.com/forum/topic/65408-automated-redpill-loader-arpl/ and this thread https://xpenology.com/forum/topic/61839-tinycore-redpill-loader-build-support-tool-m-shell/ 3) Where is the dsm file installed? (Ssd?) Its installed on your hard drives. You do need a USB thumb drive for the boot loader. All of your other questions can be answered with a quick Google search.

I have never upgraded from DSM 5, but I can confirm that DSM 6 to 7 is simple and you do not lose any data because the data is on a seperate partition than the system files.

You may want to look at Peter Suh's MSHELL instead. The build process id now similar to ARPL: https://github.com/PeterSuh-Q3/tinycore-redpill/releases

You can build a new system with an intel CPU, but unless you have the old 5.2.xxx PAT file, you may have to upgrade to a newer DSM version. If your motherboard just died and there was no issue with your disks, all your data should be in tact when you migrate. Is there a reason why you are still using DSM 5.2 and not upgrading to 6.x or 7? Here are some guides for you to look at: https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/#comment-281190 This is to select your platform/motherboard combination https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ This is if you want to migrate to DSM 7.x

Look at this post on page 8. You no longer have to do the commands you did with the old TCRP:

Looks like you are still using an older version of the loader. The new loader is now configured in a web page. You can try a different USB drive and build the loader again. Sometimes they go bad. You can also try MShell found here: https://github.com/PeterSuh-Q3/tinycore-redpill

I have a Z440 and had to disable the two standard SATA ports, using only the four sSATA ports in order for the disks to be recognised. Try only using either the six SAS ports, or the four SATA (SCU) ports. Instead if trying to build the DS3615xs, which is out of support, use the DS3622xs+ instead. It is compatible with a wider selection of hardware.

What is the hardware you are using? What model DSM are you trying to build? Which loader are you using? This will help others suggest what you need to to in order to get your build working.

Can you post the specs of your hardware? I had that issues when I used older hardware with the wrong img for my motherboard: tinycore-redpill-uefi.v0.10.0.0.img.gz - for UEFI boot tinycore-redpill.v0.10.0.0.img.gz - Legacy/BIOS boot tinycore-redpill.v0.10.0.0.vmdk.gz - Virtual machine

What brand disks are you using? Are they on the compatible drives list from Synology? Xpenology loaders overcome this with an edit in the userconfig.json to allow compatibility with (most) all drives. https://www.synology.com/en-us/compatibility?search_by=products&model=DS918%2B&category=hdds_no_ssd_trim There is also a shorter list of incompatible drives there.

Did you install the card after you built the loader? If so, restart you NAS and select configure loader and build again. The driver for that NIC should be added automatically, but you can also find it here: https://github.com/pocopico/rp-ext/blob/main/atlantic/rpext-index.json

What hardware are you using? Is the BIOS updated to the latest version?

The new TCRP has a web interface that makes the install a lot easier. No need for all the commands now. https://github.com/pocopico/tinycore-redpill Peter Suhs MShell is based on TCRP, but takes advantage of ARPL, which makes the building painless. https://github.com/PeterSuh-Q3/tinycore-redpill I would recommend you build a DS3622xs+, which is the updated version on the DS315xs. Its is compatible with most hardware and should work well with you server. I would remove your hard drives and use a spare to build the loader to make sure everything works then re-install your data hard drives.

It looks like you can have a maximum of 4x 4tb SATA hard drives, depending on the exact model you have. https://support.hpe.com/hpesc/public/docDisplay?docId=c02793565&docLocale=en_US

Are you trying to use WIFI to connect to the build? If so, WIFI is unsupported. You will have to use ethernet.

Have a look at this thread where is is stated that some users found success by switching to direct boot: https://xpenology.com/forum/topic/69563-cant-find-nas-on-find-synology/#comment-448837 Its for says its on newer hardware, but it may also work for you. As a last resort, you may want to try building a DS3622xs+, that works with most hardware.