On 09/06/11 13:46, Ron Johnson wrote:
On 06/07/2011 08:02 AM, Miles Fidelman wrote:
[snip]
- install SMART utilities and run smartctl -A /dev/your drive -- the
first line is usually the raw read error rate -- if the value (last
entry on the line) is anything except 0, that's the sign that
surreal firewal...@gmail.com writes:
From today morning i am getting strange kind of system messages on starting
the computer..
I typed dmesg and found these messages
[ 304.694936] ata4.00: status: { DRDY ERR }
[ 304.694939] ata4.00: error: { ICRC ABRT }
[ 304.694954] ata4: soft
On Tue, Jun 7, 2011 at 9:02 AM, Miles Fidelman
mfidel...@meetinghouse.net wrote:
Ralf Mardorf wrote:
For me a hard disc never gets broken without click-click-click noise
before it failed, but it's very common that cables and connections fail.
By the time a disk gets to the
Looks like controller failure or a broken pin/wire in the cable (more
likely).
On 09.06.2011 at 20:14 lee wrote:
surreal firewal...@gmail.com writes:
From today morning i am getting strange kind of system messages on
starting the computer..
I typed dmesg and found these messages
[Â
On 06/07/2011 08:02 AM, Miles Fidelman wrote:
[snip]
- install SMART utilities and run smartctl -A /dev/your drive -- the
first line is usually the raw read error rate -- if the value (last
entry on the line) is anything except 0, that's the sign that your drive
is failing, if it's in the
Ron Johnson wrote:
On 06/07/2011 08:02 AM, Miles Fidelman wrote:
[snip]
- install SMART utilities and run smartctl -A /dev/your drive -- the
first line is usually the raw read error rate -- if the value (last
entry on the line) is anything except 0, that's the sign that your drive
is failing,
From today morning i am getting strange kind of system messages on starting
the computer..
I typed dmesg and found these messages
[ 304.694936] ata4.00: status: { DRDY ERR }
[ 304.694939] ata4.00: error: { ICRC ABRT }
[ 304.694954] ata4: soft resetting link
[ 304.938280] ata4.00: configured
Couple of possibilites:
- Hard disk is failing
- Insufficient power available for your hard disk, causing it to spin up
then spin down again
- Controller error
- Faulty connection or SATA port
The more likely possibilities are 1 and 3.
If you can get another hard disk to test, that will narrow
On Tue, 2011-06-07 at 16:21 +0800, Ong Chin Kiat wrote:
If you can get another hard disk to test, that will narrow down the
possibilities
... and before doing this turn off power and disconnect and connect all
cables for this HDD on the HDD (power too) and on the mobo.
-- Ralf
--
To
] ata4: soft resetting link
(...)
What do you have attached to that port (ata 4)?
What do these messages mean? What is the solution to prevent these
messages from appearing? Help!
It can be a bad cable -or bad connection- or even a kernel issue. I mean,
it does not have to be a hard disk
On Tue, 2011-06-07 at 11:46 +, Camaleón wrote:
It can be a bad cable -or bad connection-
For me a hard disc never gets broken without click-click-click noise
before it failed, but it's very common that cables and connections fail.
A tip: If there's a warranty seal, don't break it, try to
On Tue, 2011-06-07 at 13:59 +0200, Ralf Mardorf wrote:
On Tue, 2011-06-07 at 11:46 +, Camaleón wrote:
It can be a bad cable -or bad connection-
For me a hard disc never gets broken without click-click-click noise
before it failed, but it's very common that cables and connections fail.
Ralf Mardorf wrote:
For me a hard disc never gets broken without click-click-click noise
before it failed, but it's very common that cables and connections fail.
By the time a disk gets to the click-click-click phase, there has been
LOTS of warning - it's just that today's disks include
On Tue, 2011-06-07 at 09:02 -0400, Miles Fidelman wrote:
Ralf Mardorf wrote:
For me a hard disc never gets broken without click-click-click noise
before it failed, but it's very common that cables and connections fail.
By the time a disk gets to the click-click-click phase,
A
On Tue, 07 Jun 2011, Miles Fidelman wrote:
b. you're running RAID - instead of the drive dropping out of the
array, the entire array slows down as it waits for the failing drive
to (eventually) respond
Eh, it is worse.
A failing drive _will_ drop out of the array sooner or later, and it can
Henrique de Moraes Holschuh wrote:
On Tue, 07 Jun 2011, Miles Fidelman wrote:
b. you're running RAID - instead of the drive dropping out of the
array, the entire array slows down as it waits for the failing drive
to (eventually) respond
Linux software raid is much more forgiving by
On Tue, 07 Jun 2011, Miles Fidelman wrote:
Linux software raid is much more forgiving by default (and it can tune
the timeout for each component device separately), and will just slow
down most of the time instead of kicking component devices off the array
until dataloss happens. Could be
Henrique de Moraes Holschuh wrote
Re. tuning: How? I've tried to find ways to get md to track
timeouts, and never been able to find any relevant parameters.
It is not in md. It is in the libata/scsi layer. Just tune the per-device
parameters, e.g. in /sys/block/sda/device/*
AFAIK, if
18 matches
Mail list logo
