Anyone knows what this error means?

Our server had 2 scsi drives,
One is partitioned into /home, /boot
the other /mail

When we were still using Slackware 9.0, no such LILO Timestamp error.
when we switch then Slackware 9.1 then that LILO Timestamp occured.

What could be the problem?

Have you tried to rerun lilo? What happens?

How?

I mean if you meant reinstall....still LILO Timestamp...
We chose simple and MBR...

Ok..
You did what and what went wrong.

Does there come an error message when you type '/sbin/lilo'[enter], or when you boot your system and lilo gets run? (the former one is called sometimes running, sometimes installing to be mixed up either with the bootup or with the actual installation of the lilo package).

And what is the exact error message you got?

We had a server consisting of 2 scsi hard drives...

At first, we used the slackware 9.0 platform....installing just minimal packages just to support our servers..mail, proxy...etc.
After installing slackware...reboot then.....
it booted just fine...[this system is perfectly fine]

Now, we heard that there's a new release of slackware and that's 9.1...
We decided to try it in our server, select a kernel, partitioned, format, install packages, install LILO...now when rebooted.....
an error message LILO Timestamp occured. That's it...LILO Timestamp....
that two words only....then hang.

We were thinking, maybe BIOS or the system time and other elseS....

What we want actually is to compare both...and test which of the two is likely cool to work with...and what's new with 9.1

Thanks,

I got several times that problem, it is regarding to change of lilo version,
but I've forgot how I solved that problemo.

I suggest extract the new lilo package into a temporary directory to see
wut files that lilo replaces. Some files on /boot are some wut responsible
forgot, try man lilo, man rdev and lilo related cocument on /usr/doc ..

Actually this error happens when it boots up!

Try to reinstall your slackware 9.1. When you have finish your installation and push exit dont reboot. Try to tape liloconfig and configure your lilo again . Then if no error showed up then reboot .
It works for me .

Good luck =)

/ Teo

@S_Warlock
Thanks for the reply...I'll try it...

Just wondering...what might caused it...do I have a corrupted Slack...?

It seams like lilo writes to a temporary area and when you exit the installation the temporary area disappears. When you write lilo again it writes on the ordinary space.

Sorry for my bad English hope you will understand .

/ Teo

Do LILO do that normally or else?

I don't care with English as long I understand it... :lol:

Thank you very much...

I think ToniT's advice is correct. I haven't seen the timestamp error you refer to, but anytime you want to add another kernel to your boot menu, you need to edit lilo.conf (to add an entry for that new kernel) and then rerun lilo in order for that new kernel to be recognized. If you were on Slack v9.0 before, you'd probably be running the 2.4.20 kernel, and if you then insall Slack v9.1, you'd probably be running the 2.4.22 kernel, and I'll assume both kernels would be located in /boot.

If so, after you install the 2.4.22 kernel, you will need to edit and/or verify that lilo.conf contains an entry for that new 2.4.22 kernel, and then to make those changes take effect, you need to rerun the lilo program. As root, run: /sbin/lilo

Hopefully if the timestamp error is being thrown because lilo is confused, these steps would unconfuse it. Good luck with it -- J.W.

i had that issue when i wanted to restore my mbr coz lilo wouldn't boot. it was giving the timestamp error. anyways, i got that error during the uninstall. i had to use the '-U' option (instead of '-u'). what u could do is uninstall it and then re-install. shouldn't have the timestamp issue then.

I know this post is really old, still I have gotten the timestamp error.It happened to me when I shutdown windows improperly.When I started windows back up, i saw a couple of things came up that said they were checking for errors.

After that I've been getting the lilo- timestamp error everytime.I believe that windows may have veiwed lilo as an abnormality in my hardrive mbr.

Windows 98 killed my bootloader!!

You have tried to uninstall lilo (with -U) and reinstall it again?
Is your system totally unbootable (but you can access the partitions with a bootdisk)?
Have you tried to clean the mbr and try installing lilo again ?
Have you tried to install mbr loader again (eg. by using
)?

What is the contents of your /etc/lilo.conf you are trying to use?