Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Does formatting slice 2 (backup) destroy disk geometry? Post 302561666 by fpmurphy on Tuesday 4th of October 2011 10:15:49 PM
Old 10-04-2011
You did not physically destroy the disk. You destroyed any data that was in the various partitions on the disk by creating a filesystem on slice 2 which was set to span the whole disk. There is nothing stopping you using disk in the future.
 

9 More Discussions You Might Find Interesting

1. Solaris

mirroring the boot slice (slice 8) on x86

Hi there I am about to mirror a Solaris 10 x86 box (SunFire X4100) onto a secondary disk using svm (current system is one disk). My question is this, on X86 boxes there is a slice 8 defined as boot partition (and also a slice 9, dunno what its used for tho). Do I need to mirror this boot slice... (0 Replies)
Discussion started by: hcclnoodles
0 Replies

2. UNIX for Advanced & Expert Users

Mirroring Disk Geometry

How can one mirror disk geometry from one hard disk to another in Solaris. Is disk snapshot same as a mirror? Pls explain. (3 Replies)
Discussion started by: lexusujx
3 Replies

3. Solaris

Puzzled over over the relationship between the partition and geometry of hard disk.

Not sure why solaris couldn't detect the geometry of a hard disk which has a working OS of winxp pro. Is it due to the different OS that the partition information is stored in different location? When I type '"format" it is shown as below, c3d1 < drive type unknown>... (5 Replies)
Discussion started by: just.srad
5 Replies

4. Solaris

Ways to analyse root disk slice

Hi, Recently I faced with need of analyze root disk. I figured out two possible ways to do it: 1. Practical. Boot from CD and run format 2. Theoretical. Create live upgrade boot environment on another disk, activate it, reboot, unmont all root disk partitions and run format. I've already... (3 Replies)
Discussion started by: Sapfeer
3 Replies

5. Shell Programming and Scripting

Looking for help with script to assign all disk space to slice#0 on multiple disks of varying sizes

Hi Folks, I am trying to make a script to assign all diskspace to slice 0, on multiple sized disks. Since the disks are new they may need to be labelled also to avoid the error: Cannot get disk geometry Below is my code struggling with logic which doesn't seem to be producing the desired... (0 Replies)
Discussion started by: momin
0 Replies

6. Solaris

label a slice on disk erorr

Hi there, I am trying to do root volume mirroring on SunFire V210 server. I have two disks in it.First one is c1t0do and second one is c1t1do. Both disks already have partitions in them so I am deleting the partitions of second disk(c1t1do) using format command and selecting cylinder start 0... (2 Replies)
Discussion started by: newbi8321
2 Replies

7. Solaris

ZFS - whole disk Vs slice

we have a ZFS file system that was created as a pool of just one disk (raid on a SAN) when this was created it was done as a whole disk, and so EFI label. now we want to mount this file system into an LDOM. my understanding of how ldom's and disk works this is that we can only do this as a... (1 Reply)
Discussion started by: robsonde
1 Replies

8. Solaris

Trouble creating a disk partition slice (EFI)

Hi all, I am using SPARC Solaris 11.1 with EFI labelled disks. I am new to ZFS file systems and slightly stuck when trying to create a partition (slice) on one of my LUNs. EFI labels use sectors and blocks and I am not sure how exactly it works. From here I can try and create a... (2 Replies)
Discussion started by: selectstar
2 Replies

9. Solaris

ZFS Slice disk

Hi, How to to make a slice and define as ufs from zpool? Please advice me. Thanks. ---------- Post updated at 01:53 AM ---------- Previous update was at 12:24 AM ---------- Before slice: Part Tag Flag Cylinders Size Blocks 0 root wm 0 ... (2 Replies)
Discussion started by: mzainal
2 Replies
PREP(8) 						      System Manager's Manual							   PREP(8)

NAME
prep, format - prepare hard and floppy diskettes SYNOPSIS
disk/prep [ -ra ] special [ type ] disk/format [ -t type ] [ -f ] [ -d ] [ -b bfile ] [ -c csize ] [ -l label ] drive [ files ... ] DESCRIPTION
A partition table is stored on a hard disk to specify the division of the physical disk into a set of logical units. On Plan 9 the parti- tion table is a list of triples: name, starting sector, and ending sector. The kernel fabricates the first two partitions, disk and parti- tion; the disk partition records the starting and ending sectors for the whole disk, and the partition partition, typically the last sector on the disk, holds the partition table itself. Special is the maximal prefix of names of the logical units on the disk, for example #w/hd0. Prep reads and prints the associated parti- tion table and then enters a simple interactive mode to control editing the table. The options are: -r (read only) prohibits writing the table on disk. -a automatically create default partitions if no partition table already exists. These include partitions for DOS, a boot kernel, an NVRAM substitute, a kfs(4) file system, and, if room remains, a swap partition. Format prepares for use the floppy diskette in the disk file named drive, for example /dev/fd0disk. The options are: -f Do not physically format the disc. Used to install an MS-DOS filesystem on a previously formatted disc. With this option, drive can be a plain file. -t specify a density and type of disk to be prepared. The possible types are: 31/2DD 31/2" double density, 737280 bytes 31/2HD 31/2" high density, 1474560 bytes 51/4DD 51/4" double density, 368640 bytes 51/4HD 51/4" high density, 1146880 bytes The default is the highest possible on the device, unless -f is used, in which case the default is 31/2HD. -d add MS-DOS parameter block, file access table (FAT), and root directory to the start of the floppy. The remaining options have effect only when -d is specified: -b use the contents of bfile as the bootstrap block installed in sector 0. -c use a DOS cluster size of csize sectors when creating the DOS FAT. -l add a label when creating the DOS parameter block. Again under -d, any files listed are added, in order, to the root directory of the MS-DOS filesytem. The files are contiguously allocated and created with the READONLY attribute set. The file /sys/src/boot/pc/bb is an example of a suitable bfile to make the disk a boot disk. It gets loaded by the BIOS at 0x7C00, reads the root directory into address 0x7E00, and looks at the first root directory entry. If that file is called B.COM, it uses single sector reads to load the file into address 0x10000 and then jumps to the loaded file image. EXAMPLE
Create a Plan 9 boot floppy on a previously formatted diskette: disk/format -f -b bb -d /dev/fd0disk /386/b.com SOURCE
/sys/src/cmd/disk/prep.c /sys/src/cmd/disk/format.c /sys/src/boot/pc/bb.s SEE ALSO
floppy(3), wren(3), b.com(8) PREP(8)
All times are GMT -4. The time now is 03:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy