10-22-2008
yes by cfgadm -l you can see the scsi connection too ,it will show you the controller where disk is attached some like below
Quote:
c0: scsi-bus connected configured
dmesg is located in /usr/sbin/ directory to find the command location u can user either
or
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
On my PC I have two hard disks, the first with Windows 98 SE and the second with Linux Mandrake 8.0 (Traktopel). When I have installed Linux, it has modified the boot record of the 1st HD and it has added a graphic menu (LILO) for selecting the OS to use. By default, if I don't press a key, Linux... (2 Replies)
Discussion started by: robotronic
2 Replies
2. UNIX for Advanced & Expert Users
Hey !
I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range.
According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies
3. UNIX for Dummies Questions & Answers
I have a diskless work station.
i want to boot from a remote linux machine.
what changes i will have to do in configuration.
Plz tell me
thanks (1 Reply)
Discussion started by: hemant29
1 Replies
4. SCO
I get a message saying
Not enough space to dump xxxxx pages
Press any key to reboot
Safe to power off
After rebooting it never gets to the "Press CTRL D to continue or enter password for single user" message before it goes back to "Not enough space..." message above. Vicious cycle.
... (0 Replies)
Discussion started by: deloev
0 Replies
5. UNIX for Dummies Questions & Answers
being nosey on sons laptop and set a password and now need to undo this but its in the boot system :eek::eek::eek: (4 Replies)
Discussion started by: hempel
4 Replies
6. Solaris
We have a system that won't boot. It is Sun V245 that was patched yesterday with the latest Recommended 10 patch cluster. I will post what we get during the boot at the end of the email message. We have tried rebuilding the bootblk, booting from the cdrom, and running an fsck, booting into failsafe... (2 Replies)
Discussion started by: brownwrap
2 Replies
7. Solaris
Hi,
I am running into a some problems creating a dual boot system of 2 solaris instances using ZFS file system and I was wondering if someone can help me out.
First some back ground. I have been asked to change the file system of our server from UFS to ZFS. Currently we are using Solaris... (3 Replies)
Discussion started by: estammis
3 Replies
8. HP-UX
Hello,
I have a very old hp rp2450 running 11i2 that I had to power off. When turning it back on it hangs with the following message. Would booting into SUM get me any further? I've never used SUM, so I'm asking before I go down that rabbit hole.
Thanks for the help.
#
## extra content... (1 Reply)
Discussion started by: calabaria
1 Replies
9. Red Hat
Hi
im using centos 6.4
starting yesterday i have a strange issue that im unable to resolve. the system is booting to GRUB menu and the os is not starting. i tried to run a repair install and the message attached is what i get, what can cause this?
thanks, (1 Reply)
Discussion started by: guy3145
1 Replies
10. UNIX for Advanced & Expert Users
Hi,
I got stuck in a very messy situation yesterday after attempting to resolve a filesystem full issue. The user reported that their filesystem (/var/DWS) was 100% full even after moving few files of sizes 14G, 30G and 50G out of the directory. I checked the filesystem once more after this... (5 Replies)
Discussion started by: anaigini45
5 Replies
lsmsad(8) System Manager's Manual lsmsad(8)
NAME
lsmsad - Starts the Storage Administrator (SA) daemon
SYNOPSIS
/usr/sbin/lsmsad
DESCRIPTION
The SA daemon, lsmsad, is a process required by lsmsa, the SA graphical user interface (GUI). The daemon issues commands and obtains system
information on behalf of SA.
The SA daemon runs on a Tru64 UNIX system on which LSM is initialized and running. The SA client runs on any machine that supports the
Java Runtime Environment.
The SA daemon is automatically started at boot time. Under normal conditions, the daemon does not need to be run manually.
If SA does not start during the boot process, enter:
/sbin/init.d/lsmsa stop
To restart SA, enter:
/sbin/init.d/lsmsa start
Only one SA daemon can be running on a system at a given time. If a second SA daemon attempts to start, it will fail.
RESTRICTIONS
You must be root user to run lsmsad.
FILES
The script that starts lsmsad at boot time. The command log file that tracks SA tasks. The access log file that tracks login to SA. The
server log file that tracks server startup information and server errors. The log maintenance shell script that saves and compresses log
files.
SEE ALSO
lsmsa(8), volintro(8)
lsmsad(8)