Sponsored Content
Full Discussion: resizing slices
Top Forums UNIX for Dummies Questions & Answers resizing slices Post 33179 by RTM on Wednesday 18th of December 2002 02:14:26 PM
Old 12-18-2002
You didn't lose your data dumping to the same disk since you didn't format (changing the sizes of the partitions). You are attempting to 'get around' the normal way of doing things (not wrong mind you...that is something we all try).

But, the problem is this. You aren't running Solaris 8 on a SUN system which would allow this. You are running X86. And according to SUN, it can't be done.


Quote:
[cpj@west 5/24/96]
The install program has always provided a feature to allow choosing which
slice will contain which partition. The root and swap partition can be located
anywhere. devconf appears to have a hardcoded ":a" in the constructed bootpath
which breaks this feature. Pehaps there's a swap limitation as well?

This feature can be used to allow multiple solaris versions to install on a
single
disk. By preserving the old filesystems, and installing into new slices, both
installations can be held on one disk (and switched between by setting
the appropriate root partition to type "root" with the format program).

In any event, the root partition should be determined as the other boot
stages do, by examing the vtoc for the first "root" partition.

The description field as copied from bug report 1261782 follows:

If a system is installed with the root filesystem on a slice other than slice 0,
the
installed system cannot be booted.

An attempt to boot from the hard drive will cause this screen to be displayed:

SunOs Secondary Boot version 3.00

<bootdev>:a: can't open - too many open devices
prom_panic: Could not mount filesystem.

use Ctl-Alt-Del to reboot

An attempt to boot using the boot floppy will cause these messages to appear:

Unable to mount a Solaris root filesystem from device:

......

/isa/ata@`,1f0/cmdk@0,0:a: can't open - slice not allocated
/isa/ata@`,1f0/cmdk@0,0:a: can't open - too many open devices

I tested this by installing an IDE system with the root on slice 7. I also
tried
a system with a buslogic ISA adapter with the root on slice 7. These systems
work fine if the root is on slice 0.
Work Around Top

The work around field as copied from bug report 1261782 follows:

Install with root on slice 0.
So you are back to square 1. You can either backup your data to tape, format the drive, and dump the tape back on, OR, reinstall from scratch. I don't believe there are any other choices.

One thing you might try...

IF your swap partition is set up right next to your root partition (on slice 1), you could cut a piece from slice 7 {insure you restored your data first that you put there onto the correct slice [0]} to move swap to. Then you could increase the size of your root partition....all this is dependent on what your partitions look like (please post how you had it set up originally and how it is set up now).
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Solaris 8 installation slices

Anyone know if SUN recommends users to install the root parition on 1 single slice or break out the /var , /etc, /opt etc on separate slices? What if i only have a single hdd that is only 2 GB (1 Reply)
Discussion started by: owls
1 Replies

2. UNIX for Dummies Questions & Answers

new disk slices

How do I create new disk slices taking space from an existing slice? Right now I have slice 6 (/usr) with 16G. I'd like to create slices 5 (/opt) and 7 (/export/home) and steal space from slice 6. Thanks (3 Replies)
Discussion started by: kmgrady01
3 Replies

3. Filesystems, Disks and Memory

*BSD slices - multiple questions

Can you have a second primary slice on a second hdd? I know that primary slices are defined in the mbr, but where are all the sub partitions defined at? From the OBSD installation FAQ: What exactly is in the PBR? (0 Replies)
Discussion started by: Derrek
0 Replies

4. UNIX for Dummies Questions & Answers

Resize root disk slices

I have a Sun box running Solaris 9. My root disk was slices too small when it was installed and I am now at 99% capacity for my root partition. Is it possible, and if so how?, to increase the size of slice 0 and decrease the size of slice 7?? Thanks! Current partition table... (6 Replies)
Discussion started by: FredSmith
6 Replies

5. Solaris

SAN DISKS - Number of slices ?

Good morning to one and all :-) Thank god its Friday, as its bee na rubbish week for me ! So, a quick question. Disks ! Ive got a few local disks, and a few SAN disks used on my solaris server. Whats confusing me, and Im not sure if there's an issue at the SAN end, or my end, regarding the... (3 Replies)
Discussion started by: sbk1972
3 Replies

6. Solaris

Partitioning hard disk. Want 8 slices...have 9

Hi all I'm having difficulty setting up a proper disk structure on a 72GB HDD. The drive was previously part of a zfs pool. The zpool has ben destroyed and now I want to use the disk in a raid 5 array. I need to partition the disk accordingly though. This is what the partition table currently... (7 Replies)
Discussion started by: notreallyhere
7 Replies

7. Solaris

ufs slices info in solaris

how do you get start and end sector of a UFS slice? (2 Replies)
Discussion started by: orange47
2 Replies

8. BSD

NetBSD, SPARC, UFS slices

I need to shrink a UFS slice with NetBSD on SPARC. seems the only way is backup+reformat. can someone please give me exact commands for that? presumably backup is file-by-file instead of sector-by-sector, but how to preserve permissions/dates/attributes.. ? thanks. (0 Replies)
Discussion started by: orange47
0 Replies

9. Solaris

Scrapping slices

Hi Admins, Server is sparc solaris 9 I am new into solaris with little experiemce with SVM. /dev/dsk/c3t0d1s4 /u05 /dev/dsk/c3t0d1s3 /u02 /dev/dsk/c3t0d1s5 /u11 There are 3 file system created on slices of disk c3t0d1. Now i want to scrap all the slices and... (5 Replies)
Discussion started by: newsol
5 Replies

10. UNIX for Dummies Questions & Answers

partition of slices

Hello, I am using solaris 10 x86. my root and backup slices is having same memory 10 GB and same cylinders numbers . My root and backup cylinders ends at same cylinder number 1031. so for creating a new slice i am giving starting cylinder from 1302 and this is giving me error as "out of range" .... (2 Replies)
Discussion started by: bhargav90
2 Replies
re-preinstall(1M)					  System Administration Commands					 re-preinstall(1M)

NAME
re-preinstall - installs the JumpStart software on a system SYNOPSIS
cdrom-mnt-pt/Solaris_XX/Tools/Boot/usr/sbin/install.d/re-preinstall [-m Solaris_boot_dir] [-k platform_name] target-slice DESCRIPTION
re-preinstall installs the JumpStart software (preinstall boot image) on a system, so you can power-on the system and have it automatically install the Solaris software (perform a JumpStart installation on the system). When you turn on a re-preinstalled system, the system looks for the JumpStart software on the system's default boot disk. All new SPARC systems have the JumpStart software already preinstalled. The XX in Solaris_XX is the version number of the Solaris release being used. You can use the re-preinstall command in several ways. The most common way is to run re-preinstall on a system to install the JumpStart software on its own default boot disk. This is useful if you want to restore a system to its original factory conditions. (See the first procedure described in EXAMPLES.) You can also run re-preinstall on a system to install JumpStart software on any attached disk (non-boot disk). After you install the Jump- Start software on a disk, you can move the disk to a different system and perform a JumpStart installation on the different system. (See the second procedure described in EXAMPLES.) re-preinstall creates a standard file system on the specified target-slice (usually slice 0), and re-preinstall makes sure there is enough space on the target-slice for the JumpStart software. If sufficient space is not available, re-preinstall fails with the following message: re-preinstall: target-slice too small xx Megabytes required You can use the format(1M) command to create sufficient space on the target-slice for the JumpStart software. OPTIONS
The following options are supported: -k platform_name Platform name of the system that will use the disk with the JumpStart software. The default is the platform name of the system running re-preinstall. (Use the uname(1) command (-i option) to determine a system's platform name.) -m Solaris_boot_dir Absolute path to the Solaris_XX/Tools/Boot subdirectory of a mounted Solaris CD or a Solaris CD copied to disk that re-preinstall uses to install the JumpStart software. The default is root (/), which is where the Solaris CD is mounted in single-user mode. OPERANDS
The following operands are supported: target-slice Device name of the disk slice where the JumpStart software will be installed (usually slice 0), for example, c0t3d0s0. EXAMPLES
Example 1: Installing the JumpStart Software on a System's Own Default Boot Disk The following procedure installs the JumpStart software on a system's own default boot disk: 1. From the ok prompt, boot the system from the Solaris media CD or DVD in single-user mode: ok boot cdrom -s 2. The following command installs the Jumpstart software on the System default boot disk, c0t0d0s0 on a Solaris 9 system: example# /usr/sbin/install.d/re-preinstall c0t0d0s1 3. Reboot the slice: example# reboot disk:b Example 2: Installing the JumpStart Software on a System's Attached (non-boot) Disk The following procedure installs the JumpStart software on a system's attached (non-boot) disk: 1. Mount the Solaris CD or DVD if vold(1M) is not running or CD or DVD is not mounted. 2. Use the format(1M) command to determine the target-slice where JumpStart will be installed. 3. Use the uname(1) command (-i option) to determine the platform name of the system that will use the re-preinstalled disk 4. Run re-preinstall with the -m Solaris_boot_dir option if the Solaris CD or DVD is not mounted on /cdrom. The following command installs the JumpStart software on the system's attached disk for a system with a Sun4u kernel architecture, and it uses the Solaris CD or DVD mounted with vold(1M) on a Solaris 9 system: example# /cdrom/cdrom/s1/usr/bin/install.d/re-preinstall -m /cdrom/cdrom/s1 -k sun4u c0t2d0s0 EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcdrom (Solaris CD, | | |SPARC Platform Edition) | +-----------------------------+-----------------------------+ SEE ALSO
uname(1), eeprom(1M), format(1M), mount(1M), vold(1M), attributes(5) Solaris 10 Installation Guide: Basic Installations SunOS 5.10 9 Apr 2002 re-preinstall(1M)
All times are GMT -4. The time now is 08:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy