sing "install-mbr" and this seems to have
damaged the boot record of Win98.
Booting Win98 comes up with the MBR of install-mbr. I ran DOS Fdisk /mbr
but that did not fix it. I seem to remember a similar problem some years
ago which I was able to fix with Norton Fixdisk. I won't be ho
> Hi everyone,
>
> sorry if this is a bit of a saga but please bear with me.
[trevails of repartitioning, ellided]
> A boot off RH floppy and re-install of LILO gives me the ability to boot
> into RH6.2.
> I can boot off floppy into potato on /dev/hda2.
> I can no longer boot Windoze, no great l
Tim Wood <[EMAIL PROTECTED]> writes:
> Hi everyone,
>
> sorry if this is a bit of a saga but please bear with me.
>
> [snip]
>
> Can anybody suggest a way to get back Win98 on /dev/hda1 and, more to
> the point, suggest a way to be able to boot /dev/ha1, /dev/hda5 and
> /dev/hda2?
Apart from `m
ed to remove HDA10 reduce the size of HDA3 and create HDA2 as a
primary ext2 partition. This went ok and I reloaded Potato.
At this point frustration got the better of me and I used install-mbr. I
could not boot into anything off the HD.
A boot off RH floppy and re-install of LILO gives me the ab
just re-load lilo into the MBR just make sure your lilo.conf is
configured right
to install to the MBR use the line:
boot=/dev/hda
to install to the primary, master hd, change accordingly for other
drives.
nate
John Anderson wrote:
>
> I am having an error messages such as "N
On Sun, 03 Sep 2000, John Anderson wrote:
> I am having an error messages such as "No operating system" or, 40 40
> 40... on the screen after the hard disk jumpers were not set up correctly.
> What is the command to redo the master boot record?
>
Using windows fdisk
I am having an error messages such as "No operating system" or, 40 40
40... on the screen after the hard disk jumpers were not set up correctly.
What is the command to redo the master boot record?
John Kerr Anderson
[EMAIL PROTECTED]
Debian GNU/
ice to is real root partition. then next time this happens he can
> just stick the floppy in and run /sbin/lilo just like normal, and
> everything will be everything again.
>
> > How can I prevent something like this happening again?
Something in the bios can be set to prevent things (
On Tue, Jun 06, 2000 at 04:33:03PM -0400, Arcady Genkin wrote:
>
> I'm going over tomorrow to reinstall LILO for him.
you should dd his kernel to a floppy, then use rdev to set the root
device to is real root partition. then next time this happens he can
just stick the floppy in and run /sbin/li
did nothing at all that could cause this.
>
> Could it be that Windows "repairs" the MBR by removing a "foreign"
> multy-booter and overwriting it with the native one to only boot
> Windows? If so, what could have caused this behavior. I've never
> hea
A friend of mine is experiencing a weird situation with multy-booting.
I installed Linux for him on a second harddrive all by itself, and
installed Lilo into MBR on /dev/hda to mutli-boot Linux and Windows
(Windows off /dev/hda1, and Linux off /dev/hdc1).
This worked fine for about a month until
On Thu, May 11, 2000 at 12:23:40PM -0700, Dan Hutchinson wrote:
> I have to uninstall Linux and put WindowsNT on a workstation at work.
> I have formated the disk with fdisk and I get
> LILO
> Linux Loading ..
> Error 0x01
> Linux Loading ..
> etc
> .
> .
>
gt; How do I erase the MBR?
>
> In DOS you can do "fdisk /mbr".
>
>
> --
> Steve Zinck <[EMAIL PROTECTED]>
> http://nerd.halifax.ns.ca
>
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED]
> < /dev/null
>
>
_
Use dos boot floppy with fdisk on it. Then type 'fdisk /mbr'
Oliver
Dan Hutchinson wrote:
>
> I have to uninstall Linux and put WindowsNT on a workstation at work.
> I have formated the disk with fdisk and I get
> LILO
> Linux Loading ..
> Error 0x01
On Thu, May 11, 2000 at 12:23:40PM -0700, Dan Hutchinson wrote:
> How do I erase the MBR?
In DOS you can do "fdisk /mbr".
--
Steve Zinck <[EMAIL PROTECTED]>
http://nerd.halifax.ns.ca
I have to uninstall Linux and put WindowsNT on a workstation at work.
I have formated the disk with fdisk and I get
LILO
Linux Loading ..
Error 0x01
Linux Loading ..
etc
.
.
.
How do I erase the MBR?
Dan
___
To get
>> I have a machine with two hard disks here, that other OS resides
>> on hda and I added the second drive (hdc) for Debian. The setup
>> installed a MBR on hdc, but my BIOS only supports booting from
>> hda. Is there a way to install lilo in the MBR on hda and have
&g
> >lilo.conf: change the boot=/dev/hdc into boot=/dev/hda
> >image=/dev/hdc1 should be already there and it is fine.
> >and an option other=/dev/hda1 is needed for booting the other os.
>
> I tried that, but LILO hangs with LI-. I did run lilo to update
> the MBR - se
r from /dev/hda
> Merging with /boot/boot.b
> Boot image: /vmlinuz
> Added Linux (alias lnx) *
> Boot other: /dev/hda1, loader /boot/chain.b
> Added Windows (alias win)
> /boot/boot.0300 exists - no backup copy made.
> Writing boot sector.
>
What does >fdisk -l /dev/h
On Thu, 4 May 2000, matthschulz wrote:
>On Thu, 04 May 2000, Philip Lehman wrote:
>> On Thu, 4 May 2000, Oswald Buddenhagen wrote:
>>
>> >> I have a machine with two hard disks here, that other OS resides
>> >> on hda and I added the second drive (hdc) for
On Thu, 04 May 2000, Philip Lehman wrote:
> On Thu, 4 May 2000, Oswald Buddenhagen wrote:
>
> >> I have a machine with two hard disks here, that other OS resides
> >> on hda and I added the second drive (hdc) for Debian. The setup
> >> installed a MBR on hdc,
On Thu, 4 May 2000, Oswald Buddenhagen wrote:
>> I have a machine with two hard disks here, that other OS resides
>> on hda and I added the second drive (hdc) for Debian. The setup
>> installed a MBR on hdc, but my BIOS only supports booting from
>> hda. Is there a way to
> I have a machine with two hard disks here, that other OS resides
> on hda and I added the second drive (hdc) for Debian. The setup
> installed a MBR on hdc, but my BIOS only supports booting from
> hda. Is there a way to install lilo in the MBR on hda and have
> it boot
I have a machine with two hard disks here, that other OS resides
on hda and I added the second drive (hdc) for Debian. The setup
installed a MBR on hdc, but my BIOS only supports booting from
hda. Is there a way to install lilo in the MBR on hda and have
it boot linux from hdc1?
I'm familiar
On Sun, Feb 20, 2000 at 01:05:57AM -0600, ktb wrote:
> Here it is:
>
> boot=/dev/hda
> root=/dev/hdb1
> compact
> install=/boot/boot.b
> delay=40
> map=/boot/map
> vga=4
Take it that number means something on your system...
>
> image=/vmlinuz
> label=slink
> read-only
>
> other=/dev/hda
Subject: Re: Lilo gets wiped off /mbr
> It would help if you posted your /etc/lilo.conf. My first guess is it's
> installing lilo on the second disk, rather than the first.
> --
> ++
> | Eric G. Milleregm2
It would help if you posted your /etc/lilo.conf. My first guess is it's
installing lilo on the second disk, rather than the first.
--
++
| Eric G. Milleregm2@jps.net |
| GnuPG public key: http://www.jps.net/egm2/gpg.asc |
98 or Slink
one time. The /mbr is on the Windows 98 disk, Slink is on another. I read
in the mail list that sometimes if the boot sector has virus protection
enabled this type of thing happens but I checked and it is not. Has anyone
had this problem before?
Thanks,
kent
@ www.xyf.webprovider.com
On 4/12/99 luis wrote:
how can i install a sort of mbr that runs before lilo ?
because after having instaled debian i need to install a dos
partition, but as hda1 is the swap, hda2 linux and hda3 is dos, lilo
can not load the last partition (far beyong the 1024 kbytes limit)
if LILO won&#
hello
how can i install a sort of mbr that runs before lilo ?
because after having instaled debian i need to install a dos
partition, but as hda1 is the swap, hda2 linux and hda3 is dos, lilo
can not load the last partition (far beyong the 1024 kbytes limit)
so, is possible to boot the dos
y running
> (DOS) "fdisk /mbr". Linux fdisk will not do this. This procedure will
> not alter your partition table, but it will, of course, make Linux
> unbootable from the HD.
>
Unbootable, that is, if LILO was installed to /dev/hda rather than
to one of the partitions.
On Tue, 6 Jul 1999, Felipe Alvarez Harnecker wrote:
> Can someone send me a DOS Master Boot record so a can dd it to
> /dev/hda?
No, but if you boot a DOS floppy then you can reconstitute it by running
(DOS) "fdisk /mbr". Linux fdisk will not do this. This procedure wil
try:dd man
dd is interesting, but dangerous!!
something like: dd if=/dev/hda /of=bootsec.bla bs=512 count=1
Ciao,
Kotya
>
> Can someone send me a DOS Master Boot record so a can dd it to
> /dev/hda?
>
> Please answer only if you realy know what i mean because i dont want
> to alt
ll.
Unless it is a freedos mbr, this is illegal.
Why don't you use the mbr provided in the mbr package?
HTH,
Jens
P.S.: Please vote against Spam! At
http://www.politik-digital.de/spam/
(Sorry Europeans only)
---
[EMAIL PROTECTED] [EMAIL PROTECTED]
Key ID: 2048/E451C639 Jens
The DOS MBR will only be valid for you from a hard drive with the exact
same paramaters and exact same partition table. (i.e. no one has one you
can use).
What you can do (I have done this before with success) is: (But beware,
this is not guaranteed to work--I have also done this and failed)
1
is, since I have a HD with the MBR not been
recognized, but I already Linux installed.
>
> Send me version info as well.
>
> Thanks.
>
> --
> __
>
> Felipe Alvarez Harnecker. QlSoftware.
>
> Tel.
*- On 6 Jul, Felipe Alvarez Harnecker wrote about "DOS MBR"
>
> Can someone send me a DOS Master Boot record so a can dd it to
> /dev/hda?
>
> Please answer only if you realy know what i mean because i dont want
> to alter the partition table.
>
> Send me
Can someone send me a DOS Master Boot record so a can dd it to
/dev/hda?
Please answer only if you realy know what i mean because i dont want
to alter the partition table.
Send me version info as well.
Thanks.
--
__
Felipe Alvarez Harnecker
Boot from any DOS 6.X/Win95 bootable diskette and once in the DOS prompt
type fdisk /mbr. This will reinstate your clubbered MBR.
BTW, is there anyway in this list to reply to the list instead of the
author? My problem is I have filtering of incoming emails and it doesn't
work 'coz
Evening all.
Small problem here: seems that Lilo screwed up my MBR for one of the hard
drives, specifically one with Win95 on it.
Here is lilo.conf:
boot = /dev/hda
root = /dev/hdb2
install = /boot/boot.b
map = /boot/map
vga = normal
delay = 50
ramdisk = 0
read-only
default = linux
image
:
> -BEGIN PGP SIGNED MESSAGE-
>
> On Tue, 24 Nov 1998, Patrick Colbeck wrote:
>
> > Following up to my prevous mail is the lilo or mbr shipped with Debian 2
> > faulty
> > ? When trying to boot from hda3 (hda1 is win98, hda2 is swap) it just says
> > load
-BEGIN PGP SIGNED MESSAGE-
On Tue, 24 Nov 1998, Patrick Colbeck wrote:
> Following up to my prevous mail is the lilo or mbr shipped with Debian 2
> faulty
> ? When trying to boot from hda3 (hda1 is win98, hda2 is swap) it just says
> loading Linux the reboots. It n
Reply-To:
Hi
Following up to my prevous mail is the lilo or mbr shipped with Debian 2 faulty
? When trying to boot from hda3 (hda1 is win98, hda2 is swap) it just says
loading Linux the reboots. It never gets to vmlinuz. This is like what
happens when it cant find vmlinuz when you forget
Debian doesn't install LILO as the MBR, but rather uses a program
called MBR. It is MBR that is presenting this prompt. Look in
/usr/doc/MBR for documentation.
You don't give enough of a description of your installation to
determine the problem. Here's a guess though. It s
e problem is tied in some way to Lilo and the MBR, but don't know what
to do to fix it...
Please respond to my email as well as the list, since I read the list only
through the web pages, and need an answer fairly soon (since we may need to
cancel the course...).
Cheers
-duncan
Thanx to everyone who responded to my request about removing mbr. Since
Linux is the only OS installed on the machine in question, I have
reconfigured LILO to install in the MBR. Seems to have had the intended
effect.
Thanx!
On Fri, 14 Aug 1998, Gregory T. Norris wrote:
> I was wondering how hard it is to remove/replace the mbr package. We have
> a single system running hamm, for which we want to disable the capability
> of booting from a diskette. Currently we've disabled floppy-boot in the
> BIO
On Fri, 14 Aug 1998, Gregory T. Norris wrote:
: I was wondering how hard it is to remove/replace the mbr package. We have
: a single system running hamm, for which we want to disable the capability
: of booting from a diskette. Currently we've disabled floppy-boot in the
: BIOS
I was wondering how hard it is to remove/replace the mbr package. We have
a single system running hamm, for which we want to disable the capability
of booting from a diskette. Currently we've disabled floppy-boot in the
BIOS, and configured LILO to require a password (only if kernel-option
pposed to LBA or LARGE) .. It should
work then ... I assume you can boot from floppy. If you don't have auto
detect, you can read the disk type during floppy boot and use those ..
--Jon.
>
> Thank you all for still taking a notice of me (this is the 4th letter
> concerning the
Please check to see that lilo has the right parameters for your harddisk
Particularly the bits about Large, LBA ...
--Jonathan
> "Lil-" comes up on the screen and the system hangs
>
> (Just glad I have a recent kernel boot disk =) )
>
> /boot/boot.hda doesn't exist.
>
> I have no WinNT instal
#x27; runs fine and says that it has restored the original MBR, but now
> on bootup,
> "Lil-" comes up on the screen and the system hangs
> (Just glad I have a recent kernel boot disk =) )
> /boot/boot.hda doesn't exist.
> Here's a list of the files in /boot/
>
and others, for
the NT boot loader
/dev/hda5 -- that's the NTFS partition containing NT
My system _did_ work before -- honest!!
Thank you all for still taking a notice of me (this is the 4th letter
concerning the MBR!)
Tristan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Sorry, that should have been:
dd if=/boot/boot.0301 of=/dev/hda bs=446 count=1
-Ossama
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
is /dev/hda, 0800 is /dev/sda, etc. Those backups
can be used to restore the old MBR if no easier method is available. The
commands are
dd if=/boot/boot.0300 of=/dev/hda bs=446 count=1 or
dd if=/boot/boot.0800 of=/dev/sda bs=446 count=1
respectively.
--
You appea
On Sun, May 10, 1998 at 01:23:48PM +0100, Tristan Day wrote:
> Thanks to all for all the help and ideas, but it still won't work: here's
> what has gone wrong:
Can you state the problem again? I missed your earlier posts.
> The DOS 'fdisk /MBR' ran with no erro
Thanks to all for all the help and ideas, but it still won't work: here's
what has gone wrong:
The DOS 'fdisk /MBR' ran with no errors, but made no difference to bootup.
'lilo -u /dev/hda' says "boot sector of /dev/hda does not have a lilo
signature"
You may have already come across this link for
multibooting Linux and ???.
http://www.owlnet.rice.edu/~sedmison/directboot.html
--
tony mollica
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sat, May 09, 1998 at 05:54:08PM +0100, Tristan Day wrote:
> When I load from a boot disk (created by "format /s" at dos prompt in
> Win95), fdisk doesn't work because it doesn't exist, thus
>
> fdisk /MBR
>
> doesn't work. If I try this in linux,
When I load from a boot disk (created by "format /s" at dos prompt in
Win95), fdisk doesn't work because it doesn't exist, thus
fdisk /MBR
doesn't work. If I try this in linux, it says MBR not found
=(
Tristan -- one unhappy WinNT4 and Debian dual-booter.
--
't
> boot Win95. It says "booting Win95", then returns to the LILO prompt.
>
> The problem remains, I can't seem to overwrite the MBR, not with LILO, not
> with fdisk. I found out that the Windows partition was FAT32, but surely
I bet FAT32 is the problem. It is not D
[EMAIL PROTECTED] writes:
> Where can one find information about /sbin/activate? I have it
> on my system (Debian 1.2.18), but no man pages, How-To, or other
> documentation. It does not give any meaningful response to activate -h
> or activate --help. What does this program do?
According
-Original Message-
From: Dale Harrison <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Date: Wednesday, October 29, 1997 9:26 PM
Subject: Linux, FAT32 and a mighty odd MBR.
>Hello.
>
>I had a weird problem last night, installing Debian 1.3* on a friends PC.
>F
I don't have an awsome computer like that, but I experianced problems when
installing LILO on the MBR with win95. Win95 lost all its long filenames!
I'd would try installing LILO on the root partition of Linux.
-Paul
On Thu, 30 Oct 1997, Dale Harrison wrote:
> Hello.
>
> I
AIL PROTECTED]> wrote:
> You could also try to write a new MBR with "/sbin/activate /dev/hda 1"
> or whichever partition Win95's on.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
thing is removed.
IIRC (since I last installed Debian) LILO doesn't always install on
the MBR, but in my case in /dev/hda1. What does your /etc/lilo.conf
look like?
You could also try to write a new MBR with "/sbin/activate /dev/hda 1"
or whichever partition Win95's on.
--
Dale Harrison <[EMAIL PROTECTED]> writes:
> So, I guess I'm throwing this out to you guys, is this a Windows problem?
> A Debian problem? A LILO problem? A FAT32 problem?
I can't point out a solution but I can tell you that it's probably not
related specifically to Debian or to Linux, as I have h
O boot signature on /dev/hda. Hence
nothing is removed.
Hmmm. Boot via Win95 rescue disk and fdisk /mbr. Reboot and LILO's STILL
there. Tried this more times than I can recall.. LILO won't die. System
Commander reported some wacky things about the MBR, saying things were
pretty well screwed wi
tion of lilo with the rewrite_table option was successful,
> but when I add a section for win95 in lilo.conf and run /sbin/lilo it
> complains that lilo must reside on the mbr (i assume that win95 has
> taken
> the mbr). How can I put lilo back on the mbr?
>
You need to use the '
add a section for win95 in lilo.conf and run /sbin/lilo it
complains that lilo must reside on the mbr (i assume that win95 has
taken
the mbr). How can I put lilo back on the mbr?
Any help is greatly appreciated
Thanks goes out to all who responded to my plea for help.
After reading everyones mail and falling back to a phrase we use
in the Military "when all else fails, read the instructions!" I
have my P90 back up and going again!
I checked out my boot directory and found the following files:
boot.0300
ilo on both /dev/hda & /dev/hda1.
Yep, I thought so. I did that once before.
>
> Several nice people have e-mailed me and told me to do a fdisk /mbr
> to wipe out lilo on the mbr (/dev/hda) but what about lilo on /dev/hda1?
>
> Have I trashed my DOS partiton information? What c
Gertjan Klein wrote:
>
> From what you've written, I gather that you inadvertedly told LILO to
> overwrite the boot sector (_not_ the MBR) of your DOS partition. DOS
> keeps some important bookkeeping information in it's boot sector, among
> which the size of the partiti
on your primary C: drive partition.
>[All information zapped...]
>
>>From what you've written, I gather that you inadvertedly told LILO to
>overwrite the boot sector (_not_ the MBR) of your DOS partition. DOS
>keeps some important bookkeeping information in it's boot
[EMAIL PROTECTED] (Brian Hutchinson) wrote:
> Here is some more information on my sad state!
[All information zapped...]
>From what you've written, I gather that you inadvertedly told LILO to
overwrite the boot sector (_not_ the MBR) of your DOS partition. DOS
keeps some important
o a fdisk /mbr
to wipe out lilo on the mbr (/dev/hda) but what about lilo on /dev/hda1?
Have I trashed my DOS partiton information? What can I do now?
I did run fdisk and the partition information looked correct. It knew
the partition was all dos and it was bootable/primary.
Thanks again,
On Sat, 22 Feb 1997, Rick Macdonald wrote:
> On Sat, 22 Feb 1997, Brian Hutchinson wrote:
>
> > Here is some more information on my sad state!
>
> Maybe I'll be the first to answer the simplest of your questions:
>
> The dos mbr can be replaced with dos
Brian --
For a quick fix, a provided you have a backup to boot dos, reboot
under drive a: for dos, get onto the c: drive, and run "fdisk /mbr". This
will restore the c: disk so that it will boot dos automatically.
For future reference, whenever you rebuild the kernel, it
On Sat, 22 Feb 1997, Brian Hutchinson wrote:
> Here is some more information on my sad state!
Maybe I'll be the first to answer the simplest of your questions:
The dos mbr can be replaced with dos fdisk:
c:\=> fdisk /mbr
...RickM...
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-ma
Here is some more information on my sad state!
I thought no problem, I'll just make a dos boot floppy.
wrong. When I do a C: I can get to the drive but when
I try to do a dir or anything I get:
Invalid media type reading drive C
The machine I built the kernel for (the 386) is giving me
problem
I tried using lilo to forget about my linux drive and just boot
dos but I think I ended up messing things up. I tried:
/etc/lilo.conf:
boot=/dev/hda
other=/dev/hda1
table=/dev/hda
label=dos
When I boot the machine I get LILO then unexpected EOF loading dos.
Is there any way I can rebuild my MBR
301 - 381 of 381 matches
Mail list logo
