September 21, 2021, 05:24:53 AM

News : LinuxSolved.com Linux Help Community Forum..


Author Topic: Test your hard drive  (Read 28474 times)

Offline dalek

  • LST CareTaker
  • Crescent
  • *****
  • Posts: 243
Test your hard drive
« Reply #15 on: December 07, 2003, 05:32:31 PM »
I have read that the larger the capacity the drive, given the same number of platers and RPMs, the faster they are.  That is because the data is 'squeezed' into the same space and can get it faster.

I guess that would be right huh?  I'm happy either way.  I'm just glad I could copy everything over without having to start over from scratch.

So far so good.

Later

 :D  :D  :D  :D

Offline dalek

  • LST CareTaker
  • Crescent
  • *****
  • Posts: 243
Test your hard drive
« Reply #16 on: December 28, 2003, 12:07:31 AM »
My latest with Gentoo and a 2.6 kernel:

Code: [Select]
bash-2.05b# hdparm -Tt /dev/hda

/dev/hda:
 Timing buffer-cache reads:   1516 MB in  2.00 seconds = 756.22 MB/sec
 Timing buffered disk reads:  146 MB in  3.02 seconds =  48.35 MB/sec
bash-2.05b#

I guess the kernel can make a difference.  Others were in Mandrake I think.

Pretty cool.

 :D  :D  :D  :D

Offline Ricky

  • LST CareTaker
  • Specially Skilled
  • *****
  • Posts: 2381
Test your hard drive
« Reply #17 on: December 28, 2003, 04:46:20 AM »
Hi..
Dalek I have baught new HD.  7200 rpm 40 GB
Code: [Select]
/dev/hda:
 Timing buffer-cache reads:   128 MB in  0.50 seconds =256.00 MB/sec
 Timing buffered disk reads:  64 MB in  1.45 seconds = 44.14 MB/sec

Offline dalek

  • LST CareTaker
  • Crescent
  • *****
  • Posts: 243
Test your hard drive
« Reply #18 on: December 28, 2003, 06:52:44 AM »
What distro and kernel are you using?  I can't believe the difference between 2.4 and 2.6.  2.6 is faster on Gentoo.  

Fixin to update Gentoo while I take a nap.  I took some more Nyquil stuff for my coughing.  I think my throat has sand paper in it.   :shock:

later

 :D  :D  :D

Need a sick emoticon today.

Offline Ricky

  • LST CareTaker
  • Specially Skilled
  • *****
  • Posts: 2381
Test your hard drive
« Reply #19 on: December 28, 2003, 09:14:11 AM »
I don' t think it is due to kernel.. It directly depends that during the test wht are the other loads on it.. i m checking again.. lets see wht it shws.. currently i m outside and on a window machine..

Offline Ricky

  • LST CareTaker
  • Specially Skilled
  • *****
  • Posts: 2381
Test your hard drive
« Reply #20 on: December 28, 2003, 09:19:03 AM »
Now see these results.. change.. a lot.. when hd was not having other loads.. I am sure when i run this tests only from command line. it will also have little effect...
Code: [Select]
Timing buffer-cache reads:   128 MB in  0.41 seconds =312.20 MB/sec
 Timing buffered disk reads:  64 MB in  1.35 seconds = 47.41 MB/sec

Offline dalek

  • LST CareTaker
  • Crescent
  • *****
  • Posts: 243
Test your hard drive
« Reply #21 on: December 28, 2003, 01:41:36 PM »
I wonder why the buffered cache was so low?  That should be higher, may be something to do with the drive.

If you want to see the settings, type in

Code: [Select]
hdparm /dev/hd*
Rplace the * with your letter of course.

Mine is currently

Code: [Select]
bash-2.05b# hdparm /dev/hda

/dev/hda:
 multcount    = 16 (on)
 IO_support   =  1 (32-bit)
 unmaskirq    =  1 (on)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 16383/255/63, sectors = 156301488, start = 0
bash-2.05b#

I'm going to likely make some changes though.  I preger the IO_support to be 3, sync.  Rest is OK.

Later

 :D  :D  :D

Offline Ricky

  • LST CareTaker
  • Specially Skilled
  • *****
  • Posts: 2381
Test your hard drive
« Reply #22 on: December 29, 2003, 11:35:15 AM »
Well i think i  need to optimize my hardisk.. and after optimization i l'll again post here my drive's readings ..

Offline Ricky

  • LST CareTaker
  • Specially Skilled
  • *****
  • Posts: 2381
Test your hard drive
« Reply #23 on: December 29, 2003, 11:54:31 AM »
Well not much changes. . . .  after optimization. .
Dalek post the output of following...
Code: [Select]
hdparm -i /dev/hda
I have this for my disk..  
Code: [Select]
Model=WDC WD400BB-00DEA0, FwRev=05.03E05, SerialNo=WD-WCAD1A722264
 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
 RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
 BuffType=DualPortCache, BuffSize=8192kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=78165360
 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: device does not report version:  1 2 3 4 5

Offline dalek

  • LST CareTaker
  • Crescent
  • *****
  • Posts: 243
Test your hard drive
« Reply #24 on: December 29, 2003, 03:34:04 PM »
Okie Dokie.  Here it is:

Code: [Select]
bash-2.05b# hdparm -i /dev/hda

/dev/hda:

 Model=WDC WD800BB-00DKA0, FwRev=77.07W77, SerialNo=WD-WCAHL2497094
 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
 RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=74
 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=156301488
 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: device does not report version:

 * signifies the current active mode

bash-2.05b#

That help any?  One of my other drives does the same thing yours does.  One is fast but the other is very slow.  It is about 5MBs or something.  It is a old drive though.  One is a 1GB, the other is a 2.5 Gb.

later

 :D  :D  :D

Offline Ricky

  • LST CareTaker
  • Specially Skilled
  • *****
  • Posts: 2381
Test your hard drive
« Reply #25 on: December 30, 2003, 12:30:22 PM »
Hey.. !! I have also got Western Digital.. i was not knowing that .. Huh..
Also i have got larger buffer than urs !! see.. you have 2048 and i have 8192... The only difference is of size.. and serial no..
I think my kernel has not optimized my HD.....

Offline dalek

  • LST CareTaker
  • Crescent
  • *****
  • Posts: 243
Test your hard drive
« Reply #26 on: December 30, 2003, 04:01:03 PM »
May want to look at this link.  It tells you what to try and such.

http://www.linuxgazette.com/issue79/punk.html

I noticed that your cache was bigger too.  I would have thought that it would be faster because of that.  I guess there is a difference somewhere.  I can tell a difference between 2.4 and 2.6 kernels though.  2.6 is faster.

Don't trash your drive.  i have triedabout all the settings and jusr found the fastest ones.  Sometimes you turn somethingon and it may actaually slow you down.  Always run hdparm -Tt at least 3 times to be sure there is no error.  You will also have to put the entire command in some init file to reset during boot.

Speed that thing up a bit.  It should do better.

Later

 :D  :D  :D

Offline Ricky

  • LST CareTaker
  • Specially Skilled
  • *****
  • Posts: 2381
Test your hard drive
« Reply #27 on: December 31, 2003, 08:12:33 AM »
I have seen that document already.. well that is not so informative... As it leaves me confused in pio and udma thing.. well i m happy with my current working.. i ll do this later....

Offline dalek

  • LST CareTaker
  • Crescent
  • *****
  • Posts: 243
Test your hard drive
« Reply #28 on: December 31, 2003, 05:43:42 PM »
Try reading this.

HDPARM(8)                                                            HDPARM(8)



NAME
       hdparm - get/set hard disk parameters

SYNOPSIS
       hdparm [ flags ] [device] ..

DESCRIPTION
       hdparm  provides  a command line interface to various hard disk ioctls supported by the stock Linux ATA/IDE device driver sub-
       system.  Some options may work correctly only with the latest kernels.  For best results,  compile  hdparm  with  the  include
       files from the latest kernel source code.

OPTIONS
       When no flags are given, -acdgkmnru is assumed.

       -a     Get/set  sector  count  for  filesystem  read-ahead.   This is used to improve performance in sequential reads of large
              files, by prefetching additional blocks in anticipation of them being needed by the running task.  In the current  ker-
              nel  version (2.0.10) this has a default setting of 8 sectors (4KB).  This value seems good for most purposes, but in a
              system where most file accesses are random seeks, a smaller setting might provide better performance.  Also,  many  IDE
              drives also have a separate built-in read-ahead function, which alleviates the need for a filesystem read-ahead in many
              situations.

       -A     Disable/enable the IDE drive's read-lookahead feature (usually ON by default).

       -b     Get/set bus state.

       -B     Set Advanced Power Management feature, if the drive supports it. A low value means aggressive power  management  and  a
              high value means better performance. A value of 255 will disable apm on the drive.

       -c     Query/enable  (E)IDE  32-bit  I/O  support.  A numeric parameter can be used to enable/disable 32-bit I/O support: Cur-
              rently supported values include 0 to disable 32-bit I/O support, 1 to enable 32-bit data transfers,  and  3  to  enable
              32-bit data transfers with a special sync sequence required by many chipsets.  The value 3 works with nearly all 32-bit
              IDE chipsets, but incurs slightly more overhead.  Note that "32-bit" refers to data transfers across a PCI or  VLB  bus
              to the interface card only; all (E)IDE drives still have only a 16-bit connection over the ribbon cable from the inter-
              face card.

       -C     Check the current IDE power mode status, which will always be one of unknown (drive does  not  support  this  command),
              active/idle (normal operation), standby (low power mode, drive has spun down), or sleeping (lowest power mode, drive is
              completely shut down).  The -S, -y, -Y, and -Z flags can be used to manipulate the IDE power modes.

       -d     Disable/enable the "using_dma" flag for this drive.  This option now works with most combinations  of  drives  and  PCI
              interfaces  which  support DMA and which are known to the IDE driver.  It is also a good idea to use the appropriate -X
              option in combination with -d1 to ensure that the drive itself is programmed for the correct DMA  mode,  although  most
              BIOSs  should do this for you at boot time.  Using DMA nearly always gives the best performance, with fast I/O through-
              put and low CPU usage.  But there are at least a few configurations of chipsets and drives for which DMA does not  make
              much of a difference, or may even slow things down (on really messed up hardware!).  Your mileage may vary.

       -D     Enable/disable  the on-drive defect management feature, whereby the drive firmware tries to automatically manage defec-
              tive sectors by relocating them to "spare" sectors reserved by the factory for such.

       -E     Set cdrom speed.  This is NOT necessary for regular operation, as the drive will automatically  switch  speeds  on  its
              own.  But if you want to play with it, just supply a speed number after the option, usually a number like 2 or 4.

       -f     Sync and flush the buffer cache for the device on exit.  This operation is also performed as part of the -t and -T tim-
              ings.

       -g     Display the drive geometry (cylinders, heads, sectors), the size (in sectors) of the device, and  the  starting  offset
              (in sectors) of the device from the beginning of the drive.

       -h     Display terse usage information (help).

       -i     Display the identification info that was obtained from the drive at boot time, if available.  This is a feature of mod-
              ern IDE drives, and may not be supported by older devices.  The data returned may or may not be current,  depending  on
              activity  since  booting  the  system.   However,  the  current multiple sector mode count is always shown.  For a more
              detailed interpretation of the identification info, refer to AT Attachment Interface for Disk Drives (ANSI  ASC  X3T9.2
              working draft, revision 4a, April 19/93).

       -I     Request identification info directly from the drive, which is displayed in a new expanded format with considerably more
              detail than with the older -i flag.  There is a special "no seatbelts" variation on this option, -Istdin  which  cannot
              be combined with any other options, and which accepts a drive identification block as standard input instead of using a
              /dev/hd* parameter.  The format of this block must be exactly the same as that found  in  the  /proc/ide/*/hd*/identify
              "files".  This variation is designed for use with "libraries" of drive identification information, and can also be used
              on ATAPI drives which may give media errors with the standard mechanism.

       -k     Get/set the keep_settings_over_reset flag for the drive.  When this flag is set, the  driver  will  preserve  the  -dmu
              options  over  a soft reset, (as done during the error recovery sequence).  This flag defaults to off, to prevent drive
              reset loops which could be caused by combinations of -dmu settings.  The -k flag should therefore only be set after one
              has achieved confidence in correct system operation with a chosen set of configuration settings.  In practice, all that
              is typically necessary to test a configuration (prior to using -k) is to verify that the drive can be read/written, and
              that no error logs (kernel messages) are generated in the process (look in /var/adm/messages on most systems).

       -K     Set  the drive's keep_features_over_reset flag.  Setting this enables the drive to retain the settings for -APSWXZ over
              a soft reset (as done during the error recovery sequence).  Not all drives support this feature.

       -L     Set the drive's doorlock flag.  Setting this to 1 will lock the door mechanism of  some  removeable  hard  drives  (eg.
              Syquest,  ZIP, Jazz..), and setting it to 0 will unlock the door mechanism.  Normally, Linux maintains the door locking
              mechanism automatically, depending on drive usage (locked whenever a filesystem is mounted).  But on  system  shutdown,
              this  can  be a nuisance if the root partition is on a removeable disk, since the root partition is left mounted (read-
              only) after shutdown.  So, by using this command to unlock the door after the root filesystem is  remounted  read-only,
              one can then remove the cartridge from the drive after shutdown.

       -m     Get/set sector count for multiple sector I/O on the drive.  A setting of 0 disables this feature.  Multiple sector mode
              (aka IDE Block Mode), is a feature of most modern IDE hard drives, permitting the transfer of multiple sectors per  I/O
              interrupt,  rather than the usual one sector per interrupt.  When this feature is enabled, it typically reduces operat-
              ing system overhead for disk I/O by 30-50%.  On many systems, it also provides increased data  throughput  of  anywhere
              from  5%  to  50%.   Some  drives,  however  (most notably the WD Caviar series), seem to run slower with multiple mode
              enabled.  Your mileage may vary.  Most drives support the minimum settings of 2, 4, 8, or 16  (sectors).   Larger  set-
              tings may also be possible, depending on the drive.  A setting of 16 or 32 seems optimal on many systems.  Western Dig-
              ital recommends lower settings of 4 to 8 on many of their drives, due  tiny  (32kB)  drive  buffers  and  non-optimized
              buffering  algorithms.   The  -i flag can be used to find the maximum setting supported by an installed drive (look for
              MaxMultSect in the output).  Some drives claim to support multiple mode, but lose data at some  settings.   Under  rare
              circumstances, such failures can result in massive filesystem corruption.

       -M     Get/set  Automatic  Acoustic  Management  (AAM) setting. Most modern harddisk drives have the ability to speed down the
              head movements to reduce their noise output.  The possible values are between 0 and 254. 128 is  the  most  quiet  (and
              therefore  slowest)  setting and 254 the fastest (and loudest). Some drives have ownly two levels (quiet / fast), while
              others may have different levels between 128 and 254.  THIS FEATURE IS EXPERIMENTAL AND NOT WELL TESTED.  USE  AT  YOUR
              OWN RISK.

       -n     Get or set the "ignore write errors" flag in the driver.  Do NOT play with this without grokking the driver source code
              first.

       -p     Attempt to reprogram the IDE interface chipset for the specified PIO mode, or attempt to auto-tune for the  "best"  PIO
              mode  supported  by  the drive.  This feature is supported in the kernel for only a few "known" chipsets, and even then
              the support is iffy at best.  Some IDE chipsets are unable to alter the PIO mode for a single drive, in which case this
              flag  may  cause the PIO mode for both drives to be set.  Many IDE chipsets support either fewer or more than the stan-
              dard six (0 to 5) PIO modes, so the exact speed setting that  is  actually  implemented  will  vary  by  chipset/driver
              sophistication.   Use  with extreme caution!  This feature includes zero protection for the unwary, and an unsuccessful
              outcome may result in severe filesystem corruption!

       -P     Set the maximum sector count for the drive's internal prefetch mechanism.  Not all drives support this feature.

       -q     Handle the next flag quietly, supressing normal output.  This is useful for reducing screen clutter when  running  from
      /etc/rc.c/rc.local.  Not applicable to the -i or -v or -t or -T flags.

       -Q     Set  tagged  queue  depth  (1  or  greater), or turn tagged queuing off (0).  This only works with the newer 2.5.xx (or
              later) kernels, and only with the few drives that currently support it.

       -r     Get/set read-only flag for device.  When set, write operations are not permitted on the device.

       -R     Register an IDE interface.  Dangerous.  See the -U option for more information.

       -S     Set the standby (spindown) timeout for the drive.  This value is used by the drive to determine how long to wait  (with
              no  disk activity) before turning off the spindle motor to save power.  Under such circumstances, the drive may take as
              long as 30 seconds to respond to a subsequent disk access, though most drives are much quicker.  The  encoding  of  the
              timeout value is somewhat peculiar.  A value of zero means "off".  Values from 1 to 240 specify multiples of 5 seconds,
              for timeouts from 5 seconds to 20 minutes.  Values from 241 to 251 specify from 1 to 11 units of 30 minutes, for  time-
              outs  from  30 minutes to 5.5 hours.  A value of 252 signifies a timeout of 21 minutes, 253 sets a vendor-defined time-
              out, and 255 is interpreted as 21 minutes plus 15 seconds.

       -T     Perform timings of cache reads for benchmark and comparison purposes.  For meaningful results, this operation should be
              repeated  2-3  times on an otherwise inactive system (no other active processes) with at least a couple of megabytes of
              free memory.  This displays the speed of reading directly from the Linux buffer cache without disk access.   This  mea-
              surement  is  essentially an indication of the throughput of the processor, cache, and memory of the system under test.
              If the -t flag is also specified, then a correction factor based on the outcome of -T will  be  incorporated  into  the
              result reported for the -t operation.

       -t     Perform  timings  of device reads for benchmark and comparison purposes.  For meaningful results, this operation should
              be repeated 2-3 times on an otherwise inactive system (no other active processes) with at least a couple  of  megabytes
              of  free  memory.  This displays the speed of reading through the buffer cache to the disk without any prior caching of
              data.  This measurement is an indication of how fast the drive can sustain sequential data reads under  Linux,  without
              any filesystem overhead.  To ensure accurate measurments, the buffer cache is flushed during the processing of -t using
              the BLKFLSBUF ioctl.  If the -T flag is also specified, then a correction factor based on the outcome  of  -T  will  be
              incorporated into the result reported for the -t operation.

       -u     Get/set  interrupt-unmask flag for the drive.  A setting of 1 permits the driver to unmask other interrupts during pro-
              cessing of a disk interrupt, which greatly improves Linux's responsiveness and eliminates "serial port overrun" errors.
              Use  this feature with caution: some drive/controller combinations do not tolerate the increased I/O latencies possible
              when this feature is enabled, resulting in massive filesystem corruption.  In particular, CMD-640B  and  RZ1000  (E)IDE
              interfaces  can  be  unreliable  (due  to  a  hardware flaw) when this option is used with kernel versions earlier than
              2.0.13.  Disabling the IDE prefetch feature of these interfaces (usually a BIOS/CMOS setting) provides a safe  fix  for
              the problem for use with earlier kernels.

       -U     Un-register  an  IDE  interface.   Dangerous.   The  companion  for the -R option.  Intended for use with hardware made
              specifically for hot-swapping (very rare!).  Use with knowledge and extreme caution as this can easily hang  or  damage
              your  system.   The  hdparm  source distribution includes a 'contrib' directory with some user-donated scripts for hot-
              swapping on the UltraBay of a ThinkPad 600E.  Use at your own risk.

       -v     Display all settings, except -i (same as -acdgkmnru for IDE, -gr for SCSI or -adgr for XT).  This is also  the  default
              behaviour when no flags are specified.

       -w     Perform  a  device  reset (DANGEROUS).  Do NOT use this option.  It exists for unlikely situations where a reboot might
              otherwise be required to get a confused drive back into a useable state.

       -W     Disable/enable the IDE drive's write-caching feature (default state is undeterminable; manufacturer/model specific).

       -x     Tristate device for hotswap (DANGEROUS).

       -X     Set the IDE transfer mode for newer (E)IDE/ATA drives.  This is typically used in combination with  -d1  when  enabling
              DMA  to/from  a  drive on a supported interface chipset, where -X mdma2 is used to select multiword DMA mode2 transfers
              and -X sdma1 is used to select simple mode 1 DMA transfers.  With systems which  support  UltraDMA  burst  timings,  -X
              udma2  is  used to select UltraDMA mode2 transfers (you'll need to prepare the chipset for UltraDMA beforehand).  Apart
              from that, use of this flag is seldom necessary since most/all modern IDE drives default to their fastest PIO  transfer
              mode  at  power-on.   Fiddling  with  this  can be both needless and risky.  On drives which support alternate transfer
              modes, -X can be used to switch the mode of the drive only.  Prior to changing the transfer  mode,  the  IDE  interface
              should be jumpered or programmed (see -p flag) for the new mode setting to prevent loss and/or corruption of data.  Use
         this with extreme caution!  For the PIO (Programmed Input/Output) transfer modes used by Linux, this  value  is  simply
              the  desired  PIO  mode  number  plus  8.  Thus, a value of 09 sets PIO mode1, 10 enables PIO mode2, and 11 selects PIO
              mode3.  Setting 00 restores the drive's "default" PIO mode, and 01 disables IORDY.  For multiword DMA, the  value  used
              is the desired DMA mode number plus 32.  for UltraDMA, the value is the desired UltraDMA mode number plus 64.

   -W     Disable/enable the IDE drive's write-caching feature (default state is undeterminable; manufacturer/model specific).

       -x     Tristate device for hotswap (DANGEROUS).

       -X     Set the IDE transfer mode for newer (E)IDE/ATA drives.  This is typically used in combination with  -d1  when  enabling
              DMA  to/from  a  drive on a supported interface chipset, where -X mdma2 is used to select multiword DMA mode2 transfers
              and -X sdma1 is used to select simple mode 1 DMA transfers.  With systems which  support  UltraDMA  burst  timings,  -X
              udma2  is  used to select UltraDMA mode2 transfers (you'll need to prepare the chipset for UltraDMA beforehand).  Apart
              from that, use of this flag is seldom necessary since most/all modern IDE drives default to their fastest PIO  transfer
              mode  at  power-on.   Fiddling  with  this  can be both needless and risky.  On drives which support alternate transfer
              modes, -X can be used to switch the mode of the drive only.  Prior to changing the transfer  mode,  the  IDE  interface
              should be jumpered or programmed (see -p flag) for the new mode setting to prevent loss and/or corruption of data.  Use
              this with extreme caution!  For the PIO (Programmed Input/Output) transfer modes used by Linux, this  value  is  simply
              the  desired  PIO  mode  number  plus  8.  Thus, a value of 09 sets PIO mode1, 10 enables PIO mode2, and 11 selects PIO
              mode3.  Setting 00 restores the drive's "default" PIO mode, and 01 disables IORDY.  For multiword DMA, the  value  used
              is the desired DMA mode number plus 32.  for UltraDMA, the value is the desired UltraDMA mode number plus 64.

       -y     Force  an  IDE drive to immediately enter the low power consumption standby mode, usually causing it to spin down.  The
              current power mode status can be checked using the -C flag.

       -Y     Force an IDE drive to immediately enter the lowest power consumption sleep mode, causing it to shut down completely.  A
              hard  or  soft reset is required before the drive can be accessed again (the Linux IDE driver will automatically handle
              issuing a reset if/when needed).  The current power mode status can be checked using the -C flag.

       -z     Force a kernel re-read of the partition table of the specified device(s).

       -Z     Disable the automatic power-saving  function  of  certain  Seagate  drives  (ST3xxx  models?),  to  prevent  them  from
              idling/spinning-down at inconvenient times.

BUGS
       As  noted above, the -m sectcount and -u 1 options should be used with caution at first, preferably on a read-only filesystem.
       Most drives work well with these features, but a few drive/controller combinations are not 100% compatible.   Filesystem  cor-
       ruption may result.  Backup everything before experimenting!

       Some options (eg. -r for SCSI) may not work with old kernels as necessary ioctl()'s were not supported.

       Although  this utility is intended primarily for use with (E)IDE hard disk devices, several of the options are also valid (and
       permitted) for use with SCSI hard disk devices and MFM/RLL hard disks with XT interfaces.

AUTHOR
       hdparm has been written by Mark Lord <mlord@pobox.com>, the primary developer and maintainer of the (E)IDE driver  for  Linux,
       with suggestions from many netfolk.

       The disable Seagate auto-powersaving code is courtesy of Tomi Leppikangas(tomilepp@paju.oulu.fi).

SEE ALSO
       AT Attachment Interface for Disk Drives, ANSI ASC X3T9.2 working draft, revision 4a, April 19, 1993.

       AT Attachment Interface with Extensions (ATA-2), ANSI ASC X3T9.2 working draft, revision 2f, July 26, 1994.

       AT Attachment with Packet Interface - 5 (ATA/ATAPI-5), T13-1321D working draft, revision 3, February 29, 2000.

       AT Attachment with Packet Interface - 6 (ATA/ATAPI-6), T13-1410D working draft, revision 3b, February 26, 2002.

       Western Digital Enhanced IDE Implementation Guide, by Western Digital Corporation, revision 5.0, November 10, 1993.

       Enhanced Disk Drive Specification, by Phoenix Technologies Ltd., version 1.0, January 25, 1994.




Version 5.4                        Feb 2003                          HDPARM(8)


It's a bit long but it works.

Post results of hdparm /dev/hda.  I'll help you get those settings.  Just do it when you get the time.

Later

 :D  :D  :D

Offline Ricky

  • LST CareTaker
  • Specially Skilled
  • *****
  • Posts: 2381
Test your hard drive
« Reply #29 on: December 31, 2003, 07:28:45 PM »
OOooh.. This is long.. ya.. I will sure read it out and will implement as I get time.. Thank you! for gathering the information for me..  :)