Make an iSCSI LUN clone bootable


 
Thread Tools Search this Thread
Operating Systems Solaris Make an iSCSI LUN clone bootable
Prev   Next
# 1  
Old 08-04-2014
Make an iSCSI LUN clone bootable

trying to do this for a DR situation. I've cloned an iSCSI LUN to another server. I've created an LDOM on it. set the LDOM to auto-boot=false and exported the LUN as a raw disk to the new LDOM. After starting the LDOM and telnetting to it. I can get to the OK prompt and see the disk but when I try to boot into single user mode I get the following output.

Code:
{0} ok boot disk0
NOTICE: Entering OpenBoot.
NOTICE: Fetching Guest MD from HV.
NOTICE: Starting additional cpus.
NOTICE: Initializing LDC services.
NOTICE: Probing PCI devices.
NOTICE: Finished PCI probing.


SPARC T4-4, No Keyboard
Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.35.3, 24.0000 GB memory available, Serial #83402997.
Ethernet address 0:14:4f:f8:a0:f5, Host ID: 84f8a0f5.



Boot device: /virtual-devices@100/channel-devices@200/disk@0  File and args:
The file just loaded does not appear to be executable.

how to do I make it executable?

Last edited by DukeNuke2; 08-05-2014 at 03:34 AM..
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

DM multipath :iscsi lun shows by diff names on two server where its exported

Hi, I am trying to setup multipathing (using DM multipath) for a redhat cluster setup ...all setup is done but issue is : node 1 shows the shared iscsi lun as sdc node 2 shows the same as sdg (changes on reboots) Due to this (i guess) i get i/o error & i can not read files created by... (0 Replies)
Discussion started by: heman96
0 Replies

2. AIX

Netapp iscsi lun

Hi, I have aix 6.1 box. I want to configure iscsi luns from netapp storage. I tried in google but not getting proper solution for that. i m not getting the proper iqn name. Please share me the steps to complete this requirements. Thanks in advance. (1 Reply)
Discussion started by: sunnybee
1 Replies

3. AIX

Mount a SAN LUN which contains clone copy - AIX 6.1

Hello Everyone, Can someone help me to mount a SAN hdisk which contains a clone data copy(san) of the remote server to the another machine. Both servers are running in AIX. Thanks in advance ! Regards, Gowtham.G (3 Replies)
Discussion started by: gowthamakanthan
3 Replies

4. AIX

Any tips to grow iSCSI LUN

Hi, I have an iSCSI LUN attached to an AIX 5.3 box. It's initial size is 250GB, I just grew it on the SAN to 300GB, but AIX is not seeing the change. Right now I have some processes going and it's eating up the disk space. I need to grow this lun by atleast 30GB otherwise the process with bomb... (5 Replies)
Discussion started by: bbbngowc
5 Replies

5. Solaris

Solaris10 -> iscsi -> equiliogic lun

We "lose" the iscsi device after a reboot - i.e., it appears in /dev/rdsk and /dev/dsk but format cannot find it. Obviously, it won't mount either. This happens for two separately defined luns. We must be missing a step in iscsiadm. The luns are defined as targets, we can see them in... (2 Replies)
Discussion started by: jim mcnamara
2 Replies

6. Solaris

Set up iscsi LUN on solaris 9?

Hi, I need to set up iscsi LUN on Solaris 9. I've done it on Solaris 10 with iscsiadm. How do you do it on Solaris 9 though? Currently using Solaris 9 update 2. Your help is appreciated. Thanks, Sparcman (6 Replies)
Discussion started by: sparcman
6 Replies

7. AIX

Help growing iscsi lun

Hi, I have an iSCSI LUN of 200GB. I increased it to 250GB and when I try to increase the size of the vg, I'm getting an error that none of the volumes have increased in size. How can I get the OS to see the additional 50GB? ---------- Post updated at 03:22 PM ---------- Previous update... (9 Replies)
Discussion started by: bbbngowc
9 Replies

8. Filesystems, Disks and Memory

Make non-bootable scsi drive, bootable

In our HP/Unix system, our master scsi drive was bootable and our mirrored drive was non-bootable. Are any of these alternatives possible: 1) Make the non-bootable scsi drive bootable? How? 2) Create a bootable scsi drive, then copy the mirrored data to the newly created scsi drive? I seek... (1 Reply)
Discussion started by: bfisk
1 Replies

9. Solaris

How to make a bootable disk?

The second disk that I'm trying to make bootable is to hold another version of Solaris (9). I've created the partitions with format and labeled the disk - created the filesystems with newfs - created and mounted the directories. ...but I think I've missed something out like using fdisk to... (16 Replies)
Discussion started by: pondlife
16 Replies

10. UNIX for Dummies Questions & Answers

recover DIsk and make bootable

Hello all, I'm trying to recover from backup file to a new system with a new disk. I'm able to partition my new hard drive the same way as my old drive, but I'm unable to boot off of it. I have set the fdisk to toogle as a boot flag. But it does not seem to be working. Does anyone know how to... (4 Replies)
Discussion started by: larryase
4 Replies
Login or Register to Ask a Question
ISCSI-INITIATOR(8)					    BSD System Manager's Manual 					ISCSI-INITIATOR(8)

NAME
iscsi-initiator -- refuse-based iSCSI initiator SYNOPSIS
iscsi-initiator [-46bcDfVv] [-a authentication-type] [-d digest-type] [-h target-hostname] [-p target-port-number] [-t target-number] [-u username] mount_point DESCRIPTION
The iscsi-initiator utility can be used to access an iSCSI target, such as iscsi-target(8), to access block storage which has been exported. Information pertaining to the target is displayed underneath the mount point, along with the device corresponding to the storage which the target exports. The various arguments are as follows: -4 Use an IPv4 connection to the target. -6 Use an IPv6 connection to the target. -a authentication-type Use the specified authentication type when communicating with the target. The possible values are chap, kerberos, srp or none. The default value is none. -b Show the storage as a block device. -c Show the storage as a character device. -d digest-type Use the specified digest type when communicating with the target. The possible values are header, data, both, all or none. The default value is none. -D List the LUNs on the specified target and exit (i.e. do discovery only) -f Show the storage as a regular file. -h hostname Connect to the iSCSI target running on the host specified as the argument. -p port-number Connect to the iSCSI target running on the port specified as the argument. The default value is 3260. -t target Connect to the number of the iSCSI target running as the argument. -u username Use the specified user's credentials when logging in to the iSCSI target. There is no default. -V Print out the version number and then exit. -v Be verbose in operation. The refuse(3) library is used to provide the file system features. The mandatory parameter is the local mount point. This iSCSI initiator presents a view of the targets underneath the mount point. Firstly, it creates a directory tree with the hostname of the target, and, in that directory, a virtual directory is created for each target name exported by the iSCSI target program. Within that virtual target directory, symbolic links exist for the hostname (for convenience), a textual representation of the IP address, the iSCSI tar- get product name, the iSCSI target IQN, the iSCSI target vendor and version number. One other directory entry is presented in the virtual target directory, relating to the storage presented by the iSCSI target. This can be in the form of a regular file, which is also the default, a block device or a character device. Please note that the iscsi-initiator utility needs the ``puffs'' kernel module loaded via modload(8) to operate. EXAMPLES
# ./iscsi-initiator -u agc -h iscsi-target0.alistaircrooks.co.uk /mnt # ls -al /mnt/target0 total 576 drwxr-xr-x 2 agc agc 512 May 11 22:24 . drwxr-xr-x 2 agc agc 512 May 11 22:24 .. lrw-r--r-- 1 agc agc 39 May 11 22:24 hostname -> iscsi-target0.alistaircrooks.co.uk lrw-r--r-- 1 agc agc 14 May 11 22:24 ip -> 172.16.135.130 lrw-r--r-- 1 agc agc 16 May 11 22:24 product -> NetBSD iSCSI -rw-r--r-- 1 agc agc 104857600 May 11 22:24 storage lrw-r--r-- 1 agc agc 43 May 11 22:24 targetname -> iqn.1994-04.org.netbsd.iscsi-target:target0 lrw-r--r-- 1 agc agc 8 May 11 22:24 vendor -> NetBSD lrw-r--r-- 1 agc agc 4 May 11 22:24 version -> 0 # SEE ALSO
puffs(3), refuse(3), iscsi-target(8) HISTORY
The iscsi-initiator utility first appeared in NetBSD 6.0. An earlier version called iscsifs was available in NetBSD 5.0 in source format only. AUTHORS
The iscsi-initiator utility was written by Alistair Crooks <agc@NetBSD.org>. BUGS
iscsi-initiator currently only supports a CHAP challenge length of 16 octets. Other initiators support up to 1024 and thus it is expected that most targets will also support such lengths. This means that CHAP compatibility with other targets apart from iscsi-target(8) is likely to be poor. To workaround this, please use authentication type none by not specifying a username with the -u option. BSD
February 22, 2011 BSD