FWIW i get the same thing .. some of my raid1 arrays tend to become U_ after a few months of light use. Rebooting the box allows the device to be addressable again, and the disk is not, in fact, bad .. I can do a complete dd to the "bad" disk without error, then raidhotadd it back in again as well. A few months later of uptime, it is U_ again.. On an example box where this happens, the kernel is SMP 2.4.2 the controller is motherboard Adaptec 7896, the driver is aic7xxx the disks are ultra lvds, the cables and disk mounts are all by intel so I do not suspect a termination or cabling issue. The motherboard is 440GX. I am curious to see whether my other boxes which are 2.4.18 SMP will be more stable. -Justin On Tue, Mar 19, 2002 at 11:58:46PM +0100, Marcel wrote: > Rainer Fuegenstein wrote: > > > > Additional sense indicates Unrecovered read error > > I/O error: dev 08:19, sector 12850360 > > <big snip> > > You should enable verbose SCSI error reporting in the kernel. It's a > compile time kernel option. This will tell you more about what's going > on in the disk subsystem. > > The above error message is not enough and if it's all you get, even with > verbose error reporting enabled, you should talk to people more familiar > with the SCSI drivers. Meanwhile double-check whether SCSI bus > termination is done "by the book". Failure to do so can also cause some > nasty intermittent problems. > > Marcel > > - > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
