Sponsored Content
Full Discussion: OpenSolaris UFS Question
Operating Systems Solaris OpenSolaris UFS Question Post 302838323 by jlliagre on Monday 29th of July 2013 11:30:30 AM
Old 07-29-2013
@achenle You can't mount a whole disk (outside floppies and usb keys), only slices or partitions are mountable with disks that have a fdisk partition and/or a sun label. You method is right but one step is missing, i.e. extracting the slice to a file to be lofi mounted.

By the way, replacing the partition id to either 0x63 or 0x82 is indeed a mandatory prerequisite I already suggested in post #6 (although in decimal as fdisk reports it that way).
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

UFS partition

Hi all, I have FreeBSD and Debian in my HD, the FreeBSD partition is very small and I'd like to change. I try to use partition magic but it does not work with UFS parition. Anyone know a good partition software? (1 Reply)
Discussion started by: SeVEn
1 Replies

2. UNIX for Dummies Questions & Answers

solaris File system question ( UFS )

Hello all, I'm ufs file system, how can u use the same disk in another machine with the data in tact? to make it clear, I've an ufs FS in a mount point /file1 ( 8GB). now they decide to reintall the OS. After the reinstall, how can i get the same data as it is? will mounting the disk as /file1... (3 Replies)
Discussion started by: i2admin
3 Replies

3. Solaris

UFS Version

Hi, Can anyone help me. I would like to know the ufs version on solaris 7 & 8. Also i would like to know is there any command to verify it. Regards, Raja (1 Reply)
Discussion started by: RajaRC
1 Replies

4. Solaris

UFS logging

I have a couple of servers where something weird is going on. When I run the command "mount | grep logging" I get something similair to this / on /dev/dsk/c0t0d0s0 read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=220000 But when I look at /etc/vfstab I dont... (6 Replies)
Discussion started by: csaunders
6 Replies

5. AIX

Ufs

Hi i have 2 know the full details of unix file systems. some one please help me (1 Reply)
Discussion started by: sathish2win
1 Replies

6. Solaris

UFS filesystem mounted on 2 hosts question

I have two Unix (Solaris) hosts that are both attached to our SAN. They are both presented with the same luns. What I want to do is have the same UFS filesystem mounted on both hosts at the same time. What I am trying to accomplish is creating a zone that will reside on both hosts but only... (2 Replies)
Discussion started by: beaker457
2 Replies

7. Solaris

Zones not in ufs

Hi All, I am installing Solaris Kernel Update Patch 2.1 When I am installing , An error message is saying that Non Global Zones is not mounted in ufs. I have two non global zones. When i see in the vfstab , the filesystem in vxfs. I dont know whether it will give any impact... (2 Replies)
Discussion started by: jegaraman
2 Replies

8. Solaris

UFS defragmentation

is there any other/better way to defragment the ufs slice instead of backup+restore? how to tell which slice needs defragmenting? (2 Replies)
Discussion started by: orange47
2 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 04:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy