slave drive mbr or gpt ?

[Det. Dave Starsky]

Ive been having issues with my ssd and sometimes cant boot into windows..

I swapped it out for an old mechanical hdd which couldnt boot to windows, instead of installing windows I decided to change back to the ssd..
Im now at windows but, my slave drive is 'Not Initialised' within disk manager..

"You must initialise a disk before logical disk manager can access it
use the following partition style for the selected disk
MBR (Master Boot Record)
GPT (GUID Partition Table)"

Which do I use to display the drive as a slave

When my bios didnt recognise the ssd I chose to use default settings and tried other settings on the bios hoping it would read the ssd, could this have caused the slave to need initialised ?

Thanks for any help...

[Cathulhu]

1. MBR can only manage up to 2TB of space on one drive. GPT can manage several exabyte, which is about a trillion Gigabytes. Admittedly, only of limited use for the home user.
2. GPT is more resilient by having multiple copies of the file tables. If one copy is corrupted, another is used instead.
3. GPT stores CRC values and can check almost instantly if a file is corrupted or not. MBR does not have such a feature.

[Kaldaien]

vadim lähetti viestin:

Cathulhu lähetti viestin:

Nonsense. While GPT can handle larger partitions than MBT it has quite a few other advantages over MBT that makes it superior in pretty much any way, with the exception of legacy OS reasons.

What advantages? Only real, please. Not like ability to create hundred partitions.

For one thing, it supports what amounts to metadata about each partition. The system health of a volume can be stored as user-defined attributes in the GPT to assist w/ system recovery and deciding when to do a thorough filesystem check.

[vadim]

Cathulhu lähetti viestin:

1. MBR can only manage up to 2TB of space on one drive. GPT can manage several exabyte, which is about a trillion Gigabytes. Admittedly, only of limited use for the home user.
2. GPT is more resilient by having multiple copies of the file tables. If one copy is corrupted, another is used instead.
3. GPT stores CRC values and can check almost instantly if a file is corrupted or not. MBR does not have such a feature.

Except first one the others points make no sense. Sorry. Artition table has nothing to do with the fileststem.

[Cathulhu]

And where else should a system look up where exactly a file is saved on a disc?

[vadim]

Cathulhu lähetti viestin:

And where else should a system look up where exactly a file is saved on a disc?

Partition table contains partition data only. It doesn't know anything about files. When you created partition you need to create filesystem within this partition. Any partition (GPT, MBR, BSD partition table, MINIX subpartitions, UNIXWARE slices, Solaris partitions and so on) can contain any filesystem.
For instance, you can create GPT partition with ancient FAT16 filesystem (more than that, you NEED to do that to make device bootable) and you can create modern fault-tolerance filesystem in the MBR partition.