Jump to content

JorgeB

Moderators
  • Posts

    67,884
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. New permissions tools won't work on appdata since some containers require specific permissions, best to just reinstall.
  2. Mover should fail to move any file in use, and it reports that in the log
  3. That's normal because with v6.9 and v6.10 no driver is loaded for a Matrox GPU, it uses the sock VGA driver, one was added for 6.11 since the stock VGA driver stopped working with the GUI, and like mentioned looks like the driver works for everyone with a Matrox GPU except you, not sure why or if anything can be done to fix it since it's already using the correct driver, and it also doesn't work without it.
  4. Mover cannot move files that are in use.
  5. Not the array, but one option would be to format that disk only, of course you would lose any data there, but if you have backups you could then just restore that data, another option, if there are no backups, would be using a file recovery util, like UFS explorer.
  6. What program are you using? I also have an older X7 series Supermicro, also had to blacklist the ATI driver but IPMIView 2.15 works fine.
  7. Well then it does look like the vidsk is gone, someone or something must have deleted it.
  8. With the latest releases the drive is installed automatically.
  9. Get the diagnostics over ssh.
  10. Look for CA Backup and restore, but just updating should not cause any issues.
  11. Post output of: ls -lR /mnt/disk1/domains/
  12. Rebuilding the disk won't help with a filesystem issue, you'd need to wait for a newer xfs_repair release or ask for help in the xfs mailing list.
  13. One thing you can try is to prevent the driver form loading, just in case with your server it causes issues instead of helping, click on the flash drive and add the below to sysçinux.cfg:
  14. Blacklist the radeon GPU from loading, instructions here: https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.10.0#Linux_Kernel
  15. You can a run a scrub first, if corrupt files are found look in the syslog for the list then deleted them, though formatting the pool would be safer for avoiding issues in the future.
  16. Even without network you should still have console access, try booting in safe mode, if the boot finishes grab the diags using the console.
  17. I assume you mean md3? There's no disk5, try rebooting and run it again from the console, if it still hangs it's likely an xfs_repair problem.
  18. VM service is disabled, enable it and if it doesn't start post new diags.
  19. Yes, at least one. It still means the RAM is bad, though for servers overclocking is usually not recommended, and XMP is overclocking.
  20. Disk dropped offline so there's no SMART, replace both SATA and power cables and post new diags.
  21. Btrfs is detecting data corruption, start by running memtest.
  22. NVMe device was not correctly removed from the pool. Stop array unassign Samsung SSD from the familia pool start array stop array assign both the Samsung SSD and the Crucial SSD to the familia pool start array convert pool to raid1, when done stop array unassign the Crucial SSD start array to remove the Crucial device from the pool
  23. Go to shares and click on "compute" for the domains share, post a screenshot of that together with the complete diagnostics.
  24. Try changing the mover schedule, then change it back to hourly and apply.
  25. No errors that I can see in the log, but the docker image is pretty new, suggesting it's not using the old one, look for a duplicate.
×
×
  • Create New...