Re: Debian images and USB sticks

I executed "hexdump -n 512 /dev/sdX", the command you sent didn't work:

0000000 b8fa 1000 d08e 00bc b8b0 0000 d88e c08e
0000010 befb 7c00 00bf b906 0200 a4f3 21ea 0006
0000020 be00 07be 0438 0b75 c683 8110 fefe 7507
0000030 ebf3 b416 b002 bb01 7c00 80b2 748a 8b01
0000040 024c 13cd 00ea 007c eb00 00fe 0000 0000
0000050 0000 0000 0000 0000 0000 0000 0000 0000
*
00001b0 0000 0000 0000 0000 a536 0006 0000 2080
00001c0 0021 350b 0570 0800 0000 0000 0040 3500
00001d0 0571 fe0b ffff 0800 0040 9800 0363 0000
00001e0 0000 0000 0000 0000 0000 0000 0000 0000
00001f0 0000 0000 0000 0000 0000 0000 0000 aa55
0000200

On 3 May 2016 at 10:00, Thomas Schmitt <scdbackup@gmx.net> wrote:

Hi,

Renato Bispo wrote:
> -> I partitioned my USB stick using gparted, setting the boot flag on the
> partition I wanted to put the image.

Now i wonder whether the stick already contained MBR code which
would jump on the marked partition or whether gparted installed such
x86 machine code.

See
https://en.wikipedia.org/wiki/Master_boot_record#System_bootstrapping
The third paragraph seems to describe what you experience. A small program
which looks for the bootable/active flag and executes the code at the
start of that partition.

> (I think it's relevant to say that I
> tried to do the partitioning and formatting of the stick using fdisk and
> mkfs.fat, having the same result in the end of the process, according to
> gparted, meaning everything there looked the same, but I couldn't boot from
> the stick doing it that way, I would get stuck in the black screen with the
> blinking cursor.)

Looks like gparted installed the code. But i cannot find hints in the web.

Please show the first 512 bytes of the working stick:

dd if=/dev/sdX bs=512 count=1 | od od -t x1

Have a nice day :)

Thomas

Renato Bispo