stuck in "too many errors"

This forum is to find answers to problems you may be having with ZEVO Community Edition.

Moderators: jhartley, MSR734, nola

stuck in "too many errors"

Post by jgs » Wed May 15, 2013 4:17 pm

I'm a Zevo (and ZFS) newbie so possibly the answer to my question will be embarrassingly obvious (I kind of hope so) but I've been unable to glean it from man pages, other documentation, Wiki and forums, so here goes.

After downloading and installing Zevo, I built myself a little raidz2 out of three disks I had lying around, to play with. One of the things I tried was the obvious step of "failing" one of the drives by simply turning it off. As expected, Zevo puts it into FAULTED state and puts the raidz2 into DEGRADED state. Where I am perplexed is in getting the disk out of faulted state. The output of 'zpool status' suggests a 'zpool clear'. However, when I try that, nothing useful happens. system.log shows

Code: Select all
May 15 17:12:28 Humongous-Mini kernel[0]: zfs_vdm_completion: media 0xffffff802a9f0300, media is not present (6), 0 bytes (of 8192)
May 15 17:12:28 --- last message repeated 2 times ---
May 15 17:12:28 Humongous-Mini kernel[0]: ________________________________________
May 15 17:12:28 Humongous-Mini kernel[0]: ZFS WARNING: 'error from: fs.zfs.probe_failure'
May 15 17:12:28 Humongous-Mini kernel[0]: pool: 'z2'
May 15 17:12:28 Humongous-Mini kernel[0]: vdev_type: 'disk'
May 15 17:12:28 Humongous-Mini kernel[0]: vdev_path: '/dev/dsk/GPTE_A699425F-9C0A-479C-AF53-662442B2F04F'
May 15 17:12:28 Humongous-Mini kernel[0]: parent_type: 'raidz'
May 15 17:12:28 Humongous-Mini kernel[0]: prev_state: 0

Regrettably, I feel no smarter after reading this than I did before.

I did find that some combination of dismounting the filesystem and turning all the component disks off and on again got things working, but that was not a satisfying fix for obvious reasons. I'd be obliged for any clues.
jgs Offline


 
Posts: 3
Joined: Fri May 03, 2013 12:46 pm

Re: stuck in "too many errors"

Post by grahamperrin » Thu May 16, 2013 12:25 am

Welcome to the forum!

jgs wrote:… three disks …


For the one that was disconnected, how is connection usually made?

How are the other two connected?

… nothing useful happens …


Does anything happen? Does the command complete?
grahamperrin Offline

User avatar
 
Posts: 1596
Joined: Fri Sep 14, 2012 10:21 pm
Location: Brighton and Hove, United Kingdom

Re: stuck in "too many errors"

Post by jgs » Thu May 16, 2013 10:05 am

grahamperrin wrote:Welcome to the forum!

Thanks!
For the one that was disconnected, how is connection usually made?

How are the other two connected?

USB in all cases.
… nothing useful happens …


Does anything happen? Does the command complete?

The command does complete, but the state of the component disk and the raidz2 don't change. The error that I showed in my initial post gets logged to system.log.
jgs Offline


 
Posts: 3
Joined: Fri May 03, 2013 12:46 pm

Re: stuck in "too many errors"

Post by jgs » Thu May 16, 2013 4:22 pm

I had occasion to reboot the system -- for what it's worth, it cleared the "too many errors" FAULTED state. But again, a reboot is not a happy way to mend a degraded RAID system, so I hope to find a better resolution.
jgs Offline


 
Posts: 3
Joined: Fri May 03, 2013 12:46 pm

Re: stuck in "too many errors"

Post by AnthonyButler » Sat Aug 17, 2013 3:53 am

So was the error due to upgraded system? Did degrading completely solved your problem?
AnthonyButler Offline


 
Posts: 1
Joined: Sat Aug 17, 2013 2:53 am


Return to Troubleshooting

Who is online

Users browsing this forum: bileyqrkq, ilovezfs, toduefiwu and 0 guests

cron