Jump to content

JorgeB

Moderators
  • Posts

    67,589
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. If it boots in safe mode it suggests a plug-in issue, remove them all and then add one by one.
  2. Boot in safe mode with all dockers/VMs disable, then start enabling them one by one an wait to see to see if you can find the culprit.
  3. Not just re-format, you need to delete existing partition, v6.9 uses a more optimized partition layout for SSDs: https://wiki.unraid.net/Unraid_OS_6.9.0#SSD_1_MiB_Partition_Alignment
  4. You can try resetting network config buy deleting network.cfg and network-rules.cfg, then reboot.
  5. Possibly the device dropped offline, diags could show more clues, you can also run smartctl on the console.
  6. Btrfs is finding data corruption, Ryzen with overclocked RAM is known to do that in some cases, reduce RAM speed and run memtest if errors persist.
  7. Cache filesystem is corrupt, best bet is to backup and re-format, there are some recovery options here if needed.
  8. Disk3 needs to be replaced, but if the filesystem in the emulated disk can't be fixed you can use ddrescue on it and it should be able to recover almost everything.
  9. If contents look correct you can rebuild, still and if you have a spare use it for the rebuild so you can keep the old disk intact if needed.
  10. Mar 5 13:51:20 Tower dhcpcd[1598]: br0: soliciting a DHCP lease Mar 5 13:51:20 Tower dhcpcd[1598]: br0: offered 10.0.0.15 from 10.0.0.1 Mar 5 13:51:25 Tower dhcpcd[1598]: br0: probing for an IPv4LL address Mar 5 13:51:30 Tower dhcpcd[1598]: br0: using IPv4LL address 169.254.148.36 Mar 5 13:51:30 Tower dhcpcd[1598]: br0: adding route to 169.254.0.0/16 Not really a network guy but looks like a network problem, it's being offered a DHCP address but it's not getting that and using a private IP address instead.
  11. That is usually a flash drive problem, try redoing it, back up current flash, redo using the UBS tool, restore config folder.
  12. Seems to be related to the Marvell IOMMU issue, you can try this (or disabling IOMMU if not needed), but if it's an option I would recommend replacing that controller with an LSI HBA, those controllers have multiple known issues and are not recommended for a long time.
  13. There have been multiple users with issues with the 8TB Ironwof + LSI, for now best to stick with v6.8.3 or connect those disks to a non LSI controller.
  14. Yes, if they shutdown before you hit the global shutdown timeout (settings - shutdown time out)
  15. For now run a filesystem check on the emulated disk1, not the actual disk.
  16. That's expected, libvirt is where the XMLs are stored, and should always have a backup.
  17. I don't remember if the disk was unmountable at any time, but if the used space looks about right and there's no lost+found folder (if the filesystem was repaired) you should be fine.
  18. It is strange, it should still start, and there's no error, it's like the setting changes to disable, you can try toggling VM service off then on, but doubt it helps.
  19. It wait until the set timeout (Settings - VM Settings - VM shutdown time-out), it will force after that.
  20. I don't know that specific model but there are some known issues with PMC Sierra controllers, you should stick to one to the recommended controllers.
  21. Should be fine either way but just in case better to update after. They are, just make sure the emulated disk is mounting and contents look correct before rebuilding on top.
×
×
  • Create New...