Very strange thing.. I'm puzzled.
Zibri
I have an 80GB SAMSUNG HD and 4 primary partitions.
1) NTFS
2) NTFS
3) ext2 (slackware)
4) ext2 (backtrack)
I have lilo as bootloader and everything works.
Then I bought a 160GB SAMSUNG HD.
And problems started.
I copied the old disk on the new one using ghost (I also tried partition
magic and ESEUS).
I cleaned the MBR as usual and windows starts normally.
The problem is with LILO.
As I install it there's no way to make it work.
All I get is L 99 99 99 99 99.... you know.
To be safe from errors I also remade lilo from scratch.
NO WAY.
It doesn't even show a menu so it doesn't even boot Windows.
I really don't know what the problem could be.
With the old HD everything works.
This HD is perfectly working.. no read errors, no nothing.
The worse thing is that I can't boot from USB (not supported by bios and no
new bioses around from ages).
What should I do?
(Don't tell me to buy a new laptop :P )
Leon Whyte
That should fix it.
--
Leon
A computer without Microsoft is like a chocolate cake without mustard.
< running Linux >
Lew Pitcher
wrote:
Boot from a recovery disk or "Live Linux CD", chroot to the Linux
installation that has your /etc/lilo.conf, and rerun /sbin/lilo
For the Linux kernel load, LILO reads absolute sectors from the disk. Change
the disk geometry (which you did, when you cloned your 80GB hd onto a 160GB
hd), and you have to change the sectors which LILO reads from. You do this
by running /sbin/lilo, so that it can determine the absolute sector
addresses of your /boot/vmlinuz (or equivalent) file, and rebuild the boot
sector list in the MBR.
--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
http://pitcher.digitalfreehold.ca/ | GPG public key available by request
---------- Slackware - Because I know what I'm doing. ------
Moe Trin
<4a40da37$0$47542$4faf...@reader1.news.tin.it>, Zibri wrote:
>I have lilo as bootloader and everything works.
>
>Then I bought a 160GB SAMSUNG HD.
>And problems started.
>
>I copied the old disk on the new one using ghost (I also tried partition
>magic and ESEUS).
>
>I cleaned the MBR as usual and windows starts normally.
>
>The problem is with LILO.
No - the problem is that you don't understand LILO - it's a _boot_
loader, and thus is meant to work before an operating system is
installed. I take it you also didn't bother reading the HOWTOs
-rw-rw-r-- 1 gferg ldp 23639 Aug 21 2000 Hard-Disk-Upgrade
-rw-rw-r-- 1 gferg ldp 61235 Dec 14 11:36 LILO
-rw-rw-r-- 1 gferg ldp 79391 Nov 8 2004 Large-Disk-HOWTO
-rw-rw-r-- 1 gferg ldp 8080 Apr 26 2001 Multiboot-with-LILO
They're not even that _big_
>As I install it there's no way to make it work.
>All I get is L 99 99 99 99 99.... you know.
From the LILO User Guide;
L The first stage boot loader has been loaded and started, but
it can't load the second stage boot loader. The two-digit error
codes indicate the type of problem. (See also section "bioserr"
This condition usually indicates a media failure or a geometry
mismatch (e.g. bad disk parameters, see section "diskgeo".
99 invalid second stage index sector
>I really don't know what the problem could be.
>With the old HD everything works.
>This HD is perfectly working.. no read errors, no nothing.
The old disk does not look like the "new" disk - so the instructions
to go to a certain physical location on the disk are taking you some
other place.
>The worse thing is that I can't boot from USB (not supported by bios
>and no new bioses around from ages).
Does it have a floppy?
ftp://ibiblio.org/pub/Linux/system/recovery/
1728550 May 4 2002 tomsrtbt-2.0.103.ElTorito.288.img.bz2
2242580 May 4 2002 tomsrtbt-2.0.103.dos.zip
1119 May 4 2002 tomsrtbt-2.0.103.lsm
1829836 May 4 2002 tomsrtbt-2.0.103.tar.gz
>What should I do?
Not as many people are using LILO these days, but I'd bet if you used
a search engine looking for "LILO 99"
Results 1 - 10 of about 788,000 for LILO 99. (0.69 seconds)
it used to be a VERY common problem. The fix is fairly simple once
you can get to Linux (running /sbin/lilo, see the man page)
Old guy
Matt Giwer
This is linux. Being puzzled is not strange at all.
It appears the copy process makes changes lilo does not recognize. It would
probably only work with the same make and model and thus size new drive. So
find some way to get into it, say with a rescue disk and let it configure
itself. If all else fails and you have to reinstall do windows first.
--
They hate us for our freedom to call Bush a retard.
-- The Iron Webmaster, 4147
http://www.giwersworld.org/israel/is-seg.phtml a14
Wed Jun 24 04:42:22 EDT 2009
Zibri
news:kK50m.31924$Db2.13623@edtnps83...
It didn't.
Zibri
news:d13b1$4a40eedd$4c0a94f5$26...@TEKSAVVY.COM-Free...
Yep I know how lilo works.
And that didn't fix it.
At the end I had to dd /dev/zero on the whole disk, recreate partitions,
copy data and then it worked.
I wonder what was the problem.
Zibri
news:slrnh42cs7.b...@compton.phx.az.us...
I know exactly how LILO works, thanks.
I don't know what the problem was.
To solve it, I had to ZERO all the hard disk, recreate partitions and copy
data.
Then lilo installation worked again.
Maybe the disk was messed up by partition magic/norton ghost.
That never happened to me before.
Nico Kadel-Garcia
> "Moe Trin" <ibupro...@painkiller.example.tld> wrote in message
>
> news:slrnh42cs7.b...@compton.phx.az.us...
>
>
>
> > On Tue, 23 Jun 2009, in the Usenet newsgroup comp.os.linux.setup, in
> > article
You couldn't just zero the first few blocks, to get rid of boot
loaders and partition tables? That's much faster.
Zibri
news:cb4a37a6-fa6a-470e...@v4g2000vba.googlegroups.com...
>You couldn't just zero the first few blocks, to get rid of boot
>loaders and partition tables? That's much faster.
Sure I could.
Nico Kadel-Garcia
Good. You stated that you had to "ZERO all the hard disk". This
imples that the much faster step of just zeroing the first few blocks
would have been enough.
wisdomkiller & pain
....
> At the end I had to dd /dev/zero on the whole disk, recreate partitions,
> copy data and then it worked.
> I wonder what was the problem.
Ghost doesn't really know how to deal with *nix partitions. It just raw-
copies them, keeping the old 32bit lba sectors when you actually copied over
to a bigger (>137G) drive that requires a change. It might have (sort of)
kept working when your linux partitions would have resided at the beginning
of the disk.
John Hasler
> I copied the old disk on the new one using ghost
And that's your problem. While Ghost claims to "copy the disk",
it doesn't. It tries to be "smart" and not copy things that "don't
matter" (don't matter to Windows, that is). In general Linux tools do a
better job of handling Windows installations than Windows tools do with
Linux installations.
--
John Hasler
jo...@dhh.gt.org
Dancing Horse Hill
Elmwood, WI USA