Jump to content

itimpi

Moderators
  • Posts

    20,789
  • Joined

  • Last visited

  • Days Won

    57

Everything posted by itimpi

  1. Yes, but PSU's can degrade, and fans can stop working properly.
  2. That is not good - suggests the repair did not work. Note that you are not trying to clear the red 'x' at this point, but the 'unmountable' status when running the array in normal mode. If the drive has a red 'x' as well then the repair was running against the emulated drive and not the physical drive (the check/repair does not clear the red' x' status as that requires a rebuild). It might be possible to work with the physical drive instead.
  3. The system rebooting itself strongly indicates a hardware error. Most likely suspects would be either thermal (overheating) issues with the CPU or PSU relate problems. Do you have the BIOS set to automatically boot if power is lost and then restored. If so a UPS might help if you are getting intermittent power cuts.
  4. You now need to run without -n and adding the -L option to get the file system repaired. This is mentioned in the section on repairing the file system. After that restart the array in normal mode and the drive should mount OK. For any disk that is disabled (has a red 'x' against it) the procedures to get it back online are here
  5. By this do you mean that the system shuts itself down unexpectedly; or something else (e.g crash);
  6. Have you tried the steps for troubleshooting this outlined here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.
  7. Handling of unmountable disks is covered here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.
  8. Did you reboot after making that change? If so you have another bad mapping.
  9. You can use the parity swap procedure that is for this specific Use Case.
  10. for security reasons you cannot change the permissions on the flash drive. the normal way to automate backups of the flash drive is either via Unraid Connect or the Appdata backup plugin.
  11. That is the wrong device name! If you run check filesystem via the GUI the correct device name will automatically be used.
  12. This means you have something (almost certainly a docker container) configured to use the path /mnt/appdata.. Since that path is in RAM it will likely fill up your RAM and crash the system.
  13. No. That is the ZFS ARC and it is expected to be that sort of value in normal running.
  14. Looks like you successfully repaired the emulated disk2 (which was disabled), and the system is now rebuilding the contents of that emulated disk onto the physical disk2..
  15. That path would only be valid if you had a pool called ‘app’. If not it is a location in RAM.
  16. There also seems to be an issue where the USB Creator tool sometimes rejects a flash drive, but using the Manual method works fine.
  17. XMP by definition is an overclock and it is not a good idea to overclock a server if you want to maximise stability.
  18. The syslog-previous file shows Macvlan related crashes so it is possible that is actually the cause of your problems? You should either switch docker to using ipvlan networking, or alternatively make sure bridging is disabled on eth0.
  19. I am a bit confused as the diagnostics do not show disk1 as being anywhere near full. the shares are set to use highwater allocation method so with 1x16TB and 2x8TB drives I would not expect disk 2 to start getting used until disk1 is down to 25% free., which is what it looks like what is happening. the syslog in the diagnostics contains continual USB Disconnect messages which makes it hard to look for other errors. Any idea what USB device that is, and can it be removed?
  20. Had you disabled the docker and VM services as is mentioned here for doing that in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.
  21. You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.
  22. No. Any transfer of files between the servers would require either a manual action or the running of a script written to perform this task on your specific setup.
  23. As far as I know that is all it does. The reason for safe mode is that plugins can install new components into the base Unraid OS and if these are incompatible with a particular release it can cause issues with unpredictable symptoms.
  24. Handling of unmountable array disks is covered here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.
×
×
  • Create New...