You are not logged in.

#1 2013-07-21 10:36:52

Osiris
Member
Registered: 2003-01-18
Posts: 127
Website

Drive Failure Messages?

Hello,

I keep getting these messages with a beep from the drive:

Jul 21 12:05:22 horus kernel: ata8: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jul 21 12:05:22 horus kernel: ata8.00: configured for UDMA/33
Jul 21 12:05:22 horus kernel: ata8: EH complete
Jul 21 12:05:22 horus kernel: ata8.00: exception Emask 0x50 SAct 0xff SErr 0x90a00 action 0xe frozen
Jul 21 12:05:22 horus kernel: ata8.00: irq_stat 0x00400000, PHY RDY changed
Jul 21 12:05:22 horus kernel: ata8: SError: { Persist HostInt PHYRdyChg 10B8B }
Jul 21 12:05:22 horus kernel: ata8.00: failed command: WRITE FPDMA QUEUED
Jul 21 12:05:22 horus kernel: [144B blob data]
Jul 21 12:05:22 horus kernel: ata8.00: status: { DRDY }
Jul 21 12:05:22 horus kernel: ata8.00: failed command: WRITE FPDMA QUEUED
Jul 21 12:05:22 horus kernel: [144B blob data]
Jul 21 12:05:22 horus kernel: ata8.00: status: { DRDY }
Jul 21 12:05:22 horus kernel: ata8.00: failed command: READ FPDMA QUEUED
Jul 21 12:05:22 horus kernel: [144B blob data]
Jul 21 12:05:22 horus kernel: ata8.00: status: { DRDY }
Jul 21 12:05:22 horus kernel: ata8.00: failed command: READ FPDMA QUEUED
Jul 21 12:05:22 horus kernel: [144B blob data]
Jul 21 12:05:22 horus kernel: ata8.00: status: { DRDY }
Jul 21 12:05:22 horus kernel: ata8.00: failed command: READ FPDMA QUEUED
Jul 21 12:05:22 horus kernel: [144B blob data]
Jul 21 12:05:22 horus kernel: ata8.00: status: { DRDY }
Jul 21 12:05:22 horus kernel: ata8.00: failed command: READ FPDMA QUEUED
Jul 21 12:05:22 horus kernel: [144B blob data]
Jul 21 12:05:22 horus kernel: ata8.00: status: { DRDY }
Jul 21 12:05:22 horus kernel: ata8.00: failed command: WRITE FPDMA QUEUED
Jul 21 12:05:22 horus kernel: [144B blob data]
Jul 21 12:05:22 horus kernel: ata8.00: status: { DRDY }
Jul 21 12:05:22 horus kernel: ata8.00: failed command: WRITE FPDMA QUEUED
Jul 21 12:05:22 horus kernel: [144B blob data]
Jul 21 12:05:22 horus kernel: ata8.00: status: { DRDY }
Jul 21 12:05:22 horus kernel: ata8: hard resetting link

What do these messages mean? Is a drive failure right ahead? SMART shows nothing... How can I find out which drive (/dev/sdX) is having trouble?

Thanks!

Offline

#2 2013-07-21 11:24:28

graysky
Member
From: /run/user/1000
Registered: 2008-12-01
Posts: 8,597
Website

Re: Drive Failure Messages?


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#3 2013-07-21 17:53:33

Osiris
Member
Registered: 2003-01-18
Posts: 127
Website

Re: Drive Failure Messages?

Thanks for your kind reply. Any idea to which drive ata8 translates?

Offline

#4 2013-07-21 17:59:05

graysky
Member
From: /run/user/1000
Registered: 2008-12-01
Posts: 8,597
Website

Re: Drive Failure Messages?

No... just guessing but perhaps use a util dmidecode grepping for ata8?  How many physical discs are in your system?  If it is a low number you can add just pull the power to all and add them back one-by-one.


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#5 2013-07-21 18:04:32

Osiris
Member
Registered: 2003-01-18
Posts: 127
Website

Re: Drive Failure Messages?

There a only two drives that can possibly be the cause. But these two drives form a raid0. Since these errors happen only when accessing the drive, I can't disconnect one and access the other.

dmidecode does not seem to yield any usable information. Neither does lvdisplay (i'm not using LVM) which was recommended somehwere.

Offline

#6 2013-07-21 18:08:46

graysky
Member
From: /run/user/1000
Registered: 2008-12-01
Posts: 8,597
Website

Re: Drive Failure Messages?

OK... no idea.  How is your google-fu?


CPU-optimized Linux-ck packages @ Repo-ck  • AUR packagesZsh and other configs

Offline

#7 2013-07-21 18:41:12

Osiris
Member
Registered: 2003-01-18
Posts: 127
Website

Re: Drive Failure Messages?

root@horus ~ # cat /proc/scsi/scsi
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: OCZ-VERTEX2      Rev: 1.37
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi3 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST3000DM001-9YN1 Rev: CC4B
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi4 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: SAMSUNG HD103SJ  Rev: 1AJ1
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi5 Channel: 00 Id: 00 Lun: 00
  Vendor: HL-DT-ST Model: DVDRAM GH22NS40  Rev: NL01
  Type:   CD-ROM                           ANSI  SCSI revision: 05
Host: scsi6 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST3000DM001-1CH1 Rev: CC27
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi7 Channel: 00 Id: 00 Lun: 00
  Vendor: ATA      Model: ST3000DM001-1CH1 Rev: CC26
  Type:   Direct-Access                    ANSI  SCSI revision: 05
Host: scsi9 Channel: 00 Id: 00 Lun: 00
  Vendor: ST310003 Model: 33AS             Rev:     
  Type:   Direct-Access                    ANSI  SCSI revision: 02
Host: scsi8 Channel: 00 Id: 00 Lun: 00
  Vendor: WDC WD20 Model: EARS-00MVWB0     Rev: 51.0
  Type:   Direct-Access                    ANSI  SCSI revision: 05

ata8 must be either scsi6 or scsi7. I got no idea how to map...

root@horus ~ # dmesg | grep ata8
[    2.201720] ata8: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f380 irq 22
[    2.686204] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    2.687049] ata8.00: ATA-8: ST3000DM001-1CH166, CC26, max UDMA/133
[    2.687051] ata8.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA
[    2.687963] ata8.00: configured for UDMA/133

Ok, it seems to be scsi7.

Offline

Board footer

Powered by FluxBB