Jump to content
XPEnology Community

flyride

Moderator
  • Posts

    2,438
  • Joined

  • Last visited

  • Days Won

    127

Everything posted by flyride

  1. That only works with DS3622xs+ Patch the lib file with your PCI addresses. https://xpenology.com/forum/topic/13342-nvme-cache-support/?do=findComment&comment=217008
  2. The minimum single disk size for DSM 7.x is now 21GB. 8GB reserved for DSM (/dev/md0), 2GB for swap (/dev/md1) and 10GB for data volume.
  3. I use Mellanox ConnectX-3 dual port in the riser slot on my NSC-810A. The pic does not show it but I have half-height PCIe to U.2 adapters that fit in the slots underneath.
  4. The DUMMY responses indicate that the motherboard has dual-use M.2 ports. They can support SATA SSD's or NVMe. Any SATA port that is not configured for "hotplug" is disabled by the kernel. Any disabled port results in a DSM installation failure. The dual use ports have no BIOS provision for hotplug. Thus there is no easy fix. Your idea of upgrade on another platform will probably work. There are a few other options you might consider that are outlined in the tutorial. https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ However, I strongly suggest you remove the SSD cache prior to ANY upgrade or migration, and then add it back in afterward.
  5. I cannot read the Russian image, but I suspect you have a motherboard that is exhibiting a problem we don't fully have a solution for. From TinyCore, please post the result of dmesg | grep "DUMMY" And we can advise further.
  6. Review both links carefully, you should find the answers to your questions. https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/ https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/
  7. https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/ https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ https://xpenology.com/forum/topic/62547-tutorial-install-dsm-7x-with-tinycore-redpill-tcrp-loader-on-esxi/ This documentation is intended to address the above requests.
  8. Of all the supported platforms, DS3615xs is the only one that does not support NVMe on DSM 7.x. https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/
  9. This comment really needs to be considered carefully. If we go back and look at Jun's 6.x loaders, the user was required to investigate and compute the values required for it to install successfully. Now we have scripts to help guide the computations, but that does not absolve the user from evaluating and understanding the results. I appreciate @pocopico's approach to the problem by breaking the install into understandable components, and keeping the user invested in the technical decision making process.
  10. He seems to be trying to use DSM 6
  11. identifyusb only sets VID/PID for the loader to know to substitute the usb flash drive as a synoboot device. ESXi is supposed to SATABOOT its loader so that is the reason for the message. You may have solved your problem simply with the passthrough configuration. I can't see how identifyusb has any impact on a USB device that is not used as a loader. But glad things are working for you nonetheless.
  12. I have tested this extensively including "old tricks" and can duplicate the problem. The issue is that the kernel is flagging the port as unusable as a result of hardware initialization. This happens before any SATA initialization occurs (based on dmesg sequence). The only setting I've found that changes the outcome is if SataPortMap is restricted to exclude the affected ports. This is only possible if the ports are not enumerated first in the controller (which is what you have). The tutorial now has options listed and cited below. https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ If the DSM installation reports Something went wrong/SATA ports disabled, it is usually because hotplug is not enabled for empty SATA ports that support hotplug. If supported, hotplug MUST be enabled or the port must have a disk attached. If the motherboard has M.2 SATA-capable ports, it can be impossible to configure them as hotplug even though the controller supports it. In that case, consider these workarounds/solutions: install M.2 SATA SSDs in each of the M.2 SATA-capable slots disable the M.2 SATA ports in the BIOS (if the option exists) set SataPortMap to permanently exclude those ports (this only works if M.2 SATA are not the first ports on the controller) set SataPortMap=1 for DSM installation, then rebuild loader with correct value (if M.2 SATA are not the first ports) change the installation to a Device Tree platform virtualize your DSM installation
  13. /home/tc is a reference copy. If you edit that copy, it will have no impact on your system.
  14. I can see what is probably an issue with the device tree. Port 1: ahci { pcie_root = "00:12.0"; ata_port = <0x00>; }; Port 2: ahci { pcie_root = "00:13.3,00.0"; ata_port = <0x02>; }; Port 3: ahci { pcie_root = "00:12.0"; ata_port = <0x02>; }; Port 4: ahci { pcie_root = "00:12.0"; ata_port = <0x03>; }; You have two different SATA controllers on that motherboard, each with 2 ports connected. The device tree port #1 is valid, but I think the rest of the ports are bad. If I had to guess, I would configure them like this: Port 2: ahci { pcie_root = "00:12.0"; ata_port = <0x01>; }; Port 3: ahci { pcie_root = "00:13.3,00.0"; ata_port = <0x00>; }; Port 4: ahci { pcie_root = "00:13.3,00.0"; ata_port = <0x01>; The PCI address of the second controller might be wrong (I think 00:13.3,00.0 is the actual DS920+ second controller address). You might want to confirm its PCI address with lspci -d::106 ls -la /sys/class/ata_port The device tree script is not very sophisticated yet, which is why the 7.x Loaders and Platforms matrix continues to suggest DS918+ as a preferred platform. The script only can provision ports that are populated at the time of the loader build. I'm guessing you only had one disk in the time of loader build, then you put in your second drive on the DSM install boot. You can fix this by booting into TinyCore, then: ./rploader.sh restoresession geminilake-7.x.x-xxxxx # edit the ds920+.dts file to reflect the port suggestions above vi /home/tc/redpill-load/custom/extensions/redpill-dtb/ds920p_xxxxx/model_ds920p.dtb ./rploader.sh clean ./rploader.sh build geminilake-7.x.x-xxxxx It shouldn't require a DSM reinstallation, just a loader rebuild. If it worked, you will see the second drive in Storage Manager. You'll need to add it to the array and resync.
  15. Post the results of cat /proc/cmdline Assuming you have installed DS920+, also post the dump of your dtb. sudo -i cd /usr/bin curl --location --progress-bar https://github.com/jumkey/redpill-load/raw/develop/redpill-dtb/releases/dtc -O chmod 700 dtc dtc -I dtb -O dts /var/run/model.dtb
  16. You are saying that you installed DSM to one of your array members, and went forward without a Migration install? That means that DSM told you it was going to erase your disk on install. And if so, it did. If that's true, you no longer have an array set. Is your data intact? Maybe post some screenshots of Storage Manager, and maybe a cat /proc/mdstat if this doesn't make sense.
  17. Added issue description and troubleshooting steps for "Something went wrong/SATA port disabled" error message on install.
  18. The above advice has been added to the TCRP tutorial. I'm also adding satamap checks to alert on this before the loader is built. I was able to force the error on a virtual machine by using proxmox with USB loader plus SATA data drive, then manually setting the SataPortMap port count larger than the supported 6 ports. Kernel then flags ata7/8 as DUMMY, same as hotplug failure. I checked with boot parameter hddhotplug=1 which doesn't change anything in this case. I am confident at this point that installing a SATA M.2 SSD in each slot will fix the port errors. Whether that is also true with a NVMe M.2 SSD is up to the motherboard implementation, but the issue is only when the SATA port is reported by the BIOS as empty. The state is set by the Linux kernel interrogating the controller. If hot plug is not supported on an empty SATA port, the port is permanently disabled for the session, and the DSM installer refuses to run if it sees any ports in this state. The M.2 SATA ports are not eSATA ports so I don't think twiddling with the bitmasks will help here. EDIT 1: reread your statement and I get what you are trying for now... will check! EDIT 2: sadly, portcfg happens well after the kernel query of the controller ports. Tried both esata and usb. Good idea though.
  19. This is the correct extension in the master repository. ./rploader.sh ext denverton-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json
  20. Unclear if that is true yet. Stay tuned.
  21. @Deniska one long shot is to check your BIOS and check if there is a hotplug option for the M.2 slots. I know it sounds stupid for a M.2 slot, but if you can turn hotplug on, may fix the issue.
  22. https://xpenology.com/forum/topic/53817-redpill-tinycore-loader/?do=findComment&comment=284855
  23. https://xpenology.com/forum/topic/53817-redpill-tinycore-loader/?do=findComment&comment=284855
  24. https://xpenology.com/forum/topic/53817-redpill-tinycore-loader/?do=findComment&comment=284855
×
×
  • Create New...