Jump to content
We're Hiring! Full Stack Developer ×

JonathanM

Moderators
  • Posts

    16,319
  • Joined

  • Last visited

  • Days Won

    65

Everything posted by JonathanM

  1. My speculation is that this looping happens when the list of containers too be updated is not current. I have been able to induce a loop by NOT rechecking for updates, updating one of the containers that had an update available from the automatic check, then clicking update all. It tries to pull updates for all the containers that were listed before I updated the single container, but it still includes the container I just manually updated, pulls zero bytes, and starts looping. If that is the case, you can work around the issue by first checking for updates, then hitting update all. That way you should be guaranteed to have the latest list.
  2. 6.12 is still in RC phase, so you need to select the next branch instead of stable.
  3. I use UrBackup for my local workstations, and a handful of remote machines as well. It handles windows and linux clients.
  4. No. There is no standard pinout for the PSU end of modular cables, and it's fairly common for the wrong cables to fry any drives or equipment connected. Putting +12V on the 5V pins of equipment generally ends badly.
  5. If the disk slot shows free and used space in Unraid's GUI, it takes forever, with write speeds of a few hundred k. If the GUI shows unmountable, the dd runs at full speed. Every time I umount the disk with the array running, the GUI still has something showing up in that slot. If I stop the array and start it again, it shows unmountable and runs fine. The script depends on being able to read the disk to find the text, so by definition it's mountable at the start of the script. If you umount a disk, does the GUI immediately show unmountable? Mine doesn't.
  6. In my experience, several days. It would be much quicker to simply remove the drive and rebuild parity with the new config tool.
  7. I've done multiple restores, and I remember something quirky in the process, but can't remember exactly what I tweaked. Do you have all three ports forwarded through? The server communicates through those upper ports IIRC, I don't think the web interface is used at all with a bare metal restore.
  8. Did you remove ALL the cables that went with the Thermaltake and replace them with the Corsair cables? Just because the modular ends fit doesn't mean they are compatible. The forum has MANY examples of people ruining hard drives by switching PSU's and leaving the old cables in place.
  9. Set your temp alert thresholds high enough that normal operation doesn't trigger it, or if your temps are higher than the manufacturer recommended max, fix your cooling. Temp alerts should be configured so that it's an actual issue, like a fan failure or environmental issue.
  10. Turn that off and see if the situation improves. cache dirs should be set to operate on the bare minimum of folders, it can easily become counterproductive and keep the array needlessly spinning if your RAM can't contain the full list.
  11. yes yes yes no that's all you need to get the array running, make sure you tick the "parity is already valid" box. Since the final moments of the server running were a little chaotic, you probably need to do a parity check, but that can wait until you recover your backup.
  12. https://wiki.unraid.net/Manual/Troubleshooting#Lost_boot_drive_and_do_not_know_which_are_the_parity_drives
  13. If you aren't being completely hyperbolic here, you need to change your temp alert thresholds, or fix your cooling. A fail should really indicate a full failure, like a drive going near the manufacturers recommended high temp limit, meaning a fan or environment failure that really does need your attention. Normal drive temps should be WELL below those maximums. (60C is the manufacturer's max for a Seagate Exos 16TB)
  14. How large is the pool you have assigned for domains?
  15. Temporarily set a fixed IP on the workstation ethernet connection you are using to connect to Unraid. 192.168.100.11 should work.
  16. Why so complicated? https://wiki.unraid.net/Manual/Storage_Management#Replacing_disks
  17. Are you sharing or bridging the wifi with the ethernet on the workstation? Does the workstation ethernet have a fixed IP? What is it? What IP is Unraid showing?
  18. That won't work. If you format a drive, the format will be written to parity, and the rebuilt drive will be blank, all files will be gone.
  19. Pick one or the other. Using both on the same share is asking for trouble.
  20. It can be, since if there is minimal but real damage it may only effect certain things under certain conditions.
  21. The issue seems to be with Unraid still thinking the disk has a valid filesystem, if you stop the array and start it again so the disk shows unmountable, the write speed will increase dramatically. The only issue there is that the script won't work on an unmountable drive, so you must use the manual command line. If you mess up the command line, you can permanently erase a drive you didn't want to. If you are careful and match the md? correctly you will be ok.
  22. Because it's too much work to implement securely?😀
  23. The relatively low thermal mass of the water block can allow rapid temperature spikes if the fluid stops moving or is gone. Processors do attempt to save themselves from overheating, but the engineers assume a certain amount of mass is going to be available even without airflow, so the lack of mass can allow damaging heat in a matter of seconds. Leaks can be very bad as well, even if the fluid is clean, the boards have dust and particles that will mix with the fluid and cause corrosion, a slow undetected leak is the worst as it seeps into cracks and crevices causing voltage to go where it's not supposed to. Worst case would be a slow leak above a bottom mounted PSU, you could end up with mains voltage going to all your sensitive parts at once, blowing out circuit boards on drives. Granted, that sort of failure is very rare, probably because most water coolers are in gaming rigs for show, and any leaks or failures are caught relatively quickly.
×
×
  • Create New...