Sponsored Content
Full Discussion: Wipe a Sunfire V480
Operating Systems Solaris Wipe a Sunfire V480 Post 302272238 by slowatsch on Tuesday 30th of December 2008 03:22:03 AM
Old 12-30-2008
Thank you really much for your help. Well my first thought was to boot from a external CD and run a program like dban (Darkis Boot and Nuke). Is there any advantage of the format / fmthard commands?


ps. whould be nice to have a command like "selfdestruct" :P
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

V480 w/ Solaris 9 boot problem

Our V480 w/ Solaris 9 would not boot properly. After recreating the LUNs on our StorEdge A1000, and then performing a reboot, the machine just keep cycling through the boot process. No error messages, it keeps trying to reboot over and over again. Any ideas? We managed to do a stop+a and... (6 Replies)
Discussion started by: xnightcrawl
6 Replies

2. Solaris

What do you use to wipe your disks?

What are y'all using to wipe your solaris disks? I am being question by IT Security, what I am using to wipe disk. Is anyone using a 3rd party utility? I have used the format utility in solaris previously. But they are looking for something commercial that I can use. Anyone have... (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

3. Solaris

Telnet issue E5500/V480

Our old E5500 was just turned off (planned :rolleyes: ) and the application was moved to a V480. Now if I login to the V480 and try to sudo to root my connection hangs, and I can not telnet to the E5500 after it was powered on again. I get "connection refused". Telnet to this machine was... (5 Replies)
Discussion started by: kjbaumann
5 Replies

4. Solaris

PCI slot info on V480/V490

Hi, How can I know slot wise info on a sun v480 box. I want to have the details like which slot has which card (slot 1- HBA, slot 2 - quad NIC) .. I know that sysdef, prtconf or prtdiag outputs will help to get this. But I dont know how to conclude from those outputs. Can anybody help me to... (4 Replies)
Discussion started by: vasu2020
4 Replies

5. UNIX for Dummies Questions & Answers

Reommendations for hp-ux wipe software

I am looking for software to do DoD compiliant wipes on Hp-Ux. Thank you in advance for any recommendations provided. (1 Reply)
Discussion started by: jim15800
1 Replies

6. UNIX for Advanced & Expert Users

Wipe software for Hp-ux

I am looking for recommendations on DOD compliante software to wipe disk on HP-UX. Any recommendations would be appreciated. Thank you in advance for any assistance provided. (1 Reply)
Discussion started by: jim15800
1 Replies

7. Solaris

Solaris 8 on v480 & v490

Hello, Can any kind soul please answer this? I want to boot a SunFire v490 with a dvd image we use to boot v480's. Is this possible? Are there caveats to doing this? Thanks muchly, mgb (1 Reply)
Discussion started by: mgb
1 Replies

8. Cybersecurity

How do I wipe stdout?

Today I used Terminal (invoked from Mac OS X 10.4.11) to view some data that is secured by a password. After exiting Terminal, it occurred to me that a vestige of the data displayed on my screen might reside in memory or in disk file ... the actual file used for stdout, for example. Do I need... (1 Reply)
Discussion started by: dcollins
1 Replies

9. HP-UX

Wipe tool for HP-UX

Hi, Please suggest wipe tool for hp-ux. (2 Replies)
Discussion started by: manoj.solaris
2 Replies

10. Solaris

Solaris box completely wipe

HI, I woluld like to know is it possible to boot solairs into single usermode from cd and using format -> purge command to wipe all the disk? please suggest or any other method ? my requirement is to completely wipe solaris box. (4 Replies)
Discussion started by: manoj.solaris
4 Replies
fmthard(1M)															       fmthard(1M)

NAME
fmthard - populate label on hard disks SYNOPSIS
SPARC fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 The fmthard command updates the VTOC (Volume Table of Contents) on hard disks and, on systems, adds boot information to the Solaris fdisk partition. One or more of the options -s datafile, -d data, or -n volume_name must be used to request modifications to the disk label. To print disk label contents, see prtvtoc(1M). The /dev/rdsk/c?[t?]d?s2 file must be the character special file of the device where the new label is to be installed. On systems, fdisk(1M) must be run on the drive before fmthard. If you are using an system, note that the term ``partition'' in this page refers to slices within the fdisk partition on machines. Do not confuse the partitions created by fmthard with the partitions created by fdisk. The following options are supported: -d data The data argument of this option is a string representing the information for a particular partition in the current VTOC. The string must be of the format part:tag:flag:start:size where part is the partition number, tag is the ID TAG of the partition, flag is the set of permission flags, start is the starting sector number of the partition, and size is the number of sectors in the partition. See the description of the datafile below for more information on these fields. -i This option allows the command to create the desired VTOC table, but prints the information to standard output instead of modifying the VTOC on the disk. -n volume_name This option is used to give the disk a volume_name up to 8 characters long. -s datafile This option is used to populate the VTOC according to a datafile created by the user. If the datafile is "-", fmthard reads from standard input. The datafile format is described below. This option causes all of the disk par- tition timestamp fields to be set to zero. Every VTOC generated by fmthard will also have partition 2, by convention, that corresponds to the whole disk. If the input in datafile does not specify an entry for partition 2, a default partition 2 entry will be created auto- matically in VTOC with the tag V_BACKUP and size equal to the full size of the disk. The datafile contains one specification line for each partition, starting with partition 0. Each line is delimited by a new-line character ( ). If the first character of a line is an asterisk (*), the line is treated as a com- ment. Each line is composed of entries that are position-dependent, separated by "white space" and having the fol- lowing format: partition tag flag starting_sector size_in_sectors where the entries have the following values: partition The partition number. Currently, for Solaris SPARC, a disk can have up to 8 partitions, 0-7. Even though the partition field has 4 bits, only 3 bits are currently used. For , all 4 bits are used to allow slices 0-15. Each Solaris fdisk partition can have up to 16 slices. tag The partition tag: a decimal number. The following are reserved codes: 0 (V_UNASSIGNED), 1 (V_BOOT), 2 (V_ROOT), 3 (V_SWAP), 4 (V_USR), 5 (V_BACKUP), 6 (V_STAND), 7 (V_VAR), and 8 (V_HOME). flag The flag allows a partition to be flagged as unmountable or read only, the masks being: V_UNMNT 0x01, and V_RONLY 0x10. For mountable partitions use 0x00. starting_sector The sector number (decimal) on which the partition starts. size_in_sectors The number (decimal) of sectors occupied by the partition. You can save the output of a prtvtoc command to a file, edit the file, and use it as the datafile argument to the -s option. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ uname(1), format(1M), prtvtoc(1M), attributes(5) Only fdisk(1M), installgrub(1M) Special care should be exercised when overwriting an existing VTOC, as incorrect entries could result in current data being inaccessible. As a precaution, save the old VTOC. For disks under one terabyte, fmthard cannot write a VTOC on an unlabeled disk. Use format(1M) for this purpose. 11 Apr 2005 fmthard(1M)
All times are GMT -4. The time now is 09:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy