Go Back   { mindfrost82.com } > Gadget Corner > Tech Newsgroups > Linux > Slackware

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-16-2008, 07:52 AM
AnticitizenOne
 
Posts: n/a
dd on MBR strange behavior

Hi,
I've made a copy of the MBR between two machines.
Obviously the system crash but the strange behavior is that
tehorically I've broken the partition table with this operation
The operations I've committed are
# dd if=/dev/sda of=/tmp/boot.img bs=512 count=1
and then
# dd if=/mnt/tmp/boot.img of=/dev/sda bs=512 count=1

I think in the first 512 bytes of the disk there was the boot loader
or the address of the bootloader.
Why I've broken also the partition table?

Thanks
Gio
Reply With Quote
  #2 (permalink)  
Old 07-16-2008, 08:29 AM
Kees Theunissen
 
Posts: n/a
Re: dd on MBR strange behavior

AnticitizenOne wrote:
> Hi,
> I've made a copy of the MBR between two machines.
> Obviously the system crash but the strange behavior is that
> tehorically I've broken the partition table with this operation
> The operations I've committed are
> # dd if=/dev/sda of=/tmp/boot.img bs=512 count=1
> and then
> # dd if=/mnt/tmp/boot.img of=/dev/sda bs=512 count=1
>
> I think in the first 512 bytes of the disk there was the boot loader
> or the address of the bootloader.
> Why I've broken also the partition table?


Because the partition table is also located in the first sector
(a.k.a MBR) of the disk.

The first 446 byte of the MBR contain the bootstrap code.
The next 64 bytes contain the partition table (actually only
the entries for the four primary partitions you can have).
The last two bytes of the MBR contain a "magic number"
indicating an initialized boot sector.

Regards,

Kees.

--
Kees Theunissen.
Reply With Quote
  #3 (permalink)  
Old 07-16-2008, 08:48 AM
AnticitizenOne
 
Posts: n/a
Re: dd on MBR strange behavior

On 16 Lug, 10:29, Kees Theunissen <theun...@rijnh.nl> wrote:
> AnticitizenOne wrote:
> > Hi,
> > I've made a copy of the MBR between two machines.
> > Obviously the system crash but the strange behavior is that
> > tehorically I've broken the partition table with this operation
> > The operations I've committed are
> > # dd if=/dev/sda of=/tmp/boot.img bs=512 count=1
> > and then
> > # dd if=/mnt/tmp/boot.img of=/dev/sda bs=512 count=1

>
> > I think in the first 512 bytes of the disk there was the boot loader
> > or the address of the bootloader.
> > Why I've broken also the partition table?

>
> Because the partition table is also located in the first sector
> (a.k.a MBR) of the disk.
>
> The first 446 byte of the MBR contain the bootstrap code.
> The next 64 bytes contain the partition table (actually only
> the entries for the four primary partitions you can have).
> The last two bytes of the MBR contain a "magic number"
> indicating an initialized boot sector.
>
> Regards,
>
> Kees.
>
> --
> Kees Theunissen.


thanks a lot!
I committed a stupid error :-)
Really don't know why, I think the pt was located after the MBR. Doh!
Reply With Quote
Reply

  { mindfrost82.com } > Gadget Corner > Tech Newsgroups > Linux > Slackware


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are Off
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT. The time now is 05:43 PM.


Powered by vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.1.0 ©2007, Crawlability, Inc.
© 1999-2008 mindfrost82.com v11.0

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