Date: Sat, 20 Sep 2003 14:53:51 -0500 From: Derek Ragona <derek@computinginnovations.com> To: Soren Schmidt <sos@spider.deepcore.dk> Cc: freebsd-current@freebsd.org Subject: Re: SATA drive lock-up Message-ID: <5.2.1.1.2.20030920145252.0132be50@www.computinginnovations.com> In-Reply-To: <5.2.1.1.2.20030920053435.012510b8@www.computinginnovations .com> References: <200309200807.h8K87j38049734@spider.deepcore.dk> <5.2.1.1.2.20030919151835.01308600@www.computinginnovations.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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,=
=20
>but the drive errors prevent the update.
>
>I just reloaded with the 9/19 snapshot, and will report if the error still=
=20
>exists.
>
>As for the hardware, it is all brand new hardware, and the system dual=20
>boots, the other OS has no issues.
>
> -Derek
>
>
>At 10:07 AM 9/20/2003 +0200, Soren Schmidt wrote:
>>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=20
>> repeatedly
>> > give:
>> > ad4: timeout sending command=3Dca
>> >
>> > The only recovery is the reset switch, reboot single-user fsck, and=
then
>> > come back up in multiuser.
>> >
>> > These errors occur with disk access, but not with a predictable nature=
=20
>> (not
>> > on large files, or small files, etc.)
>>
>>And you are on an uptodate -current ?
>>
>>If so I'd suspect HW ...
>>
>>-S=F8ren
>_______________________________________________
>freebsd-current@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.2.1.1.2.20030920145252.0132be50>