Skip to content
0
  • Recent
  • Tags
  • Popular
  • Search
  • ads.txt
  • Recent
  • Tags
  • Popular
  • Search
  • ads.txt
Collapse
Lime-it.us
  1. Home
  2. Categories
  3. Linux Systems
  4. Linux Systems Guides
  5. Spin up HDD in PUIS mode and wipe drive for new placement

Spin up HDD in PUIS mode and wipe drive for new placement

Scheduled Pinned Locked Moved Linux Systems Guides
shred commandhdparmcommand linewipe hard drivepuis
2 Posts 1 Posters 3.4k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • rickR Offline
    rickR Offline
    rick
    wrote on last edited by rick
    #1

    Recently I came across an older DVR unit, taking into consideration I’m not one to pass up an opportunity to harvest tech, so I took the liberties I had been granted.

    Just want the commands and take your chances? Skip down beyond my rambling.

    Not much useful inside most of these units, but there was a mechanical HDD.

    The drive is a WD5000AVVS, after a bit of googling around, I found Western Digital made these specifically for a DVR application. In other words, not really made to support a desktop environment. No reason to let that stop me from adding it for basic storage.


    The drive was utilizing PUIS or Power [Up In Standby] , something WD came up with themselves, from the wiki:

    Power-up in standby (PUIS) or power management 2 mode (PM2; Western Digital specific) is a SATA or Parallel ATA (aka PATA) hard disk configuration which prevents the drive from automatic spinup when power is applied. The spinup occurs later by an ATA command, only when the disk is needed, to conserve electric power[dubious – discuss] and to avoid a power consumption peak caused by a simultaneous spin-up of multiple disks.


    Useful tip: Since the drive will not power up on boot, I had to connect the drive to a raid controller to get it to spin up. I’m sure there are other means, such as issuing ATA commands.


    Set PUIS mode on Western Digital Hard Drive

    Enter the hdparm command , for help on commands just type in:

    hdparm
    
    hdparm - get/set hard disk parameters - version v9.43, by Mark Lord.
    
    Usage:  hdparm  [options] [device ...]
    
    Options:
     -a   Get/set fs readahead
     -A   Get/set the drive look-ahead flag (0/1)
     -b   Get/set bus state (0 == off, 1 == on, 2 == tristate)
     -B   Set Advanced Power Management setting (1-255)
     -c   Get/set IDE 32-bit IO setting
     -C   Check drive power mode status
     -d   Get/set using_dma flag
     -D   Enable/disable drive defect management
     -E   Set cd/dvd drive speed
     -f   Flush buffer cache for device on exit
     -F   Flush drive write cache
     -g   Display drive geometry
     -h   Display terse usage information
     -H   Read temperature from drive (Hitachi only)
     -i   Display drive identification
     -I   Detailed/current information directly from drive
     -J   Get/set Western DIgital "Idle3" timeout for a WDC "Green" drive (DANGEROUS)
     -k   Get/set keep_settings_over_reset flag (0/1)
     -K   Set drive keep_features_over_reset flag (0/1)
     -L   Set drive doorlock (0/1) (removable harddisks only)
     -m   Get/set multiple sector count
     -M   Get/set acoustic management (0-254, 128: quiet, 254: fast)
     -n   Get/set ignore-write-errors flag (0/1)
     -N   Get/set max visible number of sectors (HPA) (VERY DANGEROUS)
     -p   Set PIO mode on IDE interface chipset (0,1,2,3,4,...)
     -P   Set drive prefetch count
     -q   Change next setting quietly
     -Q   Get/set DMA queue_depth (if supported)
     -r   Get/set device readonly flag (DANGEROUS to set)
     -R   Get/set device write-read-verify flag
     -s   Set power-up in standby flag (0/1) (DANGEROUS)
     -S   Set standby (spindown) timeout
     -t   Perform device read timings
     -T   Perform cache read timings
     -u   Get/set unmaskirq flag (0/1)
     -U   Obsolete
     -v   Use defaults; same as -acdgkmur for IDE drives
     -V   Display program version and exit immediately
     -w   Perform device reset (DANGEROUS)
     -W   Get/set drive write-caching flag (0/1)
     -x   Obsolete
     -X   Set IDE xfer mode (DANGEROUS)
     -y   Put drive in standby mode
     -Y   Put drive to sleep
     -z   Re-read partition table
     -Z   Disable Seagate auto-powersaving mode
     --dco-freeze      Freeze/lock current device configuration until next power cycle
     --dco-identify    Read/dump device configuration identify data
     --dco-restore     Reset device configuration back to factory defaults
     --direct          Use O_DIRECT to bypass page cache for timings
     --drq-hsm-error   Crash system with a "stuck DRQ" error (VERY DANGEROUS)
     --fallocate       Create a file without writing data to disk
     --fibmap          Show device extents (and fragmentation) for a file
     --fwdownload            Download firmware file to drive (EXTREMELY DANGEROUS)
     --fwdownload-mode3      Download firmware using min-size segments (EXTREMELY DANGEROUS)
     --fwdownload-mode3-max  Download firmware using max-size segments (EXTREMELY DANGEROUS)
     --fwdownload-mode7      Download firmware using a single segment (EXTREMELY DANGEROUS)
     --idle-immediate  Idle drive immediately
     --idle-unload     Idle immediately and unload heads
     --Istdin          Read identify data from stdin as ASCII hex
     --Istdout         Write identify data to stdout as ASCII hex
     --make-bad-sector Deliberately corrupt a sector directly on the media (VERY DANGEROUS)
     --offset          use with -t, to begin timings at given offset (in GiB) from start of drive
     --prefer-ata12    Use 12-byte (instead of 16-byte) SAT commands when possible
     --read-sector     Read and dump (in hex) a sector directly from the media
     --security-help   Display help for ATA security commands
     --trim-sector-ranges        Tell SSD firmware to discard unneeded data sectors: lba:count ..
     --trim-sector-ranges-stdin  Same as above, but reads lba:count pairs from stdin
     --verbose         Display extra diagnostics from some commands
     --write-sector    Repair/overwrite a (possibly bad) sector directly on the media (VERY DANGEROUS)
    

    As we can see, there is a command we can utilize to change the PUIS setting of the drive:

    hdparm -s
    

    Of course you must enter the device name you wish to change the settings on. So we can use:

    lsblk
    

    The lsblk command will list all block devices in the system

    Which in this case spits out the following:

    NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
    sda      8:0    0 465.8G  0 disk 
    └─sda1   8:1    0 465.8G  0 part 
    sdb      8:16   0 465.8G  0 disk 
    └─sdb1   8:17   0 465.8G  0 part /media/rick/WD500GB
    sdc      8:32   0 465.8G  0 disk 
    └─sdc2   8:34   0     1K  0 part
    

    This is now that the drive is finished, formatted and partitioned in the system. Sometimes you’ll need a bit more data to make the choice as to which drive you’ll be schnookering.

    So we can use lsblk flags as well.

    lsblk --output MODE,NAME,FSTYPE,LABEL,UUID
    

    Which spits out the following infos:

    MODE       NAME   FSTYPE          LABEL   UUID
    brw-rw---- sda    isw_raid_member         
    brw-rw---- └─sda1                         
    brw-rw---- sdb                            
    brw-rw---- └─sdb1 ext4            WD500GB 4e423629-51e8-41b3-a9be-9c9af4d31732
    brw-rw---- sdc    isw_raid_member         
    brw-rw---- └─sdc2 
    

    Well I know the two disks which say raid member are not it, and at this point there is only three block devices in the system, so I’ll use /dev/sdb

    If we look at the hdparm command to turn on or off PUIS, it states the two options which are 0/1 = Off or On

    So the command I’ll run on /dev/sdb to wake it up with hdparm is:

    hdparm -s 0 /dev/sdb
    

    Done with that jazz. The drive should spin up when powered on. Lest, we are not finished here. We should clean things up a bit.


    For simplicity I enjoy the shred command, plus it sounds serious, which it is.

    To find shred commands, we just run:

    shred --help
    

    Which pukes out this:

    Usage: shred [OPTION]... FILE...
    Overwrite the specified FILE(s) repeatedly, in order to make it harder
    for even very expensive hardware probing to recover the data.
    
    Mandatory arguments to long options are mandatory for short options too.
      -f, --force    change permissions to allow writing if necessary
      -n, --iterations=N  overwrite N times instead of the default (3)
          --random-source=FILE  get random bytes from FILE
      -s, --size=N   shred this many bytes (suffixes like K, M, G accepted)
      -u, --remove[=HOW]  truncate and remove file after overwriting; See below
      -v, --verbose  show progress
      -x, --exact    do not round file sizes up to the next full block;
                       this is the default for non-regular files
      -z, --zero     add a final overwrite with zeros to hide shredding
          --help     display this help and exit
          --version  output version information and exit
    

    Remember, this can be done on any drive, so everything and anything will be lost to the abyss forever. Pay attention to which drive letter / name you are using.

    The default pass is 25 times, yea, I’ve never needed a 25 pass random write scrub and I hope never to. So we can use the flag -n to limit how many passes shred does.

    I enjoy seeing output, so I’ll use the -v or, Verbose / noisy output flag as well.

    I also had no idea what permissions were set, so I used the -f or Force flag As stated, this changes permissions to allow for the write procedure if required.

    If your obsessive about keeping things straight, use the -z flag also, this will add one more pass after ‘shredding’ and write zero’s across the drive. Instead of having the drive look as if someone intentionally randomly repeatedly wrote ‘junk’ to it. Just make your bed.

    The command I used to wipe the drive was as follows:

    shred -n 5 -v -f -z /dev/sdb 
    

    Let the shredding begin, here is the initial output:

    shred: /dev/sdb: pass 1/6 (random)...
    shred: /dev/sdb: pass 1/6 (random)...330MiB/466GiB 0%
    shred: /dev/sdb: pass 1/6 (random)...687MiB/466GiB 0%
    shred: /dev/sdb: pass 1/6 (random)...1.0GiB/466GiB 0%
    shred: /dev/sdb: pass 1/6 (random)...1.3GiB/466GiB 0%
    shred: /dev/sdb: pass 1/6 (random)...1.7GiB/466GiB 0%
    shred: /dev/sdb: pass 1/6 (random)...2.1GiB/466GiB 0%
    shred: /dev/sdb: pass 1/6 (random)...2.4GiB/466GiB 0%
    shred: /dev/sdb: pass 1/6 (random)...2.8GiB/466GiB 0%
    shred: /dev/sdb: pass 1/6 (random)...3.1GiB/466GiB 0%
    

    And this goes on for quite some time. Notice we used the -n 5 flag, for five passes, yet we can see shred is currently on pass 1/6. Good, this means the last pass will be all zeros.

    Go do something else until your ready to format and partition the drive. Let it run!

    1 Reply Last reply
    0
    • rickR Offline
      rickR Offline
      rick
      wrote on last edited by rick
      #2

      For a more comprehensive or detailed guide, as to securely wiping a drive, visit nixCraft-how-do-i-permanently-erase-hard-disk

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      FreeBSD Notes
      • rickR
        rick

        redis.png

        Create a shell script that will dump the Redis database

        cd ~ mkdir redi-backups-script cd redis-backups-script nano redis_backups-script.sh

        Paste the script below:

        #!/bin/bash rdb_file="/Place-directory-of-rdb-here/redis/dump.rdb" redis_cli="/usr/bin/redis-cli" DIR=`date +%d-%m-%y` DEST=~/redis_backups/$DIR mkdir $DEST echo save| $redis_cli exit 1

        Set script to executable:

        chmod +x ~/scripts/redis_backups-script.sh

        Create a cron to run daily:

        Then create a cron job to run the script every day at midnight:

        crontab -e 0 0 * * * ~/redis-backups-script/redis_backup.sh

        Restore RDB backup

        Disable Append Only in the config:

        nano /etc/redis/redis.conf appendonly no

        Stop redis:

        sudo service redis-server stop

        Restore the redis backup:

        rename the rdb file you wish sudo cp /home/redis/dump.rdb /home/redis/dump.rdb.bak

        You can then copy the backup rdb file as follows:

        sudo cp /redis_backups/------/dump.rdb /home/redis/dump.rdb

        Apply the proper permissions to the dump.rdb file:

        sudo chmod 660 /home/redis/dump.rdb

        Re-starting Redis server

        sudo service redis-server start
        read more

      • rickR
        rick

        Install Zabbix 7.2 repo

        wget https://repo.zabbix.com/zabbix/7.2/release/debian/pool/main/z/zabbix-release/zabbix-release_latest_7.2+debian12_all.deb

        zab1.png

        dpkg -i zabbix-release_latest_7.2+debian12_all.deb

        zab2.png

        Update repos

        apt update

        zab3.png

        Install Zabbix server and frontend

        apt install zabbix-server-mysql zabbix-frontend-php zabbix-nginx-conf zabbix-sql-scripts zabbix-agent2

        zab4.png

        Install plugins

        apt install zabbix-agent2-plugin-mongodb zabbix-agent2-plugin-mssql zabbix-agent2-plugin-postgresql

        zab5.png

        Install mysql

        wget https://dev.mysql.com/get/mysql-apt-config_0.8.30-1_all.deb

        zab-6sql.png

        sudo dpkg -i mysql-apt-config_0.8.30-1_all.deb

        Error on this new install, where lsb-release is not installed

        zab7sql-error.png

        apt-get install lsb-release

        zab7lsb.png

        Try again…

        dpkg -i mysql-apt-config_0.8.30-1_all.deb

        Error, gnupg not installed

        zab7gnupgerror.png

        apt install gnupg2

        zab7gnupg2.png

        Give it another go…

        dpkg -i mysql-apt-config_0.8.30-1_all.deb

        zab7sqltui.png

        zab7sql.png

        I had to list upgradable packages :

        apt-list --upgradable

        Which spit out : mysql-common/unknown 8.4.4-1debian12 all [upgradable from: 5.8+1.1.0]

        Then installed mysql-common

        apt-get install mysql-common

        zabbix-7-sqlgoofs.png

        Had to uninstall Mariadb to resolve these conflicts

        apt remove mariadb-client-core

        Then install mysql-server:

        apt install mysql-server

        zab7-sql-common.png

        zab7-sql-rootpass.png

        Enter your password, twice

        Now enter mysql by typing :

        mysql -u root -p

        zab7-mysql-enter.png

        Enter the following command individually Where ‘password’ is where you type in your actual own password

        mysql> create database zabbix character set utf8mb4 collate utf8mb4_bin; mysql> create user zabbix@localhost identified by 'password'; mysql> grant all privileges on zabbix.* to zabbix@localhost; mysql> set global log_bin_trust_function_creators = 1; mysql> quit;

        Populate the database with zabbix script

        zcat /usr/share/zabbix/sql-scripts/mysql/server.sql.gz | mysql --default-character-set=utf8mb4 -uzabbix -p zabbix mysql --u root -p set global log_bin_trust_function_creators = 0; quit;

        Edit file /etc/zabbix/zabbix_server.conf You can use nano

        nano /etc/zabbix/zabbix_server.conf

        Uncomment the DBPassword section, and type your password

        zabbix-dbpassword.png

        Then hold ctrl and tap x, it will ask if you want to save changes.

        Enable services:

        systemctl enable zabbix-server zabbix-agent2 nginx php8.2-fpm systemctl restart zabbix-server zabbix-agent2 nginx php8.2-fpm

        Check that zabbix service has started

        journalctl -xeu zabbix-server.service

        zabbix7startjob.png

        Delete the 'default site in nginx

        sudo rm -rf /etc/nginx/sites-enabled/default

        Make sure the symbolic link to the zabbix nginx file is present

        ln -s /etc/zabbix/nginx.conf /etc/nginx/sites-enabled/zabbix.conf

        Check that the zabbix nginx file is in the includes in nginx config

        nano /etc/nginx/nginx.conf

        Look for :

        include /etc/nginx/sites-enabled/*

        Now restart nginx

        systemctl restart nginx

        Hit the browser and type in the IP (or URL that you may have put in the zabbix nginx config file)

        zabbix.png

        Make sure to configure locales

        zabbix-locales.png

        sudo dpkg-reconfigure locales

        zabbixlocalestui.png

        zabbix-locales-2.png

        zabbix-locales-command.png

        Reboot the system

        sudo shutdown -r now

        zabbix-utf.png

        Add your database password

        zabbix-db.png

        Add a server name

        zabbix-servername.png

        zabbix-summary.png

        zabbix-config.png

        The default username is Admin, and the password is zabbix

        zabbix-home.png

        read more

      • rickR
        rick
        Unable to negotiate with 10.10.1.35 port 22: no matching host key type found. Their offer: ssh-rsa,ssh-dss

        While attempting ssh this error is generally due to mismatched versions of ssh, where an up to date version is attempting to access an older version

        Add the following to your command :

        The proper way:

        ssh -o KexAlgorithms=diffie-hellman-group14-sha1 -oHostKeyAlgorithms=+ssh-dss 10.10.1.35

        The cheap way:

        Example :

        ssh -oHostKeyAlgorithms=+ssh-dss 10.10.1.35

        or ssh -oHostKeyAlgorithms=+ssh-dss user@10.10.1.35

        This can be added to the ~/.ssh/config file

        Host my-server HostName 10.10.1.35 HostKeyAlgorithms=+ssh-dss
        read more

      • rickR
        rick

        Locate hard drive and get information

        ls -l /sys/block | grep sd.

        Output:

        lrwxrwxrwx 1 root root 0 Jun 22 06:28 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Jun 22 06:28 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Jun 22 06:28 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdc lrwxrwxrwx 1 root root 0 Jun 22 06:28 sdd -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd

        Or for a more detailed view

        strace -e trace=open lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 3.6T 0 disk ├─data--2-data--2_tmeta 252:3 0 15.9G 0 lvm │ └─data--2-data--2-tpool 252:9 0 3.6T 0 lvm │ ├─data--2-data--2 252:10 0 3.6T 1 lvm │ ├─data--2-vm--101--disk--0 252:11 0 8G 0 lvm │ ├─data--2-vm--103--disk--0 252:12 0 32G 0 lvm │ ├─data--2-vm--107--disk--0 252:13 0 500G 0 lvm │ └─data--2-vm--108--disk--0 252:20 0 100G 0 lvm └─data--2-data--2_tdata 252:6 0 3.6T 0 lvm └─data--2-data--2-tpool 252:9 0 3.6T 0 lvm ├─data--2-data--2 252:10 0 3.6T 1 lvm ├─data--2-vm--101--disk--0 252:11 0 8G 0 lvm ├─data--2-vm--103--disk--0 252:12 0 32G 0 lvm ├─data--2-vm--107--disk--0 252:13 0 500G 0 lvm └─data--2-vm--108--disk--0 252:20 0 100G 0 lvm sdb 8:16 0 698.6G 0 disk └─sdb1 8:17 0 698.6G 0 part /mnt/pve/backups sdc 8:32 0 3.6T 0 disk ├─vm--data-vm--data_tmeta 252:4 0 15.9G 0 lvm │ └─vm--data-vm--data-tpool 252:14 0 3.6T 0 lvm │ ├─vm--data-vm--data 252:15 0 3.6T 1 lvm │ ├─vm--data-vm--100--disk--0 252:16 0 270G 0 lvm │ ├─vm--data-vm--102--disk--0 252:17 0 100G 0 lvm │ ├─vm--data-vm--104--disk--0 252:18 0 25G 0 lvm │ └─vm--data-vm--106--disk--0 252:19 0 32G 0 lvm └─vm--data-vm--data_tdata 252:7 0 3.6T 0 lvm └─vm--data-vm--data-tpool 252:14 0 3.6T 0 lvm ├─vm--data-vm--data 252:15 0 3.6T 1 lvm ├─vm--data-vm--100--disk--0 252:16 0 270G 0 lvm ├─vm--data-vm--102--disk--0 252:17 0 100G 0 lvm ├─vm--data-vm--104--disk--0 252:18 0 25G 0 lvm └─vm--data-vm--106--disk--0 252:19 0 32G 0 lvm sdd 8:48 0 931.5G 0 disk ├─sdd1 8:49 0 1007K 0 part ├─sdd2 8:50 0 1G 0 part └─sdd3 8:51 0 930.5G 0 part ├─pve-swap 252:0 0 8G 0 lvm [SWAP] ├─pve-root 252:1 0 96G 0 lvm / ├─pve-data_tmeta 252:2 0 8.1G 0 lvm │ └─pve-data 252:8 0 794.3G 0 lvm └─pve-data_tdata 252:5 0 794.3G 0 lvm └─pve-data 252:8 0 794.3G 0 lvm +++ exited with 0 +++ cat /proc/partitions major minor #blocks name 8 0 3907018584 sda 8 16 732574584 sdb 8 17 732572672 sdb1 8 32 3907018584 sdc 8 48 976762584 sdd 8 49 1007 sdd1 8 50 1048576 sdd2 8 51 975712967 sdd3 252 0 8388608 dm-0 252 1 100663296 dm-1 252 2 8495104 dm-2 252 3 16650240 dm-3 252 4 16650240 dm-4 252 6 3873329152 dm-6 252 5 832888832 dm-5 252 7 3873329152 dm-7 252 8 832888832 dm-8 252 9 3873329152 dm-9 252 10 3873329152 dm-10 252 11 8388608 dm-11 252 12 33554432 dm-12 252 13 524288000 dm-13 252 14 3873329152 dm-14 252 15 3873329152 dm-15 252 16 283115520 dm-16 252 17 104857600 dm-17 252 18 26214400 dm-18 252 19 33554432 dm-19 252 20 104857600 dm-20

        Locate drive by serial and model information

        hdparm -i /dev/sda /dev/sda: Model=WDC WD4000FYYZ-05UL1B0, FwRev=00.0NS05, SerialNo=WD-WCC132262513 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0 BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=7814037168 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 AdvancedPM=yes: unknown setting WriteCache=disabled Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7 * signifies the current active mode
        read more

      • rickR
        rick

        Screen recording can use webm as their format, it can be more simple to use a gif to embed into a website or forum, than adding scripts to host different video format.

        In this case I grabbed a screen record of the progress for writing zeros to a hard drive with dd

        Use ffmpeg to convert webm to gif:

        First create a pallet:

        Move into the directory which the webm is located, or type in the path

        Where ‘dd.webm’ is the screen recording

        ffmpeg -y -i dd.webm -vf palettegen palette.png

        Output:

        dd-ffmpeg.png

        Then convert the webm to gif:

        ffmpeg -y -i dd.webm -i palette.png -filter_complex paletteuse -r 10 dd.gif

        dd-webm-2.png

        This is what I ended up with, looks like any image of any alien on the interwebz, as if shot through a potato, some tweaking of the command is in my future. None the less.

        dd.gif

        read more
      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post