See below
Tony van der Hoff wrote:
On 17/10/15 17:47, Miles Fidelman wrote:
Dominique Dumont wrote:
On Saturday 17 October 2015 14:15:52 Tony van der Hoff wrote:
Can anyone please explain what it means, and whether I should be
worried?
You should check the drive with smartctl.
See http://ww
On Sat, Oct 17, 2015 at 02:15:52PM +0100, Tony van der Hoff wrote:
> Hi,
>
> T'm occasionally getting this message in syslog on my jessie box:
>
> Oct 17 12:00:19 tony-lx kernel: [ 8838.600489] ata3.00: exception Emask 0x10
> SAct 0x10 SErr 0x40 action 0x6 frozen
> Oct 17 12:00:19 tony-lx ker
On 20/10/15 11:22, Ondřej Grover wrote:
Does this error occur by any chance after resuming from suspended state?
No, this machine doesn't suspend.
But thanks, anyway.
--
Tony van der Hoff| mailto:t...@vanderhoff.org
Buckinghamshire, England |
Does this error occur by any chance after resuming from suspended state? I
had a similar problem because of some faulty drivers, setting
echo 0 > /sys/power/pm_async
makes sure that drivers do not resume asynchronously and it might fix the
problem.
Or can it be correlated to any other system events
On 17/10/15 17:47, Miles Fidelman wrote:
Dominique Dumont wrote:
On Saturday 17 October 2015 14:15:52 Tony van der Hoff wrote:
Can anyone please explain what it means, and whether I should be
worried?
You should check the drive with smartctl.
See http://www.smartmontools.org/
HTH
Yes.. and
Hi!
You can use Disk Utility (gnome-disks / udisks) and check your hard drive
for errors, or bad sectors.
That seems to be simple enough!
Regards
Himanshu Shekhar
IIIT-Allahabad
IRM2015006
On Saturday 17 October 2015 12:47:36 Miles Fidelman wrote:
> For a lot of drives, the first line - raw read errors, can be very telling -
> anything other than 0, and your disk is failing.
Sorry, the FAQ [1] on smartmontools.org does not agree with your statement:
* What details can be interprete
Dominique Dumont wrote:
On Saturday 17 October 2015 14:15:52 Tony van der Hoff wrote:
Can anyone please explain what it means, and whether I should be worried?
You should check the drive with smartctl.
See http://www.smartmontools.org/
HTH
Yes.. and be sure to go beyond the basic tests.
Fi
On Saturday 17 October 2015 14:15:52 Tony van der Hoff wrote:
> Can anyone please explain what it means, and whether I should be worried?
You should check the drive with smartctl.
See http://www.smartmontools.org/
HTH
--
https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/
http:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Oct 17, 2015 at 02:15:52PM +0100, Tony van der Hoff wrote:
> Hi,
>
> T'm occasionally getting this message in syslog on my jessie box:
>
> Oct 17 12:00:19 tony-lx kernel: [ 8838.600489] ata3.00: exception
> Emask 0x10 SAct 0x10 SErr 0x40
Hi,
T'm occasionally getting this message in syslog on my jessie box:
Oct 17 12:00:19 tony-lx kernel: [ 8838.600489] ata3.00: exception Emask
0x10 SAct 0x10 SErr 0x40 action 0x6 frozen
Oct 17 12:00:19 tony-lx kernel: [ 8838.600501] ata3.00: irq_stat
0x0800, interface fatal error
Oct 1
On 06/12/2015 12:45 AM, Peter Viskup wrote:
Always consider using ddrescue [1] instead of dd - especially once you are
not sure about the state of the drive.
Tool ddrescue is taking 'dd' image of the drive, but will skip all the
areas where the read will return an error. Standard 'dd' will try to
Always consider using ddrescue [1] instead of dd - especially once you are
not sure about the state of the drive.
Tool ddrescue is taking 'dd' image of the drive, but will skip all the
areas where the read will return an error. Standard 'dd' will try to
continuously re-read that area which could ca
On Thursday 11 June 2015 23:46:02 Alejandro Exojo wrote:
> This is the whole smartctl output:
>
> http://paste.debian.net/220687/
>
> Can I understand the following line as that the disk might be fine?
>
> SMART overall-health self-assessment test result: PASSED
Details show that no bad sectors
On 06/11/2015 12:32 AM, Alejandro Exojo wrote:
Yesterday I found out that my extra disk shut down. I don't know what steps to
follow from now on. I'm searching online about the error as I found in the
logs, and I don't know what steps to follow.
...
I don't know where to proceed from here. The
El Thursday 11 June 2015, Ric Moore escribió:
> On 06/11/2015 03:32 AM, Alejandro Exojo wrote:
> Or should I create an image as a
>
> > file stored somewhere else?
>
> Just for grins, unplug the connector(s) from the drive AND at the
> motherboard, both. Plug it all back in again. That has work
On 06/11/2015 03:32 AM, Alejandro Exojo wrote:
Or should I create an image as a
file stored somewhere else?
Just for grins, unplug the connector(s) from the drive AND at the
motherboard, both. Plug it all back in again. That has worked for me
more than once, and I replaced those cables after
Hello.
Yesterday I found out that my extra disk shut down. I don't know what steps to
follow from now on. I'm searching online about the error as I found in the
logs, and I don't know what steps to follow.
This is the log (I just trimmed which I think it was irrelevant):
http://paste.debian.ne
Hi,
I have a raid1 array with two disks, distro is Squeeze amd64. /dev/sda
is slowly dying, here is a snippet of "smartctl -a /dev/sda":
197 Current_Pending_Sector 0x0012 100 100 000Old_age Always
- 2
198 Offline_Uncorrectable 0x0030 100 100 000Old_age
Off
Looks like controller failure or a broken pin/wire in the cable (more
likely).
On 09.06.2011 at 20:14 lee wrote:
>surreal 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] at
On Tue, Jun 7, 2011 at 9:02 AM, 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, there
surreal 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 resetting link
> [
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/ -- 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
Ron Johnson wrote:
On 06/07/2011 08:02 AM, Miles Fidelman wrote:
[snip]
- install SMART utilities and run "smartctl -A /dev/ -- 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
On 06/07/2011 08:02 AM, Miles Fidelman wrote:
[snip]
- install SMART utilities and run "smartctl -A /dev/ -- 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 1000s, failur
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
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
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:
> 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
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 phas
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 l
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 fa
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 lo
ean,
it does not have to be a hard disk failure "per se". Anyway, running a
smartctl long test will neither hurt.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lis
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 U
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 do
>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
On Wed, Jun 30, 2010 at 05:34:22PM -0400, H.S. wrote:
>
> So now I know that my backups most probably are not trustworthy, the
> ones from the last four or so days. No problem. I do rolling backups
> using cron and rsync. But what I do now?
Now you buy at least two new disks, preferably some that
On Jo, 01 iul 10, 18:42:26, H.S. wrote:
>
> Okay, did all these, but that set of file not found errors upon console
> login is still there.
They are probably gone. If you want to try to repair the system (versus
reinstalling from scratch) you can just reinstall each package
containing the missi
On 01/07/10 09:43 AM, H.S. wrote:
> On 01/07/10 03:34 AM, Andrei Popescu wrote:
>>
>> Don't you have some method of checking the integrity of you backups?
>> (http://www.taobackup.com/integrity.html)
>>
>> It is considered that a modern drive developing bad sectors visible to
>> the system[1] is n
On 01/07/10 03:34 AM, Andrei Popescu wrote:
>
> Don't you have some method of checking the integrity of you backups?
> (http://www.taobackup.com/integrity.html)
>
> It is considered that a modern drive developing bad sectors visible to
> the system[1] is not to be trusted.
>
> [1] drives are re
On Mi, 30 iun 10, 17:34:22, H.S. wrote:
> So now I know that my backups most probably are not trustworthy, the
> ones from the last four or so days. No problem. I do rolling backups
> using cron and rsync. But what I do now? Do I just delete the backups
> from the last four days and resume regula
I noticed that when I rebooted my machine earlier today, it would not
load the kernel and it was giving some "media error" messages.
I did various basic hardware debugging and ended up with my hard disk's
manufacturer's diagnostic utility telling me that there were bad sectors
on the drive. This
On 09-11-03 21:29:19, Luis Maceira wrote:
> In Ubuntu9.10 I have received warnings that a HDD is in
> pre-failure.The disk(Iomega Prestige mobile USB external) has 1
> month.In Debian Testing and OpenSolaris(installed on the same HDD I
> have no warnings.).Using smartmontools (this disk is not in i
On Tuesday 03 November 2009 17:29:19 Luis Maceira wrote:
> In Ubuntu9.10 I have received warnings that a HDD is in pre-failure.The
> disk(Iomega Prestige mobile USB external) has 1 month.In Debian Testing and
> OpenSolaris(installed on the same HDD I have no warnings.).Using
> smartmontools (this d
In Ubuntu9.10 I have received warnings that a HDD is in pre-failure.The
disk(Iomega Prestige mobile USB external) has 1 month.In Debian Testing and
OpenSolaris(installed on the same HDD I have no warnings.).Using smartmontools
(this disk is not in its database) I get below:
m...@mycomputer:~$ su
>
>
>
> Original Message
>From: longwind2...@gmail.com
>To: debian-user@lists.debian.org
>Subject: Re: need advice on scsi disk failure
>Date: Fri, 21 Aug 2009 14:33:10 -0800
>
>>On Fri, Aug 21, 2009 at 7:34 AM, wrote:
>>>>
>>> The c
On Fri, Aug 21, 2009 at 7:34 AM, wrote:
>>
> The conventional approach is first to clean the contacts on the
> connector and the card (some alcohol on a cotton swab for the
> connector and a pencil eraser for the card contacts) and try again.
> If that doesn't work go to "plan B" (run a complete d
On Fri, Aug 21, 2009 at 11:34 AM, wrote:
> The conventional approach is first to clean the contacts on the
> connector and the card (some alcohol on a cotton swab for the
> connector and a pencil eraser for the card contacts) and try again.
> If that doesn't work go to "plan B" (run a complete dis
>
>
>
> Original Message
>From: longwind2...@gmail.com
>To: debian-user@lists.debian.org
>Subject: RE: need advice on scsi disk failure
>Date: Fri, 21 Aug 2009 08:50:21 -0400
>
>>I bought a scsi 50G disk a few years ago
>>The seller said it had be
On Fri, 21 Aug 2009 09:35:25 -0400
Long Wind wrote:
> On Fri, Aug 21, 2009 at 8:56 AM, mitch
> wrote:
> >
> > I had the same problem, scsi drives failing to start, shutting down
> > while running.
> >
> > Bad power connector. The pins were not making proper contact at all
> > times.
> >
> > Chang
On Fri, Aug 21, 2009 at 8:56 AM, mitch wrote:
>
> I had the same problem, scsi drives failing to start, shutting down
> while running.
>
> Bad power connector. The pins were not making proper contact at all
> times.
>
> Changed the connectors and the problem stopped.
>
Really?
I always think scsi
On Fri, 21 Aug 2009 08:50:21 -0400
Long Wind wrote:
> It's no surprise because the light on scsi disk isn't on
> I reconnect the power cable to scsi disk again and again
> and then with some luck the disk works normally.
> It seems that the power connection becomes loose
I had the same problem,
It's no surprise because the light on scsi disk isn't on
I reconnect the power cable to scsi disk again and again
and then with some luck the disk works normally.
It seems that the power connection becomes loose
but I am afraid the disk is failing
My question is "Is that symptoms of scsi
On Wed, Nov 14, 2007 at 04:46:42PM +, michael wrote:
> On Wed, 2007-11-14 at 11:41 +, michael wrote:
> > On Wed, 2007-11-14 at 12:22 +0100, Jochen Schulz wrote:
> > > michael:
> > > > 'tiger' just told me various home directories are unavailable and upon
> > > > further investigation I see
On Wed, 2007-11-14 at 11:41 +, michael wrote:
> On Wed, 2007-11-14 at 12:22 +0100, Jochen Schulz wrote:
> > michael:
> > > 'tiger' just told me various home directories are unavailable and upon
> > > further investigation I see disk errors. Here's the first reports I can
> > > find regarding sa
On Wed, 2007-11-14 at 12:22 +0100, Jochen Schulz wrote:
> michael:
> > 'tiger' just told me various home directories are unavailable and upon
> > further investigation I see disk errors. Here's the first reports I can
> > find regarding said hard drive:
> >
> > Nov 13 02:23:01 ratty /USR/SBIN/CRON
michael:
> 'tiger' just told me various home directories are unavailable and upon
> further investigation I see disk errors. Here's the first reports I can
> find regarding said hard drive:
>
> Nov 13 02:23:01 ratty /USR/SBIN/CRON[19292]: (michael) CMD (rsync -r -v
> -P --links --stats /data_hdb1/
On Wed, 2007-11-14 at 10:36 +, michael wrote:
> 'tiger' just told me various home directories are unavailable and upon
> further investigation I see disk errors. Here's the first reports I can
> find regarding said hard drive:
>
> Nov 13 02:23:01 ratty /USR/SBIN/CRON[19292]: (michael) CMD (rsy
'tiger' just told me various home directories are unavailable and upon
further investigation I see disk errors. Here's the first reports I can
find regarding said hard drive:
Nov 13 02:23:01 ratty /USR/SBIN/CRON[19292]: (michael) CMD (rsync -r -v
-P --links --stats /data_hdb1/michael/ /data_hdd1/m
> Well, I have been wrong a few times before, but jumping to conclusions
> has stood me well over the years on average. I'm a semi-almost-nearly
> retired broadcast engineer and a Certified Electronics Technician with
> over 55 years of corraling electrons for a living. They never seem to
> want
hi,
me myself had similar troubles with SATA Seagate drive and DMA (in WinXP no
problems) - see Jeff Garzik's libsata page.
I solved it by buying a Western Digital drive.
Al_
On Thu 30. of March 2006 18:14, Ramiro Aceves wrote:
> Hello,
>
> Thank you very much for your help. I apreciate your t
Hello,
Thank you very much for your help. I apreciate your time. The hard
disk has faced the problem again today. The problem is that the disk
exhibit the same errors (with different numbers) at boot.
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { Uncorre
disk cable? Or is it an "internal"
> disk drive error?
> 2- Should I return the disk to my seller?
>
>
> Normally, restarting the computer solves the problem after a fsck.
> Sometimes I have also run a "manual" fsck with no aparent data loss. I
> am concern
On Thursday 30 March 2006 06:38, Ramiro Aceves wrote:
>smartctl -t /dev/hda
and see what falls out, but it sounds like a drive problem that needs to
be warrantied to me.
--
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and t
t;
disk drive error?
2- Should I return the disk to my seller?
Normally, restarting the computer solves the problem after a fsck.
Sometimes I have also run a "manual" fsck with no aparent data loss. I
am concerned about a more serious hard disk failure with real data
loss. (I have done backups, no problem ;-) )
Many thanks in advance:
Ramiro
On Fri, Mar 10, 2006 at 10:52:33AM +0100, Jim MacBaine wrote:
> Hello,
>
> one of my hard drives seems to be dying. To me as a layman this looks
> as if the disk should be returned to the shop where I bought it. Is
> this right?
>
> ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/1
On Friday, 10 March 2006 11:52, Jim MacBaine wrote:
> Hello,
>
> one of my hard drives seems to be dying. To me as a layman this looks
> as if the disk should be returned to the shop where I bought it. Is
> this right?
>
> ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1
Hello,
one of my hard drives seems to be dying. To me as a layman this looks
as if the disk should be returned to the shop where I bought it. Is
this right?
ata1: translated ATA stat/err 0x51/40 to SCSI SK/ASC/ASCQ 0x3/11/04
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x40 {
On Sat, Jan 07, 2006 at 11:02:25PM -0800, Mike Bird wrote:
> On Sat, 2006-01-07 at 22:15, Daniel Webb wrote:
> > On Sat, Jan 07, 2006 at 09:02:20PM -0800, Mike Bird wrote:
> > Well, yes, but supposing you *do* have a failure? Then what? Half the
> > filesystem is still there on the second disk, i
On Sat, 2006-01-07 at 22:15, Daniel Webb wrote:
> On Sat, Jan 07, 2006 at 09:02:20PM -0800, Mike Bird wrote:
> Well, yes, but supposing you *do* have a failure? Then what? Half the
> filesystem is still there on the second disk, is it recoverable, and if not,
> why not?
You may get some of the d
On Sat, Jan 07, 2006 at 09:02:20PM -0800, Mike Bird wrote:
> If you've got enough spindles, each physical volume is typically a RAID1
> or RAID5. Then you can add and remove physical volumes from
> your volume group as needed. A single disk failure is harmless.
>
> O
er to this question.
If you've got enough spindles, each physical volume is typically a RAID1
or RAID5. Then you can add and remove physical volumes from
your volume group as needed. A single disk failure is harmless.
Other than adding and removing physical volumes you don't resize
the
I've been Googling for the answer to this and failing, so:
What happens when you have a 2-disk LVM volume group and disk 1 fails?
Obviously this will depend on the filesystem you put on top of the volume,
right? So which filesystems will recover gracefully if you chop them in half
like that?
It'
Mike Fedyk wrote:
Then it will create a new array (make sure you have one missing drive
so that it doesn't try syncing the disks) with the old disks. What
you're trying to do is find the original disk order, and if you fail
multiple disks, that ordering info is lost AFAIK.
Here[1] are the comb
Hi all,
I just wrote a script runs a brute force attack against a raid5 array
that has had multiple drives removed from an active array.
Yep, that's what I did, and the last resort was (from everywhere I could
find with google) was to use the old mkraid tool if I had a raidtab. I
have been usi
On Mon, Mar 06, 2000 at 11:07:47AM +0100, Anton Emmerfors wrote:
> Hi,
>
> This is not strictly Debian related, but lots of competent people
> dwell on this list so...
>
> Yesterday I came home to find that my Quantum Fireball SCSI-disk had
> produced an "Unrecoverable read error". From kern.log:
Hi,
This is not strictly Debian related, but lots of competent people
dwell on this list so...
Yesterday I came home to find that my Quantum Fireball SCSI-disk had
produced an "Unrecoverable read error". From kern.log:
--8<--
kernel: scsi0: MEDIUM ERROR on channel 0, id 0, lun 0, CDB: Read (10)
Hi there,
today I tried to install the latest debian on a PPro180 system with an
Adaptec 2940U. Unfortunately, no boot-disk seems to work for that system.
The strangest thing I get is 'Controller at 0x378 doesn't react' (the
controller is located at e000-efff (irq 11).
Any ideas as to what c
79 matches
Mail list logo
