10 More Discussions You Might Find Interesting
1. Solaris
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
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
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
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
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
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
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
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
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
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
BOOT(8) BSD System Manager's Manual BOOT(8)
NAME
boot -- system bootstrapping procedures
DESCRIPTION
This document provides information on using common features in the NetBSD boot loader. Additional information may be found in architecture-
specific boot(8) manual pages.
In the native NetBSD boot protocol, options are passed from the boot loader to the kernel via flag bits in the boothowto variable (see
boothowto(9)).
Interactive mode
In interactive mode, the boot loader will present a prompt, allowing input of these commands:
boot [device:] [filename] [-1234abcdmqsvxz]
The default device will be set to the disk that the boot loader was loaded from. To boot from an alternate disk, the full name of
the device should be given at the prompt. device is of the form xd [N[x]] where xd is the device from which to boot, N is the unit
number, and x is the partition letter.
The following list of supported devices may vary from installation to installation:
hd Hard disks.
fd Floppy drives.
The default filename is netbsd; if the boot loader fails to successfully open that image, it then tries netbsd.gz (expected to be a
kernel image compressed by gzip), followed by netbsd.old, netbsd.old.gz, onetbsd, and finally onetbsd.gz. Alternate system images
can be loaded by just specifying the name of the image.
Options are:
-1 Sets the machine-dependent flag RB_MD1 in boothowto.
-2 Sets the machine-dependent flag RB_MD2 in boothowto.
-3 Sets the machine-dependent flag RB_MD3 in boothowto.
-4 Sets the machine-dependent flag RB_MD4 in boothowto.
-a Sets the RB_ASKNAME flag in boothowto. This causes the kernel to prompt for the root file system device, the system crash
dump device, and the path to init(8).
-b Sets the RB_HALT flag in boothowto. This causes subsequent reboot attempts to halt instead of rebooting.
-c Sets the RB_USERCONF flag in boothowto. This causes the kernel to enter the userconf(4) device configuration manager as soon
as possible during the boot. userconf(4) allows devices to be enabled or disabled, and allows device locators (such as hard-
ware addresses or bus numbers) to be modified before the kernel attempts to attach the devices.
-d Sets the RB_KDB flag in boothowto. Requests the kernel to enter debug mode, in which it waits for a connection from a kernel
debugger; see ddb(4).
-m Sets the RB_MINIROOT flag in boothowto. Informs the kernel that a mini-root file system is present in memory.
-q Sets the AB_QUIET flag in boothowto. Boot the system in quiet mode.
-s Sets the RB_SINGLE flag in boothowto. Boot the system in single-user mode.
-v Sets the AB_VERBOSE flag in boothowto. Boot the system in verbose mode.
-x Sets the AB_DEBUG flag in boothowto. Boot the system with debug messages enabled.
-z Sets the AB_SILENT flag in boothowto. Boot the system in silent mode.
consdev dev
Immediately switch the console to the specified device dev and reprint the banner. dev must be one of pc, com0, com1, com2, com3,
com0kbd, com1kbd, com2kbd, com3kbd, or auto. See Console Selection Policy in boot_console(8).
dev [device]
Set the default drive and partition for subsequent filesystem operations. Without an argument, print the current setting. device
is of the form specified in boot.
help Print an overview about commands and arguments.
ls [path]
Print a directory listing of path, containing inode number, filename, and file type. path can contain a device specification.
quit Reboot the system.
In an emergency, the bootstrap methods described in the NetBSD installation notes for the specific architecture can be used.
FILES
/boot boot program code loaded by the primary bootstrap
/netbsd system code
/netbsd.gz gzip-compressed system code
/usr/mdec/boot master copy of the boot program (copy to /boot)
/usr/mdec/bootxx_fstype primary bootstrap for filesystem type fstype, copied to the start of the NetBSD partition by installboot(8).
SEE ALSO
Architecture-specific boot(8) manual pages, ddb(4), userconf(4), halt(8), installboot(8), reboot(8), rescue(8), shutdown(8), boothowto(9)
BUGS
The kernel file name must be specified before, not after, the boot options. Any filename specified after the boot options, e.g.:
boot -d netbsd.test
is ignored, and the default kernel is booted.
BSD
September 4, 2009 BSD
09-14-2011
