Sponsored Content
Operating Systems Linux Slackware After installing linux cannot boot PC anymore? Post 50895 by woofie on Tuesday 4th of May 2004 10:30:43 PM
Old 05-04-2004
To get a dual boot (windows and linux) you need to edit the /etc/lilo.conf file.

Try adding the following lines into the lilo.conf file.

other=/dev/hda1
label=Windows


Where /dev/hda1 is replace with the Windows partition.

With your second question. When wanting to start linux do you want it to start in a graphical mode or text mode?


Cheers
Woofie

:-)
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Installing Dual Boot Xp is in first want Solaris

I'm looking to add a 2nd hard drive to my computer and make one hard drive Solaris and keep the 2nd as my origional Xp home edition. To basically keep them seperated in what they do. Now saying I have the hard drive in installed and everything and it's blank. I work for Sun Microsystems so i know... (2 Replies)
Discussion started by: Cyrix142
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 Dummies Questions & Answers

Unable to boot with XP after installing SUSE

Hi, I'm not sure if this is the right forum to post. I had following setup before installing SUSE Linux: Windows 98 installed on Primary partition Windows XP installed on Extended Partition When I installed SUSE, it shared space from primary partition and shrunk the size of Windows... (4 Replies)
Discussion started by: patras
4 Replies

4. Ubuntu

Urgent Help Needed: Installing Dual Boot Ubuntu

Hi, I have installed Ubuntu 5.04 on my second Hard Drive. My first HD contains windows. When i make my 2nd HD as boot device, i see GRUB Menu (i.e. stage 2). On trying to boot Ubuntu, I get an Error 15: File missing problem. The FS shown was FAT. On trying to boot Windows, I am presented... (5 Replies)
Discussion started by: karthikb23
5 Replies

5. Solaris

Sun Fire won't boot anymore

Hi all - I have an issue with our (way old) single processor SunFire 280R, running Solaris 9.0.4. It won't boot even after multiple power cycles. There was a power outage last week end in the computer room, so this might have to do. In normal boot mode, the screen shows a single line : ... (5 Replies)
Discussion started by: bostella
5 Replies

6. UNIX for Dummies Questions & Answers

installing centos dual boot with ubuntu

I have installed ubuntu desktop on my hard drive and I gave it all the hard drive. Now I want to repatriate the hard disk and give half of it to anther ext4. How do I do that? Can I do it fron with in the ubuntu? Second when I install the centos, how can I make to recognize the ubuntu and... (0 Replies)
Discussion started by: programAngel
0 Replies

7. Red Hat

After installing redhat, my laptop boot straight to Windows 7

Hi all, Good day. I just installed RHEL6.3 into my laptop to learn RH. There is an existing Windows 7 in there. After installing the RHEL, the laptop will just boot to Windows 7. I tried to use this BCDedit to add Linux entry to the boot menu, BUT each time i pick the redhat selection,... (5 Replies)
Discussion started by: wingcross
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 02:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy