zpool FAULTED - Please help!

[tefoster]

I was using a live version booting from CD and I tried multiple distros, I finally asked someone at work about the sleeping problem and he told me to try this: http://www.sysresccd.org/SystemRescueCd_Homepage
that turned out to be exactly what I needed, it took about 12 hours but the disk was cloned to completion. There were unrecoreverable errors but I expected that.

Yes, I have already tried to import the cloned drive and it failed with the "The pool cannot be imported due to damaged devices or data" error. I'm out of my league here but I have a feeling that if I could just get it to forget about trying to replace the disk there might be some hope. All of the drives appear as online.

Any thoughts?

Thanks,
Tom

 

[ProtoSD]

My brain is a bit burned out at the moment. I'm doing some upgrades over the weekend for a client and I'm trying to make sure I don't miss anything before everyone comes back on Tuesday! Uggghh.

I'm sure there's an answer somewhere, but you're not the first one I've seen that's been stuck with the "replacing drive" message and not able to clear or restart it. I'm sure someone with more ZFS experience than me would have some ideas. Let me give it some more thought, maybe I'll come up with something else to try.

Did you use "ddrescue" to clone your disk? It usually does an excellent job of skipping bad spots and getting the easy stuff and then scraping the bad spots for every little bit it can get if you let it run long enough. Of course it depends on how the disk is failing.

-- Proto

 

[tefoster]

Thanks Proto - Good luck with your upgrades, I wish you the best of luck!!!

Yes, I did use ddrescue. If you know of anyone with more ZFS experience please let me know.

I can't tell you how much I appreciate your help!

Thanks,
Tom

 

[ProtoSD]

Tom,

You're welcome for the help, I think all of us know how much it sucks to loose data like that, ZFS still has its downsides. After a few quick searches, I found some other posts from people that have had the same problem. It seems like its a known issue with ZFS. Here's a brief discussion with someone else that had the problem:

http://comments.gmane.org/gmane.os.solaris.opensolaris.zfs/36915

http://mail.opensolaris.org/pipermail/zfs-discuss/2009-August/030396.html



You might be able to try:

zpool clear FreeNAS device-name (like 13559610085734653217, or da1p2)