MrChunky

Members
  • Posts

    104
  • Joined

  • Last visited

Everything posted by MrChunky

  1. Did you come to some conclusion with this? I am having a similar issue...
  2. Unfortunately there is only one slot that this card fits into on this MB. What kind of bios settings would be relevant? I went through them and couln't find anything worth changing. Currently everything is default. X570D4U.pdf
  3. As stated in the title Nvidia A2000 card is not detected by sysdevs System: M/B: ASRockRack X570D4U Version BIOS: American Megatrends International, LLC. Version P1.20. Dated: 05/19/2021 CPU: AMD Ryzen 5 5600X 6-Core @ 3700 MHz HVM: Enabled IOMMU: Enabled Cache: 384 KiB, 3 MB, 32 MB Memory: 64 GiB DDR4 (max. installable capacity 128 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mbps, full duplex, mtu 1500 eth1: interface down Kernel: Linux 5.15.46-Unraid x86_64 All I see are the below devices IOMMU group 0: [1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 1: [1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge IOMMU group 2: [1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 3: [1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 4: [1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 5: [1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 6: [1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 7: [1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 8: [1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge IOMMU group 9: [1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] IOMMU group 10: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 11: [1022:1440] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0 [1022:1441] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1 [1022:1442] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2 [1022:1443] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3 [1022:1444] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4 [1022:1445] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5 [1022:1446] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6 [1022:1447] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7 IOMMU group 12: [1022:57ad] 20:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream IOMMU group 13: [1022:57a3] 21:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 14: [1022:57a3] 21:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 15: [1022:57a3] 21:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge IOMMU group 16: [1022:57a4] 21:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:1485] 2a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:149c] 2a:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller Bus 001 Device 001 Port 1-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001 Port 2-0 ID 1d6b:0003 Linux Foundation 3.0 root hub [1022:149c] 2a:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller Bus 003 Device 001 Port 3-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002 Port 3-5 ID 046b:ff01 American Megatrends, Inc. Virtual Hub Bus 003 Device 003 Port 3-5.3 ID 046b:ffb0 American Megatrends, Inc. Virtual Ethernet Bus 003 Device 004 Port 3-5.4 ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 004 Device 001 Port 4-0 ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 002 Port 4-1 ID 18a5:0243 Verbatim, Ltd Flash Drive (Store'n'Go) IOMMU group 17: [1022:57a4] 21:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:7901] 2b:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 18: [1022:57a4] 21:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge [1022:7901] 2c:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 19: [8086:1533] 26:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 20: [8086:1533] 27:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 21: [1a03:1150] 28:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 04) [1a03:2000] 29:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 41) IOMMU group 22: [1022:148a] 2d:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function IOMMU group 23: [1022:1485] 2e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP IOMMU group 24: [1022:1486] 2e:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP IOMMU group 25: [1022:149c] 2e:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller Bus 005 Device 001 Port 5-0 ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001 Port 6-0 ID 1d6b:0003 Linux Foundation 3.0 root hub IOMMU group 26: [1022:1487] 2e:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller * The card fan spins, everything seems to be powered * system boots * BIOS and BMC latest versions Any ideas how I would proceed to debug this? tower-diagnostics-20220916-2317.zip
  4. Normal behavior as far as I know. But I did not investigate exotic share configurations, beyond having cash.
  5. You would need to give a lot more detail for get help. Post logs from the container.
  6. Thanks @ephdisk, I updated the template.
  7. It means that your node cannot reach the satellite for some reason. I would recommend to have a look at the threads on storj.io or make a new thread on the forums there. People there have much more experience debugging storj related errors, as networking is most likely not an unraid issue.
  8. Suggest there is an issue with the storage path. Have a look at your config and setup instructions.
  9. Thanks for sharing, I'll add it to the description.
  10. Nothing immediate comes to mind. Can you post log output when you run it the first time with setup option. Did you generate your certificates correctly?
  11. Hard to say just from the information you have given. May be the TCP port is already in use, may be the mount path are not working properly.
  12. Yes, mover doesn't move locked files. Files that are currently in use by a process are locked, this is true for any process on the unraid system as far as I know. In theory this means that if storj starts using files differently it can breaker mover functionality. Seems to be working fine at the moment... But I think in the long run it is quite risky to have mover running on the storj folders. One thing that could be done is to use mover for the data chunks but not for the folders where the databases are... Just speculating though.
  13. Everyone has a different setup... This is an Unraid issue not a docker/ storj issue I would say.
  14. @KrisMin Thank you for pointing this out. I tested it and it seems that indeed something has changed in unraid docker implementation since I last created a node. This argument is now necessary on the first run. I added this info to the template and the topic.
  15. I really do appreciate the passion to get an optimal setup. However, this discussion should really be had on storj forums directly. The people there will be much more knowledgeable about these topics and you can probably find the answers you are seeking already there.
  16. The docker will Update automatically assuming you have this function turned on on unraid for all your docker containers. This usually achieved through auto update plugin:
  17. 1. Not sure what you mean exactly by pressure on the disks. If you are talking about reducing the read/write cycles, then enabling cache is probably a good idea. It works fine for me and the amount of cache disk used is pretty stable with mover running daily. 2. The nodes you created will be vetted first, afterwards the traffic should increase significantly. You can read more here. In general you should check out the storj forum directly for such questions, there is a lot of information there.
  18. I am not sure what you mean by this. You should not move the identity to the same folder as the data folder. And especially you should not use drives when operating on the unraid system, but rather user shares.
  19. Do not nest the identity and storage folders. e.g. the path should be /mnt/user/storj/storjidentity for the identity and /mnt/user/storj/storage for the storage folder. Here storj is a new share you should create. Make sure the port forwarding is done properly, as it looks like your issue is a network issue from the error that you showed.
  20. I agree that nesting storage and identity folders this way is probably resulting in this error.
  21. Its the right one, but it definitely doesn't have those fields as seen in the XML config, must be something on your side.
  22. These two variables are not a part of the template I am maintaining. Here is the template XML from which it is generated. there are no -v fields.
  23. No Problem. I don't think the -v flags are there normally, at least when I pull the template they are not there. Will do. Already in the description.
  24. The docker run format that you are using here is different then the xml format Unraid docker templates are using. You should remove the backslashes in the template.