Import volume failed after power loss

[Riccardo]

Hi at all,

first sorry for my english but this is not my mother language.
I'm new to Freenas, I use it sice some months.

After a power loss during a file transfer, in storage --> volumes I can't find my old one, but I see my disk in the tab "view disks".

I have a single segate 8tb hdd, used to backup data out from a dual 4tb red devices to create a raidz2 with four more 4tb drives (total 6).

I have an asus e35m1-l with 16gb of ddr3 RAM and the 8tb disk is attack directly to the motherboard.

When I try to import it fails, showing: cannot import 'my _volume' : I/O error.

Is there some logs that I can post to help you understand my problem?
I know that there are some other people that ask the same question, but I can't find a solution in older posts and I would not do worse with my trials

Thanks in advance for the availability.

Riccardo

 

[Mirfster]

So is the 8TB drive the one giving you issues or are you not able to see your normal pool (made from the 6 drives in RaidZ2)? Sorry, I am a little confused on the matter.

 

[Riccardo]

At the moment I have only the 8tb installed on my NAS, i'm waiting the others drives to arrive.
When the problem occurred I had only the 8tb attached, so this is the one giving me problem.

Thanks

 

[Yatti420]

So to confirm you went from two mirrored drives (4tb drives) to the 8tb single drive.. After which the two 4tb drives will combine with four brand new drives for a 6 drive z2pool?

So do you only have data on the single 8tb drive? Is this a ZFS drive? io error? Do you have different sata port controllers etc?

Also you don't list specs but your hardware isn't really optimal for Freenas (some aspects are horrid and will lead to data loss).. Did you encounter other errors prior to this? No ECC ram? How much do you have in the system currently?? I would upgrade all hardware to recommended specs then see fi you can mount the pool again and rebuild safely (z2pool etc)

 

[Riccardo]

Hi yatti,

thanks for your reply. I have most data already on the "old" two 4tb drives, but there is some important new data that lives only in the 8tb one.

The 8tb drive is a single ZFS, I tryed it on different sata port and an external controller (highpoint rocketraid), but no good news.
I tryed to perform a "fresh" installation of Freenas, making a backup of the config file before, but the error didn't change.

Prior this I haven't encounter other errors on this drive, olso the SMART status was good as new.
The RAM is non ECC and I have dual 8gb module for a 16gb total.

When I try to import my volume, in the Freenas browser fails and in the freenas console show this error:

Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8tb/Condivisione, error5 repeated some times with different path (condivisione/...)
Importing 'segate_8TB' failed with: cannot import 'segate_8TB' : I/O error
freenas zfsd: Zfsd event:: Process:Missing class or type data

Can I give other logs to you?

Thanks

 

[Riccardo]

With dmesg I have the following log:

Code:

ukbd0: <BTC USB Multimedia Keyboard, class 0/0, rev 1.10/1.00, addr 2> on usbus0                                                
kbd2 at ukbd0                                                                                                                   
uhid0: <BTC USB Multimedia Keyboard, class 0/0, rev 1.10/1.00, addr 2> on usbus0                                                
ugen3.2: <Kingston> at usbus3                                                                                                   
umass0: <Kingston DataTraveler 2.0, class 0/0, rev 2.00/1.00, addr 2> on usbus3                                                 
umass0:  SCSI over Bulk-Only; quirks = 0x8100                                                                                   
umass0:8:0:-1: Attached to scbus8                                                                                               
ugen1.2: <Kingston> at usbus1                                                                                                   
umass1: <Kingston DataTraveler 2.0, class 0/0, rev 2.00/1.00, addr 2> on usbus1                                                 
umass1:  SCSI over Bulk-Only; quirks = 0x8100                                                                                   
umass1:9:1:-1: Attached to scbus9                                                                                               
da0 at hptrr0 bus 0 scbus7 target 0 lun 0                                                                                       
da0: <HPT DISK 0_0 4.00> Fixed Direct Access SCSI-0 device                                                                      
da0: 7630885MB (15628053168 512 byte sectors: 255H 63S/T 972801C)                                                               
da1 at umass-sim0 bus 0 scbus8 target 0 lun 0                                                                                   
cd0 at ahcich5 bus 0 scbus5 target 0 lun 0                                                                                      
cd0: <TSSTcorp DVDWBD SH-B123L SB04> Removable CD-ROM SCSI-0 device                                                             
cd0: Serial Number R8606GHZ705257                                                                                               
cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes)                                                      
cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed                                           
da1: <Kingston DataTraveler 2.0 PMAP> Removable Direct Access SCSI-4 device                                                     
da1: Serial Number 50E549513774BF508949AA3E                                                                                     
da1: 40.000MB/s transfers                                                                                                       
da1: 7502MB (15364416 512 byte sectors: 255H 63S/T 956C)                                                                        
da1: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>                                                                                        
da2 at umass-sim1 bus 1 scbus9 target 0 lun 0                                                                                   
da2: <Kingston DataTraveler 2.0 PMAP> Removable Direct Access SCSI-4 device                                                     
da2: Serial Number 50E54951344CBF50894656E0                                                                                     
da2: 40.000MB/s transfers                                                                                                       
da2: 7502MB (15364416 512 byte sectors: 255H 63S/T 956C)                                                                        
da2: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>                                                                                        
SMP: AP CPU #1 Launched!                                                                                                        
Timecounter "TSC" frequency 1000008097 Hz quality 800                                                                           
Trying to mount root from zfs:freenas-boot/ROOT/default []...                                                                   
GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)                                                           
wbwd0: HEFRAS and EFER do not align: EFER 0x2e DevID 0xff DevRev 0xff CR26 0xff                                                 
vboxdrv: fAsync=0 offMin=0x367 offMax=0x47e3                                                                                    
Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8TB/.system/syslog-0dc2ca1e7fa9464d8c4d7c4fd81f6855, error 5
Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8TB/.system/samba4, error 5                                 
Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8TB/Condivisione, error 5                                   
Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8TB/.system/syslog-0dc2ca1e7fa9464d8c4d7c4fd81f6855, error 5
Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8TB/.system/samba4, error 5                                 
Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8TB/Condivisione, error 5                                   
Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8TB/.system/syslog-0dc2ca1e7fa9464d8c4d7c4fd81f6855, error 5
Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8TB/.system/samba4, error 5                                 
Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8TB/Condivisione, error 5                                   
Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8TB/.system/syslog-0dc2ca1e7fa9464d8c4d7c4fd81f6855, error 5
Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8TB/.system/samba4, error 5                                 
Solaris: WARNING: zil_check_log_chain: can't open objset for Segate_8TB/Condivisione, error 5                                   
[root@freenas ~]#                                                                                                                   

And when I try to import it:

Code:

[root@freenas ~]# zpool import
pool: Segate_8TB
id: 11371850169356178954
state: ONLINE
status: The pool was last accessed by another system.
action: The pool can be imported using its name or numeric identifier and
the '-f' flag.
see: http://illumos.org/msg/ZFS-8000-EY
config:

Segate_8TB ONLINE
gptid/001bea4d-6eaa-11e5-90fe-3085a9405951 ONLINE
[root@freenas ~]# zpool import -f Segate_8TB
cannot import 'Segate_8TB': I/O error
Destroy and re-create the pool from
a backup source.
[root@freenas ~]#

 

[Mirfster]

What is the result of: zpool import test ?

 

[Riccardo]

The result is:

Code:

[root@freenas ~]# zpool import                                                                                                 
   pool: Segate_8TB                                                                                                            
     id: 11371850169356178954                                                                                                  
  state: ONLINE                                                                                                                
status: The pool was last accessed by another system.                                                                         
action: The pool can be imported using its name or numeric identifier and                                                     
        the '-f' flag.                                                                                                         
   see: http://illumos.org/msg/ZFS-8000-EY                                                                                     
config:                                                                                                                       
                                                                                                                               
        Segate_8TB                                    ONLINE                                                                   
          gptid/001bea4d-6eaa-11e5-90fe-3085a9405951  ONLINE                                                                   
[root@freenas ~]#        

I posted a complete import log in my last post.

Best for me will be restore the health of my device, but also keep accessible my data again to keep them out is a valid option, even read only.

 

[Riccardo]

Hi,

there is someone who has had the same problem , or who have any advice to try to solve?

Many thanks

 

[Robert Trevellyan]

It looks like maybe your ZIL was corrupted by the power loss. In some situations you can roll back ZFS transactions and recover that way, but I have no experience of this.

 

[Riccardo]

News:

in those day's I've checked old drives that I've used like backup, inside I found, where i left, my data.

So now the question is not how to restore data for me, but for someone who will have the same issue.

I have a Disk where I can do all the trial, also losing data, and after some day's from now I'll restore the disk.

Some (even stupid) try to do?

Thanks

 

[Robert Trevellyan]

Not sure I understand your question, but here goes.

First, for someone who might have the same problem, the chances of recovery will be equally low. However, two basic precautions would help to prevent this:

1. Never put important data on a pool that has no redundancy.
2. Never put important data on a FreeNAS system that has no UPS protection.

I have a Disk where I can do all the trial, also losing data, and after some day's from now I'll restore the disk.

Some (even stupid) try to do?

Experimenting with possible failure scenarios, to see how you might be able to recover (or not), is a good idea.