09-29-2009
Quote:
Originally Posted by
System Shock
The problem with that is that Blades have IDE disks.. I don't know that I want to plug those when the chassis is powered on.
But, he could remove all disks, boot the Blade, get to the ok prompt, then like you said in your previous post set auto-boot to false, poweroff the Blade, replace the disks, and power the Blade back on.
afaik the blade 1500 has fcal disks... should be the same board as a 280r which has fcal disks!
edit:
no, you are right... it's ide:
http://sunsolve.sun.com/handbook_pub...lade1500S/spec
i thought about blade 1000/2000 which indeed have fcal disks...
10 More Discussions You Might Find Interesting
1. Solaris
Hello everybody,
I installed sun solaris i86 , the programme installation install the
"Mini Root" and after that he doing shutdown.
the camputer coming up and he can't boot.
how i can to resuled this problem ???
Thenk you in advence..... (2 Replies)
Discussion started by: yanly
2 Replies
2. Solaris
Hi,
I have Sun SPARC Enterprise T5140 and I can't access it via serial port using preconfigured administrator account, as described in Sun Integrated Lights Out Manager 2.0 User's Guide: I'm always receive "Login incorrect" message. I'm really confused! Does anyone experience such circumstances?... (12 Replies)
Discussion started by: Sapfeer
12 Replies
3. Solaris
Hi All
I have a problem on T2000 server.
bash-3.00# uname -a
SunOS 5.10 aaa Generic_120011-14 sun4v sparc SUNW,Netra-T2000After the initial solaris installation server failed to boot:
Rebooting with command: boot
Boot device: disk:b File and args:
The file just loaded does not appear... (1 Reply)
Discussion started by: ouzist
1 Replies
4. Solaris
Hi all.
I am seeing in one of our less-used servers that it crashed and now won't restart. I get the message 'continue with normal startup or boot into maintenance mode'.
I go into maintenance and run fsck on /usr0 (mentioned in error at restart) it then reboots but goes right back to... (3 Replies)
Discussion started by: jamie_collins
3 Replies
5. Solaris
Hi All,
I had install the solaris 10 into the SUNFIRE V890 server, after installed, it keep rebooting.
I wish to enter the OK mode again, and install back the Solaris 10.
i had try the "break" button and "stop+A" button, but all fail.
kindly advice... (4 Replies)
Discussion started by: SmartAntz
4 Replies
6. Hardware
hello
i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message:
Enabling system bus....... Done
Initializing CPUs......... Done
Initializing boot memory..
RAM-Copy CRC failure!Can't start: No image found
FATAL: Can't find/decompress... (0 Replies)
Discussion started by: bahjatm
0 Replies
7. Hardware
Hi all!
I have a Sun JavaStation-1 which doesn't boot: when I turn on the power switch, the power led becomes lit but the screen remains black (going in power save after about 5 seconds). :eek:
Now my question is: could be this problem due to a dead IDPROM? :confused:
I have this doubt because... (0 Replies)
Discussion started by: wisechip
0 Replies
8. Solaris
Hi all,
I have application running on sun server T5440 4x8x1.4 GHz, 64 GB RAM, application running very slow though load average too low. when I install my application on another server SUN M3000 (One CPU 1x8x2.5GHz, 8GB RAM), application run smoothly.
Here is my server T5440 info:
... (6 Replies)
Discussion started by: insatiable1610
6 Replies
9. UNIX for Beginners Questions & Answers
Hi all,
I've got a Sun ultra 30 workstation. the Nvram battery died so I replaced it. I reprogrammed the mac address using the mlpl command all that so it booted without error. But for some reason I was trying to boot via the network. So I did a STOP A and boot disk1 which is the alias for my SCSI... (2 Replies)
Discussion started by: robbo007
2 Replies
10. UNIX for Beginners Questions & Answers
-> start /SYS
Are you sure you want to start /SYS (y/n)? y
Starting /SYS
]-> show HOST
/HOST
Targets:
bootmode
diag
domain
Properties:
autorestart = reset
autorunonerror = false
bootfailrecovery = poweroff
... (29 Replies)
Discussion started by: z_haseeb
29 Replies
advfsd(8) System Manager's Manual advfsd(8)
NAME
advfsd - Starts the AdvFS graphical user interface (GUI) daemon
SYNOPSIS
/usr/sbin/advfsd
DESCRIPTION
The AdvFS daemon, advfsd, is a process required by the AdvFS GUI (dtadvfs). The
advfsd daemon issues commands and obtains system information on behalf of the AdvFS GUI.
The /usr/var/advfs/daemon/socket/hosts.allow file contains a list of all hosts on which the advfsd daemon will allow the AdvFS GUI to run.
This file can be edited to add or remove hosts. Each host name must be on a separate line. For example:
host1
host3
host27
The /usr/var/advfs/daemon/socket/gui.passwd file, if it exists, is used by advfsd to force a dtadvfs user to enter a unique password when
attempting to connect to the host. The first line of this file is the unique password required by the GUI. For example:
guipassword
For security reasons, do not use the password of the root user or any other user; make up a unique name and do not encrypt it.
The advfsd daemon allows Simple Network Management Protocol (SNMP) clients such as NetView or Performance Manager (PM) to request AdvFS
file system information. SNMP clients cannot issue system configuration commands to the advfsd daemon.
The advfsd daemon is automatically started at boot time. Under normal conditions, this daemon does not need to be run manually.
If you do not want to have the daemon started at boot time, move the /sbin/rc3.d/s53advfsd file from its default location to another
directory and run it from that directory. Whenever you want to run the daemon at boot time, move the s53advfsd file back to the
/sbin/rc3.d directory.
The daemon (called an agent in the dtadvfs GUI interface) employs a file, /usr/var/advfs/daemon/disks.ignore, in which you can place the
names of disks that the daemon will ignore when it gathers information about disks on the system. If you use the disks.ignore file, you
can improve the performance of the dtadvfs GUI.
Each line in the disks.ignore file contains the name of a disk (with no directory partition letter) to be ignored by the daemon. For
example, to cause the disks /dev/disk/dsk3d and /dev/disk/dsk2g to be ignored, enter the following names on separate lines in the file:
dsk2
dsk3
You cannot ignore an LSM volume by including the LSM volume name in the disks.ignore file; you must list the disks from which the LSM vol-
ume is built. To ignore a complete disk group, you must list all the disks in it. Because all partitions on the listed disks will be
ignored, unexpected results may occur if a disk has partitions belonging to more than one disk group.
The disks.ignore file is processed each time the disks are checked. This means that if a disk fails or becomes unavailable, you can add the
disk name to the disks.ignore file and the daemon will ignore it. Once the disk is available, remove the entry from the file. There is no
need to stop the daemon.
For more information, see the GUI interface reference page , dtadvfs(8).
RESTRICTIONS
Only one advfsd daemon can be running on a system at a given time. If a second advfsd daemon attempts to start, it will fail.
You must be the root user to use this utility and you must register the Advanced File System Utilities license.
FILES
The script that starts the advfsd daemon at boot time. The advfsd message catalog. The SNMP data files. The sh scripts used by the dae-
mon to execute commands. The advfsd daemon executable. The advfsd daemon message log file. Remove or copy this log to another location
periodically to prevent the log from becoming too large. The security file that lists all hosts with permission to connect to the advfsd
daemon with the AdvFS GUI (dtadvfs). The advfsd password file. The file that lists all disks for the advfsd daemon to ignore when col-
lecting statistics about resources.
SEE ALSO
advfs(4), dtadvfs(8)
advfsd(8)