X or kernel or mingetty broken after update
by iancshay＠comcast.net
Hi.
I am using fedora 11.
Last weekend I performed a major update - 133 packages. Now I have a problem that renders the computer usable only remotely. Something is wrong with consoles, X, or the kernel. Not sure how to determine the culprit. Here are the symptoms:
Say I start with a fresh telinit 5.
1) If I get into an X session, CTRL-ALT-F2 (say) does NOT take me to a vt.
2) If in KDM, CTRL-ALT-F2 does take me to a console, but if I then try to go back via ALT-F1, I get blank screen and no response to keyboard from this point on.
3) I think if left alone in runlevel 3, the keyboard/screen eventually locks up too, but not too sure about this.
4) To get it working again, must do telinit 3 then telinit 5 from a remote login.
5) In system log I get:
/sbin/mingetty[16865]: tty1: invalid character 0xbb in login name
init: tty1 main process (16865) terminated with status 1
init: tty1 main process ended, respawning
This happens many many times, every 5 sec or so, with different "invalid characters"
6) ps ax lists several (about 10) kerneloops processes that don't seem to go away.
18600 ? S 0:08 /usr/sbin/kerneloops --nodaemon
19155 ? S 0:07 /usr/sbin/kerneloops --nodaemon
20063 ? S 0:07 /usr/sbin/kerneloops --nodaemon
How do I go about finding the problem and how can I revert to a working system?
Thanks!
Ian
14 years, 5 months
F11 dmraid assistance (raid1)
by Michael Cronenworth
I'm pulling my hair out over a RAID1 setup.
* Two 1TB Seagate 7200.12 drives (sda and sdb)
* RAID1 using Intel OROM.
* Two partitions: /boot partition ext3, LVM2 encrypted partition with /
XFS and swap
* sdb formed a bad sector, I'm going to RMA it.
* There are no other hard drives attached.
First I attempted to shutdown and unplug the bad drive. Fedora wouldn't
boot -- gets to Password: prompt for encrypted partition. Correct
password is entered but the encrypted partition cannot be mounted. I
narrowed it down to that the /dev/sda1 and /dev/sda2 partitions are not
showing up so the kernel can't find the correct UUID from /etc/crypttab
to mount /.
Second, I plugged the bad drive back in. Fedora boots normally.
Third, I get brave and remove the bad drive from the RAID using the
Intel OROM. I then turn off the machine and remove the bad drive. Fedora
won't boot -- gets past password prompt, but during bootup it cannot
find my /boot partition and dumps me to a recovery shell.
Fourthly, I plug the bad drive back in and Fedora boots. The bad drive
is no longer in the RAID, but its old partitions are exposed. The UUID
of /dev/sdb1 matches and so it mounts /boot.
Fifthly, I couldn't get the bad drive to rebuild so I used a Fedora Live
USB install to start the rebuild. Rebooted and Fedora wouldn't boot. No
/dev/sda1 partition and no /dev/sdb1 or /dev/sdb2 partitions!
Now I'm stuck in a loop inbetween the 3rd and 4th attempt at safely
removing the bad drive from my RAID1 array. I only see the following in
/dev:
ls -l /dev/sd*
brw-rw----. 1 root disk 8, 0 2009-11-02 19:16 /dev/sda
brw-rw----. 1 root disk 8, 2 2009-11-02 19:15 /dev/sda2
brw-rw----. 1 root disk 8, 16 2009-11-02 19:16 /dev/sdb
brw-rw----. 1 root disk 8, 17 2009-11-02 19:15 /dev/sdb1
brw-rw----. 1 root disk 8, 18 2009-11-02 19:15 /dev/sdb2
This is with the bad drive not in the array of course. What happened to
my /dev/sda1 partition? Fdisk shows it. Gparted shows it. Linux doesn't!
It is obviously still there as with my bad drive out I can boot. I don't
get it.
Thanks,
Michael
14 years, 5 months
grub 2: "error: You need to load the kernel first"
by Colin Brace
Hi all,
I've just installed Ubuntu 9.10 along side F11. My disk now looks like this:
/dev/sda1 F11 boot
/dev/sda2 F11 root
/dev/sda3 F11 swap
/dev/sda5 F11 home
/dev/sda6 9.10 root
/dev/sda7 9.10 home
/dev/sda8 91.0 swap
When I reboot, I get grub, which has entries listed for both systems, but
when I try to boot Fedora now, I get an error message: "error: You need to
load the kernel first". (Ubuntu boots fine).
I've tried booting manually from the grub command line, but the commands no
longer appear to be the same, as Ubuntu is now using grub 2. Here are the
relevant section from grub.cfg (menu.lst is now obsolete):
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Fedora (2.6.30.9-90.fc11.i586) (on /dev/sda2)" {
insmod ext2
set root=(hd0,2)
search --no-floppy --fs-uuid --set 5a8b0f33-5369-4a45-a501-455ed10f4fa7
linux /boot/vmlinuz-2.6.30.9-90.fc11.i586 ro
root=UUID=5a8b0f33-5369-4a45-a501-455ed10f4fa7 rhgb resume=/dev/sda3
initrd /boot/initrd-2.6.30.9-90.fc11.i586.img
}
menuentry "Fedora (2.6.29.4-167.fc11.i586) (on /dev/sda2)" {
insmod ext2
set root=(hd0,2)
search --no-floppy --fs-uuid --set 5a8b0f33-5369-4a45-a501-455ed10f4fa7
linux /boot/vmlinuz-2.6.29.4-167.fc11.i586 ro
root=UUID=5a8b0f33-5369-4a45-a501-455ed10f4fa7 resume=/dev/sda3 rhgb
initrd /boot/initrd-2.6.29.4-167.fc11.i586.img
}
### END /etc/grub.d/30_os-prober ###
The above entries were generated automatically.
Does anyone know how to fix the error?
Alternately, is there a way of telling the MBR to boot /dev/sda1 (F11 boot)
instead of /dev/sda6 (Ubuntu root), which is what is happening now?
Thanks.
-----
Colin Brace
Amsterdam
http://lim.nl
--
View this message in context: http://old.nabble.com/grub-2%3A-%22error%3A-You-need-to-load-the-kernel-f...
Sent from the Fedora List mailing list archive at Nabble.com.
14 years, 5 months
pdf viewer wont zoom in enough
by Development discussions related to Fedora
Wondering if anyone is having trouble reading pdf files. Document
Viewer. Using poppler 0.10.7 (cairo), opens the pdf OK, but even at the
largest zoom (400%), the page is shown at less than the full height of
the screen, making it real hard to read it.
What's with that ?
DaveT.
14 years, 5 months
Re: "shutdown now" on F11 as root problems and app crashes in
by KC8LDO
Phil;
Thanks for the advice. I administer, at least I try to, the boxes myself. I
use Linux it at home as a hobby and asking a question is sometimes quicker
for me than to search around for the answer.
Regards;
Leland C. Scott
KC8LDO
14 years, 5 months
Re: "shutdown now" on F11 as root problems and app crashes in
by KC8LDO
Rick;
I can send them a note. I don't about it being "pithy" but the documentation
should be complete and correct at least.
Regards;
Leland C. Scott
KC8LDO
----- Original Message -----
From: "Rick Stevens" <ricks(a)nerd.com>
To: "KC8LDO" <kc8ldo(a)arrl.net>
Sent: Monday, November 02, 2009 2:34 PM
Subject: Re: "shutdown now" on F11 as root problems and app crashes in
> KC8LDO wrote:
>> Rick;
>>
>> I just checked the command line version, using "--help", as you
>> suggested, and the info is there, of course. I wasn't expecting that sort
>> of default behavior. Nothing in the man page that warns about it.
>> Somebody may want to consider adding that tid-bit to the man page. I
>> thought the man pages were the main source of info for various commands
>> etc., looks like it isn't. Guess I'll just have to be more careful.
>> Another day, learn something new.
>
> Yes, the man page should reflect the command better but the man pages
> are often maintained by someone other than the maintainer of the command
> itself. In this case it appears that they ARE done by the same folk
> (Canonical, Ltd.), so they should probably get a bug report. The man
> page does have a link:
>
> Report bugs at https://launchpad.net/products/upstart/+bugs
>
> If you have a chance, perhaps you should send them a pithy little note
> about it.
> ----------------------------------------------------------------------
> - Rick Stevens, Systems Engineer ricks(a)nerd.com -
> - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
> - -
> - To err is human. To forgive, a large sum of money is needed. -
> ----------------------------------------------------------------------
>
14 years, 5 months
NMI interrupt received
by pandi k
Hi All,
We are using Fedora Core 7 with 2.6.21 kernel and facing a issue in booting.
We have our PCI device on PCI slot and getting below message when system is
booting
Uhhuh. NMI received for unknown reason a1 on CPU 0.
You have some hardware problem, likely on the PCI bus.
Dazed and confused, but trying to continue
what could be reason for above display ?
Thanks,
Pandi
14 years, 5 months
Re: "shutdown now" on F11 as root problems and app crashes in
by KC8LDO
Bob;
I did go back and read it, should have done that first. I did read that one
of the options the action taken is system dependent, the "-h" option. That
makes things more interesting.
I'm sitting here at work, eating lunch, reading the man page, again, for the
shutdown command using a remote VNC session to my F10 box at home. I don't
see anything that mentions any sort of default action if you fail to supply
one of the options to the shutdown command. All it says in general at the
end of the man page is :
"When invoked it generates a runlevel event, with an argument containing the
new runlevel."
I'll have to look specifically at the one, man page, on the F11 box later
when I get home. Your comment suggests they are not the same.
One last comment. If I was not by the local attached console and saw what
happened, but was working remotely when I issued the "shutdown now" command,
having the system drop down to a CLI interface, single user mode, with the
root prompt showing isn't very comforting. Also my remote VNC session
terminated too. Not my idea of a way to lose control of the box and give
somebody else the chance to have some fun at the "free" root prompt either.
Lucky for me this box is on my home network where I'm the only one with
physical access.
Leland C. Scott
KC8LDO
14 years, 5 months
Impossible to access boot menu
by Marcel Rieux
I try to access the boot menu, where you can choose a kernel and,
whatever key I press, I can't stop the countdown and access the boot
menu.
I checked /boot/grub/grub.conf and I have hiddenmenu in it. But the
back-up, /boot/grub/grub.conf~ dates back to August and has hiddenmenu
in it too. Since I accessed the boot menu since August, I suppose this
is not the problem.
14 years, 5 months
virt-manager slow shutdown.
by Gary Artim
Hey--
I have a 64 machine running XP with kvm/virt-manager. The startup and
running are fine, but shutdown or hibernate is so slow -- go have a
smoke, come back, still shutting down. I don't
smoke so it's even more annoying. Anyone have a hack for this?
thanks much,
-- g.
14 years, 5 months
