06-02-2015
The CD ISO's #1 thru' #5 are the Solaris 10 media distribution on CD's (instead of one DVD). So #1 is bootable and should be the one to burn.
However, I have also provided a Solaris Sparc Rescue CD ISO which is a third-party (non-Oracle) bootable CD containing various rescue utilities which you may find useful.
First thing to do is to burn ISO #1 and boot the system into single user and try to fix your root filesystem.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
when installing a piece of third part software I get the error "Bad magic number" at one point when it tries to use libraries from the bea tuxedo server. Am I correct that this means that the software is expecting 32bit while I'm on 64bit? Is there a way around it or can it only be solved... (5 Replies)
Discussion started by: rein
5 Replies
2. Solaris
I tried rebooting my Sun server just a few minutes ago and I got the following at boot:
--
Sun Fire 280R (UltraSPARC-III+) , No Keyboard
Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.5, 1024 MB memory installed, Serial #xxxxxxxxx
Ethernet address... (6 Replies)
Discussion started by: deckard
6 Replies
3. Filesystems, Disks and Memory
Dear All,
i have a SCSI hard disk drive i'm installing on it solaris 5 and the workstation is sun sparc, i made an image of this H.D using Norton Ghost 6, so i took off the SCSI H.D from the sun workstation and put it on a Compaq server then i booted the server from the Norton Ghost floppy disk... (0 Replies)
Discussion started by: wesweshahaha
0 Replies
4. UNIX for Advanced & Expert Users
Hello All,
(RHEL4)
Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array.
I somehow managed to up the system with working raid1 array.
But the main problem persisted..
i.e when I reboot the system, mounting... (0 Replies)
Discussion started by: ravinandan
0 Replies
5. Solaris
Hello All,
I m very new to this forum.
i m having SUN NETRA X1 server with 40 GB HDD (Seagate) & 128 MB RAM.
i m trying this server for SUN 10 Practise.
As i m installing SUN 9 /10 with CD ,its giving me error after OK propmt
***************************
#boot cdrom
or
#boot cdrom... (16 Replies)
Discussion started by: amrut_k
16 Replies
6. Solaris
Hello,
I'm brand new to Sun/Solaris.
I have a Sun Blade 150, with SunOS 5.8.
I wanted to make a backup to prevent future data loss, so I put the disk in a normal PC with Windows XP to try to make a backup with Norton Ghost, the disk was detected, but not the file volume, so I place the disk... (6 Replies)
Discussion started by: Resadija
6 Replies
7. Solaris
I'll keep it fairly straight forward. I work with a Solaris server and magically today it decided to take a dump on me. At first it give a long list of files that couldn't be acessed before terminating the boot process and returning to the 'ok' prompt. Booting in single-user mode allowed me to run... (4 Replies)
Discussion started by: Aon
4 Replies
8. Solaris
I have created 1 LUN.
1)LUN 00BB 200GB /dev/rdsk/c1t3d44
/dev/rdsk/c2t28d44
/dev/rdsk/c3t19d44
/dev/rdsk/c4t12d44
2) Already added the new entry into sd.conf and rebooted.
3) Already done these:
powercf –q
power config
4) power display dev=all
I can see the new Symmetrix device.... (1 Reply)
Discussion started by: sirius20d
1 Replies
9. Solaris
Is there a way to recover label?
I could install (sparc) Solaris again, but it would take a lot of time. (5 Replies)
Discussion started by: orange47
5 Replies
10. Solaris
So we have a new to us v240 server with no OS installed. It has an outdated version of OB and ALOM so before we install the OS we want to update both. We have a DVD with the latest OB patch burned on it.
We do the boot cdrom command but receive the Bad Magic Number Error. Does an OS need to... (2 Replies)
Discussion started by: dunkpancakes
2 Replies
LILO(8) System Manager's Manual LILO(8)
NAME
lilo - install boot loader
SYNOPSIS
Main function:
/sbin/lilo - install boot loader
Auxiliary uses:
/sbin/lilo -q - query map
/sbin/lilo -R - set default command line for next reboot
/sbin/lilo -I - inquire path name of current kernel
/sbin/lilo {-u|-U} - uninstall lilo
DESCRIPTION
lilo installs a boot loader that will be activated next time you boot. It has lots of options.
-v Increase verbosity. Giving one or more -v options will make lilo more verbose.
-q List the currently mapped files. lilo maintains a file, by default /boot/map, containing the name and location of the kernel(s) to
boot. This option will list the names therein.
-m map-file
Use specified map file instead of the default.
-C config-file
lilo reads its instructions about what files to map from its config file, by default /etc/lilo.conf. This option can be used to
specify a non-default config file.
-d delay
If you have specified several kernels, and press Shift at boot-time, the boot loader will present you with a choice of which system
to boot. After a timeout period the first kernel in the list is booted. This option specifies the timeout delay in deciseconds.
-D label
Use the kernel with the given label, instead of the first one in the list, as the default kernel to boot.
-r root-directory
Before doing anything else, do a chroot to the indicated directory. Used for repairing a setup from a boot floppy.
-t Test only. Do not really write a new boot sector or map file. Use together with -v to find out what lilo is about to do.
-c Enable map compaction. This will merge read requests from adjacent sectors. Speeds up the booting (especially from floppy).
-f disk-tab
Specify disk geometry parameter file. (The default is /etc/disktab.)
-i boot-sector
Specify a file to be used as the new boot sector. (The default is /boot/boot.b.)
-l Generate linear sector addresses instead of sector/head/cylinder addresses.
-L Generate 32-bit Logical Block Addresses instead of C:H:S addresses, allowing access to all partitions on disks greater than 8.4Gb.
-P {fix|ignore}
Fix (or ignore) `corrupt' partition tables, i.e., partition tables with linear and sector/head/cylinder addresses that do not corre-
spond.
-s save-file
When lilo overwrites the boot sector, it preserves the old contents in a file, by default /boot/boot.NNNN where NNNN depends on the
device. This option specifies an alternate save file for the boot sector. (Or, together with the -u option, specifies from where to
restore the boot sector.)
-S save-file
Normally, lilo will not overwrite an existing save file. This options says that overwriting is allowed.
-u device-name
Uninstall lilo, by copying the saved boot sector back. A time-stamp is checked.
-U device-name
Idem, but do not check the time-stamp.
-R command line
This option sets the default command for the boot loader the next time it executes. The boot loader will then erase this line: this
is a once-only command. It is typically used in reboot scripts, just before calling `shutdown -r'.
-I label
The label of the running kernel can be found in the environment variable BOOT_IMAGE after startup. This command will print the cor-
responding path name on stdout.
-V Print version number.
The above command line options correspond to the key words in the config file indicated below.
-b bootdev boot=bootdev
-c compact
-d dsec delay=dsec
-D label default=label
-i bootsector install=bootsector
-f file disktab=file
-l linear
-L lba32
-m mapfile map=mapfile
-P fix fix-table
-P ignore ignore-table
-s file backup=file
-S file force-backup=file
-v verbose=level
SEE ALSO
lilo.conf(5).
The lilo distribution comes with very extensive documentation.
AUTHOR
Werner Almesberger (almesber@bernina.ethz.ch).
John Coffman (johninsd@san.rr.com) (lba32 extensions).
20 March 2000 LILO(8)