Sponsored Content
Full Discussion: linux boot problem
Top Forums UNIX for Dummies Questions & Answers linux boot problem Post 30294 by BSeanD on Sunday 20th of October 2002 12:53:27 AM
Old 10-20-2002
Check your lilo.conf file. Sounds like you've got the loader on the second drive and not the first.
Any chance of you posting your lilo.conf so we can have a look?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Boot problem

we have a problem with a server UNIX SUN OS 5.7 : we tried to reboot it and we have the following error message : "boot load failed the file just loaded does not appear to be executable " we booted the server in single user mode with the cdrom we made the mirrored disk bootable we tried... (2 Replies)
Discussion started by: farzolito
2 Replies

2. Red Hat

linux will not boot, boot to grub prompt

my redhat 9 will not boot. We had a power failure and when the power came back, my redhat linux will not boot. The machine come up to grub prompt. I tried the following from grub prompt root (hd0, then press tab key partition num:0 filesystem type unknown, partition type 0x83... (7 Replies)
Discussion started by: hassan2
7 Replies

3. UNIX for Advanced & Expert Users

Boot Problem

Hi All. Yesterday my pc worked fine. Today when booting the sequence gets just past mounting the root filesystem - it then says ' Module dependencies up to date (no new kernel modules found).' At this point it hangs and goes no further! Does this sound familiar to anyone? I am running... (2 Replies)
Discussion started by: silvaman
2 Replies

4. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

5. UNIX for Dummies Questions & Answers

boot loader problem - can't load linux

Hi i have both Linux and Windows XP on my PC. i used to use grub as a boot loader and everything was perfect, until i reinstalled Windows. apparently, Windows installer installed its own bootloader, that doesn't recognize Linux. i tried using a tool called GrubInstaller for Windows, and now... (4 Replies)
Discussion started by: shx2
4 Replies

6. Solaris

Boot problem

Hi everyone, I have sun fire280R machine before i it is installed with solaris5.9 now i want to upgrade it but it not booting from the cd rom ....OK prompt also not comming i dont have solaris keyboard to press stop-A key...i have a intel supported keyboard ...what may be the problem it is... (1 Reply)
Discussion started by: alakshmanrao
1 Replies

7. UNIX for Dummies Questions & Answers

Linux won't boot

I'm trying to install Fedora 9 on a Dell OptiPlex GX300 machine. The instalation runs properly, but when the computer restarts after the instalation, it simply won't boot, like there's no OS installed. I tried diffrent Linux distributions, but nothing works. This are the partitions, maybe it's... (12 Replies)
Discussion started by: teis
12 Replies

8. UNIX for Dummies Questions & Answers

boot problem

hello i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message: Enabling system bus....... Done Initializing CPUs......... Done Initializing boot memory.. RAM-Copy CRC failure!Can't start: No image found FATAL: Can't find/decompress... (0 Replies)
Discussion started by: bahjatm
0 Replies

9. Solaris

boot problem

hello i have a sun server V890 and it stops booting after adding 2 CPUs modules and gives me the following error message: Enabling system bus....... Done Initializing CPUs......... Done Initializing boot memory.. RAM-Copy CRC failure!Can't start: No image found FATAL: Can't find/decompress... (12 Replies)
Discussion started by: bahjatm
12 Replies

10. Solaris

Boot problem

Hi all, I have the the following SCSI diagnostic codes shown in the attached photo I suspect disk drive failure what can I do further to diagnose the disk. and if possible to boot into OS again. (5 Replies)
Discussion started by: h@foorsa.biz
5 Replies
LVMCREATE_INITRD(8)					      System Manager's Manual					       LVMCREATE_INITRD(8)

NAME
lvmcreate_initrd - create an initial ramdisk to boot with root on a logical volume SYNOPSIS
lvcmreate_initrd [-i|--iop IOP] [-D|--devfs] [-v|--verbose] [-V|--version] [KernelVersion] DESCRIPTION
lvmcreate_initrd creates a new compressed initial ramdisk /boot/initrd-lvm-KernelVersion.gz. The initial ramdisk contains all necessary binaries, shared libraries and a linuxrc file to switch to a logical volume based root filesystem. To build an initial ramdisk for a ker- nel other than the one currently running add the KernelVersion parameter (e.g. lvmcreate_initrd 2.3.25) on the command line. OPTIONS -h, --help Print a usage message on standard output and exit. -i, --iop IOP Specify the LVM kernel IOP version if you are using wrapper scripts in /sbin. This is only necessary if you are building an initrd for a kernel other than the current one, and you have tools for multiple IOP versions installed. -D, --devfs Force the use of devfs when building the initrd. lvmcreate_initrd by default probes for devfs by checking for /dev/.devfsd, which is created by devfsd when it is running. This option will force lvmcreate_initrd to do this, when devfsd is not currently running. -v, --verbose Gives verbose runtime information about the creation of the ram disk image. -V, --version Print version number and exit successfully. The necessary actions to change your system into a "root on logical volume" one are: Create a small (~20MB) partition which is BIOS reachable to hold the /boot filesystem (if you already have a small partition based root filesystem this can be used instead). If you want to boot standalone from this partition in an emergency, copy all the necessary binaries and libraries to that filesystem as well and create a corresponding /etc/lilo.conf entry. In order to be able to edit lilo.conf when booted standalone, you should move /etc/lilo.conf to /boot/lilo.conf and create a symbolic link to it in /etc. This is not needed if you have a boot/root floppy which contains the LVM binaries and the library. Create all logical volumes you need (for root, usr, opt etc.), create filesystems in them, mount them and transfer all files from the par- tition based filesystems into the logical volume based ones. Set up your /etc/lilo.conf with a boot configuration like: image = /boot/vmlinuz initrd = /boot/initrd-lvm-KernelVersion.gz root = /dev/YourVG/YourRootLV label = rootonlv append = 'ramdisk_size=8192' Replace YourVG and YourRootLV by your actual volume group and root logical volume names. You also need to change the ramdisk size to be at least as large as that reported while lvmcreate_initrd is run. If you have enough memory, it is OK if the ramdisk size in /etc/lilo.conf is larger than what lvmcreate_initrd reports (the memory is freed after booting). Also, your /etc/fstab in the root logical volume should contain entries for the root LV, and the boot partition, along with any other LVs you have configured: /dev/YourVG/YourRootLV / ext2 defaults 0 1 /dev/YourBootPartition /boot ext2 defaults 0 2 /dev/YourVG/YourUsrLV /usr ext2 defaults 0 3 /dev/YourVG/YourOptLV /opt ext2 defaults 0 4 etc. You can use other supported filesystem types as well (e.g. reiserfs) if you have support for those in your kernel. Run lilo, reboot and try... The partitions containing the former /usr, /opt etc. filesystems can now be used as physical volumes. Use pvcreate(8) to turn them into PVs and then use vgextend(8) to add them to e.g. YourVG. DIAGNOSTICS
lvcmcreate_initrd returns 0 for success. 1 is returned in all other cases. SEE ALSO
lilo(8), lilo.conf(5), fstab(5), lvm(8), pvcreate(8), vgextend(8), lvcreate(8), vgcreate(8) AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com> Heinz Mauelshagen LVM TOOLS LVMCREATE_INITRD(8)
All times are GMT -4. The time now is 03:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy