LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   hdparm risky parameters (https://www.linuxquestions.org/questions/slackware-14/hdparm-risky-parameters-535635/)

props666999 03-08-2007 03:55 AM

hdparm risky parameters
 
Hi

I will stuck valuable data on a 200Gig hard disk and was wondering if
the following hdparm parameters stress my cdrom and hard drive
hdparm -X34 -d1 -u1 /dev/hda (hard disk)
hdparm -X34 -d1 -u1 /dev/hdb (cdrom)

i found those on the net

if it is safe, is there anything i could do to improve speed

using the above rules i can copy data from cdrom to hard disk
at 3.7MB/Sec.


it seems very slow to me


regards

onebuck 03-08-2007 07:21 AM

Quote:

Originally Posted by props666999
Hi

I will stuck valuable data on a 200Gig hard disk and was wondering if
the following hdparm parameters stress my cdrom and hard drive
hdparm -X34 -d1 -u1 /dev/hda (hard disk)
hdparm -X34 -d1 -u1 /dev/hdb (cdrom)

i found those on the net

if it is safe, is there anything i could do to improve speed

using the above rules i can copy data from cdrom to hard disk
at 3.7MB/Sec.


it seems very slow to me


regards

Hi,

You should first read the 'man hdparm' to get some reference. The use of arbitrary commands on a drive can cause major problems.

Next do a 'hdparm -I /dev/hda' to find out your known drive information. This information will assist you in determining what you should or can do.

A sample output;
Code:

# hdparm -I /dev/hda

/dev/hda:

ATA device, with non-removable media
        Model Number:      TOSHIBA MK4025GAS                     
        Serial Number:      X5EP9507S
        Firmware Revision:  KA100A 
Standards:
        Supported: 6 5 4 3
        Likely used: 6
Configuration:
        Logical        max    current
        cylinders      16383  65535
        heads          16      1
        sectors/track  63      63
        --
        CHS current addressable sectors:    4128705
        LBA    user addressable sectors:  78140160
        device size with M = 1024*1024:      38154 MBytes
        device size with M = 1000*1000:      40007 MBytes (40 GB)
Capabilities:
        LBA, IORDY(can be disabled)
        bytes avail on r/w long: 48    Queue depth: 1
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 16  Current = 16
        Advanced power management level: unknown setting (0x0080)
        DMA: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 *udma2 udma3 udma4 udma5
            Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
            Cycle time: no flow control=120ns  IORDY flow control=120ns
Commands/features:
        Enabled Supported:
          *    NOP cmd
          *    READ BUFFER cmd
          *    WRITE BUFFER cmd
          *    Host Protected Area feature set
          *    Look-ahead
          *    Write cache
          *    Power Management feature set
                Security Mode feature set
                SMART feature set
          *    Mandatory FLUSH CACHE command
          *    Device Configuration Overlay feature set
                SET MAX security extension
          *    Advanced Power Management feature set
          *    SMART self-test
          *    SMART error logging
Security:
        Master password revision code = 65534
                supported
        not    enabled
        not    locked
        not    frozen
        not    expired: security count
        not    supported: enhanced erase
        36min for SECURITY ERASE UNIT.
HW reset results:
        CBLID- above Vih
        Device num = 0 determined by the jumper
Checksum: correct


H_TeXMeX_H 03-08-2007 12:50 PM

There's also this guide:

http://www.linuxdevcenter.com/pub/a/...29/hdparm.html

and yes, do read 'man hdparm', try to avoid options that say 'dangerous' or 'massive filesystem corrupiton', etc. unless you know very well what you are doing.


All times are GMT -5. The time now is 05:27 AM.