after upgrade zfs unknown status

[Troy Baskerville]

after upgrading freenas from 9.2.1.1 to 9.2.1.5, after upgrading the main zfs is in a unknown status.

after thinking there was a bad disk issue and finding out that a new hard drive appeared out of no where. I am stuck, I have looked through the other reports of this same issue and do not see a resolution.

when I do a zpool status on the system the backup shows as online, but nothing from System10 gets reported.


System info

freenas 9.2.1.5 x64
AMD Sempron 145 Processor

16361mb of ram

 

[Troy Baskerville]

we have also upgraded the ram from 7 gb to 16gb before the upgrade.

 

[cyberjock]

Post the output of zpool import in pastebin please.

 

[Troy Baskerville]

Code:

[root@freenas1 ~]# zpool import                                             
  pool: System10                                                           
    id: 81657227759750145                                                   
  state: FAULTED                                                             
status: The pool metadata is corrupted.                                     
action: The pool cannot be imported due to damaged devices or data.         
        The pool may be active on another system, but can be imported using 
        the '-f' flag.                                                       
  see: http://illumos.org/msg/ZFS-8000-72                                   
config:                                                                     
                                                                             
        System10                                        FAULTED  corrupted data
          raidz1-0                                      ONLINE               
            gptid/7b8e11f3-f136-11e0-81c9-1c6f654c9316  ONLINE               
            gptid/7bde9d58-f136-11e0-81c9-1c6f654c9316  ONLINE               
            gptid/7c6a7022-f136-11e0-81c9-1c6f654c9316  ONLINE               
            gptid/7cda5dbb-f136-11e0-81c9-1c6f654c9316  ONLINE               
            gptid/7d2e0155-f136-11e0-81c9-1c6f654c9316  ONLINE               
            gptid/7d84b928-f136-11e0-81c9-1c6f654c9316  ONLINE               
[root@freenas1 ~]# ^C  

 

[cyberjock]

So here's what you do.. and if you have backups you might want to hug them first...

from the CLI after bootup do the folllowing:

zpool import -f -R /mnt System10

It will either import or throw an error. If that error says add -F add that and try again. If it crashes, get a paste of the output. Post the output of whatever the end result is and don't touch the machine until I respond.

 

[Troy Baskerville]

Code:

[root@freenas1 ~]# zpool import -f -R /mnt System10                           
cannot import 'System10': I/O error                                           
        Recovery is possible, but will result in some data loss.               
        Returning the pool to its state as of Tue May 27 07:43:45 2014         
        should correct the problem.  Approximately 5 seconds of data           
        must be discarded, irreversibly.  Recovery can be attempted           
        by executing 'zpool import -F System10'.  A scrub of the pool         
        is strongly recommended after recovery.                               
[root@freenas1 ~]# zpool import -F System10                                   
cannot mount '/System10': failed to create mountpoint                         
cannot mount '/System10/.system': failed to create mountpoint                 
cannot mount '/System10/.system/cores': failed to create mountpoint           
cannot mount '/System10/.system/samba4': failed to create mountpoint           
cannot mount '/System10/.system/syslog': failed to create mountpoint           
[root@freenas1 ~]# 

 

[cyberjock]

You didn't follow my directions, but that's okay

So now do:

zpool export System10
shutdown -r now

Let the system reboot and see if everything is okay again. (It should be)

 

[Troy Baskerville]

I wanted to say thank you so much. Its back, I am running a scrub now.