1 Failed Drive: Can't import pool

Status
Not open for further replies.

staticrsa

Cadet
Joined
Aug 7, 2017
Messages
5
Hey guys,

So one of my HDD failed, now I can't import the pool ("One or more devices are missing from the system.")

Is there a zpool file that I can edit to remove the Hard Drive that has failed?

Version: FreeNAS-11.0-U1

Using PERC 6/i controller, each physical disk inside their own virtual disk.

*edit*
I put in another drive in replace of the failed drive
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Using PERC 6/i controller, each physical disk inside their own virtual disk.
That's a very dangerous configuration, but it isn't what's causing your problem--that's a bug in FN11 that should have been resolved in 11-U3. Update to 11.0-U3 and see if you can then import the pool.
 

staticrsa

Cadet
Joined
Aug 7, 2017
Messages
5
Post the output of zpool status within code tags.
Well the failed rive stopped me from booting, so I had to remove it. Seeing as the Vol1 (the original pool) won't import, it looks like it auto-created a new pool.

root:/ # zpool status
pool: freenas-boot
state: ONLINE
scan: scrub repaired 0 in 0h0m with 0 errors on Sat Aug 26 03:45:21 2017
config:

NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
mfid1p2 ONLINE 0 0 0

errors: No known data errors


zpool import
pool: Vol1
id: 261393085766929644
state: UNAVAIL
status: One or more devices are missing from the system.
action: The pool cannot be imported. Attach the missing
devices and try again.
see: http://illumos.org/msg/ZFS-8000-6X
config:

Vol1 UNAVAIL missing device
gptid/4d6f4140-76c4-11e7-b952-002219b20d75 ONLINE
gptid/4e3bb872-76c4-11e7-b952-002219b20d75 ONLINE
gptid/4ea2136e-76c4-11e7-b952-002219b20d75 ONLINE
gptid/4f1bbdf8-76c4-11e7-b952-002219b20d75 ONLINE
gptid/4f9c0194-76c4-11e7-b952-002219b20d75 ONLINE

Additional devices are known to be part of this pool, though their
exact configuration cannot be determined.
 

staticrsa

Cadet
Joined
Aug 7, 2017
Messages
5
That's a very dangerous configuration, but it isn't what's causing your problem--that's a bug in FN11 that should have been resolved in 11-U3. Update to 11.0-U3 and see if you can then import the pool.
Updating now, will post results
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
...although your zpool import output indicates you have bigger problems--you appear to have a pool of six disks striped, and one of those disks has failed. If that's the case, your data is gone. All of it.
 

rs225

Guru
Joined
Jun 28, 2014
Messages
878
You can try the failed disk in another computer and see if you can make an image, or send the failed disk for professional recovery. Otherwise, the pool is gone.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
To be clear, the bug I referred to above prevented importing pools that were degraded, but should still work--e.g., one disk failed in RAIDZ1. A pool like that should be able to be imported and used, though obviously the failed disk should be replaced ASAP. The inability to import such a pool was a bug, which should be fixed by now. But with a striped pool, which is what you appear to have, you have no redundancy--when a disk dies, the pool dies, and the odds are very slim that you'll ever be able to recover anything without spending five figures on data recovery.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
Is there now way to recreate it through zfs?
If you had a striped pool, which is what zpool import appears to be saying, then no. That's what happens with a striped pool; it's been that way as long as RAID0 has been a thing (ZFS striping isn't RAID0, exactly, but it works identically in this regard). If you wanted redundancy, you should have built a pool with redundancy. And if you cared about your data, you should have wanted redundancy. You also should have had a backup.
 

staticrsa

Cadet
Joined
Aug 7, 2017
Messages
5
If you had a striped pool, which is what zpool import appears to be saying, then no. That's what happens with a striped pool; it's been that way as long as RAID0 has been a thing (ZFS striping isn't RAID0, exactly, but it works identically in this regard). If you wanted redundancy, you should have built a pool with redundancy. And if you cared about your data, you should have wanted redundancy. You also should have had a backup.
Live and learn!

Thanks for the info
 

rs225

Guru
Joined
Jun 28, 2014
Messages
878
In this case, a full drive image data recovery (don't mention RAID or ZFS, maybe it is a DVR, Xbox or surveillance drive?), would be reasonably affordable in most countries, and would have a good chance (not guaranteed!) of reviving the pool. Files that were located in those unrecoverable blocks would be basically lost, but in some cases of sudden death drives, all blocks are recoverable.

If it was me, and somewhat important data, I would do it.
 

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419
Damn. 6 drive stripe.

How do you even do that? All at once? Or extend over time?
 
Status
Not open for further replies.
Top