Jump to content
XPEnology Community

flyride

Moderator
 View Profile  See their activity

  • Posts

    2,438

  • Joined

  • Last visited

  • Days Won

    127

 Content Type 

Everything posted by flyride

  1. flyride
    Something to read: https://forums.servethehome.com/index.php?threads/pci-sata-controllers-and-dummy-unused-ports-on-linux.32649/ This reinforces the idea that if M.2 SATA SSD's were installed in those slots, everything will behave normally. EDIT: This may also link back to hotplug. Modern BIOS that supports hotplug vs. non-hotplug support, and port not set to hotplug appears to result in DUMMY on that port if there is no disk attached - a known behavior. M.2 SATA ports might not be implemented with hotplug support in BIOS....
  2. flyride
    @wessu When you have a chance, please boot TinyCore and post the results of dmesg I'd like to validate the nature of the port failure as posted by the kernel. It doesn't seem that there is a way to fix this with satamap aside from disabling ports (but we can use dtb/dts solution or virtualization as alternatives). But if the problem is presented consistently by TC kernel we can detect it and advise the user.
  3. flyride
    I think that a dead port will still fail with sata_remap as it is visible to the DSM installer. We can short a controller with dummy ports in the middle or end of the port range with SataPortMap, but not as the first ports. And unfortunately DiskSeqReverse is no longer in the kernel.
  4. flyride
    If we figure out a way to stimulate/simulate these port failures in virtual, that would be super helpful. If the dummy ports are not the first ports on the controller, at least we can short the controller and make it work. I think I should add a scan for DUMMY in satamap and advise the user to consider another platform/alternative. But also think that there are other failure modes that may be harder to detect than "DUMMY"
  5. flyride
    H570 is an Intel chipset. @Deniska Virtualization is also a possibility for you.
  6. flyride
    I think they are not dummy, they are reserved for your M.2 in SATA mode.
  7. flyride
    Something is inconsistent with your system description and what satamap sees for ports. What motherboard make and model specifically? What does ls -la /sys/block say from TinyCore? If SataPortMap=1 there are no drives 2,3. So something else is happening.
  8. flyride
    Are you trying to install or upgrade to 42661-2? That results in a Recover loop at the moment.
  9. flyride
    Just following up on this, please review this post: https://xpenology.com/forum/topic/53817-redpill-tinycore-loader/page/147/?tab=comments#comment-284779
  10. flyride
    I have a conjecture about all the recent hard drive port errors, mostly encountered on X570, but now we have a current Intel motherboard example. The errors all seem to be on dual-definable ports that can be either NVMe slots or SATA (via M.2 port). For whatever reason, DSM is choking on unpopulated M.2 SATA ports. I realize that few people have M.2 SATA SSD's. But it would be very helpful to tabulate comparative results with a motherboard that exhibits the characteristics. 1) with nothing populated in M.2 slots 2) with all M.2 slots populated by NVMe drives 3) with all M.2 slots populated by M.2 SATA drives 4) with all M.2 slots completely disabled (if functionally configurable on the motherboard) Without additional information, there may be no baremetal satamap based solution that will work. In that case, we will want to confirm functionality with a Device Tree-based model. Of course, virtualization is and will continue to be a solution for these motherboards.
  11. flyride
    Post the output of satamap, and also ls -la /sys/block from TinyCore. Fdisk -l and dmesg aren't bad ideas either There is no need for driver extension for SATA controller as long as it is AHCI compliant.
  12. flyride
    If you change your SN it will just require a Migration. Not to worry.
  13. flyride
    Please keep in mind this FAQ entry when discussing Synology Accounts. You should not be surprised if serial numbers are blacklisted or other methods are used to deny your XPEnology installation access to Synology server services.
  14. flyride
    Writing the post-build loader image created by TCRP to the loader partition is a one-way operation. Once DSM is installed or upgraded, the loader partition is altered. ./rploader.sh backuploader makes a copy of the post-build loader image to free space on the flash drive. The loader image can then be reverted if necessary. ./rploader.sh backup saves the configuration state (pre-build) so that it is intact as you left it when you next boot TinyCore. ./rploader.sh restoresession attempts to reconstruct the configuration state (pre-build) from the previous session if it was not saved with backup.
  15. flyride
    Some functions cannot be auto-detected. If they are not part of the core RedPill code (ACPI is not) and have no PCI device associated with them for detection, this process handles them.
  16. flyride
    Of course you can.
  17. flyride
    satamap won't show you information about SAS/SCSI because they are not SATA. So that behavior is expected. @pocopico maybe I should add in the checkscsi again just to advise of connected scsi ports, even though it has nothing to do with satamap. I think you have an issue with your HBA driver at the moment. At least one X570 board recently encountered had a split SATA backplane and attached to two controllers, not one. Then those controllers were mapped high to low and low to high (ports vs. controller slots). I was working with the person with the issue to try and figure out a hack to make it work, but they went in a different direction. That was an ASUS board but it seems like a relevant data point.
  18. flyride
    https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/
  19. flyride
    The 30GB drive should be connected to a second sata controller (SATA1). If I believe what ./rploader satamap says it isn't connected to any controller at all (which would make sense to the outcome) Can you check?
  20. flyride
    0.8 is intended as "stable release" - if you are installed now there is no benefit to rebuilding. What is the configuration of your virtual drives and controllers on the VM that fails?
  21. flyride
    That is cosmetic only. Depiction of the actual device is a new feature of DSM 7.x
  22. flyride
    Thank you
  23. flyride
    @Peter Suh no offense intended, but it seems like it is inappropriate to post this in pocopico's development thread as it is not contributing to development in any way.
  24. flyride
    If you passthrough the NIC, DSM must have a driver to support it. Again, no different than baremetal. Alternatively, if ESXi has internal driver support for the card and DSM doesn't work with it, you can just provide the VM a vmxnet3 interface. The point is that you have the choice.
  25. flyride
    It is no different than if you inserted a card into baremetal system. DS918+ has 2 NICs maximum as a platform default. So on that platform, to support more cards (or multi-port cards), add maxlanport to user_config.json and set it to match the NIC count. MAC id does not explicitly need to be set; its purpose is to 1) ensure uniqueness among DSM instances, and 2) enable Wake-On-LAN features if you want to use them.
×
×
  • Create New...