SpinRite 6 “MBR Followed by EFI” Error
When I run SpinRite 6 on my Windows computer with a 3TB drive, it displays a red MBR Followed by EFI
error next to the drive, with a message saying it should not be run unless the MBR is "fixed." What is the cause of this error and how do I fix it?
data-recovery spinrite
add a comment |
When I run SpinRite 6 on my Windows computer with a 3TB drive, it displays a red MBR Followed by EFI
error next to the drive, with a message saying it should not be run unless the MBR is "fixed." What is the cause of this error and how do I fix it?
data-recovery spinrite
add a comment |
When I run SpinRite 6 on my Windows computer with a 3TB drive, it displays a red MBR Followed by EFI
error next to the drive, with a message saying it should not be run unless the MBR is "fixed." What is the cause of this error and how do I fix it?
data-recovery spinrite
When I run SpinRite 6 on my Windows computer with a 3TB drive, it displays a red MBR Followed by EFI
error next to the drive, with a message saying it should not be run unless the MBR is "fixed." What is the cause of this error and how do I fix it?
data-recovery spinrite
data-recovery spinrite
edited Aug 3 '16 at 18:37
Kaypro II
asked Aug 2 '16 at 17:48
Kaypro IIKaypro II
79451229
79451229
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I got the following response from SpinRite support:
The current version of SpinRite, v6.0, was finished in 2004 before the era of GPT partitions, so it is completely unaware of that style of hard drive formatting. Consequently, SpinRite v6.0 can handle MBR-formatted drives up to 2.2 terabytes, but not GPT-formatted drives of ANY size.
GPT (GUID partition tables) are only required for drives larger than 2.2 terabytes because MBR format partition tables are limited by their 32-bit fields for specifying the partition size and starting location. 32-bits == 4,294967,296 and if you have that many 512-byte sectors, you wind up with 2,199,023,255,552 bytes ... or 2.2 terabytes.
Though this doesn't help you now, support for GPT-format partitions is one of the major features of the next release (v6.1) of SpinRite -- which all existing v6.0 owners will be able to upgrade to at no cost.
However, there is no time line on the next version of SpinRite.
Thank you for your cooperation, time and patience.
So, it does not look like the current version of SpinRite supports modern, large capacity drives.
1
Thanks for reporting this. 6.1 seems close today, as the author tells in his regular podcast, but still no fixed timeline.
– Marcel
Feb 2 '18 at 7:17
add a comment |
protected by Community♦ Jan 17 at 20:27
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I got the following response from SpinRite support:
The current version of SpinRite, v6.0, was finished in 2004 before the era of GPT partitions, so it is completely unaware of that style of hard drive formatting. Consequently, SpinRite v6.0 can handle MBR-formatted drives up to 2.2 terabytes, but not GPT-formatted drives of ANY size.
GPT (GUID partition tables) are only required for drives larger than 2.2 terabytes because MBR format partition tables are limited by their 32-bit fields for specifying the partition size and starting location. 32-bits == 4,294967,296 and if you have that many 512-byte sectors, you wind up with 2,199,023,255,552 bytes ... or 2.2 terabytes.
Though this doesn't help you now, support for GPT-format partitions is one of the major features of the next release (v6.1) of SpinRite -- which all existing v6.0 owners will be able to upgrade to at no cost.
However, there is no time line on the next version of SpinRite.
Thank you for your cooperation, time and patience.
So, it does not look like the current version of SpinRite supports modern, large capacity drives.
1
Thanks for reporting this. 6.1 seems close today, as the author tells in his regular podcast, but still no fixed timeline.
– Marcel
Feb 2 '18 at 7:17
add a comment |
I got the following response from SpinRite support:
The current version of SpinRite, v6.0, was finished in 2004 before the era of GPT partitions, so it is completely unaware of that style of hard drive formatting. Consequently, SpinRite v6.0 can handle MBR-formatted drives up to 2.2 terabytes, but not GPT-formatted drives of ANY size.
GPT (GUID partition tables) are only required for drives larger than 2.2 terabytes because MBR format partition tables are limited by their 32-bit fields for specifying the partition size and starting location. 32-bits == 4,294967,296 and if you have that many 512-byte sectors, you wind up with 2,199,023,255,552 bytes ... or 2.2 terabytes.
Though this doesn't help you now, support for GPT-format partitions is one of the major features of the next release (v6.1) of SpinRite -- which all existing v6.0 owners will be able to upgrade to at no cost.
However, there is no time line on the next version of SpinRite.
Thank you for your cooperation, time and patience.
So, it does not look like the current version of SpinRite supports modern, large capacity drives.
1
Thanks for reporting this. 6.1 seems close today, as the author tells in his regular podcast, but still no fixed timeline.
– Marcel
Feb 2 '18 at 7:17
add a comment |
I got the following response from SpinRite support:
The current version of SpinRite, v6.0, was finished in 2004 before the era of GPT partitions, so it is completely unaware of that style of hard drive formatting. Consequently, SpinRite v6.0 can handle MBR-formatted drives up to 2.2 terabytes, but not GPT-formatted drives of ANY size.
GPT (GUID partition tables) are only required for drives larger than 2.2 terabytes because MBR format partition tables are limited by their 32-bit fields for specifying the partition size and starting location. 32-bits == 4,294967,296 and if you have that many 512-byte sectors, you wind up with 2,199,023,255,552 bytes ... or 2.2 terabytes.
Though this doesn't help you now, support for GPT-format partitions is one of the major features of the next release (v6.1) of SpinRite -- which all existing v6.0 owners will be able to upgrade to at no cost.
However, there is no time line on the next version of SpinRite.
Thank you for your cooperation, time and patience.
So, it does not look like the current version of SpinRite supports modern, large capacity drives.
I got the following response from SpinRite support:
The current version of SpinRite, v6.0, was finished in 2004 before the era of GPT partitions, so it is completely unaware of that style of hard drive formatting. Consequently, SpinRite v6.0 can handle MBR-formatted drives up to 2.2 terabytes, but not GPT-formatted drives of ANY size.
GPT (GUID partition tables) are only required for drives larger than 2.2 terabytes because MBR format partition tables are limited by their 32-bit fields for specifying the partition size and starting location. 32-bits == 4,294967,296 and if you have that many 512-byte sectors, you wind up with 2,199,023,255,552 bytes ... or 2.2 terabytes.
Though this doesn't help you now, support for GPT-format partitions is one of the major features of the next release (v6.1) of SpinRite -- which all existing v6.0 owners will be able to upgrade to at no cost.
However, there is no time line on the next version of SpinRite.
Thank you for your cooperation, time and patience.
So, it does not look like the current version of SpinRite supports modern, large capacity drives.
edited Aug 17 '16 at 15:59
answered Aug 2 '16 at 17:48
Kaypro IIKaypro II
79451229
79451229
1
Thanks for reporting this. 6.1 seems close today, as the author tells in his regular podcast, but still no fixed timeline.
– Marcel
Feb 2 '18 at 7:17
add a comment |
1
Thanks for reporting this. 6.1 seems close today, as the author tells in his regular podcast, but still no fixed timeline.
– Marcel
Feb 2 '18 at 7:17
1
1
Thanks for reporting this. 6.1 seems close today, as the author tells in his regular podcast, but still no fixed timeline.
– Marcel
Feb 2 '18 at 7:17
Thanks for reporting this. 6.1 seems close today, as the author tells in his regular podcast, but still no fixed timeline.
– Marcel
Feb 2 '18 at 7:17
add a comment |
protected by Community♦ Jan 17 at 20:27
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?