In Unix/Linux by definition "everything is a file", including your device.
If you prefer, you have to open /dev/sdc , as long as Bless can
http//
open block devices you can also open your stick with it.
If - for any reason - the particular build of Bless/your environment/whatever has not device access, just dump the first few sectors of the device to a file with dd and use Bless on the resulting file.
Or, get a hex viewer editor that surely has device access, like (example)
http//
jaclaz
Ok, finally I got a hex view of the file. I would like to upload an screenshot here. Is there a way to do it?
The 0 offset is FA, then B8, etc.
Testing the following screenshot
Link does not work
Ok, finally I got a hex view of the file. I would like to upload an screenshot here. Is there a way to do it?
The 0 offset is FA, then B8, etc.
For a partition table - if there is one - offset 0x1be is where it gets interesting
@MichaelStein
Go back to the links given in previous post.
Take as an example this page
http//
ir this one
http//
which represent MBR's.
Look at the area which is coloured in light pink at the end of the sector, that is the Partition Table, followed by Magic Bytes 55AA.
IF (or WHEN) you will have a partition table to check, you might find of interest this little spreadsheet of mine
http//
http//
jaclaz
Sorry, let's try this link
http//
This a MBR, with a partition table
The critrical value is 0xee which indicates that there is an EFI structure. To decode you will need to look in the next few sectors
http//
http//
The above links gives common partition ID values. Although these are correct 99% of the time, the only true indicator is the volume header record
NB Hex dumps are MUCH easier to read with a width of 0x10
@mscotgrove
No. (
You were tricked by the absurd view width of 27 bytes 😯
That data is a "normal" partition on a disk with signature 6BB07A04, FAT32 CHS mapped, non active, with CHS 0/34/27-923/73/46 LBA 2168/31281032.
No matter how "queer" is the start CHS of 0/34/27 it does correspond to LBA 2168.
The end CHS is not correspondent however to LBA 31281032, a "good" formatting program would set the end CHS to 1023/254/63, as a matter of fact the LBA 31281032 corresponds to 1947/73/46, two out of three is not that bad wink and since 1947-923=1024, it is is easy to understand how the *whatever* program that created that partition entry "wrapped around" the 1024 Cylinder limit.
It is anyway very strange that the partition id is set to 0B instead of 0C.
A program - if trusting the CHS data - might "choke" on that stick.
jaclaz