Jump to content

JorgeB

Moderators
  • Posts

    67,572
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. That's a common issue with Dell, you can try this:
  2. But you can post the diags if you want to check current status.
  3. Looks like the same issue, without the IOMMU error since it's disable, look for a BIOS update, v6.9 also works better for some with this issue.
  4. If it happens again grab diags before rebooting, but sounds like the typical IOMMU related Ryzen on-board controller issue.
  5. If you swapped cables like recommend just wait to see if it happens again, if it does to the same disk it might be failing dispite no SMART issues.
  6. You can also do an online replacement, but note the bold parts about single device replacement.
  7. There might be a BIOS option to limit the M.2_2 slot to x2, and the SATA ports should work then, check the manual, same for which PCIe slot to use if needed.
  8. That would need to be corrected in the plugin by the author (or any other coder).
  9. Was expecting a corrupt GPT header, but just looks like the partition is missing, best bet then is to rebuild the disk and let Unraid re-create the partition. This assumes parity is valid: Stop the array, unassign disk2, start array, check that emulated disk2 is mounting and contents look correct, if yes, and only if yes, re-assign it to rebuild.
  10. It's not the syslog, as it shouldn't be after a reboot, not sure what it might be, try booting in safe mode.
  11. M.2_2 in x4 mode disables two SATA ports, adjust BIOS or use the other M.2 socket. Also avoid SATA port multipliers.
  12. Probably a VM or docker container. Most Intel NICs are usually OK.
  13. Yes, there were errors, so parity isn't 100% valid, best bet to recover the most amount of data and to be able to identity the corrupt files is to use ddrescue like I mentioned earlier.
  14. Something is trying to access /mnt/user/isos before it's available: Jan 4 11:42:38 Tower emhttpd: error: get_filesystem_status, 6618: Operation not supported (95): getxattr: /mnt/user/isos Maybe this script? Jan 4 11:42:29 Tower emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/startScript.sh /tmp/user.scripts/tmpScripts/Dump VBIOS/script
  15. Before or during this sync? Or just post the diagnostics.
  16. You're running out of RAM, also a lot of NIC related errors, but RAM is likely the main issue.
  17. Diags after rebooting are not much help, first thing to do is to stop overclocking the RAM, then test if it still crashes, also make sure power supply idle controller is correctly set, as per the link.
  18. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  19. It is, but you'll need to run a parity check which will take the same time, just mounting/unmounting the disks will generate a few sync errors.
  20. Were there errors on disk1 during the parity sync?
  21. That's a disk issue, but it could be OK for now, see if there are errors during the sync or run an extended SMART test. P.S. next time please post diagnostics instead.
  22. You should also update to latest Unraid, since that release is very old.
  23. You started the array without disk1 so it's disable, you can justs rebuild on top.
×
×
  • Create New...