Mark Kane wrote:
I do have a tall Antec case, and have both 200's and the 160 in 5 1/4
inch trays so the cables for those are long (36 inches IIRC). Would it
be OK to have that setup, or would it be better to isolate them all on
their own cables/channels and get a Promise card or something
Mark Kirkwood wrote:
Mark Kane wrote:
I do have a tall Antec case, and have both 200's and the 160 in 5 1/4
inch trays so the cables for those are long (36 inches IIRC).
Hmm - 36 inch cable, makes me wonder if that is what is causing the
problem in UDMA133 mode. IIRC the ATA spec says 18
Mark Kane wrote:
I'm glad that it looks like running it at 100 will solve this. Thanks
for the replies. I was probably going to go through all the hassle of
getting an Asus board to replace this because I was almost certain it
was hardware, but I don't think it's worth it as long as this works
I've been having similar problems on 5.4-RELEASE. I have a brand new
board back from the factory (a RMA) and had a thread going on
freebsd-questions about this.
I currently have six Maxtor 7200RPM ATA133 hard drives that I've been
trying on and off and with various configurations in my
At 12:10 PM 16/08/2005, Mark Kane wrote:
However, note that if I turn the drives speed down to UDMA100, the
errors seem to go away. Has anyone else tried this for their problems?
Yes, I have had Maxtor drives in the past where they would not work
properly at certain bus speeds-- even back in
Mark Kane wrote:
However, note that if I turn the drives speed down to UDMA100, the
errors seem to go away. Has anyone else tried this for their problems?
I currently do this, not due to problems, but to improve the write
performance:
4xMaxtor 6E040L0 RAID0
UDMA133 - 40M/s
UDMA100 -
Mike Tancsa wrote:
Yes, I have had Maxtor drives in the past where they would not work
properly at certain bus speeds-- even back in the RELENG_4 days. Also,
doesnt UDMA133 assume no slave ?
I would just run them at 100. I dont think you would see much of a
difference anyways. Perhaps
Mark Kane wrote:
I do have a tall Antec case, and have both 200's and the 160 in 5 1/4
inch trays so the cables for those are long (36 inches IIRC).
Hmm - 36 inch cable, makes me wonder if that is what is causing the
problem in UDMA133 mode. IIRC the ATA spec says 18 inches, but most
cables
---BeginMessage---
Joel Rees wrote:
I have two which reliably fail if you put TWO disks on them in a
gmirror
config within minutes of starting a make buildworld.
Pardon the interruption, but is this two drives on one channel?
Two drives can not be on one channel on SATA controller.
Maxim M. Kazachek wrote:
SoftModems works (well, almost) perfectly under Windows. Some of these
works under Linux. SoftModems is the best, because they are cheap and
works under Windows. The FreeBSD is puny OS just because they lack
support of Software modem.
The thing is as worth as much you
I have two controllers here that are from different
manufacturers and both exhibit the same problem. The SAME
disks (two different manufacturers - hitachi and maxtor) on a
motherboard ICH5 adapter work perfectly, smartmontools says
all 4 (I have two examples of each) are healthy, and
On Thu, Aug 11, 2005 at 03:44:52PM -0700, Vinod Kashyap wrote:
I have two controllers here that are from different
manufacturers and both exhibit the same problem. The SAME
disks (two different manufacturers - hitachi and maxtor) on a
motherboard ICH5 adapter work perfectly,
Chuck Swiger wrote:
O. Hartmann wrote:
[ ... ]
One of my SATA disks, the SAMSUNG SP2004C seems to show errors
during operation (and also showd under 5.4-RELEASE-p3).
Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still
On 平成 17/08/10, at 7:36, O. Hartmann wrote:
[...] When is SCSI back for desktops?
I vote for that.
In my opinion, ATA is primarily for home media systems, if that.
Joel Rees [EMAIL PROTECTED]
digitcom, inc. 株式会社デジコム
Kobe, Japan +81-78-672-8800
** http://www.ddcom.co.jp **
Matthias Buelow wrote:
Karl Denninger wrote:
SII chipsets were ok in 4.x, but the newer ATA code broke badly with them.
I've had a PR open on this since February, and many others have reported
similar issues. The problems still exist in the 6.x-BETA releases I've
checked out, and are in
O. Hartmann wrote:
Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still keeps working.
Check your disks with MHDD (http://mhdd.com/).
--
WBR, Andrey V. Elsukov
___
freebsd
Joel Rees wrote:
On 平成 17/08/10, at 7:36, O. Hartmann wrote:
[...] When is SCSI back for desktops?
I vote for that.
In my opinion, ATA is primarily for home media systems, if that.
Joel Rees [EMAIL PROTECTED]
digitcom, inc. 株式会社デジコム
Kobe, Japan +81-78-672-8800
**
On 8/10/05, Unix [EMAIL PROTECTED] wrote:
...
I thought the WD Raptors were supposed to replace the SCSI for that
purpose. I used to run one in a Powermac and performance wise it behaved
very well, unfortunately I haven't had the chance to test the 30 or 70
GB WD Raptor SATA in FreeBSD..S/ATA
Dmitry Mityugov wrote:
On 8/10/05, Unix [EMAIL PROTECTED] wrote:
...
I thought the WD Raptors were supposed to replace the SCSI for that
purpose. I used to run one in a Powermac and performance wise it behaved
very well, unfortunately I haven't had the chance to test the 30 or 70
GB WD
On 8/10/05, Unix [EMAIL PROTECTED] wrote:
Dmitry Mityugov wrote:
On 8/10/05, Unix [EMAIL PROTECTED] wrote:
...
I thought the WD Raptors were supposed to replace the SCSI for that
purpose. I used to run one in a Powermac and performance wise it behaved
very well, unfortunately I haven't
Dmitry Mityugov wrote:
On 8/10/05, Unix [EMAIL PROTECTED] wrote:
Dmitry Mityugov wrote:
On 8/10/05, Unix [EMAIL PROTECTED] wrote:
...
I thought the WD Raptors were supposed to replace the SCSI for that
purpose. I used to run one in a Powermac and performance wise it behaved
On 8/10/05, Unix [EMAIL PROTECTED] wrote:
I thought the WD Raptors were supposed to replace the SCSI for that
purpose. I used to run one in a Powermac and performance wise it behaved
very well, unfortunately I haven't had the chance to test the 30 or 70
GB WD Raptor SATA in FreeBSD..S/ATA drives
On Wed, Aug 10, 2005 at 04:46:18AM +0200, Matthias Buelow wrote:
Karl Denninger wrote:
SII chipsets were ok in 4.x, but the newer ATA code broke badly with them.
I've had a PR open on this since February, and many others have reported
similar issues. The problems still exist in the 6.x-BETA
At 10:46 PM 09/08/2005, Matthias Buelow wrote:
Karl Denninger wrote:
SII chipsets were ok in 4.x, but the newer ATA code broke badly with them.
I've had a PR open on this since February, and many others have reported
similar issues. The problems still exist in the 6.x-BETA releases I've
On Wed, Aug 10, 2005 at 08:15:50AM -0400, Mike Tancsa wrote:
At 10:46 PM 09/08/2005, Matthias Buelow wrote:
Karl Denninger wrote:
SII chipsets were ok in 4.x, but the newer ATA code broke badly with them.
I've had a PR open on this since February, and many others have reported
similar
At 09:31 AM 10/08/2005, Karl Denninger wrote:
Also, I've yet to see a developer commit on the list that they WILL fix it if
such a controller board is forthcoming (and will return the board when
they're
done) - I've got two of these cards here (choose between Adaptec and Bustek)
and would be
On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote:
At 09:31 AM 10/08/2005, Karl Denninger wrote:
Also, I've yet to see a developer commit on the list that they WILL fix it
if
such a controller board is forthcoming (and will return the board when
they're
done) - I've got two of
Mike Tancsa wrote:
At 09:31 AM 10/08/2005, Karl Denninger wrote:
Also, I've yet to see a developer commit on the list that they WILL
fix it if
such a controller board is forthcoming (and will return the board
when they're
done) - I've got two of these cards here (choose between Adaptec and
On 8/10/05, Karl Denninger [EMAIL PROTECTED] wrote:
On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote:
At 09:31 AM 10/08/2005, Karl Denninger wrote:
Also, I've yet to see a developer commit on the list that they WILL fix it
if
such a controller board is forthcoming (and will
Yes, I agree. I don't think anyone wants to blame the entire FreeBSD
community for not being up to date on everything but if it is a known
problem we should know. I know that the developers work for free and I,
for one, appreciate all the work they've done. I know I would help if I
could..but
J. T. Farmer wrote:
Those of us who want to switch desktops and light duty servers
to FreeBSD will give up and move to Linux. OR back to WinXP.
I myself am just waiting for NetBSD 3.0, which will hopefully support
the ICH6 SATA stuff I have here (2.0.2 doesn't support it) and then
I'll move
Matthias Buelow wrote:
J. T. Farmer wrote:
Those of us who want to switch desktops and light duty servers
to FreeBSD will give up and move to Linux. OR back to WinXP.
I myself am just waiting for NetBSD 3.0, which will hopefully support
the ICH6 SATA stuff I have here (2.0.2
On 10/08/2005, at 17:44, Scot Hetzel wrote:
On 8/10/05, Karl Denninger [EMAIL PROTECTED] wrote:
On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote:
At 09:31 AM 10/08/2005, Karl Denninger wrote:
Also, I've yet to see a developer commit on the list that they
WILL fix it
if
such
On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said:
There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.
Right, i have a dead 250GB Maxline Plus II drive on my desk, only after
about 1.5 years. At least its still on warranty.
It's sad isn't it, Mike..I don't know what the hd manufacturers are
doing to the HD drives..ok, the systems get faster, there's usually bad
cooling unless you build your own system...but even if you get enough
cooling that won't change a thing some hds are prone to die an early
death such as
Mike Jakubik wrote:
On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said:
There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.
Right, i have a dead 250GB Maxline Plus II drive on my desk, only after
about 1.5 years. At least its still on
O. Hartmann wrote:
Mike Jakubik wrote:
On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said:
There are Maxtor MaXLine II and III, and perhaps several other models,
that are supposed to work 24/7.
Right, i have a dead 250GB Maxline Plus II drive on my desk, only after
about 1.5 years.
On 8/10/05, Søren Schmidt [EMAIL PROTECTED] wrote:
On 10/08/2005, at 17:44, Scot Hetzel wrote:
On 8/10/05, Karl Denninger [EMAIL PROTECTED] wrote:
On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote:
At 09:31 AM 10/08/2005, Karl Denninger wrote:
Also, I've yet to see a
Scot Hetzel wrote:
On 8/10/05, Søren Schmidt [EMAIL PROTECTED] wrote:
Since I came in late in this, I need to know what kind of controller
we are talking about, and if the problem is still present in 6.0.
I plan to backport ATA from 6.0 to 5-stable when it has settled, so
6.0 is the one
On 10/08/2005, at 20:05, Scot Hetzel wrote:
Since I came in late in this, I need to know what kind of controller
we are talking about, and if the problem is still present in 6.0.
I plan to backport ATA from 6.0 to 5-stable when it has settled, so
6.0 is the one and only (pre)release to test
On 10/08/2005, at 20:29, J. T. Farmer wrote:
Scot Hetzel wrote:
On 8/10/05, Søren Schmidt [EMAIL PROTECTED] wrote:
Since I came in late in this, I need to know what kind of controller
we are talking about, and if the problem is still present in 6.0.
I plan to backport ATA from 6.0 to
On Wed, Aug 10, 2005 at 07:24:01PM +0200, S?ren Schmidt wrote:
On 10/08/2005, at 17:44, Scot Hetzel wrote:
On 8/10/05, Karl Denninger [EMAIL PROTECTED] wrote:
On Wed, Aug 10, 2005 at 09:51:03AM -0400, Mike Tancsa wrote:
At 09:31 AM 10/08/2005, Karl Denninger wrote:
Also, I've yet
On Wed, Aug 10, 2005 at 08:36:39PM +0200, S?ren Schmidt wrote:
On 10/08/2005, at 20:05, Scot Hetzel wrote:
Since I came in late in this, I need to know what kind of controller
we are talking about, and if the problem is still present in 6.0.
I plan to backport ATA from 6.0 to 5-stable when
Am Mittwoch, 10. August 2005 19:48 CEST schrieb Unix:
O. Hartmann wrote:
Mike Jakubik wrote:
On Wed, August 10, 2005 6:37 am, Dmitry Mityugov said:
There are Maxtor MaXLine II and III, and perhaps several other
models, that are supposed to work 24/7.
Right, i have a dead 250GB Maxline
As I said I need reports on 6.0, the ATA driver as is in 5.4 is not
supported by me unless you use the ATA mkIII patches..
you know, we just upgraded a system from 4.11 to 7.0 and see problems.
we have been chasing cables, and never considered that we could blame
all our problems on you and
On 10/08/2005, at 22:51, Karl Denninger wrote:
Since I came in late in this, I need to know what kind of controller
we are talking about, and if the problem is still present in 6.0.
I plan to backport ATA from 6.0 to 5-stable when it has settled, so
6.0 is the one and only (pre)release to test
On 11/08/2005, at 0:28, Randy Bush wrote:
As I said I need reports on 6.0, the ATA driver as is in 5.4 is not
supported by me unless you use the ATA mkIII patches..
you know, we just upgraded a system from 4.11 to 7.0 and see problems.
we have been chasing cables, and never considered that
On Thu, Aug 11, 2005 at 12:46:04AM +0200, S?ren Schmidt wrote:
On 10/08/2005, at 22:51, Karl Denninger wrote:
This is the subject of the PR I filed back in February.
Again, if you want either a controller shipped to you OR access to a
development machine (e.g. ssh in and play) which has
Karl Denninger wrote:
On Thu, Aug 11, 2005 at 12:46:04AM +0200, S?ren Schmidt wrote:
[ ... ]
I've already gone WAY out of my way to try to support the sii3112,
and I'm not inclined to waste more of my precious spare time on it.
However, if it really is that important to enough people to try
On Wed, Aug 10, 2005 at 09:47:38PM -0400, Chuck Swiger wrote:
Karl Denninger wrote:
On Thu, Aug 11, 2005 at 12:46:04AM +0200, S?ren Schmidt wrote:
[ ... ]
I've already gone WAY out of my way to try to support the sii3112,
and I'm not inclined to waste more of my precious spare time on it.
Chuck Swiger wrote:
Karl Denninger wrote:
On Thu, Aug 11, 2005 at 12:46:04AM +0200, S?ren Schmidt wrote:
[ ... ]
I've already gone WAY out of my way to try to support the sii3112,
and I'm not inclined to waste more of my precious spare time on it.
However, if it really is that
Karl Denninger wrote:
From the online man page for ata.4, which is EXPLICITLY referenced as THE
authoritative list of which disk controllers it supports:
The currently supported ATA/SATA controller chips are:
Acard: ATP850P, ATP860A, ATP860R, ATP865A, ATP865R
ALI:
I have two which reliably fail if you put TWO disks on them in a
gmirror
config within minutes of starting a make buildworld.
Pardon the interruption, but is this two drives on one channel?
___
freebsd-stable@freebsd.org mailing list
SoftModems works (well, almost) perfectly under Windows. Some of these
works under Linux. SoftModems is the best, because they are cheap and
works under Windows. The FreeBSD is puny OS just because they lack support
of Software modem.
The thing is as worth as much you paid for it. If Silicon
get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still keeps working.
Other days the box crashes completely.
Is this a operating system bug or is this message an evidence of
defective hardware?
You can probably confirm a hardware issue
O. Hartmann wrote:
[ ... ]
One of my SATA disks, the SAMSUNG SP2004C seems to show errors during
operation (and also showd under 5.4-RELEASE-p3).
Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still keeps working.
Other
Chuck Swiger wrote:
O. Hartmann wrote:
[ ... ]
One of my SATA disks, the SAMSUNG SP2004C seems to show errors
during operation (and also showd under 5.4-RELEASE-p3).
Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still
disks, the SAMSUNG SP2004C seems to show errors
during operation (and also showd under 5.4-RELEASE-p3).
Sometimes I get this error:
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still keeps working.
Other days the box crashes completely
Karl Denninger wrote:
SII chipsets were ok in 4.x, but the newer ATA code broke badly with them.
I've had a PR open on this since February, and many others have reported
similar issues. The problems still exist in the 6.x-BETA releases I've
checked out, and are in some cases MORE severe (for me
[2295104 x 2048 byte records]
GEOM_LABEL: Label for provider acd0 is iso9660/CDROM.
Trying to mount root from ufs:/dev/ad8s1a
pflog0: promiscuous mode enabled
WARNING pid 525 (nasd): ioctl sign-extension ioctl c0106924
ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
while the machine still keeps working.
Other days the box crashes completely.
Is this a operating system bug or is this message an evidence of defective
hardware?
You can probably confirm a hardware issue with the smartmon
tools
61 matches
Mail list logo