From: Carlos Davila on
"That would be /boot/grub."

correct, my typo.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4B9972D7.2090208(a)lyle.smu.edu
From: Stefan Monnier on
> this evidently does not overwrite the boot sector, does grub-install do
> this? I have yet to run grub-install. Of course, this would not explain why
> my system still boots after deleting the vmlinuz files.

Yes it could: you installed `grub' on your Debian system, but you
haven't activated it, so you're still booting with Lilo, which uses
a "list of disk blocks" to find the kernel, so as long as those disk
blocks don't get overwritten, it'll boot just fine.


Stefan


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/jwvhbombh3u.fsf-monnier+gmane.linux.debian.user(a)gnu.org
From: Clive McBarton on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan Monnier wrote:
>> this evidently does not overwrite the boot sector, does grub-install do
>> this? I have yet to run grub-install. Of course, this would not explain why
>> my system still boots after deleting the vmlinuz files.
>
> Yes it could: you installed `grub' on your Debian system, but you
> haven't activated it, so you're still booting with Lilo, which uses
> a "list of disk blocks" to find the kernel, so as long as those disk
> blocks don't get overwritten, it'll boot just fine.


The bootsector which Carlos posted here (uuencoded) is a grub boot
sector. It contains the characteristic strings

"GRUB .Geom.Hard Disk.Read. Error"

which can be seen by uudecoding and looking at it with hexedit.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkuZiNwACgkQ+VSRxYk4408zQACfdylkPQHTy6A9o+pZVxLAuEPC
BXAAoJQ8RVwHQyL+EyZJ073H3C1ZG0HG
=6DC8
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4B9988DC.7090102(a)web.de
From: Carlos Davila on
Thib,

You nailed it. After having juggled hard drives around, I ended up
commenting out the line that mounts /dev/hda1 on /boot in fstab. Fixed
that, copied grub images to /boot/grub, and ran grub-install and
everything works as it should.

Thanks to all,
cd


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4B99A0BE.6030608(a)att.net
From: Tom H on
>>> MS-Windows used to have an undocumented switch "fdisk /mbr" which would
>>> remap the MBR and erase any copy of lilo or grub present.  I don't know if
>>> they still have that option.
>>
>> Undocumented?
>>
>> The command above works pre-XP.
>>
>> For XP, it is fixmbr and/or fixboot..
>>
>> For Vista and Seven, it is bootrec /fixmbr and/or bootrec /rebuildbcd.
>
> Thank you!  I'm going to be needing that information soon to re-install a DOS-style
> master boot record on a number of machines and move lilo to the boot sector
> for the /boot partition.

You're welcome. I hope that you have an actual Windows CD/DVD to use
the above commands given that most manufacturers ship recovery CDs
only that may or may not allow you to use these commands. :(


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/6d4219cc1003131715r652b570ew2de02923d0fcd384(a)mail.gmail.com