Mailinglist Archive: opensuse (3261 mails)

< Previous Next >
[SLE] LILO and NT
  • From: Oliver Ob <ob_ok@xxxxxxx>
  • Date: Sat, 07 Apr 2001 21:24:24 +0200
  • Message-id: <3ACF6968.F98265C1@xxxxxxx>
Forgot two details, added them now.
===================================


This is for some interesting challenge:

I have some leasing-notebook from my company, on which NT4 is installed
and I was not given any installation disk/cd nor manual.

This is why I have to copy that whole EXISTING NT partition using...

dd if=/dev/hda of=/data/nt4.img

My problem at this time is that both the old NT4 and the new NT4
partition
have to be precisely the same size (AFAIRC), which I have yet to
encounter...

As I have noticed now, the partitions (source and target) have not
exactly the same size, they are as follows (according to fdisk):

NTFS partition: 2096451 blocks (source partition)
NTFS partition: 2104483 blocks (target partition)

So the target is a little larger than the original.

Do I have to resize the target to fit to the original or is that not a
problem?

Now, that I have come this far, do I need to use the Blocksize (bs) and
Count Parameters when I want to copy THE WHOLE partition to an image
file?

Can I not simply skip these values?

Otherwise, to my humble knowledge, I shall go through this - hopefully
correct - way of calculation:

Units according to fdisk on the nr4 harddisk:
Units = cylinders of x * y bytes (y is typically 512 bytes large)

bs equals x, that's for sure, but what about count? Or what about
Bcount?
That what value should I set that one?
*Just in case I need this calculation*

Am I right in that this way the Partition Boot Record (NOT the mbr!) is
copied as well? (Need it for NT4 boot.)

Any friendly help appreciated - excuse my english, thanks ahead.

--
*º¤., ¸¸,.¤º*¨¨¨*¤Oliver@home*º¤., ¸¸,.¤º*¨¨*¤

--
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to
suse-linux-e-help@xxxxxxxx
Also check the FAQ at http://www.suse.com/support/faq

< Previous Next >
This Thread
  • No further messages