I upgraded my Centos 4.7 server last night. Switched from a cheaper
50$ asus motherboard to a Supermicro motherboard. I also, using dd,
copied entire 500g SATA seagate drive to new 500g SATA seagate drive
so as to have two copies in case something went wrong.
Anyway, now I keep getting this error:
Nov 21 06:08:33 server kernel: hda: status timeout: status=0xd0 { Busy }
Nov 21 06:08:33 server kernel:
Nov 21 06:08:33 server kernel: ide: failed opcode was: unknown
Nov 21 06:08:33 server kernel: hda: no DRQ after issuing WRITE
Nov 21 06:08:34 server kernel: ide0: reset: success
Found one website that told me too try hdparm -i to see whats up:
/dev/hda:
Model=ST3500320AS, FwRev=SD15, SerialNo Config={ HardSect NotMFM HdSw>15uSec
Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2
AdvancedPM=no WriteCache=enabled
Drive conforms to: unknown:
* signifies the current active mode
So from recommendation on website I did this to match MaxMultiSect:
hdparm -m16 /dev/hda
then tried this to turn MultSect off:
hdparm -m0 /dev/hda
Still getting error. The Supermicro MBD-X7SBL-LN1-O motherboard has
basically all defaults set in bios.
Any ideas? Thanks.
Matt
I am coming to conclusion that CentOS 4.7 does not support the Intel ICH9R SATA controller very well. My disk I/O is really slowing down as well. Any solutions besides replacing motherboard to fix it? Thanks. Matt> I upgraded my Centos 4.7 server last night. Switched from a cheaper > 50$ asus motherboard to a Supermicro motherboard. I also, using dd, > copied entire 500g SATA seagate drive to new 500g SATA seagate drive > so as to have two copies in case something went wrong. > > Anyway, now I keep getting this error: > > Nov 21 06:08:33 server kernel: hda: status timeout: status=0xd0 { Busy } > Nov 21 06:08:33 server kernel: > Nov 21 06:08:33 server kernel: ide: failed opcode was: unknown > Nov 21 06:08:33 server kernel: hda: no DRQ after issuing WRITE > Nov 21 06:08:34 server kernel: ide0: reset: success > > Found one website that told me too try hdparm -i to see whats up: > > /dev/hda: > > Model=ST3500320AS, FwRev=SD15, SerialNo> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% } > RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4 > BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=off > CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455 > IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} > PIO modes: pio0 pio1 pio2 pio3 pio4 > DMA modes: mdma0 mdma1 mdma2 > UDMA modes: udma0 udma1 udma2 > AdvancedPM=no WriteCache=enabled > Drive conforms to: unknown: > > * signifies the current active mode > > So from recommendation on website I did this to match MaxMultiSect: > > hdparm -m16 /dev/hda > > then tried this to turn MultSect off: > > hdparm -m0 /dev/hda > > Still getting error. The Supermicro MBD-X7SBL-LN1-O motherboard has > basically all defaults set in bios. > > Any ideas? Thanks. > > Matt >
on 11-21-2008 4:41 AM Matt spake the following:> I upgraded my Centos 4.7 server last night. Switched from a cheaper > 50$ asus motherboard to a Supermicro motherboard. I also, using dd, > copied entire 500g SATA seagate drive to new 500g SATA seagate drive > so as to have two copies in case something went wrong. > > Anyway, now I keep getting this error: > > Nov 21 06:08:33 server kernel: hda: status timeout: status=0xd0 { Busy } > Nov 21 06:08:33 server kernel: > Nov 21 06:08:33 server kernel: ide: failed opcode was: unknown > Nov 21 06:08:33 server kernel: hda: no DRQ after issuing WRITE > Nov 21 06:08:34 server kernel: ide0: reset: success > > Found one website that told me too try hdparm -i to see whats up: > > /dev/hda: > > Model=ST3500320AS, FwRev=SD15, SerialNo> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% } > RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4 > BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=off > CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455 > IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} > PIO modes: pio0 pio1 pio2 pio3 pio4 > DMA modes: mdma0 mdma1 mdma2 > UDMA modes: udma0 udma1 udma2 > AdvancedPM=no WriteCache=enabled > Drive conforms to: unknown: > > * signifies the current active mode > > So from recommendation on website I did this to match MaxMultiSect: > > hdparm -m16 /dev/hda > > then tried this to turn MultSect off: > > hdparm -m0 /dev/hda > > Still getting error. The Supermicro MBD-X7SBL-LN1-O motherboard has > basically all defaults set in bios. > > Any ideas? Thanks. > > MattIf the drives were different in size, dd could have truncated something. It isn't always the best tool to use. Maybe try again with a different tool. Also the fact that the drive is showing up as /dev/hda instead of /dev/sda means that you are not using the best driver for the hard drive. Go into the bios and try either native mode to serial ATA or SATA AHCI enable. You might need to rebuild the initrd from a rescue disk after you boot. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20081121/76fa735a/attachment-0003.sig>
> Also the fact that the drive is showing up as /dev/hda instead of /dev/sda > means that you are not using the best driver for the hard drive. Go into the > bios and try either native mode to serial ATA or SATA AHCI enable. > You might need to rebuild the initrd from a rescue disk after you boot.>>native mode to serial ATADid that. Now it shows up as sda again. I no longer get the errors either but I get this now. [root at server log]# hdparm -i /dev/sda /dev/sda: HDIO_GET_IDENTITY failed: Inappropriate ioctl for device Smartd also complains on boot up. Any ideas? Matt