Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Bad PBR Sig Operating System Not Found...why ? Post 33094 by abidmalik on Monday 16th of December 2002 02:48:19 PM
Old 12-16-2002
RTM Thanks for answring both of my questions.

Althought i did not understand the bug issue, but i do appriciate your answer/suggestion/help.

Thanks again.

Abid Malik
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Bad PBR on Intel Machine

I recentlly installed solaris 8 on a 2G HD successfully , but cannot boot pass a screen that has a error message "BAD PBR". My queston would be is how do I get pass this and how do I repair it? I have visited the SUN SYSTEM website many times trying to get information. thanks Mogfog (2 Replies)
Discussion started by: mogfog
2 Replies

2. Solaris

bad BPR sig

hello mentor. I'm getting an error " fdgetchng: write protect check failed " after I rebooted my laptop because it hangs when i open server management console. what seems to be the problem? thanks (3 Replies)
Discussion started by: eykyn17
3 Replies

3. UNIX for Dummies Questions & Answers

Bad PBR sig

ok, i recently posted asking for a distro of unix, and someone said to try solaris, so i booted up the dvd iso installer. And after making some kind of mistake in the preperation, I couldnt retry the installer, it repeated the Warning: Bad Geometry. thing, and when i tried to just boot up into... (0 Replies)
Discussion started by: FaoX666
0 Replies

4. Solaris

PBR Bad in sun solaris 10 intel version

Hai while booting sun solaris 10 in a intel machine,its showing PBR bad and its showing disk boot failure.but the is detecting.please guide me (1 Reply)
Discussion started by: subbiahvin
1 Replies

5. Red Hat

RHEL4 Upt(2): Operating System Not Found ?

Hi, My HP-Proliant Machine have faced abnormal shutdown due to a power failure. after the event : "Operating System not found" appears & the system could not load operating system. O/S: RHEL AS 4 update 2 Software Raid 1+0 were configured. Facts Gathered: All mount points are... (1 Reply)
Discussion started by: Muhammad Ahmad
1 Replies

6. Solaris

bad pbr sig

After installing Solaris 10 x86 (solaris 5 2009 update 7 ) i've been granted a “Bad PBR sig” error message on boot, making my system unbootable. any one has any solution for this problem (1 Reply)
Discussion started by: maxim42
1 Replies

7. Solaris

By loading I have received the following issue: BAD PBR SIGN.

Hi folks. By disk cloning on Solaris x86, I used a command dd. I pulled out the source and inserted the new disk. By loading I have received the following issue: BAD PBR SIGN. :( (5 Replies)
Discussion started by: wolfgang
5 Replies

8. Solaris

Solaris x86: Bad PBR sig

Hello everyone, I have a Sun x4600 (Solaris 10 x86) server.During boot up "Bad PBR sig" error comes soon after post (before GRUB). Unless the return key is pressed the server never boots up. Once the return key is pressed the boot process continues without any problem. Can you please help me... (1 Reply)
Discussion started by: pingmeback
1 Replies

9. Solaris

Operating system not found

Hi, Iam trying to instal a solaris operating system in a vmware on my local windows system via an iso image named as "solaris10.vmx". but as soon as the vm console opens i get an error message as: "PXE-MOF: Exiting Intel PXE ROM. Operating system not found" Please help me out in... (3 Replies)
Discussion started by: Laxxi
3 Replies

10. UNIX for Advanced & Expert Users

What's my Operating System

Can we know the operating given the IP address or DNS of the host. All I have is file://myserver/myapp (4 Replies)
Discussion started by: mohtashims
4 Replies
apport-bug(1)						      General Commands Manual						     apport-bug(1)

NAME
apport-bug, apport-collect - file a bug report using Apport, or update an existing report SYNOPSIS
apport-bug apport-bug symptom | pid | package | program path | .apport/.crash file apport-collect report-number DESCRIPTION
apport-bug reports problems to your distribution's bug tracking system, using Apport to collect a lot of local information about your sys- tem to help the developers to fix the problem and avoid unnecessary question/answer turnarounds. You should always start with running apport-bug without arguments, which will present a list of known symptoms. This will generate the most useful bug reports. If there is no matching symptom, you need to determine the affected program or package yourself. You can provide a package name or program name to apport-bug, e. g.: apport-bug firefox apport-bug /usr/bin/unzip In order to add more information to the bug report that could help the developers to fix the problem, you can also specify a process ID instead: $ pidof gnome-terminal 5139 $ apport-bug 5139 As a special case, to report a bug against the Linux kernel, you do not need to use the full package name (such as linux- image-2.6.28-4-generic); you can just use apport-bug linux to report a bug against the currently running kernel. Finally, you can use this program to report a previously stored crash or bug report: apport-bug /var/crash/_bin_bash.1000.crash apport-bug /tmp/apport.firefox.332G9t.apport Bug reports can be written to a file by using the --save option or by using apport-cli. apport-bug detects whether KDE or Gnome is running and calls apport-gtk or apport-kde accordingly. If neither is available, or the session does not run under X11, it calls apport-cli for a command-line client. UPDATING EXISTING REPORTS
apport-collect collects the same information as apport-bug, but adds it to an already reported problem you have submitted. This is useful if the report was not originally filed through Apport, and the developers ask you to attach information from your system. OPTIONS
Please see the apport-cli(1) manpage for possible options. ENVIRONMENT
APPORT_IGNORE_OBSOLETE_PACKAGES Apport refuses to create bug reports if the package or any dependency is not current. If this environment variable is set, this check is waived. Experts who will thoroughly check the situation before filing a bug report can define this in their ~/.bashrc or temporarily on the command line when calling apport-bug. SEE ALSO
apport-cli(1) AUTHOR
apport and the accompanying tools are developed by Martin Pitt <martin.pitt@ubuntu.com>. Martin Pitt September 08, 2009 apport-bug(1)
All times are GMT -4. The time now is 01:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy