Re: Maxtor drive access very slow

From: General Schvantzkoph (schvantzkoph_at_yahoo.com)
Date: 05/24/04

  • Next message: Rohan Beckles: "Lacie Big Disk 500GB" 
    Date: Sun, 23 May 2004 20:03:32 -0400

    On Sun, 23 May 2004 13:46:58 -0400, John-Paul Stewart wrote:

    > Michael Gass wrote:
    >> In article <saqn8c.5mb.ln@mail.binaryfoundry.ca>, John-Paul Stewart wrote:
    >>
    >>>Michael Gass wrote:
    >>>
    >>>>OK. My IDE controller is an Intel 82801BA Ultra ATA IDE U100
    >>>>I assume that I check in config-2.4.20-6, but I do not know what
    >>>>to check for there. I see lines like
    >>>>CONFIG_IDE=y
    >>>>CONFIG_BLK_DEV_IDEDISK=y
    >>>>but nothing about particular controllers. So how do I check to
    >>>>see if my particular controller is supported by the kernel I
    >>>>am running?
    >>>
    >>>There should be lines about the various controllers. The Intel 82801BA
    >>>controller is supported with the Intel PIIX driver, so grep the config
    >>>file for "CONFIG_BLK_DEV_PIIX" and see if it is set to "Y".
    >>
    >>
    >> Thank you. It is set to "y" ... Any other suggestions?
    >
    > Something is seriously wrong. Other than suggesting you try a newer
    > kernel, I don't know what to say. From the info provided in this
    > thread, it looks like everything is set up correctly. My only guess
    > (and it's certainly a wild guess) is that there's some kernel bug with
    > your hardware.

    Use smartctl to find out if there is something wrong with the disk. If
    smartctl doesn't show a bunch of errors then there are several things
    you can try. The first thing I would do is to replace the IDE cable, I
    doubt that this will help but a good rule of thumb when you suspect a
    hardware problem is to check the connections. If you still are having
    problems then the next thing that I would do is make sure that the disk is
    the only device on the IDE cable, if it is sharing the cable with another
    device remove the other device. It's possible that the other device is
    interfering with your disk is some way. The final thing I would try is to
    put the disk on a Promise card. Promise cards are well supported by all
    recent kernels so that will eliminate the driver as the possible culprit.
    Also a Promise controller will give you a couple of extra IDE ports which
    will enable you to put every device on it's own cable. IDE has been pushed
    well beyond it's original design limit, remember it comes from the PC-AT
    which ran the disks at 8 MB/second. ATA 133 drives like the Maxtor are
    running at 133MB/second. Although it still works it's on the hairy edge
    which is why it's good practice to put only one device per cable.

  • Next message: Rohan Beckles: "Lacie Big Disk 500GB"

    Relevant Pages

    • VTOBUS FAILED
      ... that looks like a hardware problem (Signal 10 aborts while ... compiling a kernel for instance). ... I have taken the root SATA disk out of ... he 2nd machine has 2 dual core CPU's vs 2 single core in the ...
      (freebsd-questions)
    • Re: "Device 08:11 not ready" - error log
      ... kernel: Device 08:11 not ready. ... Is this a hardware problem ... is for all the partition on the disk. ...
      (RedHat)
    • Re: Software RAID-5 attempt to access beyond end of device...
      ... The reiserfs is on top of an lvm2 on top of a raid5 ... >information that has previously been stored on disk. ... Sep 7 20:32:04 cu kernel: Buffer I/O error on device dm-0, ... PCI: PCI BIOS revision 2.10 entry at 0xf1150, ...
      (Linux-Kernel)
    • Re: Spontaneous reboots
      ... yet I keep experiencing spontaneous reboots and crashes. ... > I have postfix handling mail and use cyrus-imap with virtual ... Page fault while in kernel mode ... > Disk errors: ...
      (freebsd-questions)
    • athlon-xp + fakeraid regression
      ... The build completes fine, the kernel boots fine, the machine will seem to be fine as long as it remains quiescent. ... At the beginning, just after hitting enter on the make command, one of the ad4 disk light goes on solid for several seconds. ... There is a well known thing where these cheap pata fakeraid cards will try to do ata133 if the drive says it can, when really, even if he drives are new ata133 drives and the cables are new and short and shielded, you still shouldn't try to do ata133 since the spec is too tight and you'll just get bit errors or other failures. ... The fix is use ata100 somehow, either by disabling dma entirely in loader.conf (since you have no more selective option there, and the raid card bios never has an option for controlling pio/dma mode like motherboard bios's have) and then use atacontrol in rc.early to set udma5, or by using disks that can only do ata100 and only advertise ata100 to the controller. ...
      (freebsd-current)