| Author |
Message |
|
dvanbrunt
|
 Posted: Sun Nov 05, 2006 8:57 pm |
|
|
Joined: Thu Mar 31, 2005 6:17 pm
Posts: 70
|
Had a working system, but the time was WAAAYYY off... clock was too far off for the ntpdaemon to keep up, so saw the post on knoppmythwiki on Nforce2TimeDrift and followed the instructions. Since it involved editing lilo.conf, it instructed to run lilo afterward, which I did. I did all this as root. Upon reboot, I get a spewing of errors, ending with "Kernel panic no syncing: Attempted to kill init!"
So I booted off the knoppmyth install CD, escaped out of the menus to a prompt, and did:
mount /dev/hda1 /mnt/hda1
Then re-edited the lilo.conf (now at /dev/hda1/etc/lilo.conf) to put it back the way it was (took the "noapic noioapic" off the end of the "append" line). Then I did:
chroot /mnt/hda1
lilo -v
and it appeared to run without errors....
But I got the same kernel panic when I tried to reboot.
Any ideas? What to do next? Any help appreciated! I've done 3 hours worth of searching and fix attempts so far, ending with what I've posted above. I'm out of my depth!
|
|
| Top |
|
 |
|
cecil
|
Posted: Thu Nov 09, 2006 9:43 pm |
|
 |
| Site Admin |
Joined: Fri Sep 19, 2003 6:37 pm
Posts: 2659
Location:
Whittier, Ca
|
|
Can you post your lilo.conf? Perhaps you missed something, that an extra set of eyes maybe able to find.
|
|
| Top |
|
|
|
dvanbrunt
|
Posted: Fri Nov 10, 2006 3:45 pm |
|
|
Joined: Thu Mar 31, 2005 6:17 pm
Posts: 70
|
cecil wrote: Can you post your lilo.conf? Perhaps you missed something, that an extra set of eyes maybe able to find.
Oh, dear... that sounds like a good idea, but I'm not sure how I'd do that, since I can only boot off the CD... not much there in the way of services, or a persistent clipboard... unless DHCP and SSH are enabled on a CD boot?
All I had done was add the two words to the end of the "append" statement as noted above, then run "lilo -v" as root. Seemed to run OK, but wouldn't reboot.
So I took those two words back out while booted from the CD... still no love. Drive hda1 was mounted (saw the lilo.conf, was able to write it).
|
|
| Top |
|
|
|
cecil
|
Posted: Fri Nov 10, 2006 5:29 pm |
|
|
| Site Admin |
Joined: Fri Sep 19, 2003 6:37 pm
Posts: 2659
Location:
Whittier, Ca
|
|
| Top |
|
|
|
dvanbrunt
|
Posted: Fri Nov 10, 2006 7:53 pm |
|
|
Joined: Thu Mar 31, 2005 6:17 pm
Posts: 70
|
cecil wrote: Yes.
Oh, you are good.
I'll take a plug at it in the morning, then, and post the file.
It just occurred to me, too, that I had it set up with LVM.... using the knoppmythwiki instructions. Seems that shouldn't matter, though, since it was running fine before, and only stopped right after a very specific change to lilo.conf.
At any rate, I'll try to post that puppy tomorrow.
|
|
| Top |
|
|
|
dvanbrunt
|
Posted: Sat Nov 11, 2006 9:35 am |
|
|
Joined: Thu Mar 31, 2005 6:17 pm
Posts: 70
|
Here it is:
root@Knoppix:~# cat /etc/lilo.conf
Quote: vga=normal
# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
# and `/usr/share/doc/mbr/'.
# +---------------------------------------------------------------+
# | !! Reminder !! |
# | |
# | Don't forget to run `lilo' after you make changes to this |
# | conffile, `/boot/bootmess.txt', or install a new kernel. The |
# | computer will most likely fail to boot if a kernel-image |
# | post-install script or you don't remember to run `lilo'. |
# | |
# +---------------------------------------------------------------+
# Support LBA for large hard disks.
#
lba32
# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/hde
# bios=0x81
#disk=/dev/sda
# bios=0x80
# Specifies the boot device. This is where Lilo installs its boot
# block. It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda1
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller. Using `compact' is especially recommended when
# booting from a floppy disk. It is disabled here by default
# because it doesn't always work.
#
# compact
# Installs the specified file as the new boot sector
# You have the choice between: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details
#
install=/boot/boot-menu.b
# Specifies the location of the map file
#
map=/boot/map
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration. If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well. Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20
# You can put a customized boot message up if you like. If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress. `single-key' goes with the `alias' lines in the
# `image' configurations below. eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
# prompt
# single-key
# delay=100
# timeout=100
# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
append="splash=silent apm=power-off nomce"
# Boot up Linux by default.
#
default=Linux
image=/boot/vmlinuz-2.6.17-chw-8
label=Linux
initrd=/boot/initrd.gz
read-only
# restricted
# alias=1
image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
# label=HURD
# restricted
# alias=3
image=/boot/bzImage.2.4.20.poweroff
label=Poweroff Hope that's informative! The fact that I had to : Quote: mount /dev/hda1 /mnt/hda1
chroot /mnt/hda1
successfully in order to get the SSH server running suggests that the lilo -v should have written OK, too. At least with my limited understanding. Now that I can use SSH, I can post the lilo output: Quote: LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 17-Nov-2004, and compiled at 18:58:03 on Nov 18 2004
Debian GNU/Linux
/proc/devices: fopen failed: No such file or directory
Is device-mapper driver missing from kernel?
Reading boot sector from /dev/hda
Warning: '/proc/partitions' does not exist, disk scan bypassed
Using MENU secondary loader
Calling map_insert_data
Boot image: /boot/vmlinuz-2.6.17-chw-8
Mapping RAM disk /boot/initrd.gz
Added Linux *
Skipping /vmlinuz.old
Boot image: /boot/bzImage.2.4.20.poweroff
Added Poweroff
Writing boot sector.
/boot/boot.0300 exists - no boot sector backup copy made.
|
|
| Top |
|
|
|
mjl
|
Posted: Mon Nov 13, 2006 8:42 pm |
|
|
Joined: Sun Jun 12, 2005 10:55 pm
Posts: 3161
Location:
Warwick, RI
|
Hi,
Quote: mount /dev/hda1 /mnt/hda1
chroot /mnt/hda1
Try booting with install cd, quit to get a prompt:
mount -o rw,dev /dev/hda1 /mnt/hda1
chroot /mnt/hda1
Double check your /etc/lilo.conf to ensure your edits are really there
lilo -v
If I recall correctly there is only one complaint about a backup
Mike
ps: I set my clock on boot up just to ensure the ntpd can have control.
as root (only once)
echo "ntpdate -u north-america.pool.ntp.org" >> /etc/init.d/bootmisc.sh
please note, this is all one line and besure there are two >> before you press enter!
|
|
| Top |
|
|
|
dvanbrunt
|
Posted: Tue Nov 14, 2006 7:23 pm |
|
|
Joined: Thu Mar 31, 2005 6:17 pm
Posts: 70
|
No love. 
Exactly the same output as above.
Is it possible to fire up the mysql daemon while booted from the CD to run mythbackup? I did a weekly backup, but may have a couple of stragglers since the system got borked the next day. Would have to hunt down the orphan video files otherwise.
Assuming, of course, that an "auto-upgrade" would in fact fix this problem?
Do you think it would? (remember this is a LVM install, so I know I'd have to follow those instructions to get "vg" recognized again)... 
|
|
| Top |
|
|
|
mjl
|
Posted: Tue Nov 14, 2006 7:46 pm |
|
|
Joined: Sun Jun 12, 2005 10:55 pm
Posts: 3161
Location:
Warwick, RI
|
|
Hi,
Some piece of the story is missing... do a ls /boot/v* and compare it with the lilo entry.
Mike
|
|
| Top |
|
|
|
dvanbrunt
|
Posted: Tue Nov 14, 2006 8:02 pm |
|
|
Joined: Thu Mar 31, 2005 6:17 pm
Posts: 70
|
mjl wrote: Hi,
Some piece of the story is missing... do a ls /boot/v* and compare it with the lilo entry.
Mike that command give me: Quote: /boot/vmlinuz-2.6.17-chw-8
which matches one of the two listed in the output of lilo -v (see prior post for output)
My lilo.conf, pasted above, seems to refer to two different versions... but this is nothing that I've ever edited. The second one looks to be related to poweroff rather than boot. But I'm no linux expert, so I'm just guessing.
|
|
| Top |
|
|
|
dvanbrunt
|
Posted: Thu Nov 16, 2006 6:31 am |
|
|
Joined: Thu Mar 31, 2005 6:17 pm
Posts: 70
|
|
So... ignorant question, I know, but I really don't know...
would an "auto-upgrade" likely solve this?
I'd lose a few shows, but not as many as I'm "losing" with two weeks and counting of not getting any new recordings...
|
|
| Top |
|
|
|
mjl
|
Posted: Thu Nov 16, 2006 7:05 am |
|
|
Joined: Sun Jun 12, 2005 10:55 pm
Posts: 3161
Location:
Warwick, RI
|
Hi,
I don't see anything specific that is causing your problem so the only recourse may be an upgrade  However, not knowing what version you are currently running, may be it will be a true upgrade 
Check on the wiki for some excellent guidence by tjc in preparation (what you can anyway) You could aways boot with the cd and chroot so that you could make a directory in the myth partition (mount it first after the chroot) so you can save things like the current mysql, etc
Just some ideas.
Best of luck
Mike
|
|
| Top |
|
|
|
cesman
|
Posted: Thu Nov 16, 2006 12:33 pm |
|
|
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location:
Fontana, Ca
|
|
Auto Upgrade will only work when a backup has been done. I do have some steps on the forum that I used when a hard drive died on me... You could search for a post by me (I'd have to...). You can also try mounting /dev/hda3 and see if you can do a mysql dump.
_________________
cesman
When the source is open, the possibilities are endless!
|
|
| Top |
|
|
|
dvanbrunt
|
Posted: Thu Nov 16, 2006 6:31 pm |
|
|
Joined: Thu Mar 31, 2005 6:17 pm
Posts: 70
|
|
that backup remains after running autoupgrade, right?
I had done a backup about a week ago, so I'm guessing it should work. Problem is I have it set up for LVM, so I can't mount the /myth partition (at least I don't know how) to check for any backup files or to re-run a backup if needed.
Assuming the backup files are themselves not wiped out by the upgrade process, I can just do the auto-upgrade again, and my DB should be back where it was (with a few entries that lack video files, since I deleted them since, and a few video files that lack entries, since the DB of last week wouldn't have them...)
I could then just manually tidy up the orphans. (not too many of these)
Would that work?
|
|
| Top |
|
|
|
cesman
|
Posted: Fri Nov 17, 2006 1:39 am |
|
|
Joined: Fri Sep 19, 2003 7:05 pm
Posts: 5088
Location:
Fontana, Ca
|
|
Yes. You will however need to run recreate_lvm.sh. This needs to be the first thing done after rebooting from the upgrade.
_________________
cesman
When the source is open, the possibilities are endless!
|
|
| Top |
|
|
View unanswered posts
View active topics
Linux 
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register