Jump to content

JorgeB

Moderators
  • Posts

    67,779
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Please post new diags after array start to see what's happening with the libvirt.img
  2. Please try booting in safe mode, if the same best to create a bug report.
  3. Please don't make multiple posts about the same thing, had already replied to the other one, make sure you have enough RAM (4GB minimum) and enough space on the flash drive, you can also always try doing it manually by downloading the zip and extracting the bz* files overwriting existing ones.
  4. Now start the array with both cache devices unassigned, then stop the array, assign both devices to the same pool, start the array and post new diags, if it mounts there's a chance the fs will go read only again, if that happens we can try to mount manually with skip_balance.
  5. May 18 10:18:12 SW-URSVR root: '/mnt/user/system/libvirt/libvirt.img' is in-use, cannot mount Rebooting should fix it.
  6. Check this is you haven't' yet and if issues persist enable the syslog server and post that after a crash, together with the diagnostics.
  7. Blue text is because you turn on the help, VMs might me missing if the Kingston SSD was your cache device, it's not assigned.
  8. You can do a new config (-Tools -> New Config -> Retain current configuration: All -> Apply), check all assignments are correct, check "parity is already valid" next to array start button and start the array, assuming only the devices name changed, and with USB there's always some risks of other issues, it will be bring the array back.
  9. Parity disk appears to be really failing so you'll also need to replace that one, but the rebuilt disk should be 100% OK as long as no more errors on a different disk, when Unraid fails to read a sector form parity1 it will use parity2, it just took longer with all the errors, but parity2 saved your butt in this case.
  10. Now it won't work since the pool is not mounting, I asked before rebooting, but it doesn't matter now. Stop the array, unassign al pool devices, start array, stop array, run btrfs-select-super -s 1 /dev/nvme0n1p1 Reboot and post new diags before array start.
  11. Likely related to the RAID controller, unassign all pool devices, start the array to make Unraid "forget" previous config, stop array, re-assign pool devices as they were, start array, existing pools will be imported and new devices names will be saved. P.S. since there are multiple pools double check you're re-assigning the correct members to all, take a screenshot first or refer to the diags.
  12. Just make sure the controller is using the latest IT firmware.
  13. There are still ATA errors, if you didn't replace cables at least swap them around to see if the problem follows the cables.
  14. Mesmtest is a good place to start, also note that Ryzen with overclocked RAM is known to in some cases corrupt data, though yours is not overclocked by much it still is.
  15. Disk does appear to be failing, you can run an extended SMART test to confirm.
  16. See here: https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=557606
  17. Did you get this? Also please post new diags.
  18. It shouldn't. Most likely a BIOS bug, but you can look for an update if available.
  19. Those SATA link down messages are from the onboard SATA controller, there's nothing on those ports so they should be harmless other than spamming the log, just recently another user with a similar board had the same issues, so likely BIOS related.
  20. May 17 11:06:38 Tower kernel: BTRFS: error (device sdb1) in do_chunk_alloc:3467: errno=-28 No space left May 17 11:06:38 Tower kernel: BTRFS info (device sdb1): forced readonly Balance aborted due to no space left, grab the output of: btrfs fi usage -T /mnt/cache Then post that and reboot, this issue shouldn't prevent GUI access.
  21. That's not normal, see you can get the diags by typing "diagnostics" in the console, then attach here.
  22. Forgot to mention, keep in mind that a 500GB + 1TB pool in RAID1 will have 500GB usable.
×
×
  • Create New...