On 2012-07-24 21:29, Adam Vande More wrote:
> On Tue, Jul 24, 2012
at 11:40 AM, dweimer wrote:
>
>> Just curious, I
am sure the likely issue is a bad disk, but I thought there might be a
chance this could be caused by possibly by something else.
>>
>> I have
three 1TB disks I use for backup
On Tue, Jul 24, 2012 at 11:40 AM, dweimer wrote:
> Just curious, I am sure the likely issue is a bad disk, but I thought
> there might be a chance this could be caused by possibly by something else.
>
> I have three 1TB disks I use for backup, two of them are Western Digital
> drives I bought spe
On 2012-07-24 16:10, Warren Block wrote:
On Tue, 24 Jul 2012, dweimer wrote:
Just curious, I am sure the likely issue is a bad disk, but I
thought there might be a chance this could be caused by possibly by
something else.
I have three 1TB disks I use for backup, two of them are Western
Dig
On Tue, 24 Jul 2012, dweimer wrote:
Just curious, I am sure the likely issue is a bad disk, but I thought there
might be a chance this could be caused by possibly by something else.
I have three 1TB disks I use for backup, two of them are Western Digital
drives I bought specifically for this
dweimer wrote:
[snip]
>
> SMART Attributes Data Structure revision number: 10
> Vendor Specific SMART Attributes with Thresholds:
> ID# ATTRIBUTE_NAME FLAGSVALUE WORST THRESH FAIL RAW_VALUE
>1 Raw_Read_Error_Rate POSR-- 117 099 006-145191418
[...]
>7 Seek_Er
dweimer dweimer.net> writes:
> ...
> 188 Command_Timeout -O--CK 100 098 000-
> 21475164202
> ...
I can not find it for Seagate;
http://sourceforge.net/apps/trac/smartmontools/wiki/AttributesSeagate
but for Western-Digital:
http://sourceforge.net/apps/trac/smartmontools/wi
On 2012-07-24 13:37, jb wrote:
dweimer dweimer.net> writes:
...
ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328
ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request)
LBA=837397120
...
There is a story about it:
http://linux-bsd-sharing.blogspot.com/2009/03/howto-fix
On 2012-07-24 13:04, Dan Nelson wrote:
In the last episode (Jul 24), dweimer said:
I have three 1TB disks I use for backup, two of them are Western
Digital
drives I bought specifically for this purpose. One is a Seagate
drive
that came out of a barebones PC that I replaced with a couple
small
On 2012-07-24 12:50, Wojciech Puchar wrote:
Just curious, I am sure the likely issue is a bad disk, but I
thought there
actually not that likely.
i had such problems, occurring randomly on many drives, and all
problems disappeared after changing computer, with the same disk.
BTW i would recom
dweimer dweimer.net> writes:
> ...
> ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=817755328
> ad4: WARNING - WRITE_DMA48 UDMA ICRC error (retrying request)
> LBA=837397120
> ...
There is a story about it:
http://linux-bsd-sharing.blogspot.com/2009/03/howto-fix-sata-dma-timeout-issue
In the last episode (Jul 24), dweimer said:
> I have three 1TB disks I use for backup, two of them are Western Digital
> drives I bought specifically for this purpose. One is a Seagate drive
> that came out of a barebones PC that I replaced with a couple smaller
> drives in a stripe to gain perfor
Just curious, I am sure the likely issue is a bad disk, but I thought there
actually not that likely.
i had such problems, occuring randomly on many drives, and all problems
disappeared after changing computer, with the same disk.
BTW i would recommend you to turn on AHCI driver
ad4: TIMEO
Just curious, I am sure the likely issue is a bad disk, but I thought
there might be a chance this could be caused by possibly by something
else.
I have three 1TB disks I use for backup, two of them are Western
Digital drives I bought specifically for this purpose. One is a Seagate
drive tha
Wojciech Puchar wrote:
ad2: FAILURE - READ_DMA timed out LBA=0
ad2: TIMEOUT - READ_DMA retrying (1 retry left) LBA=1
ad2: TIMEOUT - READ_DMA retrying (0 retries left) LBA=1
The flash drive is detected with 3940272 sectors. Is there a way to
control the LBA= parameter? Does it matter if I try?
ad2: FAILURE - READ_DMA timed out LBA=0
ad2: TIMEOUT - READ_DMA retrying (1 retry left) LBA=1
ad2: TIMEOUT - READ_DMA retrying (0 retries left) LBA=1
The flash drive is detected with 3940272 sectors. Is there a way to control
the LBA= parameter? Does it matter if I try?
no.
How can I contr
I am working on installing 6.4-RELEASE on a Motorola CPN5360 which is an
industrial CompactPCI computer. The system boots via PXE. That much is
good. The host has two storage devices.
This is a 16MB boot flash device that is soldered to the board.
ad0: FAILURE - SETFEATURES SET TRANSFER MOD
Julien Cigar wrote:
Same problems for me with atapi CD/DVD drives (READ_BIG timeouts,
etc) .. it works a bit better when dma is turned off, but then
performances are very poor.
On Thu, 2008-08-07 at 14:17 -1000, Al Plant wrote:
N.J. Thomas wrote:
* "Snorre D. ?verb?" <[EMAIL PROTECTED]> [2008-
Same problems for me with atapi CD/DVD drives (READ_BIG timeouts,
etc) .. it works a bit better when dma is turned off, but then
performances are very poor.
On Thu, 2008-08-07 at 14:17 -1000, Al Plant wrote:
> N.J. Thomas wrote:
> > * "Snorre D. ?verb?" <[EMAIL PROTECTED]> [2008-08-07 15:29:11+000
N.J. Thomas wrote:
* "Snorre D. ?verb?" <[EMAIL PROTECTED]> [2008-08-07 15:29:11+]:
When I boot up with the installation DVD these error messages appear
on the screen.
ad1: FAILURE - READ_DMA status=51 error=84
LBA=0055347
ad0: FAILURE - READ_DMA status=51 error=84 LBA=0
etc
I got the sa
* "Snorre D. ?verb?" <[EMAIL PROTECTED]> [2008-08-07 15:29:11+]:
> When I boot up with the installation DVD these error messages appear
> on the screen.
>
> ad1: FAILURE - READ_DMA status=51 error=84
> LBA=0055347
> ad0: FAILURE - READ_DMA status=51 error=84
> LBA=0
> etc
I got the same exa
Snorre D. Øverbø wrote:
Hi all,
I'm trying to install FreeBSD 7.0 release on a box at home.
When I boot up with the installation DVD these error messages appear on
the screen.
[Written down by hand:]
ad1: FAILURE - READ_DMA status=51
error=84 LBA=0055347
ad0: FAILURE - READ_DMA status=51
error
Snorre D. Øverbø wrote:
Hi all,
I'm trying to install FreeBSD 7.0 release on a box at home.
When I boot up with the installation DVD these error messages appear on
the screen.
[Written down by hand:]
ad1: FAILURE - READ_DMA status=51
error=84 LBA=0055347
ad0: FAILURE - READ_DMA status=51
error
Hi all,
I'm trying to install FreeBSD 7.0 release on a box at home.
When I boot up with the installation DVD these error messages appear on
the screen.
[Written down by hand:]
ad1: FAILURE - READ_DMA status=51
error=84 LBA=0055347
ad0: FAILURE - READ_DMA status=51
error=84 LBA=0
etc
etc
...
bsd-questions@freebsd.org
> Subject: RE: Disk errors when copying
>
>
> On Sun, 9 Sep 2007, Ted Mittelstaedt wrote:
>
> >> From: Lars Eighner [mailto:[EMAIL PROTECTED]
>
> >> I wish I'd known that before I trashed my disc and spent a
> couple of weeks
> >&
> > >> ad10: WARNING - READ_DMA48 UDMA ICRC error (retrying request)
> > >> LBA=435128800
> > >> ad10: FAILURE - READ_DMA48 status=51
> > >> error=10 LBA=435128800
> > >> g_vfs_done():ad10s2g[READ(offset=175562145792, length=131072)]error = 5
> One of the rules of thumb when you have hardware prob
On Sun, 9 Sep 2007, Ted Mittelstaedt wrote:
From: Lars Eighner [mailto:[EMAIL PROTECTED]
I wish I'd known that before I trashed my disc and spent a couple of weeks
and hundreds of bucks building a new system.
One of the rules of thumb when you have hardware problems with a new
system (I'm
> -Original Message-
> From: Lars Eighner [mailto:[EMAIL PROTECTED]
> Sent: Sunday, September 09, 2007 11:17 AM
> To: Ted Mittelstaedt
> Cc: Richard Tobin; freebsd-questions@freebsd.org
> Subject: RE: Disk errors when copying
>
>
> On Fri, 7 Sep 2
On Fri, 7 Sep 2007, Ted Mittelstaedt wrote:
Subject: Disk errors when copying
When copy between disks (ad10 ->ad8), I get errors:
ad10: WARNING - READ_DMA48 UDMA ICRC error (retrying request)
LBA=435128800
ad10: FAILURE - READ_DMA48 status=51
error=10 LBA=435128800
g_vfs_done():ad10
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Richard Tobin
> Sent: Wednesday, September 05, 2007 3:03 PM
> To: freebsd-questions@freebsd.org
> Subject: Disk errors when copying
>
>
> When copy between disks (ad10 ->
Richard Tobin wrote:
When copy between disks (ad10 ->ad8), I get errors:
ad10: WARNING - READ_DMA48 UDMA ICRC error (retrying request) LBA=435128800
ad10: FAILURE - READ_DMA48 status=51 error=10
LBA=435128800
g_vfs_done():ad10s2g[READ(offset=175562145792, length=131072)]error = 5
I don't get t
When copy between disks (ad10 ->ad8), I get errors:
ad10: WARNING - READ_DMA48 UDMA ICRC error (retrying request) LBA=435128800
ad10: FAILURE - READ_DMA48 status=51 error=10
LBA=435128800
g_vfs_done():ad10s2g[READ(offset=175562145792, length=131072)]error = 5
I don't get these errors just readin
On 11/22/2005 6:18 PM Nicolas Blais wrote:
On November 22, 2005 09:05 pm, Drew Tomlinson wrote:
I have an old machine running 4.11. It died sometime last night from
what I think was a disk problem. The machine was still running and
still passing packets (it is my firewall) but I could not
Try smartmontools: http://www.freshports.org/sysutils/smartmontools/
If you have IBM Deskstars see if there is newer firmware available.
On 11/23/05, Drew Tomlinson <[EMAIL PROTECTED]> wrote:
> I have an old machine running 4.11. It died sometime last night from
> what I think was a disk problem
On November 22, 2005 09:05 pm, Drew Tomlinson wrote:
> I have an old machine running 4.11. It died sometime last night from
> what I think was a disk problem. The machine was still running and
> still passing packets (it is my firewall) but I could not log in via the
> console, ssh, or telnet. I
I have an old machine running 4.11. It died sometime last night from
what I think was a disk problem. The machine was still running and
still passing packets (it is my firewall) but I could not log in via the
console, ssh, or telnet. I powered the machine off/on and heard the
"click of death
On Friday 7 October 2005 01:55, RYAN vAN GINNEKEN wrote:
> My freebsd 4.11 system has been subjected to a power failure and seems
> to have many disk errors something about soft updates and not being able
> to read certain sectors it comes up with the standard single user pick
> your s
At 06:55 PM 10/6/2005, RYAN vAN GINNEKEN wrote:
My freebsd 4.11 system has been subjected to a power failure and
seems to have many disk errors something about soft updates and not
being able to read certain sectors it comes up with the standard
single user pick your shell command and tells me
My freebsd 4.11 system has been subjected to a power failure and seems
to have many disk errors something about soft updates and not being able
to read certain sectors it comes up with the standard single user pick
your shell command and tells me to run fsck manually. I have run it
several
On Mon, 2005-10-03 at 13:48, Joe S wrote:
> Mike Jeays wrote:
> > I am getting one or two of these a day on a Western Digital 80GB disk
>
> Most drive manufacturers provide diagnostic tools for the drives they
> produce. In this case, Western Digital provides a bootable diagnostic tool:
>
> * Da
Mike Jeays wrote:
I am getting one or two of these a day on a Western Digital 80GB disk
Most drive manufacturers provide diagnostic tools for the drives they
produce. In this case, Western Digital provides a bootable diagnostic tool:
* Data Lifeguard Diagnostic for DOS (CD)
http://support.
On Fri, 30 Sep 2005 20:08:15 -0400, Mike Jeays <[EMAIL PROTECTED]>
Subject: Re: Disk errors
Wrote these words of wisdom:
> On Fri, 2005-09-30 at 16:48, Gerard Seibert wrote:
> > On Fri, 30 Sep 2005 16:31:58 -0400, Mike Jeays <[EMAIL PROTECTED]>
> > Subject: Disk erro
Mike Jeays wrote:
On Fri, 2005-09-30 at 16:48, Gerard Seibert wrote:
On Fri, 30 Sep 2005 16:31:58 -0400, Mike Jeays <[EMAIL PROTECTED]>
Subject: Disk errors
Wrote these words of wisdom:
I am getting one or two of these a day on a Western Digital 80GB disk
How concerned should I be
On Fri, 2005-09-30 at 16:48, Gerard Seibert wrote:
> On Fri, 30 Sep 2005 16:31:58 -0400, Mike Jeays <[EMAIL PROTECTED]>
> Subject: Disk errors
> Wrote these words of wisdom:
>
> > I am getting one or two of these a day on a Western Digital 80GB disk
> > How conce
On Fri, 30 Sep 2005 16:31:58 -0400, Mike Jeays <[EMAIL PROTECTED]>
Subject: Disk errors
Wrote these words of wisdom:
> I am getting one or two of these a day on a Western Digital 80GB disk
> How concerned should I be? The machine seems reliable otherwise.
>
> ad0: WARNING -
I am getting one or two of these a day on a Western Digital 80GB disk
How concerned should I be? The machine seems reliable otherwise.
ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=61092255
ad0: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=61314367
ad0: WARNING - REA
Jim Hatfield <[EMAIL PROTECTED]> writes:
> Strictly speaking OT but the machine is running FreeBSD.
>
> While copying a file I got I/O errors. The console shows:
>
> >ad0: hard error cmd=read fsbn 31891359 of 31891359-31891486 status=59 error=40
> >ad0: hard error cmd=read fsbn 31891231 of 31891
Strictly speaking OT but the machine is running FreeBSD.
While copying a file I got I/O errors. The console shows:
>ad0: hard error cmd=read fsbn 31891359 of 31891359-31891486 status=59 error=40
>ad0: hard error cmd=read fsbn 31891231 of 31891231-31891486 status=59 error=40
Given that the disk i
ttempt has hung trying to access the disk for more than 20 seconds. It might
>be caused by bad blocks on the disk drive, disk wiring, cables, or any other
>disk I/O-related hardware. If the drive itself is actually bad, you will also
>see disk errors in /var/log/messages and in the outp
48 matches
Mail list logo
