Sponsored Content
Operating Systems Solaris Problems cloning Solaris 10 x86 Installation to bigger HDD Post 302750813 by BigT79 on Wednesday 2nd of January 2013 02:12:28 PM
Old 01-02-2013
Problems cloning Solaris 10 x86 Installation to bigger HDD

Dear All,

I have been trying to move my existing Solaris Installation (x86, 10/08) to a bigger HDD.

So I created a 22 cylinder boot partition and used the rest of the space for a Solaris2 partition. Then I created slices same size like on my current disk.

I copied all files with cpio and now I'm stuck.

I was following a tutorial, which seems to be for Solaris 8. Can't post the link, yet.
[u

Please can anybody tell me how I'll get my new HDD bootable?

Thank you very much in advance

Cheers

BigT
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to prepare HDD for Installation of Solaris

Hi All, I need some advice on dual booting a dell box so that I can have WinXP and Solaris 10 OS there. The question is, what is the best way of preparing the hdd for prior to installation? I have used created two partition, one for xp and the and the other unallocated partition for Solaris.... (3 Replies)
Discussion started by: S0laris_B0y
3 Replies

2. Solaris

Solaris 10 installation on X86

During installation on the desktop the error message crops up. "Failed to initialize hotplug controllers". Any help. Thanks. Chad (3 Replies)
Discussion started by: Mike Chad
3 Replies

3. Solaris

HDD cloned to a bigger one

Hello, I just cloned a 80 GB HDD(running Solaris 10) to an 320 GB HDD using g4u disk-to-disk method. Now Solaris is seeing may 320 GB HDD like 80 GB. Exactly like the old one. Could you tell me, please, how do I convince Solaris that my HDD is bigger? I would like to keep all slices as... (5 Replies)
Discussion started by: mirciulicai
5 Replies

4. Solaris

Solaris 10 x86 Installation Will Not Boot From CD Disks

Problem: Am trying to install Solaris 10 x86 on a desktop PC (PC details unspecified) from downloaded iso images (5 in all) on 5 CD disks. These were downloaded from the Sun website and unzipped. I install Disk 1of 5 into the CD drive and then restart the machine, thinkng that it will launch... (5 Replies)
Discussion started by: RobSand
5 Replies

5. Solaris

Solaris x86 - multiple problems

Recently installed a custom PC with Solaris 10 u4, kernelpatch 127112-10. I was going to use this box as a NAT router using ipf. ipf however caused the box to panic multiple times. This in turn lead to a couple other issues that I would like some input of. - None of the panic's i've... (0 Replies)
Discussion started by: ba72
0 Replies

6. Solaris

Installation of Solaris 10 on X86 Platform on the same Disk having XP SP2

Plz help me in installing solaris 10 11/06 on XP sp2 system having only one hard disk (1 Reply)
Discussion started by: skargarika
1 Replies

7. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies

8. Solaris

Can't have the GRUB menu for solaris x86 installation

Dears, I'm trying to install solaris x86 on sun x4170 M2 I started connecting consol to the machine but when I do the reset /SYS command nothing changed I can see that the /SYS is powered on but I can get the GRUB menu to start the installation of the solaris. the solaris DVD is already... (2 Replies)
Discussion started by: engwzwz
2 Replies

9. Solaris

Solaris 11 x86 installation troubles - 8G disk limit

Hi, I am trying to install Solaris 11 on an X86 machine. I am using the text install iso image burned to an optical disk. The system contains a single 500G SATA drive. When the system attempts to detect local disks, it reports that the disk only has a capacity of 8GB. How do I get... (2 Replies)
Discussion started by: jpoc
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 02:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy