Sponsored Content
Operating Systems Solaris Solaris 8 booting from wrong device Post 302206641 by incredible on Wednesday 18th of June 2008 06:24:17 AM
Old 06-18-2008
What taran says is correct. You need to do this. Btw Juha, I think you did a restore to this disk, correct?
 

4 More Discussions You Might Find Interesting

1. Solaris

What's wrong with my system? Solaris not booting.

Booting the 32-bit OS ... SunOS Release 5.7 Version Generic_106541-31 Copyright (c) 1983-2002, Sun Microsystems, Inc. configuring network interfaces: le0. Hostname: wz-ultra1 metainit: wz-ultra1: there are no existing databases The system is coming up. Please wait. checking ufs... (2 Replies)
Discussion started by: CollenM
2 Replies

2. Solaris

Booting from wrong SCSI-disk. Error -256 Stack Underflow

Hi. I need to boot on Sun Blade 150 from scsi-disk, that ran on old Sun Ultra 10. It is necessary to take some the information from an old disk and something to study. The workstation is booted and I receive the following issue::mad: Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard (tip... (3 Replies)
Discussion started by: wolfgang
3 Replies

3. Red Hat

This doesn't look like a partition table Probably you selected the wrong device.

Hi, I need to mount the device from this device # fdisk -l . . . Disk /dev/sdas: 2000.4 GB, 2000365289472 bytes 255 heads, 63 sectors/track, 243197 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size... (0 Replies)
Discussion started by: justbow
0 Replies

4. Red Hat

Device-mapper behaviour booting on init=bin/bash

Good morning Recently we needed to change the password from a redhat 6.5 system that no one knew the root password. Starting the system with the init=/bin/bash method took us to the following scenario: system_vg active with only root_lv and tmpfs mounted. our entries at fstab are like... (1 Reply)
Discussion started by: Ikaro0
1 Replies
volunroot(8)						      System Manager's Manual						      volunroot(8)

NAME
volunroot - Remove Logical Storage Manager hooks for rootable volumes SYNOPSIS
/usr/sbin/volunroot [-a | -A] OPTIONS
Specifies that all volumes on the system disk be converted back to UNIX disk partitions, not just the root and swap volumes, rootvol and swapvol. Forces removal of the private region unless it is the last one in the system. DESCRIPTION
The volunroot script can be used to restore the accessibility of the root, swap, and other file systems on the boot disk directly through disk partitions instead of through volume devices. The script also removes other changes that were made to enable booting of the system from the root volume, so that the system will boot with no dependency on the Logical Storage Manager. When used with no options, volunroot affects only the root and swap volumes, rootvol and swapvol. For volunroot to work properly, only one plex must exist for each of the affected volumes. This plex must be the one created by volrootmir or the original plex created when the root disk was encapsulated. This ensures that the underlying subdisks will have equivalent partitions defined for them on the disk. If these conditions are not met, the volunroot operation fails and none of the volumes are converted to disk partitions. The unwanted plexes can be removed using either voledit or volplex. SEE ALSO
volencap(8), voldiskadm(8), voledit(8), volintro(8), volplex(8), volrootmir(8) volunroot(8)
All times are GMT -4. The time now is 02:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy