Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: Problem with shredding HDD

  1. #1
    Join Date
    Dec 2008
    Location
    Norway
    Posts
    550

    Default Problem with shredding HDD

    I am trying to shred my HDD which is connected to my computer with a USB 3.0 disk station.

    The shredding keeps getting interrupted and it is showing some error with wrong offset. The drive regularly changes device file /dev/sdX (/dev/sdc to /dev/sdd) back and forth.
    Because of this the shred program cannot finish. I got really close to finish once before it switched device file.

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,790
    Blog Entries
    3

    Default Re: Problem with shredding HDD

    Quote Originally Posted by DJViking View Post
    The drive regularly changes device file /dev/sdX (/dev/sdc to /dev/sdd) back and forth.
    I have a disk that does that. When it happens, I wiggle the disk data cable, and it is good for a few months before it happens again.

    Apparently, on some kinds of error, the device is disconnected and then reconnected. That's probably what you are seeing.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  3. #3
    Join Date
    Dec 2008
    Location
    Norway
    Posts
    550

    Default Re: Problem with shredding HDD

    Quote Originally Posted by nrickert View Post
    I have a disk that does that. When it happens, I wiggle the disk data cable, and it is good for a few months before it happens again.

    Apparently, on some kinds of error, the device is disconnected and then reconnected. That's probably what you are seeing.
    Then it is shred that is causing this behaviour, or perhaps elsewhere.
    I'll use watch to monitor fdisk-l to check if it happens without using shred.

  4. #4
    Join Date
    Dec 2008
    Location
    Norway
    Posts
    550

    Default Re: Problem with shredding HDD

    I suspect the problem occurs when accessing the drive. I have been monitoring fdisk and the device has not yet switched device file.

    I have a 2TB HDD that needs shredding. It would probably take above 24hours (even at only default 3 iterations) Would suck if it would falter halfway through. Though I could try one single iteration, hope it manage to finish, and then try again.

  5. #5
    Join Date
    Dec 2008
    Location
    Norway
    Posts
    550

    Default Re: Problem with shredding HDD

    D***. I got 10% shredding before it switched device file
    shred: /dev/sdc: error writing at offset 49790891008: I/O-error

    Not sure what I could do short of plugging the drive directly to internal SATA.

    Somehow I have gotten a /dev/sdd4 written with aproc 191GB. Thinking perhaps I should just use dd to zero out the drive.

    And I cannot delete the "partition" /dev/sdd4
    "Operation not permitted on disk /dev/sdd

    The partitioning on your disk /dev/sdd is either not readable or not supported by the partitioning tool parted used to change the partition table."

  6. #6
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,121
    Blog Entries
    15

    Default Re: Problem with shredding HDD

    Hi
    Overheating the USB 3.X port perhaps, switch to a USB 2.0 port and see if it occurs? Disk power down, not a green device, if so look at the hdparms.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  7. #7
    Join Date
    Dec 2008
    Location
    Norway
    Posts
    550

    Default Re: Problem with shredding HDD

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Overheating the USB 3.X port perhaps, switch to a USB 2.0 port and see if it occurs? Disk power down, not a green device, if so look at the hdparms.
    The drive itself is hot, but nothing else I can detect.
    It should not power down. It is a Western Digital Black 1TB HDD.

    Code:
    mintaka:/home/djviking # hdparm /dev/sdd
    
    /dev/sdd:
     multcount     =  0 (off)
     readonly      =  0 (off)
     readahead     = 1024 (on)
     geometry      = 121601/255/63, sectors = 1953525168, start = 0
    
    mintaka:/home/djviking # hdparm -C /dev/sdd
    
    /dev/sdd:
     drive state is:  active/idle
    
    hdparm has many DANGEROUS options...

  8. #8
    Join Date
    Dec 2008
    Location
    Norway
    Posts
    550

    Default Re: Problem with shredding HDD

    Got to almost 20% before it got I/O-Error again. I think I will give up, this is just ridiculous.
    I'll put the drive in my server directly on SATA and then try again.

  9. #9
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    27,121
    Blog Entries
    15

    Default Re: Problem with shredding HDD

    Hi
    But what about the system your connecting to, could be the USB port/power cannot handle the sustained speed for two or three hours....

    When the device it plugged in, how much power is it using;
    Code:
    lsusb -vv|grep power
    lsusb -vv|grep bHubContrCurrent
    You can forget about the grep to locate the specific port.

    Check power management of the HDD;
    Code:
    hdparm -B /dev/sdX
    If it's 128 or greater it should be fine. There are also -M and -S read options -I for everything.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  10. #10
    Join Date
    Dec 2008
    Location
    Norway
    Posts
    550

    Default Re: Problem with shredding HDD

    On Idle. Not running any shred yet on the drive.

    Code:
    mintaka:/home/djviking # lsusb -vv|grep power
        Per-port power switching
       Port 1: 0000.0100 power
       Port 2: 0000.0100 power
       Port 3: 0000.0100 power
       Port 4: 0000.0100 power
       Port 5: 0000.0100 power
       Port 6: 0000.0100 power
       Port 7: 0000.0100 power
       Port 8: 0000.0103 power enable connect
        No power switching (usb 1.0)
       Port 1: 0000.0503 highspeed power enable connect
       Port 2: 0000.0100 power
        No power switching (usb 1.0)
       Port 1: 0000.02a0 5Gbps power Rx.Detect
       Port 2: 0000.02a0 5Gbps power Rx.Detect
        No power switching (usb 1.0)
       Port 1: 0000.0100 power
       Port 2: 0000.0100 power
        Per-port power switching
       Port 1: 0000.0100 power
       Port 2: 0000.0100 power
       Port 3: 0000.0100 power
       Port 4: 0000.0100 power
       Port 5: 0000.0100 power
       Port 6: 0000.0100 power
        No power switching (usb 1.0)
       Port 1: 0000.0507 highspeed power suspend enable connect
       Port 2: 0000.0100 power
        Per-port power switching
       Port 1: 0000.02a0 5Gbps power Rx.Detect
       Port 2: 0000.02a0 5Gbps power Rx.Detect
       Port 3: 0000.02a0 5Gbps power Rx.Detect
       Port 4: 0000.02a0 5Gbps power Rx.Detect
        No power switching (usb 1.0)
       Port 1: 0000.02a0 5Gbps power Rx.Detect
       Port 2: 0000.02a0 5Gbps power Rx.Detect
       Port 3: 0000.0263 5Gbps power suspend enable connect
       Port 4: 0000.02a0 5Gbps power Rx.Detect
       Port 5: 0000.02a0 5Gbps power Rx.Detect
       Port 6: 0000.0203 5Gbps power U0 enable connect
        Per-port power switching
       Port 1: 0000.0100 power
       Port 2: 0000.0100 power
       Port 3: 0000.0100 power
       Port 4: 0000.0100 power
        No power switching (usb 1.0)
       Port 1: 0000.0100 power
       Port 2: 0000.0100 power
       Port 3: 0000.0507 highspeed power suspend enable connect
       Port 4: 0000.0100 power
       Port 5: 0000.0100 power
       Port 6: 0000.0100 power
       Port 7: 0000.0100 power
       Port 8: 0000.0100 power
       Port 9: 0000.0103 power enable connect
       Port 10: 0000.0100 power
       Port 11: 0000.0100 power
       Port 12: 0000.0100 power
       Port 13: 0000.0103 power enable connect
       Port 14: 0000.0100 power
       Port 15: 0000.0100 power
    
    mintaka:/home/djviking # lsusb -vv|grep bHubContrCurrent
      bHubContrCurrent      0 milli Ampere
      bHubContrCurrent      0 milli Ampere
      bHubContrCurrent      0 milli Ampere
      bHubContrCurrent      0 milli Ampere
      bHubContrCurrent      0 milli Ampere
      bHubContrCurrent      0 milli Ampere
      bHubContrCurrent    400 milli Ampere
      bHubContrCurrent      0 milli Ampere
      bHubContrCurrent    100 milli Ampere
      bHubContrCurrent      0 milli Ampere
    
    mintaka:/home/djviking # hdparm -B /dev/sdc  
    
    /dev/sdc:
     APM_level      = not supported
    
    mintaka:/home/djviking # hdparm -M /dev/sdc   
    
    /dev/sdc:
     acoustic      = 254 (128=quiet ... 254=fast)
    mintaka:/home/djviking # hdparm -I /dev/sdc    
    
    /dev/sdc:
    
    ATA device, with non-removable media
            Model Number:       WDC WD1001FALS-00J7B0                    
            Serial Number:      WD-WMATV4034899
            Firmware Revision:  05.00K05
            Transport:          Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5
    Standards:
            Supported: 8 7 6 5  
            Likely used: 8
    Configuration:
            Logical         max     current
            cylinders       16383   16383
            heads           16      16
            sectors/track   63      63
            --
            CHS current addressable sectors:   16514064
            LBA    user addressable sectors:  268435455
            LBA48  user addressable sectors: 1953525168
            Logical/Physical Sector size:           512 bytes
            device size with M = 1024*1024:      953869 MBytes
            device size with M = 1000*1000:     1000204 MBytes (1000 GB)
            cache/buffer size  = unknown
    Capabilities:
            LBA, IORDY(can be disabled)
            Queue depth: 32
            Standby timer values: spec'd by Standard, with device specific minimum
            R/W multiple sector transfer: Max = 16  Current = 0
            Recommended acoustic management value: 128, current value: 254
            DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6  
                 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:
               *    SMART feature set
                    Security Mode feature set
               *    Power Management feature set
               *    Write cache
               *    Look-ahead
               *    Host Protected Area feature set
               *    WRITE_BUFFER command
               *    READ_BUFFER command
               *    NOP cmd
               *    DOWNLOAD_MICROCODE
                    Power-Up In Standby feature set
               *    SET_FEATURES required to spinup after power up
                    SET_MAX security extension
                    Automatic Acoustic Management feature set
               *    48-bit Address feature set
               *    Device Configuration Overlay feature set
               *    Mandatory FLUSH_CACHE
               *    FLUSH_CACHE_EXT
               *    SMART error logging
               *    SMART self-test
               *    General Purpose Logging feature set
               *    64-bit World wide name
               *    Segmented DOWNLOAD_MICROCODE
               *    Gen1 signaling speed (1.5Gb/s)
               *    Gen2 signaling speed (3.0Gb/s)
               *    Native Command Queueing (NCQ)
               *    Host-initiated interface power management
               *    Phy event counters
                    DMA Setup Auto-Activate optimization
               *    Software settings preservation
               *    SMART Command Transport (SCT) feature set
               *    SCT Read/Write Long (AC1), obsolete
               *    SCT Write Same (AC2)
               *    SCT Features Control (AC4)
               *    SCT Data Tables (AC5)
                    unknown 206[12] (vendor specific)
                    unknown 206[13] (vendor specific)
    Security:  
            Master password revision code = 65534
                    supported
            not     enabled
            not     locked
            not     frozen
            not     expired: security count
                    supported: enhanced erase
            194min for SECURITY ERASE UNIT. 194min for ENHANCED SECURITY ERASE UNIT.  
    Logical Unit WWN Device Identifier: 50014ee05710fa3f
            NAA             : 5
            IEEE OUI        : 0014ee
            Unique ID       : 05710fa3f
    Checksum: correct
    

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •