Jump to content
XPEnology Community

flyride

Moderator
  • Posts

    2,438
  • Joined

  • Last visited

  • Days Won

    127

Everything posted by flyride

  1. You need to patch to match your PCIe slot. https://xpenology.com/forum/topic/13342-nvme-cache-support
  2. see bold text below I haven't encountered anything like that in many years of ESXi hosting of 6.x and 7.x DSM guests. You'll probably need to post more information (preferably in a new thread request for help) for diagnostic help.
  3. There are a bunch of different ways for name resolution to happen. Do you know which is in use for the test? I would control that to the simplest, fastest possible exchange. If you have a small number of clients, define it in the hosts files.
  4. You don't suppose after all this development that someone would have noticed a 90% speed decrease? There is some other problem, it's not 7.1 or RedPill.
  5. What exactly are you trying to do? VMware backup can mean a lot of things.
  6. realmac reads the actual MAC from Linux. You may have two ports; they are often sequential.
  7. In the troubleshooting section there are several strategies to mitigate bad ports. It may not always be possible to resolve the problem depending upon the motherboard design. If that is the case, consider virtualizing where individual ports can be selected and attached to a virtual SATA controller (i.e. ESXi RDM) or choose a Device Tree platform where each port is specified.
  8. You might be able to adapt my solution for a different log suppression, detailed here: https://xpenology.com/forum/topic/29581-suppress-virtual-disk-smart-errors-from-varlogmessages/
  9. Anyone who thinks there is a guaranteed upgrade path to new DSM versions via XPenology should spend some time reviewing the FAQ and the support for prior DSM versions. Regardless, I don't think this is a reason to compromise the DSM installation you have and are using now. But to each their own. With direct access to disk devices, DSM offers valuable features that hardware RAID simply cannot do, including proactive device management and repair, dynamic btrfs fire corruption repair using redundant information within the array, and RAIDF1.
  10. This is a very good reason why you don't want to do it with a hardware RAID volume. https://xpenology.com/forum/topic/14091-esxi-unable-to-expand-syno-volume-even-after-disk-space-increased/
  11. Reinstalling doesn't enable more cores. You already are running a platform with the most supported threads
  12. USB drive is a loader. It does not contain an OS, and is a required part of the system (it cannot be removed). If you installed DSM to a SSD, the SSD has both the OS code and your data shares on it.
  13. DDNS itself works fine. You may be unable to use a Synology account and the synology.me DDNS because a generated serial is not valid for this service (nor should you expect to use it for free). Any of the other DDNS providers work, or you can use a Docker DDNS.
  14. It's nothing more than a way to differentate the platforms. The underlying DS3622xs+ platform supports the largest number of CPU cores, and technologies (RAIDF1, HBA support) consistent with larger-scale arrays. The loaders can override the total number of drives on any platform so that is a practical irrelevance. But a loader cannot add kernel core support, or the RAIDF1 code.
  15. It isn't a matter of software RAID working with the motherboard. The OS is providing the RAID. You don't want the controllers, or the BIOS to be doing it. A motherboard with 6 AHCI compliant ports is a good base for DSM. If you add additional ports with an AHCI-compliant controller, no drivers are required. The ASR-7805 will likely require drivers as it is a host bus adapter. HBAs are usually quite a bit more expensive than plain AHCI SATA controllers. Look for @IG-88's threads on good AHCI controller options for something to start with, unless you really need 24 ports or whatever you will get from an HBA.
  16. The point of DSM is to provide RAID via software. It adds many features that "hardware" RAID cannot provide, such as self-healing with integration with btrfs, and RAID modes that are not possible with hardware, such as RAIDF1. So you should be looking for AHCI-compliant controllers to connect your disks. Some HBAs can do this (aka "IT" mode). Simple SATA controllers can do it as well.
  17. The fact that they differ suggests to me that they are real temp values.
  18. The unusual situation with RedPill compared with Jun's loaders is that many different parties are always tinkering and improving it. So there is always code that is untested/alpha if you want to try it. The stickied links in the FAQ and Tutorials (such as this) refer to the code and procedures that are part of "stable" TCRP which is deliberately frozen with the idea that it would remain stable and predictable. There are things about DSM 7 that are more finicky than DSM 6, but TCRP is more flexible in how it can be configured. If you are chasing the latest stuff on every dev thread, good luck to you. Best practice would be the testing and migration procedure specifically outlined in the tutorial here: https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ Yes, the migration install doesn't require the platforms to be identical.
  19. I haven't seen anyone successfully map over bad ports with Sata remap. The rploader satamap is reporting your bad ports above by searching for DUMMY values in dmesg and reindexing the information to your controllers. The B660 chipset appears to share silicon with the H670 which has 8 SATA ports. Intel locks out the first 4 in your motherboard. https://images.anandtech.com/doci/17162/2022_CES_Pre-Brief_Dec 15 Final-page-029.jpg DSM won't install with ports that are electrically present and not functional (hence the DUMMY status). See the tutorial troubleshooting section for some workaround options, although they aren't really good. https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ You will have the best results with one of the folllowing: Convert to a virtualized installation, connect the storage to the hypervisor and then attach the disks to a virtual SATA controller (RDM in ESXi, for example) Use a device tree platform (i.e. DS920+) which doesn't use SATAMAP. There is some evidence that you can use a device tree configuration manually on any platform version, but this is incompletely tested. Disable your on-board SATA controller and add a PCIe SATA controller that doesn't have bad ports (this is probably least desirable with an ITX motherboard)
  20. Most of the ESXi XPe tutorials suggest that the user installs a virtual disk as an example device, separate from the loader vmdk. Maybe you want to use a virtual disk in your installation, and maybe you would rather use a passthrough controller. It is not always clear and often people install the virtual disk when it isn't necessary. Because we map the loader vmdk away (with SataPortMap=10 and DiskIdxMap=1) that causes the vmdk to be assigned outside of the addressable port range (assuming 16 ports). Any SATA devices on that same controller (SATA0) would be similarly not addressable, so we ask the user to add a second SATA controller (SATA1) for the virtual disks (or RDM devices) to be attached to. Those are then addressed at the beginning of the port range (SataPortMap=1000 and DiskIdxMap=1n, where n is the number of virtual disks). In @aerolite's case, they did not need a "21GB" virtual disk because data drives were being delivered via LSI HBA but it appears they had created one and set up the virtual controller as above. Non-SATA ports tack onto the end of whatever SATA ports are reserved by SataPortMap/DiskIdxMap. So they were asking how to get the starting port for the HBA back to the beginning of the range. Therefore, since they do not need the 21GB disk it can be deleted, the SATA1 controller also deleted, and SataPortMap and DiskIdxMap adjusted. With no SATA devices in the system (aside from the loader vmdk) then SataPortMap=1000 and DiskIdxMap=1. Unusually, the last SataPortMap 00 is required so that the HBA knows where to start addressing its ports. Unfortunately, there is an anomaly exhibited with TCRP/DSM7/HBA's that causes a single port gap between the last SATA disk and the first HBA disk. I haven't figured out how to make that go away outside of a device tree configuration.
  21. This surprises me greatly. How did you connect the RDM devices to the VM? Did you use the VMware virtual SATA controller?
  22. Hmm. This thread from the dev forum: https://xpenology.com/forum/topic/45795-redpill-the-new-loader-for-624-discussion/page/115/ It might be required to virtualize or RDM in order to support real SAS drives.
×
×
  • Create New...