log/messages and debug.log read error - what can I do?

jimnastics

Cadet
Joined
Feb 28, 2016
Messages
5
I've recently had to RMA a disk from my 2 x disk mirror, still awaiting a replacement disk. In the meantime, I have kept my server online with the single disk. Recently I've started to get checksum erros on the disk combined with read errors on the pool, saying that errors have been detected in /log/messages and log/debug.log. The log is indeed unreadable, having tried to open it over SSH. Any thoughts on how I resolve this? Best idea to me seems to be to simply delete the current log file and start fresh, but I wanted to check in here before I screw something up. Here is my zpool status:

Code:
root@freenas:~ # zpool status -v
  pool: Main
 state: DEGRADED
status: One or more devices has experienced an error resulting in data
        corruption.  Applications may be affected.
action: Restore the file in question if possible.  Otherwise restore the
        entire pool from backup.
   see: http://illumos.org/msg/ZFS-8000-8A
  scan: resilvered 0 in 0 days 02:58:02 with 4 errors on Tue Apr  5 14:25:13 2022
config:

        NAME                                            STATE     READ WRITE CKSUM
        Main                                            DEGRADED     6     0     0
          mirror-0                                      DEGRADED    12     0     0
            4164520916732105891                         UNAVAIL      0     0     0  was /dev/gptid/98cb68c8-de02-11e5-98fd-70106f3e834c
            gptid/e49769ef-b3fb-11ec-9752-70106f3e834c  ONLINE       0     0    12

errors: Permanent errors have been detected in the following files:

        /var/db/system/syslog-0dc2ca1e7fa9464d8c4d7c4fd81f6855/log/messages
        /var/db/system/syslog-0dc2ca1e7fa9464d8c4d7c4fd81f6855/log/debug.log
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
You might be able to get away with moving your system dataset to the boot pool and then back to your "main" pool (since those files actually live in the system dataset if you didn't un-tick the syslog option there).

In the meantime, check your cabling as those are checksum errors.
 
Top