gpg: failed to create temporary file '/var/lib/lurker/.#lk0x577be100.hantslug.org.uk.2356': Permission denied
gpg: keyblock resource '/var/lib/lurker/pubring.gpg': Permission denied
gpg: Signature made Tue Oct 19 21:19:26 2010 BST
gpg: using DSA key 20ACB3BE515C238D
gpg: Can't check signature: No public key
On Tue, Oct 19, 2010 at 08:39:28PM +0100, Chris Dennis wrote:
> 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.
Error messages are officially documented at:
https://ata.wiki.kernel.org/index.php/Libata_error_messages
> 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.
> -----------------------------------------------
> 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
First error starts here
> 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 }
"Requested address was not found."
> 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 }
Same again.
> ata1: hard resetting link
> ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
It's trying to reset the SATA connection.
> ata1.00: configured for UDMA/133
> sd 0:0:0:0: [sda] Result: hostbyte=DID_OKriverbyte=DRIVER_SENSE,SUGGEST_OK
There's some corruption here. "riverbyte"? :)
> 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
The OS is having trouble talking to the disk here, even at the
basic level of finding out what it is.
> 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
However, here it's worked after a retry.
> 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
Not sure what's happened here.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- It's not so much an afterlife, more a sort of après vie. ---
