t;[EMAIL PROTECTED]>
Sent: Thursday, September 25, 2003 09:32
Subject: Re: SATA drive lock-up
It seems Derek Ragona wrote:
> Søren,
>
> My setup is as follows:
> Maxtor 6Y120MO 120GB SATA drive
> Adaptec Serial ATA RAID 1210SA
> Intel® Desktop Board D845GEBV2
> 1GB RAM
> 1.
It seems Derek Ragona wrote:
> Søren,
>
> My setup is as follows:
> Maxtor 6Y120MO 120GB SATA drive
> Adaptec Serial ATA RAID 1210SA
> Intel® Desktop Board D845GEBV2
> 1GB RAM
> 1.7 GHz Celeron CPU
Ok, I'll try to get something semialr setup here and try to reproduce.
> If there is some way to g
Søren,
My setup is as follows:
Maxtor 6Y120MO 120GB SATA drive
Adaptec Serial ATA RAID 1210SA
Intel® Desktop Board D845GEBV2
1GB RAM
1.7 GHz Celeron CPU
The motherboard has the latest P17 BIOS.
The system has a teac 52x CD-ROM as the Master ATA device on the
motherboards primary IDE controller.
It seems Putinas wrote:
> Hi all,
> Inspired with all the FreeBSD is free software , windows and buggy hardware
> and blabla I realize what maybe I could do more to help solve this problem.
> I made small research on my computer and I find out what till the cvsup date
> 2003.08.24.00.00.00 till ATA
il 25 August
Best regards,
Putinas
- Original Message -
From: "Soren Schmidt" <[EMAIL PROTECTED]>
To: "Derek Ragona" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, September 20, 2003 10:07
Subject: Re: SATA drive lock-up
> It seem
I don't want to get into some flame war here. I am trying to provide what
information I can. If Soren, or anyone else wants more debugging
information I will be happy to do what I can to provide that
information. I simply need them to tell me what and how to capture the
information. As the
On Mon, 2003-09-22 at 06:54, Derek Ragona wrote:
> I couldn't make a kernel with 9/19 cvsuped. I downloaded and installed the
> 9/20 snapshot. That also wouldn't complete a buildworld without breaking
> with the hard drive error.
>
> I booted windows and stress tested the drive with all kinds
I couldn't make a kernel with 9/19 cvsuped. I downloaded and installed the
9/20 snapshot. That also wouldn't complete a buildworld without breaking
with the hard drive error.
I booted windows and stress tested the drive with all kinds of I/O. Not a
hiccup.
It isn't the hardware, it has to b
The system died in buildworld, this time it fell into the debugger.
spec_getpages(ad4s1d) I/O read failure (error=5)
-Derek
At 02:53 PM 9/20/2003 -0500, Derek Ragona wrote:
The 9/19 snapshot has the same issues.
I will try to cvsup it and build a new kernel, if I can.
-Derek
A
The 9/19 snapshot has the same issues.
I will try to cvsup it and build a new kernel, if I can.
-Derek
At 05:36 AM 9/20/2003 -0500, Derek Ragona wrote:
This was using the 9/18 snapshot, I tried to cvsup it to the most current,
but the drive errors prevent the update.
I just reloaded wi
This was using the 9/18 snapshot, I tried to cvsup it to the most current,
but the drive errors prevent the update.
I just reloaded with the 9/19 snapshot, and will report if the error still
exists.
As for the hardware, it is all brand new hardware, and the system dual
boots, the other OS has
na" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, September 20, 2003 10:07 AM
Subject: Re: SATA drive lock-up
It seems Derek Ragona wrote:
> I have a single SATA drive on an Adaptec 1210SA card.
>
> The drive will give a write error warning a few time
It seems Derek Ragona wrote:
> I have a single SATA drive on an Adaptec 1210SA card.
>
> The drive will give a write error warning a few times, then will repeatedly
> give:
> ad4: timeout sending command=ca
>
> The only recovery is the reset switch, reboot single-user fsck, and then
> come back
I have a single SATA drive on an Adaptec 1210SA card.
The drive will give a write error warning a few times, then will repeatedly
give:
ad4: timeout sending command=ca
The only recovery is the reset switch, reboot single-user fsck, and then
come back up in multiuser.
These errors occur with di
14 matches
Mail list logo
