10-03-2005
Here is something else to check: If the box is in diagnostic mode, boot-device is ignored and the box will boot from the value stored in diag-device instead. The variable diagnostic-mode? controls whether or not you are in diagnostic mode.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi!
I installed Slackware on my computer so I thought I could have dual booting with ME, but that didn't work. So I installed another bootmanager that I find on internet. When I startup my computer the second bootmangaer that I did find on internet lets me choose system. When I have choosen... (3 Replies)
Discussion started by: Mr.Rudiment
3 Replies
2. UNIX for Advanced & Expert Users
Hai
I have installed win 98 o.s in my system after that i have
installed Red Hat Linux 7.0,there is a problem in dual
booting,by default win98 is being booted, when i insert
bootable linux floppy linux is loaded
My doubt how to overwrite windows MBR and palce the
lilo in MBR.so that it... (2 Replies)
Discussion started by: rajashekaran
2 Replies
3. UNIX for Dummies Questions & Answers
i have the Redhat installed in this Hard Drive and i wanna use it in this old computer of mine.. it works fine in my new computer.. but when i put it in my old one.. which is.. P1 150MHz 32MBramz it wont load the kernal and keeps on restarting the computer.. keeps on goin like this.. i get the GRUB... (2 Replies)
Discussion started by: dezithug
2 Replies
4. Solaris
any one can help me. my system running on solaris 2.7. recently there is sudden power failure while system running. after that unable to boot the system. it is giving comment that "can not open /etc/path_to_inst" and then returning back to "OK" after comment of termination. The processor is... (10 Replies)
Discussion started by: prabir
10 Replies
5. UNIX for Dummies Questions & Answers
Dear List,
While I was adding second hard disk to my system, I changed the /etc/fstab file by adding the following line:
/mnt/sdb1 /dev/sdb1 ext3 default 2 1
Now system does not boot and gives the following error:
Checking filesystems
/: Clean, 309260/18495840 files, 1064776/18486790... (2 Replies)
Discussion started by: siavoush
2 Replies
6. Solaris
Hi,
Basically the original configuration on my Solaris 9 server was two LUNs configured as Veritas file systems that were connected to a NetApp filer (filer1). These two LUNs are still configured on the server - but are not being used. They are there as a backup just in case the new... (0 Replies)
Discussion started by: sparcman
0 Replies
7. Solaris
Hi all
i have a veritas volume with the size of 600MB and formatted with vxfs filesystem. I want to grow the filesystem to 700MB. I knew that three ways are there to resize. vxresize, vxvol and vxassit. vxresize works fine. I want to try the same thing with vxvol and vxassist. Can someone tell me... (4 Replies)
Discussion started by: kingston
4 Replies
8. AIX
Hi,
I have IBM RS/6000 44P MODEL 170 server with Aix 5.1
Till the morning server is working fine, i turned off properly but now i tried to start it is showing below error on LED and going down (power off)
E051 >>>E0E0 >>>> E0E1>>>> 种种种种 >>>> 40210014 P1-C1-F1 ccccccc >>>> 40210014 >>>>E043... (3 Replies)
Discussion started by: ANAND KURADE
3 Replies
9. AIX
Dears,
I have a problem when i reboot the machine last time "AIX 5.3", that after rebooting it not login to graphical desktop, it just stop at console login command line.
Kindly find the attached screenshot.
Anyway to let it login automatically to Desktop?
Would appreciate any pointers to... (1 Reply)
Discussion started by: moudmm
1 Replies
10. AIX
Hi Everyone,
We have IBM p730 that I am trying to booting up to AIX 7.1.
But it stops at RUNTIME.
C7004087
C7004091
C7004091 (show is code number twice)
STANDBY
RUNTIME
The explanation for C7004091 is the final IPL status progress code to be displayed before the system reaches... (5 Replies)
Discussion started by: lilyn
5 Replies
LEARN ABOUT DEBIAN
mkqdisk
mkqdisk(8) Quorum Disk Management mkqdisk(8)
NAME
mkqdisk - Cluster Quorum Disk Utility
WARNING
Use of this command can cause the cluster to malfunction.
SYNOPSIS
mkqdisk [-?|-h] | [-L] | [-f label] [-c device -l label] [-d [-d ...]]
DESCRIPTION
The mkqdisk command is used to create a new quorum disk or display existing quorum disks accessible from a given cluster node.
OPTIONS
-c device -l label
Initialize a new cluster quorum disk. This will destroy all data on the given device. If a cluster is currently using that device
as a quorum disk, the entire cluster will malfunction. Do not run this on an active cluster when qdiskd is running. Only one
device on the SAN should ever have the given label; using multiple different devices is currently not supported (it is expected a
RAID array is used for quorum disk redundancy). The label can be any textual string up to 127 characters - and is therefore enough
space to hold a UUID created with uuidgen(1).
-f label
Find the cluster quorum disk with the given label and display information about it.
-L Display information on all accessible cluster quorum disks.
-d Increase debugging level. Specify multiple times for more information. Currently, specifying more than twice has no effect.
SEE ALSO
qdisk(5), qdiskd(8), uuidgen(1)
July 2006 mkqdisk(8)