Everything else is just a consequence of that. It seems that your system has lost touch with the hard disk(s) once attached to it. Reasons could be (the list is not exhaustive):
- disk(s) have been removed physically
- adapter(s) to which the disk(s) is/are attached is/are removed/broken
- if disks are LUNs the zoning has been changed
and many reasons more. Can you tell us how your system was built (hardware-wise) so that we can narrow the possible reasons down?
Well i install successfully Solaris on my Second Hard disk, although i had to make it primary Master and my orignal hard disk as pirmary slave, because solaris will not let Windows on primary master.
Anyway after installation when i try to boot from hard disk , it shows message
bad PBR Sig ... (3 Replies)
Hi Folks,
I have an AIX server and I would like the server to run the command saprouter -r at every system restarts. It needs to be run by a specific user. How would I do that?
Thanks!!! (1 Reply)
Hi,
My HP-Proliant Machine have faced abnormal shutdown due to a power failure.
after the event : "Operating System not found" appears & the system could not load operating system.
O/S: RHEL AS 4 update 2
Software Raid 1+0 were configured.
Facts Gathered:
All mount points are... (1 Reply)
Hello,
When I try to upgrade AIX from 5.1 to 5.3 I get this error message
20EE0008 : No adapters found Adapter, Riser, System Bd.
Anyone know anything about it ? (1 Reply)
Hi guys and ladies!
The application not found required fonts.
I checked, the packages SUNWi5rf, SUNWi5of are installed.
Then I checked availability the directories iso8859-5, iso8859_5 at /usr/openwin/lib/locale.
I checked after that.
% xlsfonts | grep "lucida-"
The system showed only ... (0 Replies)
Hi
currently my linux instance is running in runlevel 3 ( someone has set the default to 3)
i have to change it to runlevel 5 . my question
1) does the editing of /etc/inittab needs system restart to enter runlevel 5.
2) how can we avoid system restart because if some users are... (3 Replies)
I have a Xen VM guest image with a lost root password. In order to get to /etc/passwd and /etc/shadow I need to mount the filesystems within the image with everything but /boot is in a LVM partition. The VM host also have an LVM image, and both (host and guest) are called VolGroup00. I want to... (1 Reply)
Guys,
I am new to FreeBSD. I have this weird issue where when i issue the command "/etc/rc.d/named restart" i get --> command not found.
I am running BIND 9.6.-ESV-R3 on FreeBSD 8.2
I have added named_enable="YES" in rc.conf as per manual
named works great: No issue there. I just would like... (3 Replies)
Hi,
Iam trying to instal a solaris operating system in a vmware on my local windows system via an iso image named as "solaris10.vmx". but as soon as the vm console opens i get an error message as:
"PXE-MOF: Exiting Intel PXE ROM.
Operating system not found"
Please help me out in... (3 Replies)
Our AIX system is currently having an issue where calls to various executables are returning errors such as
ksh: /usr/bin/oslevel: not found.
This is even happening with system files, third party scripts, and with the full path included.
Telnet connections are also closing immediately upon... (6 Replies)
Discussion started by: Chthonic
6 Replies
LEARN ABOUT OSF1
volunroot
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)