Re: [OT] Linux should not be booting

Tom H wrote: 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. :( Maybe the mbr package is what we're looking for here. http://packages.debian.org/l

Re: [OT] Linux should not be booting

>>> 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

Re: Re: Linux should not be booting

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 debi

Re: Linux should not be booting

-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

Re: Re: Linux should not be booting

"That would be /boot/grub." correct, my typo. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b9972d7.2090...@lyle.smu.edu

Re: Linux should not be booting

> 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,

Re: Linux should not be booting

Carlos E. Davila wrote: [...] but this evidently does not overwrite the boot sector, does grub-install do this? Yes. > I have yet to run grub-install. Of course, this would not explain why my system still boots after deleting the vmlinuz files. Did you evaluate our little theories? I imagi

Re: Re: Linux should not be booting

Thanks to all who have responded. I think the problem may be related to an issue I had with grub in January (see ddd4daee1001091255n7cfa4037l1663b317fdf09...@mail.gmail.com ). Running "apt-get install grub", created the /boot/grub/ dir

Re: Linux should not be booting

On Thu, Mar 11, 2010 at 10:03 AM, Clive McBarton wrote: > > Interesting. You seem to have figured out some secret "block mode" of > grub, which I have been looking for but didn't find. Can you post your > boot sector here? Typing the following (as root) will print the boot > sector in ASCII, which

Re: Linux should not be booting

On Thu, 11 Mar 2010, Tom H wrote: 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? Yes, it didn't appear in any of their regular help sources, at least

Re: [OT] Linux should not be booting

On Thu, 11 Mar 2010 12:49:55 -0500 (EST), Tom H wrote: > On Thu, 11 Mar 2010 09:40:14 -0500 (EST), Robert Brockway wrote: >> 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

Re: Linux should not be booting

> 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 bo

Re: Linux should not be booting

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Carlos Davila wrote: > I deleted the following files from /: > > initrd.img initrd.img.old vmlinuz vmlinuz.old > > and I deleted all files in /boot: > > config-2.6.26-2-686initrd.img-2.6.26-2-686 > System.map-2.6.26-2-amd64 > config

Re: Linux should not be booting

On Thu, 11 Mar 2010, Carlos Davila wrote: Yet linux still boots. I am using Lenny and grub. Where is the kernel actually stored then? Hi Carlos. This is actually the expected behaviour with lilo. I've seen it myself many times with lilo. This is because lilo maps the blocks of the kernel

Re: Linux should not be booting

On 2010-03-11 06:41, Carlos Davila wrote: I deleted the following files from /: initrd.img initrd.img.old vmlinuz vmlinuz.old and I deleted all files in /boot: config-2.6.26-2-686initrd.img-2.6.26-2-686System.map-2.6.26-2-amd64 config-2.6.26-2-amd64 initrd.img-2.6.26-2-amd64 vmlin

Re: Linux should not be booting

Carlos Davila wrote: Yet linux still boots. I am using Lenny and grub. Where is the kernel actually stored then? Ha. What I can think of: * You were using block-lists to reference the second stage file of grub1 from the first stage in the boot sector, and you didn't store filesystem driver

Linux should not be booting

I deleted the following files from /: initrd.img initrd.img.old vmlinuz vmlinuz.old and I deleted all files in /boot: config-2.6.26-2-686initrd.img-2.6.26-2-686System.map-2.6.26-2-amd64 config-2.6.26-2-amd64 initrd.img-2.6.26-2-amd64 vmlinuz-2.6.26-2-686 grub Syste