Sponsored Content
Operating Systems Linux Red Hat Grub screen issue while booting...... Post 302337788 by Scott on Saturday 25th of July 2009 08:37:37 AM
Old 07-25-2009
If you have the Red Hat CD / DVD you should be able to boot from that and repair the problem from there.

If all else fails, you could download a third-party boot loader (google it, there's plenty of them).
 

8 More Discussions You Might Find Interesting

1. Linux

How to get back Linux Grub screen

I had Linux and win98 installed on my PC, then I installed winXP and it has replaced the Grub Bootloader, now on booting up I get to see only win98 and winXP to choose from, Now how do I get Back the Grub screen with Linux as a option or how do I boot into linux. :confused: (3 Replies)
Discussion started by: er.pankaj
3 Replies

2. Solaris

Blank GRUB Screen

Hello. I had installed solaris 10 in morning , and all was running fine... I just logged out and logged in with another user ID oracle - It got stuck and then I pressed the button for restart. Now I see only word GRUB written in top line rest everything is black. What to do? (2 Replies)
Discussion started by: panchpan
2 Replies

3. Solaris

How To Remove Grub When Booting

Hi All, I am new to Solaris OS and have been able to load the kernel on GRUB prompt with root(hd0,0,a) i.e the slice of the installed solaris OS, kernel /platform/i86pc/multiboot , module /platform/i86pc/boot_archive. Please i need help on how i can remove GRUB at startup so that X-server starts... (1 Reply)
Discussion started by: edsonede
1 Replies

4. Linux

grub error 22,after removing linux partitions only windows is threre.Pc not booting.i

hi, in my pc linux and windows was there with 2 hdd in raid.i removed linux partititons.Now my ps is not booting giving grub error 22.Nothing works.I hace my data in windows.Hard disks are RAID.when tried to go to recovery mode from windoes boot cd,it says hard disk not detected.when tried with... (2 Replies)
Discussion started by: pankajd
2 Replies

5. UNIX for Dummies Questions & Answers

GRUB and booting from LVM volumes?

I'm setting-up my new computer, and would like to try out and switch between several OS (mostly different Linux distros). As I prefer to use separate partition for various dirs (/, home, usr, var, opt and perhaps local), I've come to the conclution that I'll run-out of partitions too soon, so I've... (1 Reply)
Discussion started by: koppe
1 Replies

6. Red Hat

Fedora booting in text mode (screen messes up)

Hello everyone Had a problem booting Fedora. I installed it as a server without any desktop environment(kde, gnome) except for X. Problem is when i booting system after it loads kernel suddenly screen messes up with parts of fedora graphics(it's not clear but you can see it -... (8 Replies)
Discussion started by: dimamu15
8 Replies

7. Solaris

Booting from Grub CLI

Hi, Hoping someone out there has seen this before. My backup/restore operation failed when my system ran out of memory Restore operation failed Setting ZFS Boot Environment to rootpool cannot set property for 'rootpool': out of space Installing GRUB Boot Loader into the first disk stage1... (2 Replies)
Discussion started by: A-Train
2 Replies

8. Red Hat

grub splash screen not displayed

I re-installed grub on /dev/sdb on a 3ware raid machine and now the grub splash screen is not displayed when booting. Server when boots up comes and halt in the grub menu and I need to manually load kernel and initrd to get the machine up. I have not changed any grub setting. I used the command... (0 Replies)
Discussion started by: anil510
0 Replies
GPTBOOT(8)						    BSD System Manager's Manual 						GPTBOOT(8)

NAME
gptboot -- GPT bootcode for UFS on BIOS-based computers DESCRIPTION
gptboot is used on BIOS-based computers to boot from a UFS partition on a GPT-partitioned disk. gptboot is installed in a freebsd-boot par- tition with gpart(8). IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptboot only boots from tables with 128 partitions or less. PARTITION ATTRIBUTES
gptboot checks and manages several attributes of GPT UFS partitions. bootme Attempt to boot from this partition. If more than one partition has the bootme attribute set, gptboot will attempt to boot each one until successful. bootonce Attempt to boot from this partition only one time. Setting this attribute with gpart(8) automatically also sets the bootme attribute. Multiple partitions may have the bootonce and bootme attributes set. bootfailed The bootfailed attribute marks partitions that had the bootonce attribute set, but failed to boot. This attribute is managed by the system. See BOOTING and POST-BOOT ACTIONS below for details. USAGE
For normal usage, the user does not have to set or manage any of the partition attributes. gptboot will boot from the first UFS partition found. The bootonce attribute can be used for testing an upgraded operating system on an already-working computer. The existing system partition is left untouched, and the new version of the operating system to be tested is installed on another partition. The bootonce attribute is set on that new test partition. The next boot is attempted from the test partition. Success or failure will be shown in the system log files. After a successful boot of the test partition, a user script can check the logs and change the bootme attributes so the test partition becomes the new system partition. Because the bootonce attribute is cleared after an attempted boot, a failed boot will not leave the system attempting to boot from a partition that will never succeed. Instead, the system will boot from the older, known-working operating system that has not been modified. If the bootme attribute is set on any partitions, booting will be attempted from them first. If no partitions with bootme attributes are found, booting will be attempted from the first UFS partition found. BOOTING
gptboot first reads the partition table. All freebsd-ufs partitions with only the bootonce attribute set, indicating a failed boot, are set to bootfailed. gptboot then scans through all of the freebsd-ufs partitions. Boot behavior depends on the combination of bootme and bootonce attributes set on those partitions. bootonce + bootme Highest priority: booting is attempted from each of the freebsd-ufs partitions with both of these attributes. On each partition, the bootme attribute is removed and the boot attempted. bootme Middle priority: booting is attempted from each of the freebsd-ufs partitions with the bootme attribute. If neither bootonce nor bootme attributes are found on any partitions, booting is attempted from the first freebsd-ufs partition on the disk. POST-BOOT ACTIONS The startup script /etc/rc.d/gptboot checks the attributes of freebsd-ufs partitions on all GPT disks. Partitions with the bootfailed attribute generate a ``boot from X failed'' system log message. Partitions with only the bootonce attribute, indicating a partition that successfully booted, generate a ``boot from X succeeded'' system log message. The bootfailed attributes are cleared from all the partitions. The bootonce attribute is cleared from the partition that successfully booted. There is normally only one of these. FILES
/boot/gptboot bootcode binary /boot.config parameters for the boot blocks (optional) EXAMPLES
gptboot is installed in a freebsd-boot partition, usually the first partition on the disk. A ``protective MBR'' (see gpart(8)) is typically installed in combination with gptboot. Install gptboot on the ada0 drive: gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0 gptboot can also be installed without the PMBR: gpart bootcode -p /boot/gptboot -i 1 ada0 Set the bootme attribute for partition 2: gpart set -a bootme -i 2 ada0 Set the bootonce attribute for partition 2, automatically also setting the bootme attribute: gpart set -a bootonce -i 2 ada0 SEE ALSO
boot.config(5), rc.conf(5), boot(8), gpart(8) HISTORY
gptboot appeared in FreeBSD 7.1. AUTHORS
This manual page written by Warren Block <wblock@FreeBSD.org>. BSD
February 5, 2014 BSD
All times are GMT -4. The time now is 01:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy