Garance A Drosihn writes:
> First question: which SATA controller are you using?
The controller is built into the Asus P4P800-E motherboard, and is
based on the Intel ICH5R southbridge chipset. There's also a Promise
20378 RAID controller on board but I do NOT use it (disabled in BIOS).
> And w
Ted Mittelstaedt writes:
> Rule of thumb on IDE hard drives, if they show more than a few errors
> with a tool like smartmon, they need to be thrown in the garbage.
Seems prudent to me, but right now I don't have the budget to replace
this drive (yes, 40 GB IDE drives are cheap, but I don't have
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Anthony
> Atkielski
> Sent: Sunday, February 27, 2005 2:10 PM
> To: freebsd-questions@freebsd.org
> Subject: Re: WRITE_DMA errors on SATA drive under 5.3-RELEASE
>
>
> Mike
At 3:53 PM +0100 2/27/05, Anthony Atkielski wrote:
I've gotten two messages like the ones below today on my
production server (5.3-RELEASE):
... kernel: ad10: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=4848803
... kernel: ad10: FAILURE - WRITE_DMA timed out
What do these messages mean? The
On Sun, 27 Feb 2005 23:09:50 +0100, in sentex.lists.freebsd.questions
you wrote:
>Mike Tancsa writes:
>
>> Could be a bad sector on the drive, or bad cable. Hard to say. Try
>> /usr/ports/sysutils/smartmontools/
>>
>> It can read all sorts of info off the drive and help you narrow down
>> what th
Mike Tancsa writes:
> Could be a bad sector on the drive, or bad cable. Hard to say. Try
> /usr/ports/sysutils/smartmontools/
>
> It can read all sorts of info off the drive and help you narrow down
> what the problem might be.
Wow! That is a very cool tool. There's even a Windows port so I ca
[EMAIL PROTECTED] writes:
> Actually, it's not that hard. You need three mappings:
>
> 1. (lba address, (filesystem, block #))
> 2. ((filesystem, block #), (filesystem, inode #))
> 3. ((filesystem, inode #), (list of filenames linking to inode #))
Seems like it would be straightforward with adequ
On Sun, 27 Feb 2005 15:53:30 +0100, in sentex.lists.freebsd.questions
you wrote:
>I've gotten two messages like the ones below today on my production server
>(5.3-RELEASE):
>
>messages:Feb 27 14:48:17 freebie kernel: ad10: TIMEOUT - WRITE_DMA retrying (2
>retries left) LBA=4848803
>messages:Feb 2
On Sun, Feb 27, 2005 at 05:19:32PM +0100, Anthony Atkielski wrote:
> [EMAIL PROTECTED] writes:
>
> > Theoretically, one could use 'fsdb -r' in a scripted manner, to
> > generate a mapping of file names to blocks (relative to the partition
> > of the file system you are mapping). Once you have the
[EMAIL PROTECTED] writes:
> Theoretically, one could use 'fsdb -r' in a scripted manner, to
> generate a mapping of file names to blocks (relative to the partition
> of the file system you are mapping). Once you have the blocks, you'll
> need to do so artithmetics to map those blocks to LBA addres
On Sun, Feb 27, 2005 at 03:53:30PM +0100, Anthony Atkielski wrote:
> messages:Feb 27 14:48:17 freebie kernel: ad10: TIMEOUT - WRITE_DMA retrying
> (2 retries left) LBA=4848803
> messages:Feb 27 14:48:17 freebie kernel: ad10: FAILURE - WRITE_DMA timed out
[...]
> Is there a way to work backwards
I've gotten two messages like the ones below today on my production server
(5.3-RELEASE):
messages:Feb 27 14:48:17 freebie kernel: ad10: TIMEOUT - WRITE_DMA retrying (2
retries left) LBA=4848803
messages:Feb 27 14:48:17 freebie kernel: ad10: FAILURE - WRITE_DMA timed out
What do these messages m
12 matches
Mail list logo
