(b) Cabling troubles are purely down to the build quality achieved
by your supplier. Generally with SATA cables what seems to work
best is to use cables that are as short as possible given that the
cables should have at least an inch of slack in them, and also the
cables should neither be straine
I was getting the following error flooding my dmesg:
ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=*
so they replaced all the hardware in the box. Still, with entirely different
hardware, I am getting the same error:
ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=1068482
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Matt Juszczak wrote:
> Hi all,
>
> My dedicated server company is deploying me a new FreeBSD 6.2 server.
> The box uses SATA drives, and is an AMD Athlon box.
>
> I was getting the following error flooding my dmesg:
>
> ad4: TIMEOUT - WRITE_DMA r
Hi all,
My dedicated server company is deploying me a new FreeBSD 6.2 server. The
box uses SATA drives, and is an AMD Athlon box.
I was getting the following error flooding my dmesg:
ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=*
so they replaced all the hardware in the box.
