Identify Boot from SAN


 
Thread Tools Search this Thread
Operating Systems Solaris Identify Boot from SAN
# 1  
Old 09-14-2011
Identify Boot from SAN

How to identify the server is BOOT FROM SAN.
Also how one can find from which device it is booted?

Thanks
Rahul

Moderator's Comments:
Mod Comment Double post, continued here

Last edited by pludi; 09-14-2011 at 09:20 AM..
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

How to identify if disk is attached to SAN and assist in migration.?

I am working on VM host and collecting data to identify the type of storage attached to the server which will be migrated to VNX. it has one ldom created on it luxadm probe output --- No Network Array enclosures found in /dev/es Found Fibre Channel device(s): Node... (7 Replies)
Discussion started by: kpatel786
7 Replies

2. UNIX for Dummies Questions & Answers

How can we identify SAN devices in fdisk -l output.?

We can Know the storage devices in fdisk -l. But Please tell me how can i identify the SAN devices :wall: How SAN devices are represented in the fdisk -l output :wall::wall: Thanks in Advance........:D (3 Replies)
Discussion started by: vamshigvk475
3 Replies

3. Red Hat

Identify Boot from SAN

Hi, I have many servers all of these are boot from SAN. Can anybody let me know that how to identify the server is Boot fron SAN and from which device? Thanks Rahul (1 Reply)
Discussion started by: rahul.kurumkar
1 Replies

4. Solaris

SAN boot solaris 10

I have a solaris 10 box which does not have internal disks it has just a single dual port HBA card. Storage team has assigned 2 LUNs to the system and i can see it from the probe-scsi-all /pci@3,700000/SUNW,emlxs@0,1 Device PortID 10100 WWPN 5006016941e0a08d LUN 0 Disk DGC ... (0 Replies)
Discussion started by: fugitive
0 Replies

5. Red Hat

Identify SAN disks not in use

Hello, How can I identify SAN disks not in use by the OS? Thank you. (8 Replies)
Discussion started by: asanchez
8 Replies

6. UNIX for Dummies Questions & Answers

Identify SAN disks

Hello everybody, I'm using the binary inqraid (Linux RHEL) in order to retrieve information about SAN disks. The questions are: Given an LDEV, how do I know if the SAN disk related to this LDEV is being used by the OS? I mean, how can I demonstrate to "Storage department" that all disks of... (4 Replies)
Discussion started by: asanchez
4 Replies

7. UNIX for Advanced & Expert Users

Can AIX 5.3 - 6 Boot From HP EVA 6000 SAN

Hi There, Has anyone had any luck with or know how to get AIX 5+ to boot from a HP EVA 6000 SAN? The servers used here will be P Class Blades My initial searches on this so far did not bring results so I am guessing this may not be possible on HP SAN's but please let me know if I am... (0 Replies)
Discussion started by: fazzasx
0 Replies

8. Solaris

Solaris in a SAN BOOT

My current situation is like this, I have a v440 connected to a netapp central storage 3140 via fiber channel, my OS and oracle is installed in the internal drive of the v440. What I would like to do is to advertise another LUN in netapp to the v440 and let my v440 boot from it so I can start... (3 Replies)
Discussion started by: q8devilish
3 Replies

9. Red Hat

rhel-5.2-64bit, boot from SAN

hi all, i have qle 2460 hba card in my server. and i have a lun from promise array from raid 0. I want to boot my OS (rhel5.2-64 bit) lun on a dell t300 server. can some one help me on this please asap.. (0 Replies)
Discussion started by: navadeep
0 Replies

10. HP-UX

Need Help for configuring Boot from San

Hi all, I am trying to configure my HPUX host 11.31 IA64 to boot from a LUN for EMC clariion CX3-80 (Flaire PNR 26). I am following the below mentioned steps.. vi /tmp/idf 3 EFI 500MB HPUX 100% HPSP 400MB idisk -f /tmp/idf -w /dev/rdisk/diskxxx insf -e pvcreate -B... (0 Replies)
Discussion started by: barun agarwal
0 Replies
Login or Register to Ask a Question
root_archive(1M)														  root_archive(1M)

NAME
root_archive - manage bootable miniroot archives SYNOPSIS
/boot/solaris/bin/root_archive pack archive root /boot/solaris/bin/root_archive unpack archive root /boot/solaris/bin/root_archive packmedia solaris_image root /boot/solaris/bin/root_archive unpackmedia solaris_image root The root_archive utility is used to manage bootable miniroot archives and is currently only available on platforms. The utility can pack and unpack boot/root archives in both ufs and hsfs (iso9660) format. It will always generate ufs archives. root_archive also uses the lofi file driver to export a file as a block device (see lofi(7D)) and mount to mount or unmount file systems and remote resources (see mount(1M)). root_archive requires the same privileges that are needed to run these commands. SUBCOMMANDS
The root_archive command has the following subcommands: pack archive root Pack from the image found under the root directory to the archive. unpack archive root Unpack from the archive to an unpacked image under the root directory. packmedia solaris_image root Pack the solaris image to the root directory. unpackmedia solaris_image root Unpack the solaris image from the root directory. For packmedia and unpackmedia, other items that do not go into the ramdisk image are copied or uncopied (see cpio(1)) as well. Specifi- cally, this includes all the packaging databases needed for pkgadd and the other packaging utilities to succeed which are not used in the running and hence pruned to conserve memory. EXAMPLES
Example 1: Unpacking the Solaris x86 install image The following command unpacks the current Solaris image from the root directory: # root_archive unpackmedia /export/nv/solarisdvd.nvx_dvd/latest /export/Boot Where /export/nv/solarisdvd.nvx_dvd/latest represents a path to a Solaris x86 install image and /export/Boot is a directory that will be purged or created, as necessary. Example 2: Packing the Solaris x86 install image The following command packs the current Solaris image to the root directory: # root_archive packmedia /export/nv/solarisdvd.nvx_dvd/latest /export/Boot The following exit values are returned: 0 The command completed successfully. 1 The command exited due to an error. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ cpio(1), bootadm(1M), mount(1M), attributes(5), lofi(7D) 26 Sep 2005 root_archive(1M)