flyride

SCSI does not seem to work at all on Device Tree at the moment. I'm in the process of researching a solution for that.

Yes, this is a problem. Post /etc/lvm/backup/vg1

What you are really talking about is making your DS1815+ into a DS3622xs+ or some current XPe version. Similar things have been done. Search for DS1010+ conversion.

AHCI compliant and no port multiplier are the key factors for a SATA controller. There is no need for driver or chipset support if these are met.

That must be completed before you build the loader. If you change user_config.json after the loader is built, the changes won't be incorporated.

You can rebuild the loader with TinyCore without reinstalling DSM. https://xpenology.com/forum/topic/63135-cant-see-all-disks-on-dsm-7x/

The Linux kernel is reporting those ports (3,4,5) as inaccessible. Most of the time it is because they are not set for hotplug and have no disks attached. DSM won't install when a port is in this state. You can attach more drives, or you can use ./rploader.sh satamap to set the port count to "2" so that you can install DSM. Then once DSM is installed, go back into TinyCore and reconfigure the loader again, now with the full port count to make all the ports available in DSM. https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/

What platform are you installing, and what motherboard is it? Make sure all ports are set to hotplug in BIOS.

As I recall the virtio compile was from ThorGroup, and the new platforms have not been implemented with it. Anyone using a new platform has to use v9fs

The system is detecting 6 ports because the motherboard has two M.2 slots which are connected to the SATA controller. If you cannot set those slots to disabled, or hotplug (often it is not possible), you need to work around the problem. One option will be to set the port count to "2" and then install DSM. You can rebuild the loader afterward, changing the port count to 6 to get access to your other two ports. For more information, see the first item in the Troubleshooting section from the tutorial: https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/

Awesome, you have the new satamap code that looks for bad ports. Thanks for posting that screen. Ports 3 and 4 on your system need to be set to hotplug. If you can't do that, then override the number of ports to 2 and then you are limited to 2 disks on that system.

For 42661-2 look here: https://xpenology.com/forum/topic/53817-redpill-tinycore-loader/?do=findComment&comment=284855 Generally you want to look at the updates reporting forum before attempting any update. https://xpenology.com/forum/forum/78-dsm-updates-reporting/

That is an Aquantia chipset. There are drivers that work with it.

https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/

You can force a DSM reinstall but retain Storage Pools and Volumes with synodsdefault --reinstall This can be executed from junior mode shell (serial console). https://xpenology.com/forum/topic/9392-general-faq/?do=findComment&comment=89619 This will lose all system settings but not data. If you have a dss backup most of it can be restored. I don't know how to make it just do a patch.

If maxdisks is 24, sata controller 0/hard disk 1/Jun's loader needs to be mapped to it (0x18). You have a 100GB virtual disk which is not strictly necessary but if you want it, it takes up a mapping slot. That makes SataPortMap=11 and DiskIdxMap=1800. SasIdxMap is obsolete so don't bother with it. Your passthrough HBA drives should come in at port 2 with Jun's loader. If you want to get rid of the virtual disk and sata controller 1, then SataPortMap=1 and DiskIdxMap=18 Now you may not see all the disks until you get DSM booted and can adjust the portcfg bitmasks to match maxdisks. 24 disks = 0000 1111 1111 1111 1111 1111 1111 or internalportcfg = 0xFFFFFF 4 USB = 1111 0000 0000 0000 0000 0000 0000 or usbportcfg = 0xF000000 0 esata = 0 esataportcfg = 0x0 Remember to change in both /etc/synoinfo.conf and /etc.defaults/synoinfo.conf Reboot and you should have everything accessible.

The loader has to be rebuilt for the change to take effect. I suspect that didn't happen. Reach out to me via PM if you want to sort through it after your crisis is averted.

VMware's virtual SATA controller has 30 ports on it. If you don't set sataportmap and diskidxmap correctly, the ports on your LSI will not be mapped to usable ports in DSM. Post your synoinfo.conf maxdisks value, your grub sataportmap and diskidxmap values, and a screenshot of your VM configuration.

You have found a script bug but I don't think it changes your outcome. DSM is fundamentally designed to work with SATA drives and you have none, but you have a SATA controller. This is an odd use case and that causes a script error. If you can actually electrically disable the SATA controller from the BIOS (not just the ports), the satamap=1 and diskidxmap=00 should cause the ports to behave as expected.If you do encounter the hang on boot, please report that so we can override the invalid value.

No, that is all that ever will be displayed on a VGA console. Thus, the need for a serial console if troubleshooting is required.

synodsdefault --reinstall from the junior mode shell or regular DSM shell will do it. It's in the FAQ here: https://xpenology.com/forum/topic/9392-general-faq/?do=findComment&comment=89619

Serial console displays the kernel message (what normally is visible in dmesg) and alerts from the loader. Lots of examples on the forum. Like I said, I'd try simple. Maybe download a new clean non-UEFI loader and try again. If all else fails, consider virtualizing.

I think the postupdate feature will fix this.

I just added a note in the installation tutorial. For a migration install only, DSM will reset the Manual Update option to Automatic. It tells you this during the migration install. Unfortunately that means it can download an incompatible update and apply it before you can do anything. At minimum, go into Control Panel and change the setting ASAP. Alternatively you may want to disconnect your Internet when you see the notification and leave it offline until you can get to the setting in Control Panel. If someone knows the configuration file options that force the Manual Update setting maybe we can get the loader to address this for migrations.

TCRP rploader.sh 0.8.0.2 has an omitted space in line 1201: awk-F"/" should be awk -F"/" It won't affect users that do not require a SATABOOT configuration. But if you are using SATABOOT, manually edit in this change to rploader.sh before running satamap, until it is updated.