Received a critical error, but I can't find any trace of it

[anderstn]

Hi

A critical error came up in my notifications. No I have checked the SMART data and all drives have passed several short and one extended test since this alert came up and the SMART error log on each drives is empty. The drives themselves are brand new and just a few weeks old.

The pool is displayed as ONLINE (Unhealthy) in the web interface, but as far as I can tell everything works without any sort of noticeable performance degradation.

Now I have some experience with Linux and not finding any place to locate logs in the web interface I checked the obvious files in /var/log/console but I couldn't really see any traces of an error anywhere. Are there some other log files I'm missing here? From what I could tell the other files in /var/log did not seem to be relevant for a critical error.

 

[artlessknave]

please read the forum rules.

to answer your question, this is a zfs error, not a system error.
zpool status -v should tell you which files are damaged and unrecovereable.
in the webUI, you should be able to also see this by going to the pool status.
storage>pools>WD_RED>gear icon>status

unrecoverable errors are usually because you don't have any redundancy. part of the forum rules is your system build and pool topology is also really a good idea, so we can understand enough to answer questions.

 

[anderstn]

please read the forum rules.

to answer your question, this is a zfs error, not a system error.
zpool status -v should tell you which files are damaged and unrecovereable.
in the webUI, you should be able to also see this by going to the pool status.
storage>pools>WD_RED>gear icon>status

unrecoverable errors are usually because you don't have any redundancy. part of the forum rules is your system build and pool topology is also really a good idea, so we can understand enough to answer questions.

Thx. I will check it when I get home. I suspected it was something like this, but I expected to see this logged to console or to a dedicated log file, but pulling it via a dedicated command or the UI is just as easy once I know where to look