|
|
Sponsored Content
Operating Systems
Solaris
How to find missing disks on Sun x4150 without reboot?
Post 302519937 by aixlover on Thursday 5th of May 2011 12:12:16 PM
05-05-2011
|
|
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a V490 that has couple internal disks attached to the same dual-port HBA card that I'm planning attach to the SAN for additional storage.
Would I sacrifice performance if I use the same HBA?
Is it better to throw in a new HBA instead? (1 Reply)
Discussion started by: kiem
1 Replies
2. Solaris
Hi,
I have SE 220R with 2 disks mirrored using SVM and running OS - solaris 9.
Because of performance issues on 220R I'd like to move the OS/application data to SF 280R. Having found that SF280R will only support Fiber channel disks, I am now wondering how to move complete data from SCSI... (3 Replies)
Discussion started by: upengan78
3 Replies
3. Red Hat
Dear all ,
i ve configured raid 0 in redhat machine(VM ware), by following steps:
#mdadm -C /dev/md0 -l 0 -n 2 /dev/sdb1 /dev/sdc1
#mkfs.ext3 /dev/md0
#mdadm --detail --scan --config=mdadm.conf >/etc/mdadm.conf
then
mounted the/dev/md0 device and also added a entry in fstab.
how... (2 Replies)
Discussion started by: sriniv666
2 Replies
4. Solaris
Dear Team,
This time i am facing some new problems which is beyond my thinking. I need some expert advice.
We are having 4 Servers ( 2 nos Sun SPARC Enterprise T5220 & 2 nos of SF e2900 Servers ). Both the T5220 Servers are Termed as Node A and Node B . The same things are followed with... (1 Reply)
Discussion started by: sudhansu
1 Replies
5. Solaris
Hi, I was trying to upgrade firmware for this Sun x4150 from ELOM to ILOM. I did it under GUI ELOM Manager > Maintenance > Firmware Upgrade. It then showed 'Someone is upgrading firmware' and took forever. I believe its hung due to unknown reason (wrong file used?). I poweroff and poweron the... (4 Replies)
Discussion started by: aixlover
4 Replies
6. Fedora
Hello world,
One of the servers, a Fedora one,rebooted today (Luckily, a testbox).
I tried to get the reason the server rebooted. After going through the messages, I think that the log entries just before and after reboot are missing.
Please below: (****** is the server name, for privacy... (0 Replies)
Discussion started by: satish51392111
0 Replies
7. Solaris
Hey everyone. First, let me start by saying I'm primarily focused on linux boxes, and just happened to get pulled into building two T5220's. I'm not super educated on sun boxes.
Both T5220's have 8 146GB 15k SAS drives. Inside the service processor, I can run SHOW /SYS/HDD{0-7} and they all come... (2 Replies)
Discussion started by: msarro
2 Replies
8. Solaris
Help Please!
I picked up a V440 and it has 4 disks. I installed Solaris fine to disk 3, but I cannot see the other disks in Solaris.
I have run probe-scsi-all from OBP and I see the other disks and they have names in devalias AFAIK. It's just in Solaris they do not appear. I have run... (6 Replies)
Discussion started by: greg1975
6 Replies
9. Solaris
Hi Guys,
Just a quick question hopefully someone will have seen this before and will be able to enlighten me.
I have been doing some Infrastructure Verification Testing and one of the tests was booting the primary domain from alternate disks, this all went well - however on restarting one of... (7 Replies)
Discussion started by: gull04
7 Replies
LEARN ABOUT OSF1
reboot
reboot(8) System Manager's Manual reboot(8) NAME
reboot - Restarts the machine SYNOPSIS
/usr/sbin/reboot [-dlnq] DESCRIPTION
When the system is running and multiple users are logged in, use the shutdown -r command to perform a reboot operation. If no users are logged in, use the reboot command. The reboot command normally stops all running processes, syncs the disks, logs the reboot, and writes a shutdown entry in the login accounting file, /var/adm/wtmp. The reboot command uses the sync call to synchronize the disks, and to perform other shutdown activities such as resynchronizing the hard- ware time-of-day clock. After these activities, the system reboots. By default, the system starts and the file systems are automatically checked. If the start-up activities are successful, the system comes up in the default run-level. You must have root privileges to use this command. Using the -n flag can result in file system damage. FLAGS
Generates a crash dump of the system before halting it. Can be used with any of the other flags. Does not log the reboot using syslog Does not sync the disks or log the reboot using syslog Performs a quick reboot without first shutting down running processes; does not log the reboot using syslog EXAMPLES
To enable the default reboot action, enter: reboot This command causes the system to stop all running processes, sync the disks, log the shutdown, and perform other routine shutdown and reboot activities. To shut down the system without logging the reboot, enter: reboot -l This command shuts down the system and performs all shutdown and reboot activities, except logging the shutdown. To reboot the system abruptly, enter: reboot -q This command reboots the system abruptly without shutting down running processes. FILES
Specifies the command path Specifies the login accounting file Specifies the path of the syslog daemon RELATED INFORMATION
Commands: fsck(8), halt(8), init(8), savecore(8) shutdown(8), syslogd(8) Functions: reboot(2), sync(2), syslog(3) delim off reboot(8)