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.
On Friday 29 October 2004 16:44, [EMAIL PROTECTED] wrote:
> The same problem with similar IDE Seagate HDD:
>
> ad0: ATA-6 disk at ata0-master
> ad0: 152627MB (312581808 sectors), 310101 C, 16 H, 63 S, 512 B
> [...]
> ad0: FAILURE - READ_DMA status=51 error=10
> LBA=268435455
Perhaps it is only Se
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 f
Hello,
On our next file server, I want to make one large FTP area out of 4 drives (so
that system sees them as one volume). Vinum appears to be exactly what I
need.
I haven't worked with Vinum previously, but hear a lot about it. My question
is how to implement the above (unite four drives int
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 th
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
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, an
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
&g
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 f
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 r
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
> > > r
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,
> > an
Hi,
This question probably has been discussed numerous times, but I'm somewhat
unsure what really causes ATA failures..
I have pretty basic server here which has two IDE drives - each is 200GB.
System is FreeBSD-5.2.1-p9
That server has been setup about 9 months ago, and just about 3 months ago
13 matches
Mail list logo
