File: 79.html

package info (click to toggle)
lg-issue36 2-4
  • links: PTS
  • area: main
  • in suites: woody
  • size: 2,920 kB
  • ctags: 242
  • sloc: makefile: 36; sh: 4
file content (371 lines) | stat: -rw-r--r-- 13,825 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<META NAME="generator" CONTENT="lgazmail v1.1G.e">
<TITLE>The Answer Guy 36: 
Persistent Boot Sector
</TITLE>
</HEAD><BODY BGCOLOR="#FFFFFF" TEXT="#000000"
	LINK="#3366FF" VLINK="#A000A0">
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<H4>"The Linux Gazette...<I>making Linux just a little more fun!</I>"</H4>
<P> <hr> <P>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<center>
<H1><A NAME="answer">
	<img src="../../gx/dennis/qbubble.gif" alt="(?)" border="0" align="middle">
	<font color="#B03060">The Answer Guy</font>
	<img src="../../gx/dennis/bbubble.gif" alt="(!)" border="0" align="middle">
</A></H1> 
<BR>
<H4>By James T. Dennis,
	<a href="mailto:answerguy@ssc.com">answerguy@ssc.com</a><BR>
	Starshine Technical Services,
	<A HREF="http://www.starshine.org/">http://www.starshine.org/</A> 
</H4>
</center>

<p><hr><p>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<!-- begin 79 -->
<H3 align="left"><img src="../../gx/dennis/qbubble.gif" height="50" width="60"
	  alt="(?) " border="0">
Persistent Boot Sector
</H3>


<p><strong>From Hummingbird Designs on Thu, 24 Dec 1998  
</strong></p>
<!-- ::
Persistent Boot Sector
~~~~~~~~~~~~~~~~~~~~~~
:: -->
<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
Hi,
</STRONG></P>
<P><STRONG>
I installed Linux on my PC at work and had everything working with
System commander, I have to use NT for some apps we use at work.
</STRONG></P>
<P><STRONG>
anyway, I was trying to get the nic card working so I tried using
the setup tool to install the kernel from the Cdrom that is used
to install linux off a network.  Now everytime I turn on the
machine it gives me the screen as if I had installed a bootdsk
like when you first install Linux. I have done EVERYTHING I know
of to get that out of there . . .I used a zerofill utility that
goes over each and every sector of every track and fills it with
0's including the MBR. and that damn message still comes up
everytime I boot. . .  I was thinking of removing my Hard drive
and seeing if it flashed my BIOS or something cause according to
Quantum9its a quantum drive) their utility is almost like a low
level format.
</STRONG></P>
<P><STRONG>

</STRONG></P>
<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
"the setup tool..." (what setup tool?)
"the screen as if I had installed a bootdsk[sic]" (what
screen?)
"EVERYTHING" (what is "everything?").
"zerofill utility" (what utility?)
"that damn message" (what damn message?).
</BLOCKQUOTE>
<BLOCKQUOTE>
You do seem to be a bit sketchy on the specifics so I'll
have to guess.
</BLOCKQUOTE>
<BLOCKQUOTE>
You had (some distribution of) Linux installed on your
system in a dual boot configuration with NT.  You were using
System Commander as your primary boot manager.  Presumably
you installed LILO (the Linux loader) into the "logical boot
record" (the "superblock") of one of your Linux filesystems
(presumably the root fs).  While trying to configure or
troubleshoot some problem with a network card (NIC) you used
some sort of "setup" utility which somehow configured your
system to bypass System Commander's boot record (presumably
by overwriting it with a copy of LILO).  You've tried some
ways to restore your System Commander installation, and/or
to build a new MBR, and those have been unsuccessful.
</BLOCKQUOTE>
<BLOCKQUOTE>
O.K.  Given that guess work I have a hypothesis.  You may
have run something like '<TT>FDISK /MBR</TT>' from your NT boot disk.
This may have enabled the active partition in your MBR.  The
DOS MBR code would load the logical boot record of the
active partition.  If your Linux partition (with its copy
of LILO in the superblock" ) just happened to be the active
partition at the time --- you might see that copy of LILO
(one of two that had been installed on your disk, one on the
MBR and the other in the LBR/superblock) as the first screen
on boot up.
</BLOCKQUOTE>
<BLOCKQUOTE>
(I'm not sure this scenario accounts for all of your
symptoms since this is all based on guesswork).
</BLOCKQUOTE>
<BLOCKQUOTE>
I have no idea what your "zero fill" utility is doing ---
but it almost certainly is not zero'ing out track zero of
your hard drive (including the MBR).  That would render the
system unbootable and would destroy the primary copy of your
partition table (the last 50 bytes or so of the MBR).  The
Linux/Unix command to do this is very simple:
</BLOCKQUOTE>
<BLOCKQUOTE> <BLOCKQUOTE> <CODE>
dd if=/dev/zero of=/dev/hda bs=512 count=63
</CODE> </BLOCKQUOTE> </BLOCKQUOTE>

<BLOCKQUOTE>
... where <TT>/dev/hda</TT> is the first IDE drive, 512 is the bytes
per sector and count is the number of sectors in a typical
track.  DON'T DO THIS!  (If you insist on doing this, first
double check which device you want to use, the first IDE is
<TT>/dev/hda</TT> and the first SCSI is <TT>/dev/sda</TT>, then check the
number of sectors per track --- which should be listed in
your CMOS setup for an IDE drive and would be listed in your
vendor documentation and <EM>possibly</EM> by your SCSI adapter
diagnostics firmware).
</BLOCKQUOTE>
<BLOCKQUOTE>
You could save a copy of your MBR and partition table using
dd with a command like:
</BLOCKQUOTE>
<BLOCKQUOTE> <BLOCKQUOTE> <CODE>
dd if=/dev/hda bs=512 count=1 of=/root/mbr.bin
</CODE> </BLOCKQUOTE> </BLOCKQUOTE>

<BLOCKQUOTE>
... which you can use in scripts to compare and replace your
MBR in future mishaps.
</BLOCKQUOTE>
<BLOCKQUOTE>
It's possible that System Commander's boot loader is still
in the MBR --- but that it's been configured to skip it's
opening menu/selection prompting and boot directly off of
your Linux partition.
</BLOCKQUOTE>
<BLOCKQUOTE>
Of course it's also possible that Linux as completely
taken over your system; that's it's run amok and overwritten
every partition and drive on the system.  In my experience
that would only happen if you (or someone) <EM>told</EM> it do
do this.  I've never seen Linux touch any part of a hard
drive unless it was "told" to do so.  (Unlike MS-DOS,
OS/2, and Windows which periodically trash the MBR when
they hang --- apparently scribbling register or random
memory contents over track zero, sector zero when those
zero's just happen to be in the the register during the
dying spasms of those systems).
</BLOCKQUOTE>
<BLOCKQUOTE>
There is virtually no chance that Linux touched your flash
BIOS --- so this is not a bug in your firmware.  I'd say
that this "zerofill" utility is highly suspect.  Obviously
Linux users just use the 'dd' command for this sort of
thing.
</BLOCKQUOTE>
<BLOCKQUOTE>
As for how to fix you problem.  You could try re-installing
System Commander.  I've never used it --- but it seems
that it can find most types of partitions during
installation --- so it should be able to find your NT and
Linux filesystems and install a new copy of it's boot loader
code to  start either of these systems.  I've never used
System Commander --- but it is commercial software --- so
it <EM>SHOULD</EM> come with some technical support.  Perhaps they
can walk you through the re-installation.
</BLOCKQUOTE>
<BLOCKQUOTE>
Keep in mind that LILO can still be installed on your MBR,
your superblock, or <EM>both</EM>, so it might still show up after
you have System Commander or NT's boot manager installed.
It should then only come up <EM>after</EM> you've selected an
option from your primary boot loader.  This can be a
bit confusing --- so you can reconfigure lilo to
bypass any prompts or delays when you're calling it
in this fashion.
</BLOCKQUOTE>
<BLOCKQUOTE>
Keep in mind that you can also find, download, and
install LOADLIN.EXE into a DOS directory somewhere on
your system.  You can use that instead of LILO (it's a
DOS program that loads linux kernels).  I've heard a
rumor that there is an NT native console application
(an NT .EXE that you'd run under a CMD.EXE shell) to
load Linux.  I've never seen it.
</BLOCKQUOTE>
<BLOCKQUOTE>
If you end up having to re-install Linux and NT (probably
unnecessary --- but it might be the easiest way) you
can configure Linux to boot from floppy and never touch the
boot records on your hard disk.  It's also possible to
configure Linux to use some other hard disk on your system
--- and not have it touch your primary drive at all.
</BLOCKQUOTE>
<BLOCKQUOTE>
Read through back issues of this column and go through the
various multi-boot HOWTO's and mini-HOWTO's at the LDP site
(<A HREF="http://metalab.unc.edu/LDP">http://metalab.unc.edu/LDP</A>) 
and it's mirrors.  There are many options.
</BLOCKQUOTE>

<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
C's from home and a nic card I know to install linux over the
network and see if that gets rif of it.
</STRONG></P>

<BLOCKQUOTE><IMG SRC="../../gx/dennis/bbub.gif" alt="(!)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
I don't get this at all.  How would you expect
installing Linux (over a network or otherwise) to <em>get
rid of</em> a Linux boot loader.
</BLOCKQUOTE>

<P><STRONG><IMG SRC="../../gx/dennis/qbub.gif" ALT="(?)"
	HEIGHT="28" WIDTH="50" BORDER="0"
	>
any help would be appreciated
<br>Brian Korsund
</STRONG></P>

<!-- sig -->

<!-- end 79 -->
<!--startcut ======================================================= -->
<P> <hr> <P>
<H5 align="center"><a href="http://www.linuxgazette.com/ssc.copying.html"
        >Copyright &copy;</a> 1999, James T. Dennis
<BR>Published in <I>The Linux Gazette</I> Issue 36 January 1999</H5>
<P> <hr> <P>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<P align="center">
<table width="98%"><tr valign="center" align="center">
<td rowspan="3" colspan="6"><A HREF="../lg_answer36.html"><IMG
        SRC="../../gx/dennis/answernew.gif"
        ALT="[ Answer Guy Index ]"></A></td>
  <TD><A HREF="./a.html">a</A></TD>
  <TD><A HREF="./b.html">b</A></TD>
  <TD><A HREF="./c.html">c</A></TD>
  <TD><A HREF="./1.html">1</A></TD>
  <TD><A HREF="./2.html">2</A></TD>

  <TD><A HREF="./3.html">3</A></TD>
  <TD><A HREF="./4.html">4</A></TD>
  <TD><A HREF="./5.html">5</A></TD>
  <TD><A HREF="./6.html">6</A></TD>
  <TD><A HREF="./7.html">7</A></TD>

  <TD><A HREF="./9.html">9</A></TD>
  <TD><A HREF="./10.html">10</A></TD>
  <TD><A HREF="./11.html">11</A></TD>
  <TD><A HREF="./12.html">12</A></TD>

</tr><tr valign="center" align="center">
  <TD><A HREF="./15.html">15</A></TD>
  <TD><A HREF="./16.html">16</A></TD>
  <TD><A HREF="./18.html">18</A></TD>
  <TD><A HREF="./19.html">19</A></TD>

  <TD><A HREF="./20.html">20</A></TD>
  <TD><A HREF="./21.html">21</A></TD>
  <TD><A HREF="./22.html">22</A></TD>
  <TD><A HREF="./23.html">23</A></TD>
  <TD><A HREF="./24.html">24</A></TD>

  <TD><A HREF="./25.html">25</A></TD>
  <TD><A HREF="./26.html">26</A></TD>
  <TD><A HREF="./27.html">27</A></TD>
  <TD><A HREF="./28.html">28</A></TD>

</tr><tr valign="center" align="center">
  <TD><A HREF="./29.html">29</A></TD>
  <TD><A HREF="./31.html">31</A></TD>
  <TD><A HREF="./32.html">32</A></TD>
  <TD><A HREF="./33.html">33</A></TD>
  <TD><A HREF="./34.html">34</A></TD>

  <TD><A HREF="./35.html">35</A></TD>
  <TD><A HREF="./36.html">36</A></TD>
  <TD><A HREF="./37.html">37</A></TD>
  <TD><A HREF="./38.html">38</A></TD>
  <TD><A HREF="./39.html">39</A></TD>

  <TD><A HREF="./40.html">40</A></TD>
  <TD><A HREF="./41.html">41</A></TD>
  <TD><A HREF="./42.html">42</A></TD>
  <TD><A HREF="./44.html">44</A></TD>

</tr><tr valign="center" align="center">
  <TD><A HREF="./45.html">45</A></TD>
  <TD><A HREF="./46.html">46</A></TD>
  <TD><A HREF="./47.html">47</A></TD>
  <TD><A HREF="./48.html">48</A></TD>
  <TD><A HREF="./49.html">49</A></TD>
  <TD><A HREF="./50.html">50</A></TD>

  <TD><A HREF="./51.html">51</A></TD>
  <TD><A HREF="./52.html">52</A></TD>
  <TD><A HREF="./53.html">53</A></TD>
  <TD><A HREF="./54.html">54</A></TD>
  <TD><A HREF="./55.html">55</A></TD>

  <TD><A HREF="./56.html">56</A></TD>
  <TD><A HREF="./57.html">57</A></TD>
  <TD><A HREF="./60.html">60</A></TD>
  <TD><A HREF="./61.html">61</A></TD>
  <TD><A HREF="./62.html">62</A></TD>

  <TD><A HREF="./63.html">63</A></TD>
  <TD><A HREF="./64.html">64</A></TD>
  <TD><A HREF="./65.html">65</A></TD>
  <TD><A HREF="./66.html">66</A></TD>

</tr><tr valign="center" align="center">
  <TD><A HREF="./67.html">67</A></TD>
  <TD><A HREF="./69.html">69</A></TD>
  <TD><A HREF="./72.html">72</A></TD>
  <TD><A HREF="./76.html">76</A></TD>
  <TD><A HREF="./77.html">77</A></TD>
  <TD><A HREF="./78.html">78</A></TD>

  <TD><A HREF="./79.html">79</A></TD>
  <TD><A HREF="./80.html">80</A></TD>
  <TD><A HREF="./81.html">81</A></TD>
  <TD><A HREF="./82.html">82</A></TD>
  <TD><A HREF="./84.html">84</A></TD>

  <TD><A HREF="./85.html">85</A></TD>
  <TD><A HREF="./86.html">86</A></TD>
  <TD><A HREF="./87.html">87</A></TD>
  <TD><A HREF="./91.html">91</A></TD>
  <TD><A HREF="./94.html">94</A></TD>

  <TD><A HREF="./95.html">95</A></TD>
  <TD><A HREF="./96.html">96</A></TD>
  <TD><A HREF="./97.html">97</A></TD>
  <TD><A HREF="./98.html">98</A></TD>
</tr></table>
	</P>
<P> <hr> <P>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
<A HREF="../lg_toc36.html"
        ><IMG SRC="../../gx/indexnew.gif" ALT="[ Table Of Contents ]"></A>
<A HREF="../../index.html"
        ><IMG SRC="../../gx/homenew.gif" ALT="[ Front Page ]"></A>
<A HREF="../lg_bytes36.html"
        ><IMG SRC="../../gx/back2.gif" ALT="[ Previous Section ]"></A>
<A HREF="../larriera.html"
        ><IMG SRC="../../gx/fwd.gif" ALT="[ Next Section ]"></A>
<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->
</BODY></HTML>
<!--endcut ========================================================= -->