- Code: Select all
[ihecc:~] root# zpool import -d /dev
pool: gaia
id: 827519048864586214
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://zfsonlinux.org/msg/ZFS-8000-72
config:
gaia FAULTED corrupted data
raidz2-0 ONLINE
disk14 ONLINE
disk11 ONLINE
disk12 ONLINE
disk13 ONLINE
disk10 ONLINE
logs
disk3s2 ONLINE
[ihecc:~] root# zpool import -d /dev gaia
cannot import 'gaia': I/O error
Destroy and re-create the pool from
a backup source.
[ihecc:~] root#
A week ago I got the same thing on my other pool. After trying to export/import disks to see if I could find the failing disk and/or enclosure slot. No luck. So I recreated the pool as I had a backup.
Now this shit happens to the second pool. Luckily I had just copied everything back so I have not lost any data. Still, shipping 15+ TB back and forth is not fun and it takes a loooong time.
What I did was halting the machine. That is using the command "halt", not the power-switch-hard-halt. I had a scrub going on, otherwise everything was normal.
What is this "I/O error"? I cannot just be a disk that is messing up, or? All the disks are ONLINE.
So, did some über-blocks get messed up?
A nice halt, should be OK to do, right? Or do I have to export the disks? What if there is a power-outage...
And where can I find the disk error logs in Sierra. Seems that /var/logs/system is being depreciated.
I have been a happy camper of ZFS for quite some time now, but my confidence in ZFS just got a severe blow.