Sponsored Content
Full Discussion: Booting Problem
Top Forums UNIX for Advanced & Expert Users Booting Problem Post 14149 by Kenan on Monday 28th of January 2002 08:01:51 PM
Old 01-28-2002
Installing LILO into the MBR

Hello!

You can use "loadlin" so you don't need to install LILO into your MBR. If you want to use LILO anyway, you should find out what disk and what partition your root filesystem "/" is mounted on. You also should know the same information for your Windows partition (i.e. /dev/hda1 or something like that).
Post here the contents of your /etc/lilo.conf file and I will try to help you further!

Regards,

Kenan Kalajdzic
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problem with booting

Hi! I installed Slackware on my computer so I thought I could have dual booting with ME, but that didn't work. So I installed another bootmanager that I find on internet. When I startup my computer the second bootmangaer that I did find on internet lets me choose system. When I have choosen... (3 Replies)
Discussion started by: Mr.Rudiment
3 Replies

2. UNIX for Dummies Questions & Answers

<< booting problem with redhat 8.0 >>

i have the Redhat installed in this Hard Drive and i wanna use it in this old computer of mine.. it works fine in my new computer.. but when i put it in my old one.. which is.. P1 150MHz 32MBramz it wont load the kernal and keeps on restarting the computer.. keeps on goin like this.. i get the GRUB... (2 Replies)
Discussion started by: dezithug
2 Replies

3. Solaris

Problem with 280R not booting

The box is in Houston, and I am in Dallas. Anyway, I do have serial access to the console. The box is hanging just after the WARNING's for the SDS modules not loading (normal boot message). I booted off CD, and mounted up all the file systems. Everything looked normal, and I could not find any... (3 Replies)
Discussion started by: 98_1LE
3 Replies

4. Solaris

Booting problem Veritas

Hi , I am having 490 Sun Fire Server ,Server having Two 72 GB each Disk.Disk are under veritas VM 4 control. Both disk are mirred with veritas VM4. Fisrt disk is encapsulate and other disk is mirred.System is working Fine but when I removed Fitrst Disk and reboot the system it does not boot from... (4 Replies)
Discussion started by: pradeeprajput_k
4 Replies

5. Solaris

booting problem

any one can help me. my system running on solaris 2.7. recently there is sudden power failure while system running. after that unable to boot the system. it is giving comment that "can not open /etc/path_to_inst" and then returning back to "OK" after comment of termination. The processor is... (10 Replies)
Discussion started by: prabir
10 Replies

6. Ubuntu

Problem while booting linux

Hi all, We are using linux Redhat 9. While booting the server, it says /proc not mounted and it says "Segmentation fault" and doesn't continue with booting. Basically, it started while we inserted a pen drive and removed it without mounting and un mounting it. After removing the pen drive &... (1 Reply)
Discussion started by: mjdarm
1 Replies

7. UNIX for Dummies Questions & Answers

problem booting

Dear List, While I was adding second hard disk to my system, I changed the /etc/fstab file by adding the following line: /mnt/sdb1 /dev/sdb1 ext3 default 2 1 Now system does not boot and gives the following error: Checking filesystems /: Clean, 309260/18495840 files, 1064776/18486790... (2 Replies)
Discussion started by: siavoush
2 Replies

8. AIX

Booting problem

Dears, I have a problem when i reboot the machine last time "AIX 5.3", that after rebooting it not login to graphical desktop, it just stop at console login command line. Kindly find the attached screenshot. Anyway to let it login automatically to Desktop? Would appreciate any pointers to... (1 Reply)
Discussion started by: moudmm
1 Replies

9. AIX

Problem to booting up p730

Hi Everyone, We have IBM p730 that I am trying to booting up to AIX 7.1. But it stops at RUNTIME. C7004087 C7004091 C7004091 (show is code number twice) STANDBY RUNTIME The explanation for C7004091 is the final IPL status progress code to be displayed before the system reaches... (5 Replies)
Discussion started by: lilyn
5 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 04:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy