Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,793

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    @bonienlany idea why network-rules.cfg is not being created here? The NICs are being detected.
  2. JorgeB
    Then you should post the diagnostics.
  3. JorgeB
    What Unraid release? There were some fixes for that in v6.10.2
  4. JorgeB
    When nothing else is running looks like it's awaiting mostly for sdb (disk4), this is not conclusive, but if you have a spare you could replace disk4 with it would be the first thing to try, the fact it's only linking at SATA1 is also strange, though that by itself doesn't explain such a low speed.
  5. JorgeB
    Yes, if the HBA is in IT mode.
  6. JorgeB
    Nothing obvious, load average is a little high, but appears to be dropping, likely since you stopped the dockers, VMs, just to try and confirm it's not a disk you can install the systat package from nerd pack, then post the output of: sar -dp 5 5
  7. JorgeB
    Try clearing the browser history, cookies, etc
  8. JorgeB
    Diags show writings to multiple disks, make sure nothing is writing to the array and post new diags during a check.
  9. JorgeB
    Log is getting spammed with Bluetooth errors, disable Bluetooth in the BIOS, and post new diags after array start.
  10. JorgeB

    Kaput!

    JorgeB replied to tucansam's topic in General Support

    If it keeps crashing enable the syslog server and post that after a crash.
  11. JorgeB
    Could also be a power/connection problem, check all connections and re-sync parity, if it happens again try with a different PSU if you have one available.
  12. JorgeB
    You're likely the first to try using Unraid with so many devices, you should create a bug report.
  13. JorgeB
    May 30 02:37:46 Skynet kernel: ahci 0000:03:00.1: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xcdf34000 flags=0x0000] Looks like the typical Ryzen onboard SATA controller problem, BIOS update might help but best bet might be using an add-on controller.
  14. JorgeB
    All indications so far are that Dell servers can run with vt-d enable without issues, to do that see here: https://forums.unraid.net/bug-reports/stable-releases/after-i-upgraded-to-6102-my-network-interfaces-dissappeared-r1956/?do=findComment&comment=19584
  15. JorgeB
    Try to create a new share and post diags after that.
  16. JorgeB
    Yes, select the raid1c3 profile.
  17. JorgeB
    May 30 16:51:12 NAS kernel: macvlan_broadcast+0x116/0x144 [macvlan] May 30 16:51:12 NAS kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right))
  18. JorgeB
    My supposition was based on the cases found so far, all had vt-d enable and the only common hardware, besides a lot of Intel devices which seemed unlikely to me as the source of the problem or there would be a lot more affected servers, were the NICs, can't say why your server is not affected, but @Thorstenjust found what looks like the exact same issue reported in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970453 This should hopefully help get to the bottom of the problem.
  19. JorgeB
    Good find, looks like the exact same issue.
  20. JorgeB
    00:17.0 RAID bus controller [0104]: Intel Corporation Device [8086:43de] (rev 11) DeviceName: Onboard - Other Subsystem: ASUSTeK Computer Inc. Device [1043:8694] No SATA controller being detected, only this, see if there's an option in the BIOS to change it to AHCI/SATA
  21. JorgeB
    Should be OK to re-enable the NIC with that server, see below how to: https://forums.unraid.net/bug-reports/stable-releases/after-i-upgraded-to-6102-my-network-interfaces-dissappeared-r1956/?do=findComment&comment=19584 You can also check this post for more info about this issue: https://forums.unraid.net/topic/124108-unraid-os-version-6102-available/?do=findComment&comment=1132815
  22. JorgeB
    Might not be the same as this thread, did you upgrade to v6.10.0 or v6.10.2? Do you now what the NIC you have?
  23. JorgeB
    No corruption detected by btrfs so far, and when there's a problem it's usually quick to detect some, so if you ran other v6.10.x release for more than a day I would think it should be fine to enable vt-d, just monitor the log for the iommu error described in the post linked above, if you don't see that after a few hours use with vt-d enabled it's another indication you should be fine.
  24. JorgeB
    It's not a known affected model, but since most affected servers have been from HP it's difficult to say more for sure, if you have been running previous v6.10.x releases with vt-d enable for a few days and didn't notice any issues or errors logged you are most likely OK, diagnostics might also give a better idea.
  25. JorgeB
    I don't know if that's possible, but if it is, yes, I agree it would be better.
×
×
  • Create New...