On Fri, May 19, 2017 at 07:19:52PM -0400, Ted Unangst wrote:
| Paul de Weerd wrote:
| > Hi all,
| >
| > I've got a system with several softraid crypto devices mounted, and
| > one seems to be having issues. dmesg shows several of these:
| >
| > softraid0: i/o error on block 1104 target 0 b_error 5
| >
| > Is there a way to figure out which sd(4) device these come from? Or
| > what b_error 5 is?
|
| error 5 is EIO, I/O error. Target 0 doesn't reveal much, though, that's not a
| very helpful print out.
Thanks to a diff krw@ sent me off-list, I now get the following:
softraid0: i/o error on block 53584 target 0 (sd18)b_error 6
softraid0: i/o error on block 53584 target 0 (sd18)b_error 6
softraid0: i/o error on block 53584 target 0 (sd18)b_error 6
softraid0: i/o error on block 53584 target 0 (sd18)b_error 6
softraid0: i/o error on block 1104 target 0 (sd17)b_error 5
softraid0: i/o error on block 53456 target 0 (sd17)b_error 5
softraid0: I/O error 5 on dev 0x430 at block 16
softraid0: could not write metadata to sd3a
sd3 is the physical device that's backing sd17. I guess it's obvious
there's a broken disk there :(
Having this extra info (the '(sd17)' and '(sd18)' in those errors)
helps identify the problematic hardware. Any chance something like
this could be included?
Paul 'WEiRD' de Weerd
--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
http://www.weirdnet.nl/
