I recently upgraded my old FreeNAS server, which I hadn't touched in over a year (it was in storage following a move). I'm not sure if it is in any way related to the upgrade, but I had to replace one of the disks. The new disk has been resilvered, however the volume still shows as degraded. I'm still very much a noob wrt all of this, but I'm hoping there is some way I can tell FreeNAS to reset just the corrupt files (I'm not all that bothered if I lose some old logs and have to recreate a couple of jails). Unfortunately, I no longer have access to any (complete) backups for this machine.
- Can I safely delete the bit_1 jail (and the transmission jail for that matter) without destroying any of my actual data?
- Is there any way I can avoid losing all of my data/trashing everything and having to start over from scratch?
Code:
[root@freenas ~]# zpool status -v pool: freenas-boot state: ONLINE scan: scrub repaired 0 in 0 days 00:03:44 with 0 errors on Sun Feb 18 16:48:46 2018 config: NAME STATE READ WRITE CKSUM freenas-boot ONLINE 0 0 0 da0p2 ONLINE 0 0 0 errors: No known data errors pool: volume_0 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 1.21T in 0 days 04:52:34 with 22 errors on Mon Feb 19 23:13:25 2018 config: NAME STATE READ WRITE CKSUM volume_0 DEGRADED 0 0 531 raidz1-0 DEGRADED 0 0 2.07K gptid/265bd017-14b5-11e8-b180-902b346112a7 DEGRADED 0 0 0 too many errors gptid/f2a6824f-029a-11e4-abc4-902b346112a7 DEGRADED 0 0 0 too many errors gptid/f2922de8-541d-11e3-b4a0-902b346112a7 DEGRADED 0 0 0 too many errors errors: Permanent errors have been detected in the following files: volume_0/jails/bit_1:<0x0> volume_0/jails/transmission_1:<0x0> volume_0/.system/syslog-23007cbd716d443e91dae9064fd69a8e@volume_0-manual-20180220:/log/userlog volume_0/.system/syslog-23007cbd716d443e91dae9064fd69a8e@volume_0-manual-20180220:/log/utx.log volume_0/.system/syslog-23007cbd716d443e91dae9064fd69a8e@volume_0-manual-20180220:/log/daemon.log volume_0/.system/syslog-23007cbd716d443e91dae9064fd69a8e@volume_0-manual-20180220:/log/middlewared.log volume_0/.system/syslog-23007cbd716d443e91dae9064fd69a8e@volume_0-manual-20180220:/log/uwsgi.log volume_0/.system/syslog-23007cbd716d443e91dae9064fd69a8e@volume_0-manual-20180220:/log/debug.log volume_0/.system/syslog-23007cbd716d443e91dae9064fd69a8e@volume_0-manual-20180220:/log/messages volume_0/.system/syslog-23007cbd716d443e91dae9064fd69a8e@volume_0-manual-20180220:/log/nginx/access.log volume_0/.system/syslog-23007cbd716d443e91dae9064fd69a8e@volume_0-manual-20180220:/log/cron volume_0/jails/bit_1@volume_0-manual-20180220:<0x0> volume_0/jails/transmission_1@volume_0-manual-20180220:<0x0> /var/db/system/syslog-23007cbd716d443e91dae9064fd69a8e/log/userlog /var/db/system/syslog-23007cbd716d443e91dae9064fd69a8e/log/utx.log /var/db/system/syslog-23007cbd716d443e91dae9064fd69a8e/log/daemon.log /var/db/system/syslog-23007cbd716d443e91dae9064fd69a8e/log/debug.log /var/db/system/syslog-23007cbd716d443e91dae9064fd69a8e/log/cron volume_0/.system/syslog-23007cbd716d443e91dae9064fd69a8e:<0x3f> /var/db/system/syslog-23007cbd716d443e91dae9064fd69a8e/log/nginx/access.log
