facelessone

Exactly. If you manage to install it with one drive, when you build loader again again with sataportmap 4 it will still boot from 1st drive into DSM, but you will see other drives. Make sure the other data in user_config.json stay the same. That's how I got it to work, hope you will to

Try This. Build a loader with SataPortMap 1, install with only one hdd on port0, When you install build loader again with sataportmap 4 and connect other drives.

- Outcome of the update: SUCCESSFUL - DSM version prior update: new install - Loader version and model: Redpill Tinycore V0.4.6 DSM 7.1-42661 Update 1 (DS918+) - Using custom extra.lzma: NO - Installation type: HP ProDesk 600 G1 SFF - Additional comments: Only one HDD must be connected for install and use "SataPortMap": "1", after install you can connect other drives and change to "SataPortMap": "4"

Thanks you guys. You are great. I have decided to give DS918+ another try, or more like 10 tries to be correct. I finally manged to install DS918 with "SataPortMap": "1" and only one disk inside. I made a fresh install on a cleaned drive and will move my data around and configure stuff later on. Later I build a loader again with "SataPortMap": "4" and it boots now and detects other drives. I moved back the drive from DS920+ install with data on and it recovered the pool with no problems. Still one drive to move from DS3615xs later but I belive it will go without prob

I have a problem and I don't know if it is loader related. I'm using DS920+, with DS918+ I can't get past SATA errors when installing. I have 1 HDD that I migrated from 6.2.2 to 7.1 and is showing in Storage manager under HDD/SSD. Now I added second drive that was also from other NAS and it is now showing at all. I wiped it, cleaned partition and all. Still not showing under HDD/SSD, only Drive 1. If I ssh into NAS and check with fdisk -l I can see both drives. 1st drive that is installed, this one is showing Disk /dev/sata1: 3.7 TiB, 4000787030016