10-30-2013
Where your second disk is giving error ? While booting ?
Are you able to mount your second disk on /a when you boot from CD ?
9 More Discussions You Might Find Interesting
1. Solaris
I had installed solaris 10 on 440 on disk 0. I had done ufsrestore on disk1 from tape and then rebooted
Rebooting with command: boot disk1
Boot device: /pci@1f,700000/scsi@2/disk@1,0 File and args:
SunOS Release 5.10 Version Generic_118833-24 64-bit
Copyright 1983-2006 Sun Microsystems,... (3 Replies)
Discussion started by: vr76413
3 Replies
2. Solaris
Hi All,
We had a Sun Netra T1 go down the other day, the root disk was mirrored using vxvm. Upon boot from either disk, we had the following error appear:
WARNING: Error writing ufs log state
WARNING: ufs log for / changed state to Error
WARNING: Please umount(1M) / and run... (4 Replies)
Discussion started by: badoshi
4 Replies
3. Red Hat
Hello,
I have a test PC running Fedora 10. Friday evening it was working fine, I have some perl scripts which are scheduled to run every morning.
But when I started work this morning, I found I cannot ping the machine. When I switched on the monitor, I saw the GRUB promt :(. I am not sure... (10 Replies)
Discussion started by: SivaramaRaju
10 Replies
4. Hardware
Hey All,
Im using Fedora 2.6 (which is cannot be changed for compatibility reasons).
I cloned a drive from a different server and when i added this drive to a new box, during startup it hangs on "Configuring Kernel Parameters:"
Is there any way to bypass this process and still boot... (0 Replies)
Discussion started by: robfwauk
0 Replies
5. Fedora
hello everyone,
I have Matlab installed on Fedora 16. I tried running it by simply typing on terminal:
$ matlabBut it returned the follwoing error:
--- can anyone suggest a solution?
cheers,
peter
---------- Post updated at 10:57 PM ---------- Previous update was at 10:54 PM ----------... (1 Reply)
Discussion started by: peter_071
1 Replies
6. Solaris
Hi,
Can you help me on booting x86 server configured under VxVM. Server boots fine normally from both the disks but if I try to boot server from mirror disk without starting veritas, then it does not boot.
vxplex -g rootdg dis var-02
vxplex -g rootdg dis swapvol-02
vxplex -g rootdg dis... (2 Replies)
Discussion started by: milindphanse604
2 Replies
7. Solaris
Hi Solaris 10 Experts,
I am wondering what is the correct syntax to edit in Grub when trying to specify the local ZFS boot disk while booting up from a Solaris 10 x86 64bits DVD installation disk. In other word, I try to boot up from local disk without removing the Solaris installation disk... (0 Replies)
Discussion started by: gjackson123
0 Replies
8. Solaris
Hi,
I'm looking to copy a boot disk on an old Solaris 8 system using dd. I'll bring the system down to single user mode and begin from there. I'm copying my source disk to a larger target disk. Do I need to do anything other than the 'dd' command below because the target disk is bigger? ... (2 Replies)
Discussion started by: sparcman
2 Replies
9. Red Hat
Hi,
I just P2V an old machine running Redhat 5.5 on a physical server. After P2V was completed, when boot up it got an error. Please refer to the attachment for the error. Please assist. Thanks. (2 Replies)
Discussion started by: freshmeat
2 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)