Jump to content

JorgeB

Moderators
  • Posts

    67,416
  • Joined

  • Last visited

  • Days Won

    706

Everything posted by JorgeB

  1. Yes, if current cache is already btrfs, more info here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480417
  2. No, parity will still be valid. Ignore that, you don't need to create a new config since it's already one, just assign the devices and check "parity is already valid" before first array start.
  3. Thanks for reporting back, if you don't mind I'm going to tag it solved.
  4. Unlikely to see any difference with gigabit.
  5. Backup flash drive, recreate a new flash with the USB tool, restore only super.dat and the key (both on the config folder), it should now boot correctly like that, than either restore the other settings a few at time until you find the problem or just reconfigure the server.
  6. Apr 16 02:20:56 Unraid emhttpd: unclean shutdown detected A few sync errors are normal, even expected, after an unclean shutdown.
  7. This happened because you were using a RAID controller, usual solution is to rebuild one disk at a time on top, since the partitions are outside parity and will be recreated by Unraid, though since you didn't check that parity was valid after the new config you need to wait for the sync to finish first, when it's done, stop the array, unassign one of the data disks, start the array, if the emulated disk mounts and data looks correct rebuild on top, then repeat for the remaining disks.
  8. Try writing directly to a disk share, user shares always add some overhead, more noticeable in some hardware configurations than others.
  9. https://unraid.net/blog/top-support-and-forum-questions-answered Install UD plugin, one disk won't be mountable, that's parity, if you want to mount the other disks to test mount them read only, to keep parity in sync, then do a new config and check "parity is already valid" before array start.
  10. Sorry, assumed it was the regular diags, but yeah, don't see a reason for the reboot.
  11. Can't help with either of those, for Wireguard there are a couple of threads about it, in the Guides and Plugins forums, best to ask for help there.
  12. 16TB are CMR, though usually SMR disks work fine with Unraid.
  13. Depends on what you prefer, you can see the differences by enabling the GUI help.
  14. Diags will only show after the reboot, if it keeps happening enable the syslog server.
  15. Sorry, missed this one, but yes, you can use either one, it's in the FAQ.
  16. Yes, that's fine as long as flashed to LSI IT mode, same as a 9200-8e
  17. That's about right writing to the array with default write mode, you can speed that up with a cache device or by enabling turbo write.
  18. Router is not assigning an IP address, there are some users with recent release that need to set a static IP address, try that but if it doesn't work it's likely a LAN problem.
  19. Not understating the question, see if this helps: you can do a new config, keep all assignments, then unassign the disks you want to remove, you can take the opportunity to re-order the remaining data devices, then start array to begin parity sync.
  20. Yes, and if that's not the culprit start removing/uninstalling the others one by one.
  21. In that case go ahead and replace the failing disk.
×
×
  • Create New...