08-17-2010
unable to find a root hard disk on vmware
Hello guys i need some guidence on why i am getting the unable to find a root disk and how i can overcome this problem.
Thanks
Paddyl
9 More Discussions You Might Find Interesting
1. SCO
Hey,I'm new with Unixware.
Lately,I worked with Unixware7.1.3.I ran into problems while installing it.The problem is :
Error:unable to find a root hard disk...
Well,I have a HBA floppy disk,but my pc has no floppy driver.Is there any way to solve the problem with USB driver?What should I... (1 Reply)
Discussion started by: DorrSmith
1 Replies
2. Solaris
The master copy was set to 5 gigs. As the instance is cloned, additional space is provided. I was given a new instance along with 15 gigs of additional space. The problem is I can't see the additional space, either as additional space on the primary disk or as a second disk.
# format
Searching... (8 Replies)
Discussion started by: BOFH
8 Replies
3. Solaris
Friends,
I have an 80 GB HDD, but I wish to know if there is a direct command in Solaris 10 to find out the size of my hard disk (similar to fdisk -l in Linux).
Thank you
saagar (3 Replies)
Discussion started by: saagar
3 Replies
4. Virtualization and Cloud Computing
Hi
I have downloaded vmware server 1.0.10 and ubuntu 9.10. Installed
vmware server on my windows xp and created the disk space for Ubuntu.
Now when i am running the virtual machine using the above downloaded
iso image, I get the installation window. I selected 'Install Ubuntu'
option and... (2 Replies)
Discussion started by: kushal154
2 Replies
5. SCO
hi
I've a fresh installation of SCO 5.0.7 on the IDE hard disk.
For SCSI hard disk I can declare, for example blc disk driver using:
# mkdev hd 0 SCSI-0 0 blc 0but it works for IDE hard disk? (3 Replies)
Discussion started by: ccc
3 Replies
6. Linux
Hi all,
I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies
7. Solaris
Hi All
Hope it's okay to post on this sub-forum, couldn't find a better place
I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies
8. Linux
Hi All,
I installed Red-hat linux(64bit-x86) os on vmware 8,configure IP address and services but it is unable to come in to network.it is production server.
please provide solution to me , it is very urgent... (2 Replies)
Discussion started by: Rajesh_Apple
2 Replies
9. Solaris
Hi,
I am unable to find remaining space on solaris 10. below is output.
I am facing this issue on zone server.
bash-3.00# df -h /
Filesystem size used avail capacity Mounted on
/ 59G 59G 0K 100% /
bash-3.00# pwd
/
bash-3.00# du -sh *
1K File_Stores
19K TT_DB
9K app
1K bin... (4 Replies)
Discussion started by: manoj.solaris
4 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)