SEO

I used to have a /dev/hdb hard disk which I have removed. I have removed
it's entry from /etc/fstab but when I boot up hdparm still tries to set up
it's parameters. My /etc/conf.d/hdparm has only the following,

all_args="-d1"

which I believe sets all drives to DMA enable, but why is hdparm trying
to set hdb when it doesn't exist?
The odd thing is that I don't get the message in my kernel log file but it
appears during boot up. How do I get hdparm to ignore this non-existent
device?

Andrew Walker napisał(a):
>
> all_args="-d1"
>
> How do I get hdparm to ignore this non-existent
> device?
>
Hi!

Try this! This is my hdparm config file...

# Copyright 1999-2004 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header:
/var/cvsroot/gentoo-x86/sys-apps/hdparm/files/hdparm-conf.d.3,v 1.2
2004/09/06 02:17:08 swegener Exp $

# You can either set hdparm arguments for each drive using hdX_args,
# discX_args, cdromX_args and genericX_args, e.g.
#
# hda_args="-d1 -X66"
# disc1_args="-d1"
# cdrom0_args="-d1"

# or, you can set hdparm options for ALL drives using all_args, e.g.
#
#all_args="-d1 -X69"

hda_args="-d1 -X69"
hdc_args="-d1 -X69"
hdd_args="-d1 -X68"

# end


"-X" flag tune up you DMA settings.
X66 - DMA 2 33
X67 - DMA 3 66
X68 - DMA 4 100
X69 - DMA 5 150?? I think...

On Tue, 05 Apr 2005 19:27:41 +0000, Andrew Walker wrote:

> How do I get hdparm to ignore this non-existent device?

I suspect you have the drive setup in the bios? or is it set to autodetect
on boot?

What does 'file -s /dev/hdb' say when run as root?

--
BOFH Excuse #86:

Runt packets

I tried what you suggested and got this

bash-2.05b# file -s /dev/hdb
/dev/hdb: writable, no read permission
bash-2.05b#

Very strange, how can it be writable when it doesn't exist!







On Tue, 05 Apr 2005 23:47:02 +0000, Geoff King wrote:

> On Tue, 05 Apr 2005 19:27:41 +0000, Andrew Walker wrote:
>
>> How do I get hdparm to ignore this non-existent device?
>
> I suspect you have the drive setup in the bios? or is it set to autodetect
> on boot?
>
> What does 'file -s /dev/hdb' say when run as root?

Thanks for the info, just one question you may be able to help me with.
I have a RAID partition from a Promise PDC20276 chip which works but I'd
like to enable DMA ATA133 on it. It's fstab entry is

/dev/md0 /mnt/raid ext3 noatime,user 0 0

Do I edit /etc/conf.d/hdparm with the lines

hde_args="-d1 -X69"
hdg_args="-d1 -X69"

or do I need to specify md0 ?
Also, is X69 DMA133 or should I use X68 , they are not sata drives just
normal ATA133 drives in raid0.

Andrew Walker wrote:
> I tried what you suggested and got this
>
> bash-2.05b# file -s /dev/hdb
> /dev/hdb: writable, no read permission
> bash-2.05b#
>
> Very strange, how can it be writable when it doesn't exist!
>
>
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".

On Wed, 06 Apr 2005 09:58:23 +0000, Andrew Walker wrote:

> Thanks for the info, just one question you may be able to help me with.
> I have a RAID partition from a Promise PDC20276 chip which works but I'd
> like to enable DMA ATA133 on it. It's fstab entry is
>
> /dev/md0 /mnt/raid ext3 noatime,user 0 0
>
> Do I edit /etc/conf.d/hdparm with the lines
>
> hde_args="-d1 -X69"
> hdg_args="-d1 -X69"
>
> or do I need to specify md0 ?
> Also, is X69 DMA133 or should I use X68 , they are not sata drives just
> normal ATA133 drives in raid0.

what does 'hdparm -i /dev/md0' produce when run as root?

--
#ifdef STUPIDLY_TRUST_BROKEN_PCMD_ENA_BIT
linux-2.4.0-test2/drivers/ide/cmd640.c

Andrew Walker napisał(a):
> I have a RAID partition from a Promise PDC20276 chip which works but I'd
> like to enable DMA ATA133 on it. It's fstab entry is
> /dev/md0 /mnt/raid ext3 noatime,user 0 0
>
> Do I edit /etc/conf.d/hdparm with the lines
>
> hde_args="-d1 -X69"
> hdg_args="-d1 -X69"
>
> or do I need to specify md0 ?
> Also, is X69 DMA133 or should I use X68 , they are not sata drives just
> normal ATA133 drives in raid0.
>

I'm sorry, but I'm never used RAID controller...

> 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"

Here it is in full

# /etc/conf.d/rc:
# $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/conf.d/rc,v 1.13 2004/02/26 18:01:29 azarah Exp $

#
# Global config file for the Gentoo RC System
#
# NOTE: most of these are not in use yet!!
#


# This is the amount of tty's used in most of the rc-scripts (like
# consolefont, numlock, etc

RC_TTY_NUMBER=11

# Set to "yes" if you want the rc system to try and start services
# in parallel for slight speed improvement.

RC_PARALLEL_STARTUP="no"

# Set to "yes" if the default behaviour of at least one net.*
# service starting beside net.lo is NOT enouth to consider
# the 'net' dependency up and running.

RC_NET_STRICT_CHECKING="no"

# Set to "yes" if you want to save /dev to a tarball on shutdown
# and restore it on startup. This is useful if you have a lot of
# custom device nodes that udev do not handle/know about.
# (ONLY used by UDEV enabled systems!)

RC_DEVICE_TARBALL="yes"

# Set to "yes" if you want devfsd to start upon bootup. This is
# the default for Gentoo.
# Set to "no" only if you understand the full implications. A
# number of files may need to be altered (i.e. /etc/inittab,
# /etc/fstab, etc.).
# Also note that it does _NOT_ start for UDEV enabled systems,
# even if RC_DEVFSD_STARTUP="yes" ...

RC_DEVFSD_STARTUP="yes"

# Set to "yes" if stop-daemon() should always retry killing the
# service if it fails the first time.

RC_RETRY_KILL="yes"


# Set the amount of seconds stop-daemon() should wait between
# retries. $RC_RETRY_KILL should be set to "yes".

RC_RETRY_TIMEOUT=1


# Set the amount of times stop-daemon() should try to kill
# a service before giving up. $RC_RETRY_KILL should be set to "yes".

RC_RETRY_COUNT=5


# Set to "yes" if stop-daemon() should fail if the service
# is marked as started, but not actually running on stop.

RC_FAIL_ON_ZOMBIE="no"



#
# Internal configuration variables
#
# NB: These are for advanced users, and you should really
# know what you are doing before changing them!
#


# rc-scripts dep-cache directory
#
# NOTE: Do not remove the next line, as its needed by the baselayout ebuild!
#
# svcdir="/var/lib/init.d"

svcdir="/var/lib/init.d"


# Should we mount $svcdir as a tmpfs or ramfs for some speed
# increase for slower machines, or for the more extreme setups ?

svcmount="no"


# FS type that should be used for $svcdir. Note that you need
# $svcmount above set to "yes" for this to work ... Currently
# "tmpfs" and "ramfs" are supported, with "tmpfs" the default.

svcfstype="tmpfs"


# Size of $svcdir in KB

svcsize=2048

>
> what does 'hdparm -i /dev/md0' produce when run as root?

It doesn't like it,

bash-2.05b# hdparm -i /dev/md0

/dev/md0:
HDIO_GET_IDENTITY failed: Invalid argument
bash-2.05b#

but I tried doing this

bash-2.05b# hdparm -i /dev/hde

/dev/hde:

Model=Maxtor 6E030L0, FwRev=NAR61590, SerialNo=E16AZ7XE
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=60058656
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=yes: disabled (255) WriteCache=enabled
Drive conforms to: (null):

* signifies the current active mode

bash-2.05b#



bash-2.05b# hdparm -i /dev/hdg

/dev/hdg:

Model=Maxtor 6E030L0, FwRev=NAR61590, SerialNo=E1532E3E
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=60058656
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=yes: disabled (255) WriteCache=enabled
Drive conforms to: (null):

* signifies the current active mode

bash-2.05b#

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

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?