ChatNoir

Moderators
  • Posts

    3705
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by ChatNoir

  1. Can't say for sure why it worked and does not now. Might be more plugins, maybe it was working with barely any spare room and some little config change pushed it over the limit ? In any case, the specs are higher, from the product page :
  2. I've cleaned that up, please only post the zip file.
  3. You might want to try the new UD preclear (Unassigned Devices is required) Jul 24 09:56:06 TheBox root: Fix Common Problems: Warning: preclear.disk.plg Not Compatible with Unraid version 6.9.2 Jul 24 09:56:09 TheBox root: Fix Common Problems: Warning: Setting up of authorized keys possibly found in go file Jul 24 09:56:10 TheBox root: Fix Common Problems: Warning: Share appdata set to use pool vm_docker, but files / folders exist on the cache pool Jul 24 09:56:10 TheBox root: Fix Common Problems: Warning: Share domains set to use pool vm_docker, but files / folders exist on the cache pool Jul 24 09:56:10 TheBox root: Fix Common Problems: Warning: Share Media set to use pool cache, but files / folders exist on the vm_docker pool Looks like there are other things that you'd want to look into.
  4. Your logs are filled by errors like : Jul 18 05:05:53 Totanon kernel: w83795 0-002f: Failed to read from register 0x03c, err -6 Jul 18 05:05:53 Totanon kernel: w83795 0-002f: Failed to set bank to 2, err -6 Not sure if the register in question is RAM, CPU or something else. Have you tried to run a Memtest ? (the one from https://www.memtest86.com/ might be required if you run ECC memory)
  5. You should set up a syslog server and post that file after a crash.
  6. You'll have a better answer if you attach your diagnostics to your next post.
  7. Yes. I think the plugin does not offer that. But you should probably ask that on the plugin support thread :
  8. RAID controllers are not recommended, but an IT mode HBA maybe ?
  9. I have to type it several times on occasion too so that it stays closed. Probably some kind of bug.
  10. no logs but your diagnostics will have the last SMART report
  11. Your diagnostics would provide more information. Attach the full zip to your next post.
  12. I think it's not an acronym at all. Simply the higher hexadecimal two digit value. (00 => FF) From my understanding, it is generally the value at the end of the boot process. Of course, different manufacturers could manage that differently, but my Supermicro board starts at 00 and increment the counter along the boot process then reachs FF.
  13. The default is RAID1. But you can balance the pool to the BTRFS profile of your choosing. Open the pool, select the profile in the drop down menu and hit 'Balance'. That works too. One limitation is that the free space tends to be off for an odd number of devices in an pool. It gets better as the pool fills up, that's a BTRFS issue, nothing Unraid can do about that. More details on the BTRFS RAID profiles and the capacity depending on the drives : https://carfax.org.uk/btrfs-usage/
  14. Only when the share is empty. Then you have a tick box and can remove a share.
  15. Your diagnostics would provide more information, please attach the full zip file to your next post.
  16. Difficult to provide an accurate answer without your diagnostics. Attach the full zip file to your next post.
  17. Try again without the -n suffix (no_modify).
  18. It is, as soon as the drive has the opportunity to properly test that area I think. You should run an extended SMART test on the drive (deactivate spin down for the drive first). In any case, already 8 reallocated sectors after less than 2000 hours is not great.
  19. I'd second that. When checking several drives in a row like that, it is generally to check one type of value or setting. It seems logical to stay on the same tab.
  20. Yes, the cumulative Parity check suffered a regression in 6.10.3 and is not working for now. It will be fixed for the next release. 6.10.3 is probably safer than other 6.10 releases though. As for the rest, I don't know.
  21. If the drives are not visible in BIOS either, there no real hope that the OS would see them. It seems to be very specific to your server board, in your situation I would contact Supermicro support and ask if that's normal behavior and how to make the drives available to the OS.
  22. On 6.10, you can also use the plugin Dynamix File Manager.
  23. Hello David, the license is linked to the unique identifer (GUID) of your flashdrive. That's it ! If you do not have VMs with Hardware passthrough and/or RAID controller, you should be fine just transplanting your flashdrive and disks to a new config. Make a backup of your flashdrive ! I would advise to deactivate Array automatic startup, deactivate Docker and VM services too. Maybe a screenshot of your disks assignements from 'Main' just in case.