Sponsored Content
Operating Systems Solaris How to create new partitions in solaris,from the raw disk? Post 302202770 by incredible on Thursday 5th of June 2008 02:59:05 PM
Old 06-05-2008
then no issues,
just continue to create slice 4 5 6 and 7 , resize the partiton as needed. since u have not instALLED THE OS YET, u can re-format the whole drive (starting from cylinder 0 onwards), and so on.
eg
Part tag flag cylinders size
0 root wm 0 - 12 129.19MB
1 swap wu 13 - 25 129.19MB
2 backup wu 0 - 14086 136.71GB
3 unassigned wm 0 0
4 unassigned wm 0 0
5 unassigned wm 0 0
6 usr wm 26 - 14086 136.36GB
7 unassigned wm 0 0



The drive is already formatted. Just change the partitions using the format command -> par -> select slice -> label the disk and you are done.
Remember - partition 2 is the whole disk, don't change this partition!!
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

raw partitions

i want to know, how do i to create a rwa partttions in unixware 7 wit raid 5 best regards felix arteaga (1 Reply)
Discussion started by: farteaga
1 Replies

2. Filesystems, Disks and Memory

Problem setting up raw partitions on SUSE v8.0 using LVM on Oracle 8.1.7.URGENT!!!!!!

Hi all! Working on Oracle v8.1.7.0.0 with OS  as Suse v8.0 Linux. I had created LVM,linked raw devices to LVM as below: # for binding raw devices raw /dev/raw/raw1 /dev/oracle/sam_raw_system_251m raw /dev/raw/raw2 /dev/oracle/sam_raw_users_26m raw /dev/raw/raw3... (2 Replies)
Discussion started by: Amitstora
2 Replies

3. Solaris

Reading raw disk on Solaris

Hello I wonder if someone could help me in reading a raw (non-Solaris) disk on a Solaris system... I have an IDE HDD in my Sun Blade and would like to read it (using C). It appears on the system and with the format command shows up as c0t1d0. I use the dd command to read the disk as such:... (19 Replies)
Discussion started by: son_t
19 Replies

4. SCO

create disk partitions in sco

i have one 9 gb hdd having root 2 gb fs now i want to create additional 1gb fs in remaining space unix partation created in entired 9gb thanx (1 Reply)
Discussion started by: sudhir69
1 Replies

5. Solaris

How to create more partitions in x86 Solaris?

Friends, I have an 80 GB IDE hard disk on which I installed Solaris 10, the layout being Total size of the partition being 30 GB c0d0s0 = / directory = 15 GB c0d0s1 = swap file system = 1 GB c0d0s7 = /export/home directory = 1GB c0d0s8= boot c0d0s9 = alternates ... (3 Replies)
Discussion started by: saagar
3 Replies

6. Solaris

How to create mirror disk in solaris machine?

hi, I'm newbie in Solaris 10. can someone explain me the steps of how to create mirror disk in Solaris machine. thanks in advance (5 Replies)
Discussion started by: Wong_Cilacap
5 Replies

7. Solaris

Create a boot disk mirror on Solaris 10 x86

I’m setting up a boot disk mirror on Solaris 10 x86. I’m used to doing it on SPARC, where you can copy the partition table using fmthard. My x86 boot disk has 2 primary partitions, a Solaris one and a diagnostic one. Is there a way to copy those 2 primary partitions to the second disk without... (6 Replies)
Discussion started by: TKD
6 Replies

8. Solaris

Convert from raw disk to solaris volume manager disk

I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below: root@moneta # df -h Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 9.8G 513M 9.3G 6% / ... (0 Replies)
Discussion started by: fretagi
0 Replies

9. Solaris

Convert from raw disk to solaris volume manager disk

I have a solaris 10 system configured using NetApp as its storage, and the file systems are already configured as you can see from the example below: root@moneta # df -h Filesystem size used avail capacity Mounted on /dev/md/dsk/d0 9.8G 513M 9.3G 6% /... (4 Replies)
Discussion started by: fretagi
4 Replies

10. Solaris

SVM RAID5: Can an app access raw partitions?

I am using Solaris 9 (Sparc based) with Sybase and a proprietary DB application that works with Sybase. In the past we have not used SVM or any RAID config. The DBs were configured such that each DB had its own partition. Now I would like to setup a new machine with the DBs on a RAID5 config... (1 Reply)
Discussion started by: DavidC_SysEngr
1 Replies
BSDLABEL(8)						    BSD System Manager's Manual 					       BSDLABEL(8)

NAME
bsdlabel -- read and write BSD label SYNOPSIS
bsdlabel [-A] disk | -f file bsdlabel -w [-An] [-B [-b boot]] [-m machine] disk | -f file [type] bsdlabel -e [-An] [-B [-b boot]] [-m machine] disk | -f file bsdlabel -R [-An] [-B [-b boot]] [-m machine] [-f] disk | -f file protofile DESCRIPTION
The bsdlabel utility installs, examines or modifies the BSD label on a disk partition, or on a file containing a partition image. In addi- tion, bsdlabel can install bootstrap code. Disk Device Name When specifying the device (i.e., when the -f option is not used), the /dev/ path prefix may be omitted; the bsdlabel utility will automati- cally prepend it. General Options The -A option enables processing of the historical parts of the BSD label. If the option is not given, suitable values are set for these fields. The -f option tells bsdlabel that the program will operate on a file instead of a disk partition. The -n option stops the bsdlabel program right before the disk would have been modified, and displays the result instead of writing it. The -m machine argument forces bsdlabel to use a layout suitable for a different architecture. Current valid values are i386, amd64, and pc98. If this option is omitted, bsdlabel will use a layout suitable for the current machine. Reading the Disk Label To examine the label on a disk drive, use the form bsdlabel [-A] [-m machine] disk disk represents the disk in question, and may be in the form da0 or /dev/da0. It will display the partition layout. Writing a Standard Label To write a standard label, use the form bsdlabel -w [-An] [-m machine] disk [type] If the drive type is specified, the entry of that name in the disktab(5) file is used; otherwise, or if the type is specified as 'auto', a default layout is used. Editing an Existing Disk Label To edit an existing disk label, use the form bsdlabel -e [-An] [-m machine] disk This command opens the disk label in the default editor, and when the editor exits, the label is validated and if OK written to disk. Restoring a Disk Label From a File To restore a disk label from a file, use the form bsdlabel -R [-An] [-m machine] disk protofile The bsdlabel utility is capable of restoring a disk label that was previously saved in a file in ASCII format. The prototype file used to create the label should be in the same format as that produced when reading or editing a label. Comments are delimited by '#' and newline. Installing Bootstraps If the -B option is specified, bootstrap code will be read from the file /boot/boot and written to the disk. The -b boot option allows a different file to be used. FILES
/boot/boot Default boot image. /etc/disktab Disk description file. SAVED FILE FORMAT
The bsdlabel utility uses an ASCII version of the label when examining, editing, or restoring a disk label. The format is: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 81920 16 4.2BSD 2048 16384 5128 b: 1091994 81936 swap c: 1173930 0 unused 0 0 # "raw" part, don't edit If the -A option is specified, the format is: # /dev/da1c: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 51 tracks/cylinder: 19 sectors/cylinder: 969 cylinders: 1211 sectors/unit: 1173930 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 81920 16 4.2BSD 1024 8192 16 b: 160000 81936 swap c: 1173930 0 unused 0 0 # "raw" part, don't edit Lines starting with a '#' mark are comments. The partition table can have up to 8 entries. It contains the following information: # The partition identifier is a single letter in the range 'a' to 'h'. By convention, partition 'c' is reserved to describe the entire disk. size The size of the partition in sectors, K (kilobytes - 1024), M (megabytes - 1024*1024), G (gigabytes - 1024*1024*1024), % (percentage of free space after removing any fixed-size partitions other than partition 'c'), or * (all remaining free space after fixed-size and percentage partitions). For partition 'c', a size of * indicates the entire disk. Lowercase versions of suffixes K, M, and G are allowed. Size and suffix should be specified without any spaces between them. Example: 2097152, 1G, 1024M and 1048576K are all the same size (assuming 512-byte sectors). offset The offset of the start of the partition from the beginning of the drive in sectors, or * to have bsdlabel calculate the correct off- set to use (the end of the previous partition plus one, ignoring partition 'c'). For partition 'c', * will be interpreted as an off- set of 0. The first partition should start at offset 16, because the first 16 sectors are reserved for metadata. fstype Describes the purpose of the partition. The above example shows all currently used partition types. For UFS file systems and ccd(4) partitions, use type 4.2BSD. For Vinum drives, use type vinum. Other common types are swap and unused. By convention, partition 'c' represents the entire slice and should be of type unused, though bsdlabel does not enforce this convention. The bsdlabel utility also knows about a number of other partition types, none of which are in current use. (See the definitions starting with FS_UNUSED in <sys/disklabel.h> for more details.) fsize For 4.2BSD file systems only, the fragment size; see newfs(8). bsize For 4.2BSD file systems only, the block size; see newfs(8). bps/cpg For 4.2BSD file systems, the number of cylinders in a cylinder group; see newfs(8). EXAMPLES
Display the label for the first slice of the da0 disk, as obtained via /dev/da0s1: bsdlabel da0s1 Save the in-core label for da0s1 into the file savedlabel. This file can be used with the -R option to restore the label at a later date: bsdlabel da0s1 > savedlabel Create a label for da0s1: bsdlabel -w /dev/da0s1 Read the label for da0s1, edit it, and install the result: bsdlabel -e da0s1 Read the on-disk label for da0s1, edit it, and display what the new label would be (in sectors). It does not install the new label either in-core or on-disk: bsdlabel -e -n da0s1 Write a default label on da0s1. Use another bsdlabel -e command to edit the partitioning and file system information: bsdlabel -w da0s1 Restore the on-disk and in-core label for da0s1 from information in savedlabel: bsdlabel -R da0s1 savedlabel Display what the label would be for da0s1 using the partition layout in label_layout. This is useful for determining how much space would be allotted for various partitions with a labeling scheme using %-based or * partition sizes: bsdlabel -R -n da0s1 label_layout Install a new bootstrap on da0s1. The boot code comes from /boot/boot: bsdlabel -B da0s1 Install a new label and bootstrap. The bootstrap code comes from the file newboot in the current working directory: bsdlabel -w -B -b newboot /dev/da0s1 Completely wipe any prior information on the disk, creating a new bootable disk with a DOS partition table containing one slice, covering the whole disk. Initialize the label on this slice, then edit it. The dd(1) commands are optional, but may be necessary for some BIOSes to properly recognize the disk: dd if=/dev/zero of=/dev/da0 bs=512 count=32 fdisk -BI da0 dd if=/dev/zero of=/dev/da0s1 bs=512 count=32 bsdlabel -w -B da0s1 bsdlabel -e da0s1 This is an example disk label that uses some of the new partition size types such as %, M, G, and *, which could be used as a source file for ``bsdlabel -R ada0s1 new_label_file'': # /dev/ada0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 400M 16 4.2BSD 4096 16384 75 # (Cyl. 0 - 812*) b: 1G * swap c: * * unused e: 204800 * 4.2BSD f: 5g * 4.2BSD g: * * 4.2BSD DIAGNOSTICS
The kernel device drivers will not allow the size of a disk partition to be decreased or the offset of a partition to be changed while it is open. COMPATIBILITY
Due to the use of an uint32_t to store the number of sectors, BSD labels are restricted to a maximum of 2^32-1 sectors. This usually means 2TB of disk space. Larger disks should be partitioned using another method such as gpart(8). The various BSDs all use slightly different versions of BSD labels and are not generally compatible. SEE ALSO
ccd(4), geom(4), md(4), disktab(5), boot0cfg(8), fdisk(8), gpart(8), newfs(8) BSD
October 1, 2013 BSD
All times are GMT -4. The time now is 05:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy