From: Robert Hancock <hancockr@shaw.ca>
To: Nathan <nathan.stocks@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Did my SATA drive fail? What should I do?
Date: Sat, 24 Jan 2009 02:34:03 -0600 [thread overview]
Message-ID: <497AD27B.8000204@shaw.ca> (raw)
In-Reply-To: <96c9d6a80901221431u16dbf135ife7b59f7b38cb8fa@mail.gmail.com>
Nathan wrote:
> First off: Hi! I'm new to this list. Googling some of the errors in
> my logs brought up several posts to this list, none of which led to
> any obvious resolutions, so I thought I'd try joining the list...
>
> I have a linux server[1] that has been acting as an asterisk pbx for
> about three months without a problem. Today, the SATA hard drive
> suddenly went into read-only mode (!?). Reading seems to work just
> fine, as I've ssh'd in and looked at a bunch of files, including
> /var/log/messages [2].
>
> Is this just my hardware failing? Could this a kernel bug?
> Recommendations? I would just reboot the thing, but asterisk is still
> successfully handling dozens of calls right now, despite not being
> able to write to the disk...
>
> [1] # uname -a
> Linux phoneserver3 2.6.25-gentoo-r7 #2 SMP Thu Oct 16 20:59:53 MDT
> 2008 x86_64 Intel(R) Xeon(R) CPU E5410 @ 2.33GHz GenuineIntel
> GNU/Linux
>
> [2] (last several lines from /var/log/messages)
>
> Jan 22 14:43:09 phoneserver3 dhcpd: DHCPDISCOVER from
> 00:04:f2:1e:7e:21 via eth2: network 10.254.254/24: no free leases
> Jan 22 14:43:09 phoneserver3 dhcpd: DHCPDISCOVER from
> 00:04:f2:1e:7c:6b via eth2: network 10.254.254/24: no free leases
> Jan 22 14:43:35 phoneserver3 dhcpd: DHCPDISCOVER from
> 00:04:f2:1e:0d:47 via eth2: network 10.254.254/24: no free leases
> Jan 22 14:43:36 phoneserver3 dhcpd: DHCPDISCOVER from
> 00:1f:28:83:00:80 via eth2: network 10.254.254/24: no free leases
> Jan 22 14:43:41 phoneserver3 ata1.00: exception Emask 0x0 SAct 0x0
> SErr 0x0 action 0x0
> Jan 22 14:43:41 phoneserver3 ata1.00: BMDMA stat 0x25
> Jan 22 14:43:41 phoneserver3 ata1.00: cmd
> ca/00:20:00:7c:ef/00:00:00:00:00/ef tag 0 dma 16384 out
> Jan 22 14:43:41 phoneserver3 res 51/10:20:00:7c:ef/00:00:00:00:00/ef
> Emask 0x81 (invalid argument)
> Jan 22 14:43:41 phoneserver3 ata1.00: status: { DRDY ERR }
> Jan 22 14:43:41 phoneserver3 ata1.00: error: { IDNF }
Most likely this is the disk failing. It's reporting the sector wasn't
found during a write operation.
next prev parent reply other threads:[~2009-01-24 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 22:31 Did my SATA drive fail? What should I do? Nathan
2009-01-24 8:34 ` Robert Hancock [this message]
2009-01-26 3:45 ` Nathan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=497AD27B.8000204@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan.stocks@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox