Re: Adaptec 2410SA starts doing this: aac0: COMMAND 0xc551a7e8 TIMEOUT AFTER 147 SECONDS (Modified by Chad Leigh -- Shire.NetLLC)

2004-03-17 Thread Albert Shih
Le 05/03/2004 à 22:05:25-0700, Scott Long a écrit On Sun, 29 Feb 2004, Chad Leigh -- Shire.Net LLC wrote: Now the machine, when it tries to check the two aacd volumes on this controller, starts printing out this message below every 20 seconds or so and the disk volumes cannot be used.

Re: Adaptec 2410SA starts doing this: aac0: COMMAND 0xc551a7e8 TIMEOUT AFTER 147 SECONDS (Modified by Chad Leigh -- Shire.NetLLC)

2004-03-17 Thread Mark Terribile
--- Albert Shih [EMAIL PROTECTED] wrote: Le 05/03/2004 à 22:05:25-0700, Scott Long a écrit On Sun, 29 Feb 2004, Chad Leigh -- Shire.Net LLC wrote: Now the machine, when it tries to check the two aacd volumes on this controller, [... :] aac0: COMMAND 0xc551a7e8 TIMEOUT AFTER 147

Re: Adaptec 2410SA starts doing this: aac0: COMMAND 0xc551a7e8 TIMEOUT AFTER 147 SECONDS (Modified by Chad Leigh -- Shire.Net LLC)

2004-03-05 Thread Scott Long
On Sun, 29 Feb 2004, Chad Leigh -- Shire.Net LLC wrote: I originally sent this to -questions, but got no response. I hope this is a good place to send this. While the drives and controller are SATA, the driver is the SCSI aac driver for the adaptec raid, hence this group. I would appreciate

Re: Adaptec 2410SA starts doing this: aac0: COMMAND 0xc551a7e8 TIMEOUT AFTER 147 SECONDS (Modified by Chad Leigh -- Shire.NetLLC)

2004-03-05 Thread Chad Leigh -- Shire.Net LLC
On Mar 5, 2004, at 10:05 PM, Scott Long wrote: On Sun, 29 Feb 2004, Chad Leigh -- Shire.Net LLC wrote: I originally sent this to -questions, but got no response. I hope this is a good place to send this. While the drives and controller are SATA, the driver is the SCSI aac driver for the

Adaptec 2410SA starts doing this: aac0: COMMAND 0xc551a7e8 TIMEOUT AFTER 147 SECONDS

2004-02-29 Thread Chad Leigh -- Shire.Net LLC
Hi I have an Adaptec 2410SA RAID card with 3 drives attached, 2 in a RAID 1 array and one as a separate disk. This has been working under 5.2-RELEASE in my test server for some time now. However, for some reason the machine locked up (may not be related) and I had to do a hard reset. Now