Jump to content

JonathanM

Moderators
  • Posts

    16,741
  • Joined

  • Last visited

  • Days Won

    66

Everything posted by JonathanM

  1. It would be nice to have in the GUI, but it's fairly easy to do with scripting if you wish.
  2. Flipping the switch on the PSU kills power to the motherboard, then you need to press the normal power switch to drain the residual power in the capacitors in the PSU and on the motherboard. No need to leave it off for long, just so the motherboard has no more power to maintain the failed state, and has to reinitialize from a known state.
  3. Have you shut down, removed power and discharged the PSU by hitting the power button while the power is off, then started back up?
  4. Ideally you would remove all the spinning rust drives and put them in a drive carrier meant for shipping, each drive gets its own impact absorbing compartment. Another issue is the CPU heatsink, they are typically rather heavy, and not always securely fastened to the board. If it comes loose it has sharp corners that can ruin the motherboard and any PCIe cards it hits inside the case.
  5. 2 parity disks allow the failure of any 2 disks simultaneously without losing data. If you could arrange it the way you propose, then if both 16TB drives died, you would lose the information on the 16TB data drive, with no recovery possible.
  6. Best policy is to stop the container when it's not needed. Start it when you want to use it, and stop it as soon as you are done.
  7. The reason there isn't a guide is largely because intel tends to just work with default settings, unlike amd which can be a project just to get running smoothly. Sure, intel can use some tweaks for certain situations, but it's much less hassle to get running.
  8. Building a second server is always better IMHO, that way when you experiment just a little too much it doesn't effect your daily routine.
  9. Reformat will erase the drive, including what is emulated by parity. Parity doesn't hold files, it has the entire drive, filesystem and all. If you reformat it updates parity and the rebuilt drive will match.
  10. See here. https://forums.unraid.net/topic/48383-support-linuxserverio-nextcloud/
  11. Why are you still on the RC when the stable for 6.12 is out?
  12. The shutdown status is recorded on the flash drive, so if that's not connected Unraid has to assume the shutdown was unclean.
  13. How is it urgent? There is a workaround. Not a showstopper, data loss, or server crash.
  14. Keep in mind that IP range is not meant for internal private use, those are owned by Microsoft, and you may run into issues if you use that range internally.
  15. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/#comment-511923
  16. You can use the current version of Unraid with a trial version, assign all the drives as data drives, that should get you back in. If you know the email address you used to obtain your original license you should be able to contact support with your info and get your license back. In any case, your drives are probably using ReiserFS as itimpi said, and you need to copy that data to different drives with a newer format, as ReiserFS is not being updated and will be discontinued in the near future.
  17. That worked, thanks! I added a few steps, but the end result was the same. I first selected auto as the file system type, and as expected, it imported the existing BTRFS pool. Then I did the erase and reset. BTW, the three way default after I did the erase and selected ZFS was RAID0, don't know if that's intended.
  18. Also, do you want to leave this report open until the GUI is fixed?
  19. So, what would be the best way to reset? 🤣 Well, at least I uncovered it early. Too bad I didn't try it during the RC cycle.
  20. Parity is NOT valid, unless you successfully completed the dd to zero the drive. I was under the impression you gave up before it completed.
×
×
  • Create New...