Re: [CentOS] SATA errors on CentOS 5.2

2008-11-05 Thread Phil Schaffner
MHR wrote: Good info here: http://www.seagate.com/ww//index.jsp?locale=en-US&name=SATA_Troubleshooter_-_BIOS_Configuration&vgnextoid=83744a3cdde5c010VgnVCM10dd04090aRCRD I got a 404 on that one. A character 'v' got lost in translation. For posterity, the correct URL is http://www.seagat

RE: [CentOS] SATA errors on CentOS 5.2

2008-11-04 Thread Joseph L. Casale
>I got a 404 on that one. Watch the wrap, or search google for "sata configuration enhanced" it's the first hit... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] SATA errors on CentOS 5.2

2008-11-04 Thread MHR
On Tue, Nov 4, 2008 at 2:09 PM, Joseph L. Casale <[EMAIL PROTECTED]> wrote: >>Should we go ahead and reset to AHCI and reinstall (again)? Or will >>"enhanced" be enough for the long run? > > Enhanced/AHCI for SATA drives under Linux. > > Good info here: > http://www.seagate.com/ww//index.jsp?local

RE: [CentOS] SATA errors on CentOS 5.2

2008-11-04 Thread Joseph L. Casale
>Should we go ahead and reset to AHCI and reinstall (again)? Or will >"enhanced" be enough for the long run? Enhanced/AHCI for SATA drives under Linux. Good info here: http://www.seagate.com/ww//index.jsp?locale=en-US&name=SATA_Troubleshooter_-_BIOS_Configuration&vgnextoid=83744a3cdde5c010VgnVCM

Re: [CentOS] SATA errors on CentOS 5.2

2008-11-04 Thread MHR
On Tue, Nov 4, 2008 at 6:39 AM, Joseph L. Casale <[EMAIL PROTECTED]> wrote: > > Heh, Actually you don't "have two SATA controllers for a single disk drive" > but you have two controllers. > Well, yes, of course! ;-) > As the last poster suggested, use AHCI for Linux. > Interesting. I just spoke

RE: [CentOS] SATA errors on CentOS 5.2

2008-11-04 Thread Joseph L. Casale
>>>What am I missing? Is it odd to have two SATA controllers for a >>>single disk drive, or is that at all relevant? >> >> You don't, it would be odd :) > >Actually, we do - it is configured to have two SATA controllers in it. Heh, Actually you don't "have two SATA controllers for a single disk d

Re: [CentOS] SATA errors on CentOS 5.2

2008-11-04 Thread Morten Torstensen
MHR wrote: "enhanced," the other is set to IDE, but can be set to RAID or AHCI. I've used CentOS5 with many different mobos and SATA. I always configure SATA to AHCI if the mobo/bios allows it. I have not seen any problems with AHCI. A couple machines with both PATA and SATA has brought so

Re: [CentOS] SATA errors on CentOS 5.2

2008-11-03 Thread MHR
On Mon, Nov 3, 2008 at 5:35 PM, MHR <[EMAIL PROTECTED]> wrote: > On Mon, Nov 3, 2008 at 4:57 PM, Joseph L. Casale > <[EMAIL PROTECTED]> wrote: >> >> Is your Mass Storage Controller configured as IDE instead of AHCI? >> > It's "compatible" as IDE. > It has two settings here - one is "compatible" (th

Re: [CentOS] SATA errors on CentOS 5.2

2008-11-03 Thread MHR
On Mon, Nov 3, 2008 at 4:57 PM, Joseph L. Casale <[EMAIL PROTECTED]> wrote: >>What am I missing? Is it odd to have two SATA controllers for a >>single disk drive, or is that at all relevant? > > You don't, it would be odd :) Actually, we do - it is configured to have two SATA controllers in it.

Re: [CentOS] SATA errors on CentOS 5.2

2008-11-03 Thread MHR
On Mon, Nov 3, 2008 at 4:57 PM, Joseph L. Casale <[EMAIL PROTECTED]> wrote: > > Is your Mass Storage Controller configured as IDE instead of AHCI? > It's "compatible" as IDE. >>What am I missing? Is it odd to have two SATA controllers for a >>single disk drive, or is that at all relevant? > > You

RE: [CentOS] SATA errors on CentOS 5.2

2008-11-03 Thread Joseph L. Casale
>/var/log/messages.1-Nov 1 18:19:00 Centos5 kernel: hda: status >timeout: status=0xd0 { Busy } >/var/log/messages.1:Nov 1 18:19:00 Centos5 kernel: ide: failed opcode >was: unknown >/var/log/messages.1-Nov 1 18:19:00 Centos5 kernel: hda: no DRQ after >issuing MULTWRITE_EXT >/var/log/messages.1-No

[CentOS] SATA errors on CentOS 5.2

2008-11-03 Thread MHR
We have a new machine here that we are trying to use for CentOS as a base for our primary application. Although I do not have direct access to the physical machine, I have begun looking into it remotely (via ssh) to see why we are getting the following errors periodically: /var/log/messages.1-Nov