Andrew Walker wrote:
>>The drive might not exist, but the device file surely does. Try deleting
>>the device file and/or changing the drive setting to "no drive" or
>>"auto" in the bios. Do you use udev? If so, try setting in
>>/etc/conf.d/rc RC_DEVICES="udev" and RC_DEVICE_TARBALL="no".
>
>
> There is no option for RC_DEVICES="udev" in my /etc/conf.d/rc file, do
> you mean replace the line
> RC_DEVFSD_STARTUP="yes"
> with
> RC_DEVICES="udev"
>

Well, I think this pretty much answers my question asking if you use udev.
Also, I hadn't read you other post about the disk being in a RAID so
please don't be trying to delete any of the device files I mentioned
before. Oops.

Andrew Walker wrote:
>>The drive might not exist, but the device file surely does. Try deleting
>>the device file and/or changing the drive setting to "no drive" or
>>"auto" in the bios. Do you use udev? If so, try setting in
>>/etc/conf.d/rc RC_DEVICES="udev" and RC_DEVICE_TARBALL="no".
>
>
> There is no option for RC_DEVICES="udev" in my /etc/conf.d/rc file, do
> you mean replace the line
> RC_DEVFSD_STARTUP="yes"
> with
> RC_DEVICES="udev"
>

Ok, I guess this answers my question about whether you use udev or not.
I spose you're still using devfsd instead.
I read in the other thread for this post that you have some kind of
raid. This raid doesn't include the mystery hdb does it? It seems that
they are hde and hdg right?
Anyway, if this disk has indeed been taken out of the computer and is
safely out of harm's way, try deleting the device file and all the links
to/from it. Or you could just remove it from your hdparm conf file.

On Thu, 07 Apr 2005 13:29:03 +0100, Ben O'Brien wrote:


> Well, I think this pretty much answers my question asking if you use udev.
> Also, I hadn't read you other post about the disk being in a RAID so
> please don't be trying to delete any of the device files I mentioned
> before. Oops.

Now I'm really confused. I should be using udev as I installed it
following the link below

http://www.gentoo.org/doc/en/udev-guide.xml

and it seems to mention that udev is being used on boot-up.

On Thu, 07 Apr 2005 09:21:14 +0000, Andrew Walker wrote:

> And it appears they are already using udma6, it this right?

yes.

> However, I tried this on hda and it looks like it's using udma4 when it
> could use udma5, am I right about this as well?

yes, and it could even use udma6.

--
Bell Labs Unix -- Reach out and grep someone.

Andrew Walker enlightened us with:
> and it looks like it's using udma4 when it could use udma5, am I
> right about this as well?

The drive supports udma6, but maybe the controller only supports up to
udma4?

Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?

Andrew Walker wrote:
> On Thu, 07 Apr 2005 13:29:03 +0100, Ben O'Brien wrote:
>
>
>
>>Well, I think this pretty much answers my question asking if you use udev.
>>Also, I hadn't read you other post about the disk being in a RAID so
>>please don't be trying to delete any of the device files I mentioned
>>before. Oops.
>
>
> Now I'm really confused. I should be using udev as I installed it
> following the link below
>
> http://www.gentoo.org/doc/en/udev-guide.xml
>
> and it seems to mention that udev is being used on boot-up.
Sorry, I tried to cancel this message of mine, but it seems you already
read it.
Anyway, if you want udev, you'll probably have to change your
/etc/conf.d/rc in so that RC_DEVICES="udev" and if you also want to get
rid of all the useless files in /dev/ you should set
RC_DEVICE_TARBALL="no". Refer to the guide, it's a good one (as usual).
Also, read my other post in this thread... the one I meant to post.

Andrew Walker wrote:

==snipped==
> However, I tried this on hda
>
> bash-2.05b# hdparm -i /dev/hda
>
> /dev/hda:
>
> Model=MAXTOR 6L020J1, FwRev=A93.0500, SerialNo=661208113614
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=16383/16/63, TrkSize=32256, SectSize=21298, ECCbytes=4
> BuffType=DualPortCache, BuffSize=1819kB, MaxMultSect=16, MultSect=16
> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=40132503
> 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 udma3 *udma4 udma5 udma6
> AdvancedPM=no WriteCache=enabled
> Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1:
>
> * signifies the current active mode
>
> bash-2.05b#
>
> and it looks like it's using udma4 when it could use udma5, am I right
> about this as well?
>
>
>
>
There are three (3) possible reasons:
1st Mode isn't enabled in the bios (most likely)
2nd Cable isn't rated (replace cable)
3rd Chipset doesn't support mode (least likely)

Andrew Walker wrote:

==snipped==
> bash-2.05b# hdparm -i /dev/hda
>
> /dev/hda:
>
> Model=MAXTOR 6L020J1, FwRev=A93.0500, SerialNo=661208113614
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=16383/16/63, TrkSize=32256, SectSize=21298, ECCbytes=4
> BuffType=DualPortCache, BuffSize=1819kB, MaxMultSect=16, MultSect=16
> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=40132503
> 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 udma3 *udma4 udma5 udma6
> AdvancedPM=no WriteCache=enabled
> Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1:
>
> * signifies the current active mode
>
> bash-2.05b#
>
> and it looks like it's using udma4 when it could use udma5, am I right
> about this as well?
>
>
>
>
There are three reasons you may not be getting full udma6 support from the
onboard controller.
1st You don't have it enabled in the bios (most likely problem)
2nd Cable doesn't support it (replace the cable)
3rd Chipset doesn't support that mode (least likely problem)