[Hampshire] SATA drive went read-only

Top Page

Reply to this message
Author: Chris Dennis
Date:  
To: Hampshire
Subject: [Hampshire] SATA drive went read-only
Hello folks

A client's Debian-based HP Proliant server suddenly decided to put make
some of its partitions read-only the other day -- see the syslog extract
below.

I need to work out whether it's a problem with the SATA disk drive, or
the controller, or whatever, and I can't make head or tail of the error
codes -- googling hasn't been much help.

And the server is a production machine that the client can't live
without, so I can't run tests very easily.

Can anyone point me to some information about SATA error codes, so that
I can begin to make a diagnosis?

My first thought is to replace the hard drive, but I don't know if that
would solve anything.

cheers

Chris

-----------------------------------------------
ata1: EH in SWNCQ mode,QC:qc_active 0x3 sactive 0x3
ata1: SWNCQ:qc_active 0x1 defer_bits 0x2 last_issue_tag 0x0
    dhfis 0x1 dmafis 0x1 sdbfis 0x0
ata1: ATA_REG 0x41 ERR_REG 0x10
ata1: tag : dhfis dmafis sdbfis sacitve
ata1: tag 0x0: 1 1 0 1
ata1.00: exception Emask 0x1 SAct 0x3 SErr 0x0 action 0x6 frozen
ata1.00: Ata error. fis:0x21
ata1.00: cmd 61/04:00:8b:93:0c/00:00:00:00:00/40 tag 0 ncq 2048 out
    res 41/10:04:8b:93:0c/10:00:00:00:00/40 Emask 0x81 (invalid argument)
ata1.00: status: { DRDY ERR }
ata1.00: error: { IDNF }
ata1.00: cmd 61/18:08:df:5c:fa/00:00:09:00:00/40 tag 1 ncq 12288 out
    res 41/10:04:8b:93:0c/10:00:00:00:00/40 Emask 0x81 (invalid argument)
ata1.00: status: { DRDY ERR }
ata1.00: error: { IDNF }
ata1: hard resetting link
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Result: hostbyte=DID_OKriverbyte=DRIVER_SENSE,SUGGEST_OK
sd 0:0:0:0: [sda] Sense Key : Aborted Command [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
    72 0b 14 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    00 0c 93 8b
sd 0:0:0:0: [sda] Add. Sense: Recorded entity not found
end_request: I/O error, dev sda, sector 824203
sd 0:0:0:0: [sda] Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE,SUGGEST_OK
sd 0:0:0:0: [sda] Sense Key : Aborted Command [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
    72 0b 14 00 00 00 00 0c 00 0a 80 00 00 00 00 00
    00 0c 93 8b
sd 0:0:0:0: [sda] Add. Sense: Recorded entity not found
end_request: I/O error, dev sda, sector 167402719
ata1: EH complete
sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't 
support DPO or FUA
Aborting journal on device dm-0.
Aborting journal on device dm-5.
ext3_abort called.
EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected aborted 
journal
Remounting filesystem read-only
----------------------------------------------------


-- 
Chris Dennis                                  cgdennis@???
Fordingbridge, Hampshire, UK