Difference between revisions of "Unraid 6/Troubleshooting"

From unRAID
Jump to: navigation, search
m (Troubleshooting)
m (Boot Issues)
Line 18: Line 18:
 
: Normally the logs are only written to RAM so do not survive the system being rebooted.  If you are investigating a system crash then as long as you are running Unraid 6.7.2 or later you can go to ''Settings->Network Services->Syslog Server'' and enable the server and then tick the ''Mirror to Flash'' option to get a syslog that survives a crash and is appended to on a reboot.   
 
: Normally the logs are only written to RAM so do not survive the system being rebooted.  If you are investigating a system crash then as long as you are running Unraid 6.7.2 or later you can go to ''Settings->Network Services->Syslog Server'' and enable the server and then tick the ''Mirror to Flash'' option to get a syslog that survives a crash and is appended to on a reboot.   
 
: Note, however, that you do '''not''' want to leave the ''Mirror to Flash'' option ticked if you are not investigating such a problem as this can cause a lot of additional writes to the flash drive that can shorten it's lifetime.  
 
: Note, however, that you do '''not''' want to leave the ''Mirror to Flash'' option ticked if you are not investigating such a problem as this can cause a lot of additional writes to the flash drive that can shorten it's lifetime.  
 +
 +
== Capturing Diagnostics ==
 +
 +
''THIS SECTION IS STILL UNDER CONSTRUCTION''
 +
 +
Unraid has a GUI  option under ''Tools->Diagnostics'' to capture a lot of information about the state of your system that can be
 +
helpful when trying to diagnose any issues.  Using this tool will result in a zip file being produced that can be downloaded and then attached to forum posts.
 +
If the GUI cannot be accessed for any reason then using the '''diagnostics''' command from the Linux level will generate the same information and
 +
put the resulting zip file into the '''logs''' folder on the flash drive.
 +
 +
These system diagnostics include configuration information, state information and key system logs.
 +
When creating the diagnostics from the GUI then details of the sort of information that will be included is listed.
 +
The diagnostics are anonymized to try and avoid including any information that might be deemed sensitive.   
 +
All the files in the diagnostics are text files so a user is free to examine them to check for themselves exactly what information is present.
 +
 +
'''Note on anonymization of the diagnostics'''<br>
 +
It has been pointed out that the diagnostics are not completely anonymized if you have enabled ''mover'' logging under ''Settings->Mover Settings''
 +
as the ''syslog'' will give the full names of files that mover is operating on. 
 +
This is a bit of a catch-22 scenario as when one has enabled mover logging it is normally to investigate a problem
 +
where as much detail as terrible is captured so attempting to anonymize such information may well be counter-productive.
 +
Since mover logging is disabled by default and recommended practice is to only have it enabled when investigating why mover
 +
is not giving the expected results this is probably acceptable?
 +
 +
<br>
  
 
== Boot Issues ==
 
== Boot Issues ==
  
 
''THIS SECTION IS STILL UNDER CONSTRUCTION''
 
''THIS SECTION IS STILL UNDER CONSTRUCTION''
 +
 +
<br>
 +
 +
== Crash Issues ==
 +
 +
''THIS SECTION IS STILL UNDER CONSTRUCTION''
 +
 +
<br>
  
 
== Data Recovery ==
 
== Data Recovery ==

Revision as of 17:16, 2 January 2020

Official Documentation Contents List

Troubleshooting

THIS SECTION IS STILL UNDER CONSTRUCTION

A lot more detail still needs to be added

Most of the time Unraid systems function with minimal problems. This section is intended to help with resolving issues that are most commonly encountered.

There are some important general guidelines that it is recommended that a user follows that will help with any troubleshooting that may be required:

  • Enable Notifications: Unraid has a notification system that can be used to keep you informed about the health of your Unraid system. This can be enabled and the level of notifications you receive tuned under Settings->User Preferences->Notification Settings. Since Unraid systems often function for very long times without needing any user oversight it can be important that you are informed problems when they first occur as if left unresolved they can grow into more serious ones.
  • Proactively fix any reported issues:
  • Ask for help in the forums: Unraid has a vibrant user community and many knowledgeable users who are active in the Unraid forums. Any time you encounter a problem and you are not sure how to proceed it is a good idea to ask questions in the forums. There is nothing worse than rushing into trying to fix a problem using a process you do not understand and as a result making a problem that was initially easy to resolve into something more serious
  • Capture diagnostics: If you want to ask a question in the forums about a problem you are encountering you are frequently going to be asked to provide your system diagnostics file. This is a zip file contains anonymized configuration information about your system, status information, and the current logs. It can be added as an attachment to your forum post.
The simplest way to do this is to use the Tools->Diagnostics option that will give you a zip file that you can upload to the forum attached to any question you might have. You can get the same zip file generated from the Unraid command line by using the command diagnostics and in this case the file is placed into the logs folder on the flash drive.
Normally the logs are only written to RAM so do not survive the system being rebooted. If you are investigating a system crash then as long as you are running Unraid 6.7.2 or later you can go to Settings->Network Services->Syslog Server and enable the server and then tick the Mirror to Flash option to get a syslog that survives a crash and is appended to on a reboot.
Note, however, that you do not want to leave the Mirror to Flash option ticked if you are not investigating such a problem as this can cause a lot of additional writes to the flash drive that can shorten it's lifetime.

Capturing Diagnostics

THIS SECTION IS STILL UNDER CONSTRUCTION

Unraid has a GUI option under Tools->Diagnostics to capture a lot of information about the state of your system that can be helpful when trying to diagnose any issues. Using this tool will result in a zip file being produced that can be downloaded and then attached to forum posts. If the GUI cannot be accessed for any reason then using the diagnostics command from the Linux level will generate the same information and put the resulting zip file into the logs folder on the flash drive.

These system diagnostics include configuration information, state information and key system logs. When creating the diagnostics from the GUI then details of the sort of information that will be included is listed. The diagnostics are anonymized to try and avoid including any information that might be deemed sensitive. All the files in the diagnostics are text files so a user is free to examine them to check for themselves exactly what information is present.

Note on anonymization of the diagnostics
It has been pointed out that the diagnostics are not completely anonymized if you have enabled mover logging under Settings->Mover Settings as the syslog will give the full names of files that mover is operating on. This is a bit of a catch-22 scenario as when one has enabled mover logging it is normally to investigate a problem where as much detail as terrible is captured so attempting to anonymize such information may well be counter-productive. Since mover logging is disabled by default and recommended practice is to only have it enabled when investigating why mover is not giving the expected results this is probably acceptable?


Boot Issues

THIS SECTION IS STILL UNDER CONSTRUCTION


Crash Issues

THIS SECTION IS STILL UNDER CONSTRUCTION


Data Recovery

THIS SECTION IS STILL UNDER CONSTRUCTION

A lot more detail still needs to be added

This section is about recovering your data when Unraid reports problems with one or more drives.

There are some important points to bear in mind about securing your data(

  • Backup critical data: Unraid will protect you against most types of simple hardware failure, but not catastrophic failure. You should ALWAYS have backups of any critical data that you cannot afford to lose. Ideally one of those copies should be offsite or on the cloud to protect yourself against unforeseen issues such as fire, theft, flood, etc.
    • Each user has to make their own determination of what they deem critical and make an assessment of the level of risk they are prepared to take.
    • Personal data such as photographs & documents tend to always be deemed critical. Luckily these tend to be relatively small so easy to back up.
    • Media files are often deemed non-critical and are relatively large so a user may well decide these do not merit being backed up
    • Personal video that can never be replaced should fall into the critical category regardless of it's size
    • Remember that there are things such as ransomware around so there should be at least one copy of critical files that cannot be accessed online and corrupted if you are unfortunate enough to suffer from such an attack!
  • Be pro-active about resolving any issues that are detected by Unraid. Make sure that notifications are enabled under Settings->Notifications so that you get told as soon as issues are detected. For many users Unraid operates in a fire-and-forget mode so that they will not be actively checking for problems so need such reminders.
  • Ask for Advice:
    • The Unraid forums have lots of knowledgeable users who can help guide you through what needs doing to get your data back into a standard if you are not sure what are the best steps to take.
    • Unraid is very good about protecting your data against typical hardware failures , but it is not immune against users taking inappropriate steps to recover their data after a failure occurs.