10-01-2008
Quote:
Originally Posted by
admin@solaris
#sudo format
select your disk on which you have to make partition........
format> partition
print - check current status of your disk
modify - to create partition
Select partitioning base:
0. Current partition table (default)
1. All Free Hog
Choose base (enter number) [0]? 1
Part Tag Flag Cylinders Size Blocks
0 root wm 0 0 (0/0/0) 0
1 swap wu 0 0 (0/0/0) 0
2 backup wu 0 - 49149 60.00GB (49150/0/0) 125824000
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 usr wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
Do you wish to continue creating a new partition
table based on above table[yes]?
Free Hog partition[6]? 5
Enter size of partition '0' [0b, 0c, 0.00mb, 0.00gb]: 12gb
Enter size of partition '1' [0b, 0c, 0.00mb, 0.00gb]: 12gb
Enter size of partition '3' [0b, 0c, 0.00mb, 0.00gb]: 12gb
Enter size of partition '4' [0b, 0c, 0.00mb, 0.00gb]: 12gb
Enter size of partition '6' [0b, 0c, 0.00mb, 0.00gb]: 0gb
Enter size of partition '7' [0b, 0c, 0.00mb, 0.00gb]: 0gb
Part Tag Flag Cylinders Size Blocks
0 root wm 0 - 9830 12.00GB (9831/0/0) 25167360
1 swap wu 9831 - 19661 12.00GB (9831/0/0) 25167360
2 backup wu 0 - 49149 60.00GB (49150/0/0) 125824000
3 unassigned wm 19662 - 29492 12.00GB (9831/0/0) 25167360
4 unassigned wm 29493 - 39323 12.00GB (9831/0/0) 25167360
5 unassigned wm 39324 - 49149 11.99GB (9826/0/0) 25154560
6 usr wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
Okay to make this the current partition table[yes]? yes
Enter table name (remember quotes): new
Ready to label disk, continue? yes
After this we can create the file systems on each slice:
newfs /dev/rdsk/c0t0d0s and so on....
At this point we must create the mount points:
mkdir -p /mount/data (note -p makes the parent directories if they don't exist since
Now change ownership to oracle user for all file systems so oracle database can write to them:
sudo chown oracle:dba /mount/data
Finally, we're ready to edit the vfstab with the new entries:
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 2
no -
Now we can mount up the file systems:
sudo mount /mount/data
and now he has no OS on his disk!
The only guaranteed way to do this is to take a copy of your more important data and reinstall the OS, doing your relayout as you go along.
You can do this by running a backup to an external disk and then making the changes as listed above and then restoring your OS but in the long run yuor would be better to just reinstall.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need to know how to make a boot disk to get Solaris 7 to load on a intel machine.
I have checked out Sun.Com, but did not understand how to download and convert the files to a disk.
any help would be appericated
thanks
Bobby (2 Replies)
Discussion started by: Youngadmin
2 Replies
2. UNIX for Dummies Questions & Answers
Hello all,
I'm trying to recover from backup file to a new system with a new disk. I'm able to partition my new hard drive the same way as my old drive, but I'm unable to boot off of it. I have set the fdisk to toogle as a boot flag. But it does not seem to be working. Does anyone know how to... (4 Replies)
Discussion started by: larryase
4 Replies
3. HP-UX
Hi,
I was wondering if there was a way to change the disk device files ex. /dev/dsk/cxtxd0 ?
What I have are two HPUX 11.0 servers using MC Service Guard 11.13. A consultant attached a SAN and both servers had created the same identical LUN device files. Now I could begin creating my volume... (0 Replies)
Discussion started by: mvizza
0 Replies
4. Solaris
The second disk that I'm trying to make bootable is to hold another version of Solaris (9).
I've created the partitions with format and labeled the disk - created the filesystems with newfs - created and mounted the directories.
...but I think I've missed something out like using fdisk to... (16 Replies)
Discussion started by: pondlife
16 Replies
5. UNIX for Advanced & Expert Users
Hi All:
I am using an adaptor between a 1TB SATA hard drive and solaris 8 box with 68 pin scsi. I use the format utility to partition the HD which works fine but when I use newfs, I get some errors. I will place them below.
I have blocked and the error message is in red.
Anybody got any... (1 Reply)
Discussion started by: mndavies
1 Replies
6. Solaris
I attached a README file that I will refer to.
I successfully completed everything in the README file until step 4.
# pwd
/gani/gani-2.4.4
# ls
COPYING Makefile.macros gem.c
Makefile Makefile.sparc_gcc gem.h
Makefile.amd64_gcc ... (1 Reply)
Discussion started by: Bradj47
1 Replies
7. Solaris
Hi, I want to make sure a local disk c1t1d0s2 is not being used. SVM and VxVM are used on this Solaris 10 systems. This disk can not be found using 'df -k', 'metastat' and 'vxprint -ht'. But I can't mount it though format shows it contains ufs filesystem:
# mount /dev/dsk/c1t1d0s0 /mnt
Aug 18... (5 Replies)
Discussion started by: aixlover
5 Replies
8. SCO
Dear All,
I have a standalone desktop with SCO Openserver V 5, this is used to control a machine with custom written software. The problem is that the machine manufacturer has closed shop (bankruptcy) and there is no support on software.
As a precaution I would want to make a complete backup of... (3 Replies)
Discussion started by: iqbal_siddiqui
3 Replies
9. Ubuntu
hi all:
as we know , when usb flash disk plug in and aotu mounted , the default permission of the usb flash disk is 700. that means others have no permission . the question: how to make others have read/write permission when the aotu mounted usb flash disk pluge in ? thanks !! (0 Replies)
Discussion started by: arnold.king
0 Replies
10. Red Hat
Hello,
1 ) Fdisk -l # Displays all the disk with partition table information
My Query )
A ) How can i make one disk ex: /dev/sdd not visible in fdisk -l output ?
B) From where fdisk -l collect and display the information ? (8 Replies)
Discussion started by: saurabh84g
8 Replies
LEARN ABOUT OPENSOLARIS
fmthard
fmthard(1M) System Administration Commands 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
x86
fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c?
[t?] d?s2
DESCRIPTION
The fmthard command updates the VTOC (Volume Table of Contents) on hard disks and, on x86 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 x86 systems, fdisk(1M) must be run on the drive before fmthard.
If you are using an x86 system, note that the term ``partition'' in this page refers to slices within the x86 fdisk partition on x86
machines. Do not confuse the partitions created by fmthard with the partitions created by fdisk.
OPTIONS
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 - (a hyphen), fmthard reads
from standard input. The datafile format is described below. This option causes all of the disk partition 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 automatically 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 char-
acter (
). If the first character of a line is an asterisk (*), the line is treated as a comment. Each line is composed of entries
that are position-dependent, separated by white space and having the following 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 x86, 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 mount-
able 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.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
uname(1), format(1M), prtvtoc(1M), attributes(5)
x86 Only
fdisk(1M), installgrub(1M)
NOTES
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 two terabytes, fmthard cannot write a VTOC on an unlabeled disk. Use format(1M) for this purpose.
SunOS 5.11 25 Sep 2008 fmthard(1M)