I previously had mythtv setup only on a 160gb drive. Now I want to do an automatic install on another drive and use the 160gb drive only for /myth.

After going through automatic installation on the primary drive, and rebooting, I get the error:
LILO - Timestamp mismatch

I encountered this problem before on another system and gave up, thats why I was only using the 160gb drive by itself. I tried to set up grub to see what would happen and it worked, but I did not know how to set it up completely.

To get grub I did the following:
apt-get install grub
grub-install /dev/hda
update-grub

My question is how do I configure it? Is this correct for /boot/grub/grub.conf:
default 0
timeout 1
splashimage=(hd0,0)grub/splash.xpm.gz

title=Knoppmyth
root (hd0,0)
kernel (hd0,0)/vmlinuz-2.4.21-xfs
initrd (hd0,0)/initrd.gz

Is there anything else I need to add for it to boot?

I finally, finally, finally figured out the issue.... I got the exact same problem on another hard drive on which I had fully installed mythtv, but when I had tried this previously with windows installed on the same drive it had no issues booting. So this showed me that something that was installed on the hard drive was giving me the problem. So I gave up on trying to figure out how to configure grub

To fix the issue I needed to wipe out the master boot record from the secondary disk and poof no more LILO Timestamp mismatch. Just in case anyone else ever has this issue you would use the following command to clear the master boot record(MBR) from DOS/Windows:
fdisk /mbr

Hi,

After the install but before you reboot, go to a console and do:

$ apt-get update
....
$ apt-get install lilo

The lilo version included in v4 is broken.

jason

_________________
Jason L. Froebe

HealthyPals (http://www.healthypals.com)
Bookcrossing (http://www.bookcrossing.com)
WebBlog http://www.livejournal.com/users/jfroebe

Hi,

After the install but before you reboot, go to a console and do:


$ mount /dev/hda1 /mnt
$ cp /etc/resolv.conf /mnt/etc/resolv.conf
$ chroot /mnt /bin/bash
$ source /etc/profile
$ apt-get update
....
$ apt-get install lilo
....
$ lilo -v
$ exit
$ umount /dev/hda1

The lilo version included in v4 is broken.

jason

_________________
Jason L. Froebe

HealthyPals (http://www.healthypals.com)
Bookcrossing (http://www.bookcrossing.com)
WebBlog http://www.livejournal.com/users/jfroebe

Thanks jfroebe. Updating lilo worked.

Thank you so much for your comment. I used google to debug this the first time. Couldn't find the solution. Seemed a lot of people were scratching their heads on this one. Should have searched here first.

I popped in a win98 bootable cd after unplugging the first drive, and did the fdisk /mbr on the second drive. Bingo it boots fine!

I'm putting a second drive in for general file sharing, with a 200gig for Mythtv. Now to figure out the configureation on a dual capture card.

hey guys...newb here...how do you get to a console after the installation without rebooting first?

ctrl+alt+F1

ctrl+alt+F7 will get you back.

I too have had the "no boot" lilo issue after install, HOWEVER it was not solved in the same way that others have here.

I found by re-booting on the CD and then exiting to BASH, that lilo.conf had some "garbage" in the 2nd line (see below)

vga=791
part: /dev/hdb1, typ: 66

by commenting this line out, lilo would then write the MBR and the install would boot.

of course, this required mounting the disk and chrooting etc etc etc.

I had this problem after moving the data around from my old system to the new one and changing disks etc. I almost lost hope, since I could not come across any solution. I thought I had to reinstall everything again.

Luckily I came across your post and that fixed my problem. Since this happened after installation and multiple reboots, I used the following steps to resolve the problem.

---
I booted from the knppmyth install/boot cd. Selected option 6 for root shell.

# mount /dev/hda1 /mnt/hda1

Then followed the steps outlined here by Jason. It worked like magic.

Thanks again.

Siva.