JorgeB

Moderators
  • Posts

    60391
  • Joined

  • Last visited

  • Days Won

    630

Everything posted by JorgeB

  1. LT is already aware of this, I think they were looking to use rasdaemon for v6.13
  2. If there are 10 ports, 5 of them will from a SATA port multiplier, so with v6.12.9 you could only use 5 device tops, from what I've found, it was a change in the kernel that will make any devices connected to a SATA PM on these controllers unavailable, because apparently they don't report the PM as they should, this change has already been reverted, but it didn't make it to the kernel this release is using. P.S. note that controllers with port multipliers are generally not recommended, but because of other issues that they can have, not this.
  3. Same as this one: https://forums.unraid.net/bug-reports/stable-releases/zpool-problems-after-upgrading-to-the-6129-r2921/ Is this a 6 port controller or does it have more ports, i.e., it has a SATA port multiplier?
  4. @blue8lucianis this a 6 port controller or does it have more ports, i.e., it has a SATA port multiplier?
  5. Yes, if it's not readable it likely failed. Create a new flash drive and start the array so you can get the backup, see here if you don't know the assignments: https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/#what-to-do-if-you-have-no-backup-and-do-not-know-your-disk-assignments
  6. Sorry, can't help with the other issue, someone from Connect support should get back to you in that thread.
  7. Diags confirm flash drive problems, you can first try to re-format it and/or using a different USB port, ideally USB 2.0, if the same replace it.
  8. If you swap them does the problem follow the device or the slot?
  9. El disco parece estar fallando, puede ejecutar una prueba SMART extendida para confirmar, si falla debe reemplazarlo, el disco emulado se está montando, por lo que todos los datos deberían ser recuperables.
  10. Looks like it, @ich777should be able to confirm if that driver is still available, or re-post in the Nvidia plugin support thread.
  11. This looks like a controller/kernel issue, some of these controllers, despite having only 6 SATA ports, list much more in the kernel, example from your Asmedia1166 controller and v6.12.8, it's listing 30 good ports, just 2 dummy: Mar 27 18:18:42 MedHP kernel: ata1: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780100 irq 59 Mar 27 18:18:42 MedHP kernel: ata2: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780180 irq 59 Mar 27 18:18:42 MedHP kernel: ata3: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780200 irq 59 Mar 27 18:18:42 MedHP kernel: ata4: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780280 irq 59 Mar 27 18:18:42 MedHP kernel: ata5: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780300 irq 59 Mar 27 18:18:42 MedHP kernel: ata6: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780380 irq 59 Mar 27 18:18:42 MedHP kernel: ata7: DUMMY Mar 27 18:18:42 MedHP kernel: ata8: DUMMY Mar 27 18:18:42 MedHP kernel: ata9: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780500 irq 59 Mar 27 18:18:42 MedHP kernel: ata10: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780580 irq 59 Mar 27 18:18:42 MedHP kernel: ata11: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780600 irq 59 Mar 27 18:18:42 MedHP kernel: ata12: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780680 irq 59 Mar 27 18:18:42 MedHP kernel: ata13: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780700 irq 59 Mar 27 18:18:42 MedHP kernel: ata14: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780780 irq 59 Mar 27 18:18:42 MedHP kernel: ata15: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780800 irq 59 Mar 27 18:18:42 MedHP kernel: ata16: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780880 irq 59 Mar 27 18:18:42 MedHP kernel: ata17: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780900 irq 59 Mar 27 18:18:42 MedHP kernel: ata18: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780980 irq 59 Mar 27 18:18:42 MedHP kernel: ata19: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780a00 irq 59 Mar 27 18:18:42 MedHP kernel: ata20: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780a80 irq 59 Mar 27 18:18:42 MedHP kernel: ata21: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780b00 irq 59 Mar 27 18:18:42 MedHP kernel: ata22: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780b80 irq 59 Mar 27 18:18:42 MedHP kernel: ata23: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780c00 irq 59 Mar 27 18:18:42 MedHP kernel: ata24: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780c80 irq 59 Mar 27 18:18:42 MedHP kernel: ata25: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780d00 irq 59 Mar 27 18:18:42 MedHP kernel: ata26: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780d80 irq 59 Mar 27 18:18:42 MedHP kernel: ata27: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780e00 irq 59 Mar 27 18:18:42 MedHP kernel: ata28: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780e80 irq 59 Mar 27 18:18:42 MedHP kernel: ata29: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780f00 irq 59 Mar 27 18:18:42 MedHP kernel: ata30: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780f80 irq 59 Mar 27 18:18:42 MedHP kernel: ata31: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc781000 irq 59 Mar 27 18:18:42 MedHP kernel: ata32: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc781080 irq 59 With 6.12.9 looks like the kernel is enforcing just 6 ports, so all ports after ATA6 are considered dummy ports: Mar 27 18:13:36 MedHP kernel: ahci 0000:04:00.0: ASM1166 has only six ports Mar 27 18:13:36 MedHP kernel: ata1: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780100 irq 62 Mar 27 18:13:36 MedHP kernel: ata2: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780180 irq 62 Mar 27 18:13:36 MedHP kernel: ata3: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780200 irq 62 Mar 27 18:13:36 MedHP kernel: ata4: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780280 irq 62 Mar 27 18:13:36 MedHP kernel: ata5: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780300 irq 62 Mar 27 18:13:36 MedHP kernel: ata6: SATA max UDMA/133 abar m8192@0xfc780000 port 0xfc780380 irq 62 Mar 27 18:13:36 MedHP kernel: ata7: DUMMY Mar 27 18:13:36 MedHP kernel: ata8: DUMMY Mar 27 18:13:36 MedHP kernel: ata9: DUMMY Mar 27 18:13:36 MedHP kernel: ata10: DUMMY Mar 27 18:13:36 MedHP kernel: ata11: DUMMY Mar 27 18:13:36 MedHP kernel: ata12: DUMMY Mar 27 18:13:36 MedHP kernel: ata13: DUMMY Mar 27 18:13:36 MedHP kernel: ata14: DUMMY Mar 27 18:13:36 MedHP kernel: ata15: DUMMY Mar 27 18:13:36 MedHP kernel: ata16: DUMMY Mar 27 18:13:36 MedHP kernel: ata17: DUMMY Mar 27 18:13:36 MedHP kernel: ata18: DUMMY Mar 27 18:13:36 MedHP kernel: ata19: DUMMY Mar 27 18:13:36 MedHP kernel: ata20: DUMMY Mar 27 18:13:36 MedHP kernel: ata21: DUMMY Mar 27 18:13:36 MedHP kernel: ata22: DUMMY Mar 27 18:13:36 MedHP kernel: ata23: DUMMY Mar 27 18:13:36 MedHP kernel: ata24: DUMMY Mar 27 18:13:36 MedHP kernel: ata25: DUMMY Mar 27 18:13:36 MedHP kernel: ata26: DUMMY Mar 27 18:13:36 MedHP kernel: ata27: DUMMY Mar 27 18:13:36 MedHP kernel: ata28: DUMMY Mar 27 18:13:36 MedHP kernel: ata29: DUMMY Mar 27 18:13:36 MedHP kernel: ata30: DUMMY Mar 27 18:13:36 MedHP kernel: ata31: DUMMY Mar 27 18:13:36 MedHP kernel: ata32: DUMMY But your controller is using 4 of those dummy ports, ATA29, 30, 31 and 32. So technically I think this is more a controller firmware issue, it should only indicate actual 6 ports, not 30, still the kernel should be able to use them, either by using a quirk or reverting this recent change, since I suspect a lot of users will be affected.
  12. That's only with the mover tuning plugin, so you should ask there.
  13. Unfortunately there's still nothing relevant logged, this usually points to a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  14. No, you type in the CLI, or copy/paste the line below echo "blacklist radeon" > /boot/config/modprobe.d/radeon.conf Can't really help with the ROMs.
  15. Nothing else of note that I see, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
  16. Try this first, if it doesn't help try a different m.2 slot or a different NVMe device (or board).