Sponsored Content
Full Discussion: Unable to boot Fedora 10
Operating Systems Linux Red Hat Unable to boot Fedora 10 Post 302468213 by SivaramaRaju on Tuesday 2nd of November 2010 04:56:46 AM
Old 11-02-2010
Hi,

Thanks a lot for your reply.

I am not exactly sure why there are seven partitions on the hard disk. The system earlier had windows XP professional installed on it. On my request, the internal IT team, installed Fedora 10 on it for my testing purposes.

Sure, I will try booting with rescue CD and let you know the results.

Thanks again,
Siva
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Fedora Core 3 boot diskette

I want to upgrade from Red Hat Linux 8.0 to Fedora Core 3. I have already downloaded FC3 on CD's. My current config. on my PC is that I have Win XP on primary hard drive and Red Hat 8.0 on another hard drive. Because my Compaq Presario reserves the first cylinder of my primary hard drive, I... (1 Reply)
Discussion started by: Mark McWilliams
1 Replies

2. Linux

Dual Boot Win XP And Fedora with Fedora Installed First

Hi everyone, I hope this question goes here. Anyways, I have a unique situation where my friend's comp has Fedora installed and wants to add Win XP as a dual boot without formatting the drive. Is it possible to create a partition on the current hard drive and then install win xp? I couldn't find... (4 Replies)
Discussion started by: eltinator
4 Replies

3. UNIX for Advanced & Expert Users

Lesson Learned: Dual boot XP and Fedora 9

This post captures my recent experience in getting my Dell XPS Gen 3 to support dual boot of Windows XP (Professional) and the Fedora 9 Linux distribution. I searched quite a bit on the internet and found, of course, a variety of opinions regarding how to setup this type (dual boot) of... (1 Reply)
Discussion started by: rlandon@usa.net
1 Replies

4. Linux

How to boot Fedora 8 from USB

Hi, friends, can anyone suggest me how to boot fedora 8 from USB flash drive? thanks. :confused: (3 Replies)
Discussion started by: MULTIVERSE
3 Replies

5. Red Hat

boot floppy for fedora 13

Is there a way to create a boot floppy for a fedora 13 system? Rescue disk image from the official boot.iso is too big. (1 Reply)
Discussion started by: druidmatrix
1 Replies

6. Red Hat

fedora grub help, moving to tri boot (XP, ubuntu, fedora soemething)

I will shortly be adding a fedora flavor to my devel box. I currently have XP (installed first on an ssd), ubuntu 10.04 (installed second on the first partition of a platter drive), and I want to add either Cent or SL on the second partition of the platter drive. I will probably also want to... (0 Replies)
Discussion started by: LMHmedchem
0 Replies

7. Red Hat

Kernel can not boot after upgrade on Fedora OS 15.

Hello, everyone. I am using Fedora 15, and want to upgrade to version 16. I follow the official link Upgrading Fedora using yum - FedoraProject to upgrade my OS by the following command: yum update kernel* --releasever=16 yum groupupdate Base --releasever=16 reboot After reboot, OS... (2 Replies)
Discussion started by: 915086731
2 Replies

8. Red Hat

Unable to boot after updating to kernel-3.1.4-1 in fedora 16

hi guys, I was using kernel-3.1.2-1 in fedora 16. then updated to kernel-3.1.4-1. after reboot now grub shows command prompt instead of boot menu. i tried to load manually with: set root=(hd0,msdos3) linux /vmlinuz-3.1.4-1.fc16.x86_64 initrd /initramfs-3.1.4-1.fc16.x86_64.imgbut in the middle... (0 Replies)
Discussion started by: majid.merkava
0 Replies

9. Red Hat

Fedora 17 - No video after boot

Hi, I'm new to the Linux world and I'm having issues. Screen goes blank after Fedora boots up. I can see the POST and Fedora Grub screen but afterwards, goes blank. I believe I installed something but I cant remember what....its been a couple days. (0 Replies)
Discussion started by: gps1976
0 Replies
RESCUE(8)						    BSD System Manager's Manual 						 RESCUE(8)

NAME
rescue -- rescue utilities in /rescue DESCRIPTION
The /rescue directory contains a collection of common utilities intended for use in recovering a badly damaged system. With the transition to a dynamically-linked root beginning with FreeBSD 5.2, there is a real possibility that the standard tools in /bin and /sbin may become non-functional due to a failed upgrade or a disk error. The tools in /rescue are statically linked and should therefore be more resistant to damage. However, being statically linked, the tools in /rescue are also less functional than the standard utilities. In particular, they do not have full use of the locale, pam(3), and nsswitch libraries. If your system fails to boot, and it shows a prompt similar to: Enter full pathname of shell or RETURN for /bin/sh: the first thing to try running is the standard shell, /bin/sh. If that fails, try running /rescue/sh, which is the rescue shell. To repair the system, the root partition must first be remounted read-write. This can be done with the following mount(8) command: /rescue/mount -uw / The next step is to double-check the contents of /bin, /sbin, and /usr/lib, possibly mounting a FreeBSD rescue or ``live file system'' CD-ROM (e.g., disc2 of the officially released FreeBSD ISO images) and copying files from there. Once it is possible to successfully run /bin/sh, /bin/ls, and other standard utilities, try rebooting back into the standard system. The /rescue tools are compiled using crunchgen(1), which makes them considerably more compact than the standard utilities. To build a FreeBSD system where space is critical, /rescue can be used as a replacement for the standard /bin and /sbin directories; simply change /bin and /sbin to be symbolic links pointing to /rescue. Since /rescue is statically linked, it should also be possible to dispense with much of /usr/lib in such an environment. In contrast to its predecessor /stand, /rescue is updated during normal FreeBSD source and binary upgrades. FILES
/rescue Root of the rescue hierarchy. SEE ALSO
crunchgen(1), crash(8) HISTORY
The rescue utilities first appeared in FreeBSD 5.2. AUTHORS
The rescue system was written by Tim Kientzle <kientzle@FreeBSD.org>, based on ideas taken from NetBSD. This manual page was written by Simon L. Nielsen <simon@FreeBSD.org>, based on text by Tim Kientzle <kientzle@FreeBSD.org>. BUGS
Most of the rescue tools work even in a fairly crippled system. The most egregious exception is the rescue version of vi(1), which currently requires that /usr be mounted so that it can access the termcap(5) files. Hopefully, a failsafe termcap(3) entry will eventually be added into the ncurses(3) library, so that /rescue/vi can be used even in a system where /usr cannot immediately be mounted. In the meantime, the rescue version of the ed(1) editor can be used from /rescue/ed if you need to edit files, but cannot mount /usr. BSD
July 23, 2003 BSD
All times are GMT -4. The time now is 11:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy