06-04-2013
Hello,
You can try to mount your iso image using lofiadm, this command create a special file that you can use to simulate cd-rom/dvd.
Then use ldom command to add virtual device as cdrom/dvd.
then from boot prompt boot from cdrom.
NB: make verification on your obp regarding the aliases and devices
- # lofiadm -a /path/to/cd.iso
OUTPUT: /dev/lofi/1
- # ldm add-vdsdev /dev/lofi/1 cdrom@primary-vds0
- ok boot cdrom
PLEASE GIVE FEEDBACK
These 2 Users Gave Thanks to mat_solaris For This Post:
9 More Discussions You Might Find Interesting
1. AIX
Hi,
I need to install the package bos.loc.iso.en_GB on an AIX 5.3 server but try as I might I cannot find the file which contains this package.
I have all the AIX 5.3 CDs and also the majority of the packages installed locally on the server. If I create a .toc file from the local packages I... (3 Replies)
Discussion started by: m223464
3 Replies
2. Solaris
Hi all
Im rebuilding an 6800 domain with solaris 10. Server is located in a different town and cant be bothered to drive down and install a dvd into its drive.
So, apart from jumpstarting it and using a local DVD, is there a way I can an ISO image to build a new client ?? eg. mount an ISO... (2 Replies)
Discussion started by: sbk1972
2 Replies
3. Solaris
Hi Gurus
Recently i had download the ISO installer (sol-10-u8-ga-sparc-dvd.iso) for Solaris 10.
And i ftp to a Server.
May i know is it possible to install the Solaris by using this ISO file directly (not using network)? (8 Replies)
Discussion started by: SmartAntz
8 Replies
4. Solaris
Hi,
I have issues installing Solaris into a LDom using a Solaris10u5/08 DVD. I have been troubleshooting for the past 2 days and I still cannot get it up.
Here is the logs:
root@eld-app2# ldm add-vdsdev /cdrom/sol_10_508_sparc/s0 cdrom0@primary-vds0
root@eld-app2# ldm add-vdisk cdrom0... (4 Replies)
Discussion started by: bolasutra
4 Replies
5. Solaris
Apologies if this is the wrong forum..
I have some LDOMs running on a Sparc server. I copied the disk0 file from one chassis over to another, stopped the ldom on the source system and started it on the 2nd one. All fine. Shut it down and flipped back. We then did a fair bit of work on the... (4 Replies)
Discussion started by: tommyq
4 Replies
6. SCO
Trying to restore a 5.0.6 server to a new server but the owner doesnt have their install media. Saw that many people have this. Please let me know of anyone that has a download link. Much appreciation! (1 Reply)
Discussion started by: gavinseabrook
1 Replies
7. Solaris
Hi,
Our existing environment is having primary domain and 3 guest domains are running over it. See the attached image.
Now we want to add a new primary virtual switch and move LDOM3 to be connected with new primary switch.
So, I am not sure how to achieve this because. If I remove the... (7 Replies)
Discussion started by: praveensharma21
7 Replies
8. Solaris
used mkisofs -lJR -o output_image.iso directory_name to create an iso on the primary domain of a server.
mounted it locally in the primary using
lofiadm -a /path/to/cd.iso
mount -o ro -F hsfs /dev/lofi/1 /mnt
verified that I could read the disk correctly.
then created a vdsdev using... (2 Replies)
Discussion started by: os2mac
2 Replies
9. Solaris
I have a Sun T4-1 running Solaris 11.4 with a static IP 192.168.0.183. On this machine is a Solaris 10 LDOM with a static IP of 192.168.0.78. The other day I had to stop the LDOM to do a memory reconfigure. When I rebooted it I got an error that the IP 192.168.0.78 was already in use and so... (4 Replies)
Discussion started by: Michele31416
4 Replies
lofi(7D) Devices lofi(7D)
NAME
lofi - Loopback file driver
DESCRIPTION
The lofi file driver exports a file as a block device. Reads and writes to the block device are translated to reads and writes on the
underlying file. This is useful when the file contains a file system image. Exporting it as a block device through the lofi file driver
allows normal system utilities to operate on the image through the block device (like fstyp(1M)fsck(1M), and mount(1M). This is useful for
accessing CD-ROM and FAT floppy images. See lofiadm(1M) for examples.
File block device entries are contained in /dev/lofi, while /dev/rlofi contains the character (or raw) device entries. Entries are in the
form of decimal numbers which are assigned through lofiadm(1M). When created, these device entries are owned by root, in group sys, and
have permissions 0600. While ownership, group, and permission settings can be altered, there are possible ramifications. See lofiadm(1M)
for more information.
FILES
/dev/lofictl
Master control device
/dev/lofi/n
Block device for file n
/dev/rlofi/n
Character device for file n
/kernel/drv/lofi
32-bit driver
/kernel/drv/lofi.conf
Driver configuration file. (Should not be altered.)
/kernel/drv/sparcv9/lofi
64-bit driver
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsr, SUNWcarx.u |
+-----------------------------+-----------------------------+
SEE ALSO
lofiadm(1M), fsck(1M), fstyp(1M), mount(1M), newfs(1M), attributes(5), lofs(7FS)
NOTES
Just as you would not directly access a disk device that has mounted file systems, you should not access a file associated with a block
device except through the lofi file driver.
For compatability purposes, a raw device is also exported along with the block device. For example, newfs(1M) requires one.
SunOS 5.10 30 Jul 1999 lofi(7D)