Jump to content

JorgeB

Moderators
  • Posts

    67,783
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. If not needed disabling IOMMU should get rid of that, BIOS update might also help.
  2. NIC is being detected but it's not loading a driver, and can't see any related error in the log, do you have an add-on NIC you can use?
  3. You are having some strange issues, first try booting in safe mode, if that doesn't help I would consider re-creating the flash drive and start with minimal config or re-configure the server.
  4. Try re-creating the flash drive, backup current one, download v6.10.0 and unzip the files after formatting or use the USB tool, then restore the config folder from the backup.
  5. Try re-creating the flash drive, backup current one, download v6.10.0 and unzip the files after formatting or use the USB tool, then restore the config folder from the backup.
  6. It's a device issue with the Samsung 980 NVMe:
  7. Password for root is now required, you can't leave it blank.
  8. libvirt.img is mounting correctly, though it looks like a fairly recent file, see if you have multiple images: find /mnt -name libvirt.img
  9. Try typing "diagnostics" in the console, if that also fails copy the syslog to the flash drive: cp /var/log/syslog /boot/syslog.txt then attach here.
  10. With -n nothing will be done, also the xfs_repair output doesn't always make it clear that corruption was found, unless the fs has a lot of issues, a way to check is to first run with -n and look at the exit code, 0 means no corruption detected, 1 means corruption detected, if the latter case run it again without -n.
  11. It's above AMD max officially supported speed for that configuration, so yes, also if the RAM runs at 3200MT/s only using an XMP profile, not the default JEDEC then the RAM itself is technically also overclocked, RAM that runs a 3200MT/s using the JEDEC profile is not overclocked.
  12. Could be a UD issue, but in that case you'd need to report it in the existing UD plugin support thread.
  13. Check filesystem on disk5
  14. Board is spamming the log with ATA lonk info, the disk looks OK though, there a lot of UDMA CRC errors, and the LSI firmware you're using has known issues, you should update to latest, and since the emulated disk is mounting and assuming contents look correct you can then swap/replace cables to rule that out and re-enable the disk.
  15. Once a disk gets disabled it needs to be rebuilt/re-synced: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
  16. Still not enough unallocated space, try with -dusage=90, if you get an error you might need to move/delete some data first.
  17. Only what's reported can be fixed, once a release goes stable it starts being used by many more users, so a few new issues are expected/inevitable.
  18. Yes, but when there's one it should be posted there, and I'm going to re-open the report since it's not really solved.
  19. Looks more like a board issue, try updating BIOS to latest.
  20. Follow here for possible solutions or fix:
  21. Sorry, missed that it won't even boot now, backup current flash, download and install v6.10.0, recreate the flash drive and see if it boots, if yes restore the config folder from the backup and check if it still boots.
  22. Assign it as an Unraid pool device and after array start click format, if it still doesn't please post the diagnostics after that attempt.
  23. Good, first make sure backups are up to date, then you need to re-balance the pool, after that's done and there's some unallocated space you can remove the device, in doubt post new diags before doing it.
×
×
  • Create New...