Jump to content
XPEnology Community

djvas335

Member
  • Posts

    161
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by djvas335

  1. If you can, use a microserver gen10 plus, its stable and no issues
  2. Then just leave iommu disabled and issue solved
  3. The best way if you have access to your data is backup your data and then recreate the raid and volume, do not play with it, you can have bad consequences.
  4. Can you post your user_config.json after loader build ?
  5. How is your controller setup in bios ? AHCI Mode ?
  6. This is because of new all-modules integration where the problematic mlx4 driver is now bundled, I had to build my own all-modules to overcome this issue for my systems, I run connect-x3 40gb
  7. I have below error when trying to build latest loader and DSM [#] Verifying /home/tc/redpill-load/custom/extensions/disks/ds3622xsp_64570/install.sh file... [ERR] [!] Checksum mismatch - expected 63d8722edb9c5f7cb7160bead82e2909bb977a1aad96dff74f39629fde03c3bf but computed d1f4003ea029a2f44db3c105e04f245a87e6c0d0b1685ff237d2278b55e43481 *** Process will exit ***
  8. Just use below steps with latest loader version ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DS3622xs+ ./rploader.sh identifyusb now ./rploader.sh satamap now - pay attention, here you need to answer "yes" twice ./rploader.sh build ds3622xsp-7.2.0-64570
  9. Actually DSM 7.2 final was released on 22 May 2023, I am running it on several servers with latest loader, did not see any stability issues.
  10. Latest tinycore with dsm 7.2 ds3622xs works with no issues on microserver gen7, gen8, gen10 and gen10 plus, I have tested those myself.
  11. I am running it on several n40l and on n54l with no issues, disable c1 in bios and do not use friend option to boot
  12. Just load the tinycore and go to it's dhcp address no custom port necessary
  13. I did not see any issues with this for now, just trying to avoid possible issues that can creep up in the future
  14. As it's not working in junior mode can I ask that you please keep the mlx4 module out of the all-modules integration pack for now ? You can add it later when it will be working better. The reason I am asking for this are those errors in dmesg about unknown symbol backport dependency.
  15. I did the test, I erased the hdd's to also be able to make an install test and recompiled the loader, unplugged igb and rebooted the server, after reboot during the install phase, the mellanox card did not initialize, ie no lights on the cards, no system in synology assistant, replugged igb and installed DSM via igb, system started without issue and Mellanox card is available however there is someting about unknown symbol backport in dmesg, attached below.
  16. Sure, I can test, however I can't disable the IGB because of the particularities of my setup, ie I can't access mellanox nic directly because it's on another network switch which I do not have direct access to and is only used for the storage network, please tell me if you still want me to do the test without disabling the igb nic
  17. Thank you very much for your time and support, I really appreciate this
  18. Success, the system started up and working properly, below screen with dmesg with correct driver, do you maybe need some additional information ?
  19. Let me explain better, I added your igb entry on line 2490 and rebuilt the loader, after restart the system shows as not installed, I even tried to upload the dsm installation file and after reboot it still shows as not installed in Synology Assistant
  20. I followed your instructions and got a corresponding entry in the log however my device still shows as not installed, I added the entry on line 2490 by the way
  21. I have changed the files according to instructions and rebuilt the loader, however after the restart the system is now listed as not installed in Synology Assistant
  22. I have managed to build a loader using M Shell, same issue please see below screens
  23. I need to use mshell we are trying to diagnose an issue with the mlx4 driver
  24. I am having diffculty compiling the loader using mshell, I am getting this error Mounting /dev/sdb1 to localdiskp1 /dev/sdb2 localdiskp2 cp: error writing 'localdiskp1/zImage': No space left on device Modify Jot Menu entry I also see that my partition table is different than yours, my sdx1 is smaller than yours, I am using latest tcrp image version tinycore-redpill-uefi.v0.9.4.6.img, can you maybe point to an image with correct partition layout please ?
×
×
  • Create New...