On 06/30/2015 04:36 PM, Chris Murphy wrote:
On Tue, Jun 30, 2015 at 4:32 PM, jd1008 <jd1008@xxxxxxxxx> wrote:
Here is what happened after the 2 bytes at offset 511 and 512 were null'ed:
fdisk /dev/sdb
Welcome to fdisk (util-linux 2.24.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x2c945747.
Command (m for help): p
Disk /dev/sdb: 1.8 TiB, 2000398933504 bytes, 3907029167 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: dos
Disk identifier: 0x2c945747
So, you see, those 2 bytes must have also been encoded to contain
something about the partitions.
So, with this kind of change, it destroys the partition table.
It invalidates it not destroys it. If you restore the signature, the
partition table is valid again and will work.
You really shouldn't use dd for these sorts of things, it's dangerous.
This is what wipefs is for. It also has a backup facility that makes
it easy to reverse mistakes.
http://man7.org/linux/man-pages/man8/wipefs.8.html
So, it begs the question:
Can I create a disk with msdos partitioning scheme,
none of the partitions marked as bootable, and have bios
quickly skip over it to the next device in the boot sequence?
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
