Dan Ritter:
> Jochen Spieker wrote: 
> 
>> The sector number mentioned at the bottom is increasing during the
>> check.
> 
> So it repeats, and it's contiguous. That suggests a flaw in the
> drive itself.

It definitely looks like that:

| Oct 06 14:27:11 jigsaw kernel: I/O error, dev sdb, sector 9361257600 op 
0x0:(READ) flags 0x0 phys_seg 150 prio class 3
| Oct 06 14:27:30 jigsaw kernel: I/O error, dev sdb, sector 9361275264 op 
0x0:(READ) flags 0x4000 phys_seg 161 prio class 3
| Oct 06 14:27:37 jigsaw kernel: I/O error, dev sdb, sector 9361277696 op 
0x0:(READ) flags 0x0 phys_seg 71 prio class 3
| Oct 06 14:28:02 jigsaw kernel: I/O error, dev sdb, sector 9361283584 op 
0x0:(READ) flags 0x0 phys_seg 160 prio class 3
| Oct 06 14:28:09 jigsaw kernel: I/O error, dev sdb, sector 9361284864 op 
0x0:(READ) flags 0x4000 phys_seg 160 prio class 3
| Oct 06 14:34:03 jigsaw kernel: I/O error, dev sdb, sector 9400838400 op 
0x0:(READ) flags 0x0 phys_seg 168 prio class 3
| Oct 06 14:34:17 jigsaw kernel: I/O error, dev sdb, sector 9400841088 op 
0x0:(READ) flags 0x0 phys_seg 153 prio class 3
| Oct 06 14:34:24 jigsaw kernel: I/O error, dev sdb, sector 9400842496 op 
0x0:(READ) flags 0x4000 phys_seg 138 prio class 3
| Oct 06 14:34:31 jigsaw kernel: I/O error, dev sdb, sector 9400845056 op 
0x0:(READ) flags 0x0 phys_seg 44 prio class 3
| Oct 06 14:34:39 jigsaw kernel: I/O error, dev sdb, sector 9400846464 op 
0x0:(READ) flags 0x0 phys_seg 16 prio class 3
| Oct 06 14:34:46 jigsaw kernel: I/O error, dev sdb, sector 9400846592 op 
0x0:(READ) flags 0x0 phys_seg 4 prio class 3
| Oct 06 14:34:53 jigsaw kernel: I/O error, dev sdb, sector 9400846848 op 
0x0:(READ) flags 0x4000 phys_seg 59 prio class 3
| Oct 06 14:35:00 jigsaw kernel: I/O error, dev sdb, sector 9400849408 op 
0x0:(READ) flags 0x0 phys_seg 27 prio class 3
| Oct 06 14:35:11 jigsaw kernel: I/O error, dev sdb, sector 9400850944 op 
0x0:(READ) flags 0x4000 phys_seg 160 prio class 3
| Oct 06 14:35:19 jigsaw kernel: I/O error, dev sdb, sector 9400852224 op 
0x0:(READ) flags 0x4000 phys_seg 160 prio class 3
| Oct 06 14:35:26 jigsaw kernel: I/O error, dev sdb, sector 9400853504 op 
0x0:(READ) flags 0x4000 phys_seg 160 prio class 3
| Oct 06 14:35:37 jigsaw kernel: I/O error, dev sdb, sector 9400855040 op 
0x0:(READ) flags 0x0 phys_seg 32 prio class 3
| Oct 06 14:35:45 jigsaw kernel: I/O error, dev sdb, sector 9400855296 op 
0x0:(READ) flags 0x0 phys_seg 160 prio class 3
| Oct 06 14:35:52 jigsaw kernel: I/O error, dev sdb, sector 9400856576 op 
0x0:(READ) flags 0x4000 phys_seg 160 prio class 3
| Oct 06 14:35:59 jigsaw kernel: I/O error, dev sdb, sector 9400857856 op 
0x0:(READ) flags 0x4000 phys_seg 159 prio class 3
| Oct 06 14:36:14 jigsaw kernel: I/O error, dev sdb, sector 9400859392 op 
0x0:(READ) flags 0x4000 phys_seg 160 prio class 3
| Oct 06 14:36:21 jigsaw kernel: I/O error, dev sdb, sector 9400860672 op 
0x0:(READ) flags 0x4000 phys_seg 160 prio class 3
| Oct 06 14:36:28 jigsaw kernel: I/O error, dev sdb, sector 9400861952 op 
0x0:(READ) flags 0x4000 phys_seg 160 prio class 3
| Oct 06 14:36:41 jigsaw kernel: I/O error, dev sdb, sector 9400863488 op 
0x0:(READ) flags 0x0 phys_seg 160 prio class 3
| Oct 06 14:36:48 jigsaw kernel: I/O error, dev sdb, sector 9400864768 op 
0x0:(READ) flags 0x4000 phys_seg 168 prio class 3
| Oct 06 14:37:00 jigsaw kernel: I/O error, dev sdb, sector 9400867584 op 
0x0:(READ) flags 0x0 phys_seg 160 prio class 3
| Oct 06 14:37:07 jigsaw kernel: I/O error, dev sdb, sector 9400868864 op 
0x0:(READ) flags 0x4000 phys_seg 160 prio class 3
| Oct 06 14:37:20 jigsaw kernel: I/O error, dev sdb, sector 9400871680 op 
0x0:(READ) flags 0x0 phys_seg 160 prio class 3

… and so on. On the second RAID check, the numbers are not the same, but
in the same range.

> If the disk is a few days away from being replaced, I would not
> bother shutting it off, but I would assume that it is not a full
> mirror and somehow having the good disk fail would be bad.

Thanks a lot for your input, that is exactly the kind of advice that I
was looking for.

J.
-- 
Thy lyrics in pop songs seem to describe my life uncannily accurately.
[Agree]   [Disagree]
                 <http://archive.slowlydownward.com/NODATA/data_enter2.html>

Attachment: signature.asc
Description: PGP signature

Reply via email to