Sponsored Content
Full Discussion: Installing Solaris 10
Operating Systems Solaris Installing Solaris 10 Post 302187238 by fabtagon on Sunday 20th of April 2008 12:42:59 PM
Old 04-20-2008
your machine obviously tries to boot from some NTFS or FAT partition.

i) remove any usb sticks or floppy disks
ii) have you burnt that iso image as iso image? (not as a file onto the disc)
iii) does any other boot cd (Windows Install Disc, Knoppix, ...) work correctly on that machine?
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Installing Solaris 8

I'm new to Unix, and Installed Solaris 8 (IA) for the first time with the end user software group, I got the login screen at startup. When I re-installed it with the Full Distribution plus OEM support it bypasses the login screen and logs me as superuser (root). Is this normal? Thanks in... (3 Replies)
Discussion started by: tdrivas
3 Replies

2. UNIX for Dummies Questions & Answers

Installing Solaris

Hi I am trying to install Solaris for Intel, I am getting a error message saying can't open -VTOC. I have tried installing it on two PCs and I get the same error message on both PCs. Can some please help me. Thanks alot Chamkila (1 Reply)
Discussion started by: chamkila
1 Replies

3. Solaris

installing solaris 10

hi all, i am trying to install solaris 10 into sun ultra 3000 i burn .iso image into cd-rw with 6x speed(iomega) and when i put into cdrom server i got the problem like below: {a} ok boot cdrom -s Boot device: /sbus@3,0/SUNW,fas@3,8800000/sd@6,0:f File and args: -s Bad magic number in disk... (11 Replies)
Discussion started by: waterbear
11 Replies

4. Solaris

installing solaris

i have a laptop that i am no longer using and wish to try and install solaris 10 on it for learning purposes but im stumped. i went to sun.com and downloaded the dvd image but i feel like im at a dead end. the files and folders on the dvd image are clearly meant to be used on an existing unix-based... (2 Replies)
Discussion started by: S1CK_0F_WINDOHS
2 Replies

5. Solaris

Re-installing Solaris

I am a Windows admin but we require the use of at least one SUN for an application that cannot be installed on Windows. We've had two SUN Netra X1 boxes for some time that have seen some use, but I'm told the newest version of the application cannot be installed on the version of Solaris that is... (12 Replies)
Discussion started by: tawnos42
12 Replies

6. Solaris

Installing Solaris 8 bootblock without Solaris Install CD

Hello everyone, Background: I'm having an issue with booting a clone of hard drive with Solaris 8 installation. For cloning process I have used g4l, running under click'n'clone option. As far as I know the actual operation ran behind g4l's interface was dd, though I do not have any information... (12 Replies)
Discussion started by: johnny994
12 Replies

7. Hardware

Installing Solaris

Hello ladies and gentlemen I had a notebook 250 GB for windows 7, 250 GB for slackware, by the live dvd slaris i installed solaris in partition of windows, instalation ok, when i restart, i can not access menu bios or menu boot, and my notebook doesn't boot any dvd ,.. any help what i can... (0 Replies)
Discussion started by: gitac
0 Replies
MKRESCUE(8)						      System Manager's Manual						       MKRESCUE(8)

NAME
mkrescue - make rescue floppy or CD SYNOPSIS
/sbin/mkrescue makes a bootable rescue floppy or CD using the default kernel specified in lilo.conf. DESCRIPTION
mkrescue takes its specifation for the kernel from the default image specified in /etc/lilo.conf. If the actual default is an other= spec- ification, then use the first image= specification. Any associated initial ramdisk (initrd=), and append= options will also be used. The root directory will be taken to be the current root. A bootable floppy or CD-image will be created using LILO version 22.5.5 or later. mkrescue normally requires no options, unless a CD-image is desired (--iso). OPTIONS
--append <string> Override any append= options taken from the default image. If there is any doubt about whether the lilo.conf options are correct, then specify no kernel parameters by providing the null string (--append ""). --debug Provide verbose output of the operation of mkrescue, pausing to allow the setting of internal operating parameters to be viewed. <CR> must be hit to proceed from these pauses. --device <device> Make the floppy on a device other than /dev/fd0. The floppy disk will always be made to boot on BIOS device code 0x00 (A: drive), without regard to the drive on which it is created. --fast Use a faster method of creating the boot floppy. This involves first creating a file of --size 1k blocks (default is 1440) mounted using a loopback device, creating the bootable floppy, then copying the entire file to the disk. --fs [ ext2 | msdos | minix ] Specify the type of filesystem to create on the drive. ext2 is the default, but msdos and minix allow slightly more disk sectors for really big kernels. --help Print a short usage synopsis, including a list of command options. --image <label> Specifies the label or alias of the particular image from which the append, initial ramdisk, root, keytable, and kernel information is to be taken. --initrd <filepath> and --kernel <filepath> These options, which must be used together, allow specification of an arbitrary kernel file and initial ramdisk file to be used on the created boot floppy. Be sure you know what you are doing before you use these options. If no inital ramdisk is needed with a particular kernel, then you MUST specify --initrd "", meaning a null pathname. --install [ text | menu ] Allows overriding the default human interface used with the rescue bootloader (configuration file "install=" option). text is the default on 1.2MB and 1.44MB floppy disks, and menu is the default on 2.88MB floppies and HD emulation on CD-R media. --iso Create an ISO-9660 bootable CD image (El Torito Format) suitable for burning to a CD-R or CD-RW. The --device specification defaults to the filename rescue.iso, and the --size defaults to 2880. A utility such as "wodim" may be used to burn the ISO file to a recordable CD medium. With this ISO option, the --size HD option is allowed. --nocompact For faster kernel loading from a floppy, LILO map compaction is normally enabled. This option will disable map compaction by omit- ting the lilo -c switch. --noformat Suppresses creation of a new filesystem on the boot floppy. This option may be used ONLY when you know that the floppy you will be writing upon is formatted with the same filesystem as specified by --fs XXX (default is ext2). --root <device> Specify the root filesystem for the kernel on the boot floppy. The currently mounted root is taken as the default specification. --size [ 1440 | 1200 | 2880 | HD ] The default floppy disk size is 1440, meaning a 1.44MB floppy. When --iso is specified, the default size is 2880. Allowed specifi- cations are 1200, 1440, or 2880, meaning a 1.2MB, 1.44MB or 2.88MB floppy, respectively. No other floppy disk sizes are supported. The HD specification, meaning "hard disk", may only be used with the --iso option, to indicate a 16MB hard disk is to be generated for emulation. This allows for very large kernel/initial ramdisk combinations on CD-R. The hard disk image is created using loop- back devices /dev/loop0 and /dev/loop1, which must be free to utilize this size option. --version Print the version number of mkrescue, then terminate. SEE ALSO
cdrecord(1), dd(1), wodim(1), lilo.conf(5), lilo(8), mkfs(8), mkinitrd(8), mkisofs(8), mount(8) 6 Mar 2011 MKRESCUE(8)
All times are GMT -4. The time now is 01:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy