So I upgraded to Lenny over the weekend, and now I'm having issues with my RAID1 were there weren't any before. Every few hours one of the devices making up any /dev/md will fail. It's usually on /dev/sdb but it's happening on /dev/sda as well. I can set the device faulty in mdadm and then readd and it builds fine, but then fails again 4 or 5 hours later. I'm new to Linux software RAID so i'm hoping someone can point me in the right direction.
Here's some of the output from dmesg:
[144376.558796] ata2.00: status: { DRDY }
[144381.956229] ata2: link is slow to respond, please be patient (ready=0)
[144387.540534] ata2: device not ready (errno=-16), forcing hardreset
[144528.694227] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[144528.694231]********* res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[144528.694317] ata1.00: status: { DRDY }
[144534.215757] ata1: link is slow to respond, please be patient (ready=0)
[144818.556583]********* res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[144818.556667] ata2.00: status: { DRDY }
[144823.887918] ata2: link is slow to respond, please be patient (ready=0)
[144829.469773] ata2: device not ready (errno=-16), forcing hardreset
[144829.469816] ata2: soft resetting link
[144829.746129] ata2.00: configured for UDMA/133
[144829.746129] ata2: EH complete
:
Thanks for any assistance,
Ryan
02-19-2009, 07:22 AM
Adrian Levi
Repeated Raid1 Failures after upgrade to Lenny
2009/2/19 Ryan Wetterich <rwetterich@gmail.com>:
> So I upgraded to Lenny over the weekend, and now I'm having issues with my
> RAID1 were there weren't any before. Every few hours one of the devices
> making up any /dev/md will fail. It's usually on /dev/sdb but it's happening
> on /dev/sda as well. I can set the device faulty in mdadm and then readd and
> it builds fine, but then fails again 4 or 5 hours later. I'm new to Linux
> software RAID so i'm hoping someone can point me in the right direction.
>
> Here's some of the output from dmesg:
Do you still have Etch's kernel installed?
Boot from that and see if it continues?
Adrian
--
24x7x365 != 24x7x52 Stupid or bad maths?
<erno> hm. I've lost a machine.. literally _lost_. it responds to
ping, it works completely, I just can't figure out where in my
apartment it is.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
02-19-2009, 07:43 AM
martin f krafft
Repeated Raid1 Failures after upgrade to Lenny
also sprach Ryan Wetterich <rwetterich@gmail.com> [2009.02.19.0534 +0100]:
> [144376.558796] ata2.00: status: { DRDY }
> [144381.956229] ata2: link is slow to respond, please be patient (ready=0)
> [144387.540534] ata2: device not ready (errno=-16), forcing hardreset
> [144387.540577] ata2: soft resetting link
> [144387.793049] ata2.00: configured for UDMA/133
> [144387.793095] ata2: EH complete
> [144387.793564] sd 1:0:0:0: [sdb] 2930277168 512-byte hardware sectors
> (1500302
> MB)
> [144387.816527] end_request: I/O error, dev sdb, sector 10313569
> [144387.816527] md: super_written gets error=-5, uptodate=0
> [144387.816527] raid1: Disk failure on sdb5, disabling device.
[...]
This looks like a hardware problem, not a software problem. It's
probably just your disk breaking, but it could the the SATA
controller too.
Install smartmontools and see the output of
smartctl -d ata -H -l error /dev/sdb
--
.'`. martin f. krafft <madduck@d.o> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
... with a plastic cup filled with a liquid that was almost,
but not quite, entirely unlike tea.
-- douglas adams, "the hitchhiker's guide to the galaxy"