On 8th October, Mikhail P. [EMAIL PROTECTED] reported the error:
ad0: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=10NID_NOT_FOUND
LBA=268435455
On Sun, 10 Oct 2004, Søren Schmidt wrote:
so that leaves the disks for scrutiny. One thing to try is change the
tripping point where we
This sounds very possible to me. I have been experiencing the same
error, on a system that I've been trying to set up using 5.3-RC1 and
a new 160Gbyte SATA drives My hardware is:
atapci0: SiI 3112 SATA150 controller port
0xb000-0xb00f,0xac00-0xac03,0xa800-0xa807,0xa400-0xa403,0xa000-0xa007
On Friday 29 October 2004 16:44, [EMAIL PROTECTED] wrote:
The same problem with similar IDE Seagate HDD:
ad0: ST3160023A/3.06 ATA-6 disk at ata0-master
ad0: 152627MB (312581808 sectors), 310101 C, 16 H, 63 S, 512 B
[...]
ad0: FAILURE - READ_DMA status=51READY,DSC,ERROR error=10NID_NOT_FOUND
On Friday 29 October 2004 16:50, Mikhail P. wrote:
Perhaps it is only Seagate - FreeBSD5-related. Same drives, but with
FreeBSD4 do work well together without a glitch.
Actually not only seagates.. similar happened on a 200GB Western Digital drive
to me, FreeBSD-5.3.
regards,
M.
On Fri, 29 Oct 2004, Mikhail P. wrote:
On Friday 29 October 2004 16:50, Mikhail P. wrote:
Perhaps it is only Seagate - FreeBSD5-related. Same drives, but with
FreeBSD4 do work well together without a glitch.
Actually not only seagates.. similar happened on a 200GB Western Digital drive
to
Add Western Digital Raptors to the list as well. However I have not
had a problem since 5.3-BETA3.
aaron.glenn
On Fri, 29 Oct 2004 16:57:33 +, Mikhail P. [EMAIL PROTECTED] wrote:
On Friday 29 October 2004 16:50, Mikhail P. wrote:
Perhaps it is only Seagate - FreeBSD5-related. Same drives,
On Sunday 10 October 2004 08:59, Søren Schmidt wrote:
There is definitly something fishy here, since I dont have either the
disks nor any VIA chips here in the lab I cannot do any testing here.
However I dont know of any problems with the VIA chips in this regard,
so that leaves the disks for
Martin Nilsson wrote / skrev:
Something is rotten with ATA on 5.x (or I have a rotten motherboard!)
I have an E7320 Lindenhurst VS 6300ESB box with 2*3GHz EM64T Xeons and
2*80GB Seagate SATA disks. Sometimes when booting the whole ATA/SATA
system hangs after two READ_DMA or WRITE_DMA timeout
On Thursday 14 October 2004 19:59, Martin Nilsson wrote:
I really don't know what to with this box, maybe put regular ATA or SCSI
disks in it?
Well, there are no problems with SCSI to my knowledge 5.3 and 5.2.1 work well
on my SCSI servers.. only the ATA driver..
Would be sad to still have
On Sunday 10 October 2004 23:30, Mikhail P. wrote:
On Saturday 09 October 2004 17:01, Mikhail P. wrote:
I also got another message off-list, where author suggested to play with
UDMA values. I switched from UDMA100 to UDMA66. System's uptime is 12
hours, and no timeouts so far.. but I'm
Mikhail P. wrote:
On Sunday 10 October 2004 23:30, Mikhail P. wrote:
On Saturday 09 October 2004 17:01, Mikhail P. wrote:
I also got another message off-list, where author suggested to play with
UDMA values. I switched from UDMA100 to UDMA66. System's uptime is 12
hours, and no timeouts so far..
Mikhail P. wrote:
Well, now those timeouts popped up on 5.3-BETA7 system with 4 IDE drives..
They start appearing with high disk activity.
System had FreeBSD-4.7 prior to that, and has been rock solid for almost a
year. Drives have no problems, that's for sure (4.7 did not show up any
timeouts,
On Wednesday 13 October 2004 13:51, Søren Schmidt wrote:
Well, thats not up to me to judge I guess, but have you tried to change
the tripping point for using 48Bit addressing as I suggested earlier ?
How one would do it? In BIOS?
Forgive my ignorance.
I cant reproduce this problem with any of
I used to get that error prior to 5.3-BETA3 (5.2.1-RELEASE, and all
previous 5.3-BETA's). Randomly after reboot the machine would spew
about 100 of these and then hardlock. I've got two identical boxes
running BETA3 and BETA7 without any issues. Intel 6300ESB controller
and Western Digital
On Saturday 09 October 2004 17:01, Mikhail P. wrote:
I also got another message off-list, where author suggested to play with
UDMA values. I switched from UDMA100 to UDMA66. System's uptime is 12
hours, and no timeouts so far.. but I'm quite sure they will get back in
few days.
1.5 days of
Mikhail P. [EMAIL PROTECTED] writes:
I reloaded OS on the new drives, then restored all data from the old drives.
All seemed to be fine for 2 months now... but today I woke up, and noticed
these messages again.
A lot of them, or just one or two? Some ATA drives will spin down at
regular
On Saturday 09 October 2004 15:01, Dag-Erling Smørgrav wrote:
Mikhail P. [EMAIL PROTECTED] writes:
I reloaded OS on the new drives, then restored all data from the old
drives. All seemed to be fine for 2 months now... but today I woke up,
and noticed these messages again.
A lot of them,
On Sat, 9 Oct 2004, Mikhail P. wrote:
MP I reloaded OS on the new drives, then restored all data from the old
MP drives. All seemed to be fine for 2 months now... but today I woke up,
MP and noticed these messages again.
MP
MP A lot of them, or just one or two? Some ATA drives will spin
Mikhail P. [EMAIL PROTECTED] writes:
On Saturday 09 October 2004 15:01, Dag-Erling Smørgrav wrote:
A lot of them, or just one or two? Some ATA drives will spin down at
regular intervals to recalibrate, and you'll get a harmless timeout if
you try to write to the disk while it's doing that.
On Saturday 09 October 2004 16:23, Dag-Erling Smørgrav wrote:
Mikhail P. [EMAIL PROTECTED] writes:
On Saturday 09 October 2004 15:01, Dag-Erling Smørgrav wrote:
A lot of them, or just one or two? Some ATA drives will spin down at
regular intervals to recalibrate, and you'll get a
about 3 months ago my
logs quickly filled up with:
ad0: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=10NID_NOT_FOUND
LBA=268435455
Hmm, that means that the drive couldn't find the sector you asked for.
Now, what has me wondering is that it is the exact sector where we
switch to 48bit
On Saturday 09 October 2004 18:26, Søren Schmidt wrote:
Hmm, that means that the drive couldn't find the sector you asked for.
Now, what has me wondering is that it is the exact sector where we
switch to 48bit adressing mode. Anyhow, I've just checked on the old
Maxtor preproduktion 48bit
Mikhail P. [EMAIL PROTECTED] writes:
Well, there is no pattern. [...]
Could be bad cables, could be bad drives. Environmental factors are a
more likely cause, though. Are all the failing disks in the same
machine? If they're in separate machines, are those rack-mount, or
are they standing on
On Saturday 09 October 2004 20:53, Dag-Erling Smørgrav wrote:
Mikhail P. [EMAIL PROTECTED] writes:
Well, there is no pattern. [...]
Could be bad cables, could be bad drives. Environmental factors are a
more likely cause, though. Are all the failing disks in the same
machine? If they're
ago my
logs quickly filled up with:
ad0: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=10NID_NOT_FOUND
LBA=268435455
Server was still running, but I was unable to write to certain files/folders
on the drive - whenever I tried to access $HOME/.fetchmailrc, for example, it
wouldn't read/write
25 matches
Mail list logo
