Wipeout - NonStop_Decommission_Disks_Sanitization

[magomes]

My customer requested a procedure to Wipeout all Disks including $SYSTEM.

I did several research and did not find a solution that give the option to do this without moving $SYSTEM to another server.

So, finally I found a way, and if someone is interested on this topic, ping me and or let me know if needs to me to upload here the solution, I'll be happy to share it.

[Thaufique_Mod]

Hello @magomes,

Thank you so much for taking the time to research and find a solution to such a complex and critical task. Your dedication and willingness to go the extra mile, especially with a challenge like wiping all disks, including $SYSTEM, is truly appreciated.

I’m grateful for your offer to share the solution — that kind of collaboration and knowledge sharing is what helps everyone grow. Please do upload it when you can; I’m sure many of us would benefit from your insights.

Thanks again for your hard work and generosity!

[magomes]

Preliminary Implementation Section / Step 1

    Get Customer approved to access the Site console

• Login to Storage OSM Low Level application root user and check “Processor Status”

    Make sure All CPU's are not running NSK

    Connect to Storage CLIM and check the local discs configuration

• Login to Storage CLIM using PuTTY root user using the Factory IP assigned to Storage CLIM

Output Example: (LAB Example)

• Login to Storage CLIM using PuTTY root user

S1002531(%DEFAULT):~# df

Filesystem           1K-blocks      Used Available Use% Mounted on

/dev/sda1            276645940   3765944 258827140   2% /

tmpfs                  1696628         0   1696628   0% /lib/init/rw

udev                   1690828       412   1690416   1% /dev

tmpfs                  1696628       144   1696484   1% /dev/shm

S1002531(%DEFAULT):~#

Connect to Storage CLIM and check the disks available to NonStop use

Login to Storage CLIM using PuTTY root user

Output Example: 

S1002531(%DEFAULT):~# fdisk -l |grep Disk

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sdc doesn't contain a valid partition table

Disk /dev/sdd doesn't contain a valid partition table

Disk /dev/sde doesn't contain a valid partition table

Disk /dev/sdf doesn't contain a valid partition table

Disk /dev/sdg doesn't contain a valid partition table

Disk /dev/sdh doesn't contain a valid partition table

Disk /dev/sdi doesn't contain a valid partition table

Disk /dev/sdj doesn't contain a valid partition table

Disk /dev/sdk doesn't contain a valid partition table

Disk /dev/sdl doesn't contain a valid partition table

Disk /dev/sdm doesn't contain a valid partition table

Disk /dev/sdn doesn't contain a valid partition table

Disk /dev/sdo doesn't contain a valid partition table

Disk /dev/sda: 300.0 GB, 299959511040 bytes

Disk identifier: 0x00051f5d

Disk /dev/sdb: 146.8 GB, 146815737856 bytes

Disk identifier: 0x00000000

Disk /dev/sdc: 146.8 GB, 146815737856 bytes

Disk identifier: 0x00000000

. . .

. All disks but /dev/sda and /dev/sda1 that is local CLIM OS disk, can be added to the script to be formated

Prepare and run the script commands to execute the shred command

• Login to Storage CLIM using PuTTY root user

             shred command example:

S1002531(%DEFAULT):~# shred -vfz /dev/sdz 

• Output example:

S1002531(%DEFAULT):~# shred -vfz /dev/sdz

shred: /dev/sdz: pass 1/4 (random)...

shred: /dev/sdz: pass 1/4 (random)...641MiB/137GiB 0%

shred: /dev/sdz: pass 1/4 (random)...1.2GiB/137GiB 0%

shred: /dev/sdz: pass 1/4 (random)...1.3GiB/137GiB 0%

shred: /dev/sdz: pass 1/4 (random)...1.9GiB/137GiB 1%

shred: /dev/sdz: pass 1/4 (random)...2.0GiB/137GiB 1%

• Execution time:

Average of 1 hour per disk

• Script used to test and aproved by Customer, and needs to be updated depending on the result found on the Preliminary Step:

for i in {b..z}; do

        echo "Start Date /dev/sd${i} `date`" > sd${i}_purge.log

shred -vfz /dev/sd${i} >> sd${i}_purge.log 2>&1

echo "Stop Date /dev/sd${i} `date`" >> sd${i}_purge.log

echo "Start Date /dev/sdaa `date`" > sdaa_purge.log

shred -vfz /dev/sdaa >> sdaa_purge.log 2>&1

echo "Stop Date /dev/sdaa `date`" >> sdaa_purge.log

echo "Start Date /dev/sda${i} `date`" > sda${i}_purge.log

shred -vfz /dev/sda${i} >> sda${i}_purge.log 2>&1

echo "Stop Date /dev/sda${i} `date`" >> sda${i}_purge.log

echo "Start Date /dev/sdb${i} `date`" > sdb${i}_purge.log

shred -vfz /dev/sdb${i} >> sdb${i}_purge.log 2>&1

echo "Stop Date /dev/sdb${i} `date`" >> sdb${i}_purge.log

done

PS: 

Command to execute the script background:

./script_name &

Connect to Storage CLIM and check the disks available to NonStop status

S1002531(%DEFAULT):~# fdisk -l

Disk /dev/sda: 300.0 GB, 299959511040 bytes

255 heads, 63 sectors/track, 36468 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00051f5d

   Device Boot      Start         End      Blocks   Id  System

/dev/sda1   *           1       34990   281057143+  83  Linux

/dev/sda2           34991       36468    11872035    5  Extended

/dev/sda5           34991       36468    11872003+  82  Linux swap / Solaris

Disk /dev/sdbb: 146.8 GB, 146815737856 bytes

255 heads, 63 sectors/track, 17849 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x00000000

. All disks but /dev/sda that is local CLIM OS disk, shows as “Disk identifier: 0x00000000”

PS: Aditionally if your Customer request to wipe out CLIM local disk you can use iLO and Initialize local disks