03-19-2008
if you are not root, no.
luxadm and other commands need root also...
10 More Discussions You Might Find Interesting
1. Solaris
Has anyone ever relocated an HBA card after already having it configured in another PCI slot? I've found that the HBA instance #'s start incrementing past the previous. It results in me having to have my instance numbers in /kernel/drv/qla2300.conf be 4,5,6,7 instead of 0,1,2,3. Cleanup with... (5 Replies)
Discussion started by: kduffin
5 Replies
2. Solaris
Hi all,
I have a compatibly issues with a new hardware
My config is the following one :
Solaris 10
V490 Hardware
2 X HBA Qlogic 2310f cards
An HP EVA 5000 for storage ...
Veritas VxVM 4.1 MP1
When I reboot my server, VxVM is trying to mount/use the volume before it's... (0 Replies)
Discussion started by: unclefab
0 Replies
3. Solaris
Due to speed mismatch, the server kept crashing. Sun suggests that I need to move the two HBA cards from the 66Mhz to the 33Mhz slots. There are tons of disks that are connected to these HBAs and I have Veritas volume manager.
Does anyone have a list of what I need to do prior/after moving to... (3 Replies)
Discussion started by: kiem
3 Replies
4. UNIX for Advanced & Expert Users
I have worked with Qlogic (Sun) fiber cards a lot and with Emulex fiber cards only a little. Here is the scenario: I have a Sun 490 with 3 Emulex cards in it. A pair are for the 6120 array that is attached, the other is a direct attach so our SAN for Veritas Netbackup to back up the system.I... (0 Replies)
Discussion started by: lm_admin_dh
0 Replies
5. UNIX for Advanced & Expert Users
Hi,
I'm trying to determine which HBA cards are installed on my Solaris 10 (Sun-Fire-V240) machine.
The relevant data I have is below, but from it I cannot ascertain for sure if I have Emulex 10000 or 11000 HBA cards.
Can anyone suggest how to determine my HBA hardware ?
Thanks,
Ron.
... (3 Replies)
Discussion started by: ronbarak
3 Replies
6. Solaris
Hiii... Every one....
I want to know the command to get the details and number of HBA cards
attached to a server.
I know that we can use "powermt display", but nither my cards are connected to the storage nor powerpath is active.
I am using SUN server with Solaris -9.
Thanks in... (4 Replies)
Discussion started by: Reboot
4 Replies
7. Solaris
Hello,
In Solaris 10 I can use fcinfo to find what speed the hba ports are running at, am I able to find this out using Solaris 9? I have tried a few variations on luxadm but cant find anything relevant.
Thanks. (1 Reply)
Discussion started by: Actuator
1 Replies
8. BSD
Hi,
The title is a bit misleading, but it seems I can't re-edit the title after creating the post - apologies.
I have been handed a variety of servers, whereas quite a few of these are older FreeBSD (4.8, thank you legacy). I now have one of these servers which has a HBA card installed, and... (0 Replies)
Discussion started by: brightstorm
0 Replies
9. Solaris
Hello,
I am very new to solaris so please bear with me. I have 2 machines in question. For both I am trying to get the HBA Card Hardware information such as:
HBA Model Name
HBA Firmware version
HBA Port details
HBA Driver details
First machine is a Solaris 10. When I execute fcinfo... (6 Replies)
Discussion started by: flagman5
6 Replies
10. Red Hat
hi all,
I am trying to view the hba cards on a rhel7 server (storage says they are there, but I am not seeing them.
I tried lspci -nn | grep -i hba
lspci |grep qla
I tried looking in /sys/class/fc_host.. but it is empty.
I am not sure if I am looking in the right spot... (0 Replies)
Discussion started by: gartie
0 Replies
LEARN ABOUT OPENSOLARIS
systemd-volatile-root.service
SYSTEMD-VOLATILE-ROOT.SERVICE(8) systemd-volatile-root.service SYSTEMD-VOLATILE-ROOT.SERVICE(8)
NAME
systemd-volatile-root.service, systemd-volatile-root - Make the root file system volatile
SYNOPSIS
systemd-volatile-root.service
/lib/systemd/systemd-volatile-root
DESCRIPTION
systemd-volatile-root.service is a service that replaces the root directory with a volatile memory file system ("tmpfs"), mounting the
original (non-volatile) /usr inside it read-only. This way, vendor data from /usr is available as usual, but all configuration data in
/etc, all state data in /var and all other resources stored directly under the root directory are reset on boot and lost at shutdown,
enabling fully stateless systems.
This service is only enabled if full volatile mode is selected, for example by specifying "systemd.volatile=yes" on the kernel command
line. This service runs only in the initial RAM disk ("initrd"), before the system transitions to the host's root directory. Note that this
service is not used if "systemd.volatile=state" is used, as in that mode the root directory is non-volatile.
SEE ALSO
systemd(1), systemd-fstab-generator(8), kernel-command-line(7)
systemd 237 SYSTEMD-VOLATILE-ROOT.SERVICE(8)