Jump to content

JorgeB

Moderators
  • Posts

    67,572
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/
  2. As expected disks look fine, if the emulated disk is mounting and data looks correct you can rebuild on top, but also good idea to try and fix the problem or it will likely happen again, try at least to replace the cables for both disks.
  3. No, but note that it's just part of the fix, other things like the new partition alignment in v6.9 also make a difference.
  4. Actual disk will have a green ball on main page, emulated disk yellow or red. You can use -v for increased verbosity, though it doesn't make much difference.
  5. Disks 1 and 2 dropped offline at the same time (and reconnected with different identifiers), because of that SMART reports are empty, but unlikely to be a disk problem with 2 disks at the same time, most likely power/connection issue, start by checking if the disks share a power cable or splitter, then post new diags after a reboot just to check SMART.
  6. It's mostly because of the recent reflink support with xfs.
  7. It's a known issue, upgrading to v6.9 and re-formatting the SSD will decrease writes by a large factor, as much as 10x.
  8. Yes, any of the recommended controllers, the problem is the onboard SATA controller.
  9. It's again the typical AMD controller problem, if there's no newer BIOS you basically have 3 options: wait for a newer Unraid release with a newer kernel and hope it helps, use an ad-don HBA/controller or try a different board model.
  10. Your system share exists on cache and disk3, libvirt.img is likely on disk3, move everything to cache since disk3 is out of space.
  11. It's logged as a disk problem, though these can sometimes be intermittent, run an extended test on disk4 and if it passes keep an eye on this attribute: ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 1 It it continues to increase there will likely be more errors.
  12. Several places already exist with info, easily found with google, e.g.: https://ma.juii.net/blog/interpret-smart-attributes
  13. Run a filesystem check (without -n) on those drives, if the emulated disk5 is not fixable or is severely corrupt it could be better to re-sync parity with the old disk then upgrade again.
  14. Please use the exiting plugin support thread:
  15. Do you mean it's working now or not? If not please post new diags.
  16. That looks like a very corrupt filesystem, but basically you can only attempt to repair it without -n, is that an emulated disk or actual disk?
  17. No problem, I would recommend getting rid of those controllers though, or you'll likely run into trouble again, see here for as list of recommended ones:
  18. There's no such button, you just do a new config, keep all assignments, changes the ones you want and start the array to begin the parity sync.
  19. It is, you might not need a new cooler, just to clean, re-apply thermal paste and make sure the current one is correctly installed.
×
×
  • Create New...