It's hard to say what the issue really is, Apple's firmware is finicky. So I assume you got the Windows 7 DVD booted, and it repaired the Windows volume, and you can now boot Windows?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
How to recover Bootcamp NTFS Partition?
- Thread starter PerceptorC5
- Start date
- Sort by reaction score
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Windows 7 now able to boot w/o Seagate drive connected
Actually, I didn't use the Windows CD at all and I don't think anything was repaired. I did subsequent tests w/o Windows CD and can recreate the problem at will, by simply reconnecting the Seagate drive.
Here's some additional info: The Seagate was partitioned into 4 volumes/partitions. All 4 partitions were to be used for backup as follows:
The 1st volume was to clone the Bootcamp (Windows) partition using CCC
The 2nd volume was for Mac OS Time Machine - to backup the Mac HD
The 3rd volume was to clone the WD external drive using CCC
The 4th volume was to clone the Mac HD (kinda extra insurance) using CCC
So, I still can't narrow down the problem yet, whether a Bootcamp, Seagate or Windows problem. So, I connected my Seagate to another PC (my Windows 7 multi-media PC). The Windows 7 PC booted up with no problems, although it seemed like the boot process took longer than usual (but maybe I'm spending too much time rebooting). Granted, Windows 7 didn't recognize the Seagate external drive, as expected, since they were all Mac OS NFS partitions. Then I renamed the 1st volume/partition, since the name of that partition was "BOOTCAMP Backup". Granted, it was a long-shot.
As always, I'm open to other suggested test scenarios. Thanks again.
It's hard to say what the issue really is, Apple's firmware is finicky. So I assume you got the Windows 7 DVD booted, and it repaired the Windows volume, and you can now boot Windows?
Actually, I didn't use the Windows CD at all and I don't think anything was repaired. I did subsequent tests w/o Windows CD and can recreate the problem at will, by simply reconnecting the Seagate drive.
Here's some additional info: The Seagate was partitioned into 4 volumes/partitions. All 4 partitions were to be used for backup as follows:
The 1st volume was to clone the Bootcamp (Windows) partition using CCC
The 2nd volume was for Mac OS Time Machine - to backup the Mac HD
The 3rd volume was to clone the WD external drive using CCC
The 4th volume was to clone the Mac HD (kinda extra insurance) using CCC
So, I still can't narrow down the problem yet, whether a Bootcamp, Seagate or Windows problem. So, I connected my Seagate to another PC (my Windows 7 multi-media PC). The Windows 7 PC booted up with no problems, although it seemed like the boot process took longer than usual (but maybe I'm spending too much time rebooting). Granted, Windows 7 didn't recognize the Seagate external drive, as expected, since they were all Mac OS NFS partitions. Then I renamed the 1st volume/partition, since the name of that partition was "BOOTCAMP Backup". Granted, it was a long-shot.
As always, I'm open to other suggested test scenarios. Thanks again.
can recreate the problem at will, by simply reconnecting the Seagate drive.
Find the disk identifier by typing:
Code:
diskutil listThis lists all disks and their partitions, find the one for the 3TB Seagate. Then type:
Code:
sudo dd if=/dev/rdisk[B][U]X[/U][/B] count=1 2>/dev/null | hexdump -CX=the number for the Seagate 3TB drive you found with diskutil list.
This command reads the first sector, and filters it through hexdump. Post the result, highlight the pasted text, then click the # button in the forum toolbar so that the pasted text is wrapped with code tags for proper formatting.
Last edited:
Here are the results from the diskutil list. Seagate is disk3.
However, when I entered the dd command, I got an error message, indicating unknown operand. I checked the manpage for dd, but I couldn't figure it out what to do, I think you are attempting to dump the 1st 2 sectors. If I entered the syntax incorrectly, let me know that as well. thanks.
Code:
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *750.2 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS JR Mac HD 374.0 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
4: Microsoft Basic Data BOOTCAMP 375.3 GB disk0s4
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.5 TB disk1
1: EFI 209.7 MB disk1s1
2: Apple_HFS WD JR BlackBook 1.5 TB disk1s2
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: CD_partition_scheme *804.4 MB disk2
1: Apple_partition_scheme 700.4 MB disk2s0
2: Apple_partition_map 32.3 KB disk2s0s1
3: Apple_HFS WD SmartWare 160.8 MB disk2s0s2
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *3.0 TB disk3
1: EFI 209.7 MB disk3s1
2: Apple_HFS BC clone 150.0 GB disk3s2
3: Apple_HFS JR MacHD TM 700.0 GB disk3s3
4: Apple_HFS WD JR BB Clone 1.7 TB disk3s4
5: Apple_HFS JR MacHD Clone 499.3 GB disk3s5However, when I entered the dd command, I got an error message, indicating unknown operand. I checked the manpage for dd, but I couldn't figure it out what to do, I think you are attempting to dump the 1st 2 sectors. If I entered the syntax incorrectly, let me know that as well. thanks.
Code:
sudo dd if=/dev/rdisk3 count=1 2 >/dev/null | hexdump -C
dd: unknown operand 2Code:sudo dd if=/dev/rdisk3 count=1 2 >/dev/null | hexdump -C dd: unknown operand 2
You have a space after the 2, and there shouldn't be one.
You have a space after the 2, and there shouldn't be one.
Sorry about that, you were redirecting std err, yes?
I finally entered the command correctly; however, I get nothing displayed. To double-check whether I entered the syntax correctly, I tried disk2, same thing. Then I tried disk0 and disk1, I got information displayed.
So, what does this mean? Thanks.
Just cleans up excess before being run through hexdump.Sorry about that, you were redirecting std err, yes?
I finally entered the command correctly; however, I get nothing displayed.
You should get at least something like this:
Code:
mingisapsycho:~ chris$ sudo dd if=/dev/rdisk0 count=1 2>/dev/null | hexdump -C
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fe |................|
000001c0 ff ff ee fe ff ff 01 00 00 00 af 32 cf 1d 00 00 |...........2....|
000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200I get a Hex/ASCII dump only from disk0 and disk1, but nothing from disk2 and disk3.
Please keep in mind that this was Seagate already formatted for Windows and I ended up reformatting/repartitioning for Mac OS with the 4 partitions as mentioned earlier, so I don't know what that means in terms of MBR. I've done this before with 2 WD HDs (reformatting external drives for Mac OS), so I didn't see this as a problem w/Seagate HD.
Please keep in mind that this was Seagate already formatted for Windows and I ended up reformatting/repartitioning for Mac OS with the 4 partitions as mentioned earlier, so I don't know what that means in terms of MBR. I've done this before with 2 WD HDs (reformatting external drives for Mac OS), so I didn't see this as a problem w/Seagate HD.
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: CD_partition_scheme *804.4 MB disk2
1: Apple_partition_scheme 700.4 MB disk2s0
2: Apple_partition_map 32.3 KB disk2s0s1
disk2 uses an APM partition map, so I don't expect a result from it. But it's curious there's nothing from disk3, as it's GPT and should have a PMBR in the first sector. What do you get for:
Code:
sudo gpt -r -v show /dev/disk3and
Code:
sudo dd if=/dev/rdisk3 count=2 2>/dev/null | hexdump -CI checked the manpage for dd, but I couldn't figure it out what to do, I think you are attempting to dump the 1st 2 sectors.
I was looking for evidence of code in the first 440 bytes of the first sector, which is the MBR bootstrap code region. This is used by BIOS as a first stage boot loader. Apple's CSM-BIOS is only going to use one. But it's clear it doesn't have such code, but it's confusing it also doesn't have a protective MBR which also should be in the first sector. So now I'm wondering what's in the 2nd sector.
This could be some obscure Apple firmware bug actually, is what I'm chasing after. And there might be a work around.
Here's the gpt results:
Here's the hex dump
Ignore the hex dump - that was accidentally disk0. For disk3, I got nothing again.
Code:
gpt show: /dev/disk3: mediasize=3000592977920; sectorsize=4096; blocks=732566645
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 4 Pri GPT table
6 51200 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
51206 36621096 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
36672302 32768
36705070 170898440 3 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
207603510 32768
207636278 402976808 4 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
610613086 32768
610645854 121888018 5 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
732533872 32768
732566640 4 Sec GPT table
732566644 1 Sec GPT headerHere's the hex dump
Ignore the hex dump - that was accidentally disk0. For disk3, I got nothing again.
Last edited:
For disk3, I got nothing again.
Hmm I wonder if it's because it's an AF disk. Try this, disk3 instead of rdisk3:
Code:
sudo dd if=/dev/disk3 count=1 2>/dev/null | hexdump -C
Code:
sudo dd if=/dev/disk3 bs=4096 count=1 2>/dev/null | hexdump -Csudo dd if=/dev/disk3 count=1 2>/dev/null | hexdump -C
Some results this time . . .
Code:
sudo dd if=/dev/disk3 count=1 2>/dev/null | hexdump -C
Password:
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fe |................|
000001c0 ff ff ee fe ff ff 01 00 00 00 74 14 aa 2b 00 00 |..........t..+..|
000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200The following results with count=2
Code:
sudo dd if=/dev/disk3 count=2 2>/dev/null | hexdump -C
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fe |................|
000001c0 ff ff ee fe ff ff 01 00 00 00 74 14 aa 2b 00 00 |..........t..+..|
000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200 00 00 00 00 00 00 00 d0 79 11 49 b5 fc 07 00 10 |........y.I.....|
00000210 4b 01 ae 78 ff 7f 00 00 8c 07 40 00 00 00 00 00 |K..x......@.....|
00000220 0f 41 70 70 6c 65 5f 45 6e 63 72 79 70 74 65 64 |.Apple_Encrypted|
00000230 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000240 00 00 00 00 00 00 00 d0 0a 10 49 b5 fc 07 00 c0 |..........I.....|
00000250 04 00 ae 78 ff 7f 00 00 8c 07 40 00 00 00 00 00 |...x......@.....|
00000260 0f 41 70 70 6c 65 5f 42 6f 6f 74 5f 52 61 69 64 |.Apple_Boot_Raid|
00000270 00 00 00 00 00 00 00 00 00 00 00 00 00 00 28 00 |..............(.|
00000280 d8 7a ae 78 ff 7f 00 00 8c 07 40 00 00 00 00 00 |.z.x......@.....|
00000290 09 41 70 70 6c 65 5f 44 4d 47 00 00 00 00 00 00 |.Apple_DMG......|
000002a0 be 11 49 b5 fc 07 00 50 f4 0c 49 b5 fc 07 00 a0 |..I....P..I.....|
000002b0 32 01 70 70 6c 65 5f 46 72 65 65 00 00 00 00 00 |2.pple_Free.....|
000002c0 00 00 00 00 00 00 00 d0 e2 0c 49 b5 fc 07 00 b0 |..........I.....|
000002d0 02 00 70 70 6c 65 5f 4a 6f 75 72 6e 61 6c 04 00 |..pple_Journal..|
000002e0 d8 7a ae 78 ff 7f 00 00 8c 07 40 00 00 00 00 00 |.z.x......@.....|
000002f0 12 41 70 70 6c 65 5f 52 41 49 44 5f 4f 66 66 6c |.Apple_RAID_Offl|
00000300 69 6e 65 00 00 00 00 00 00 00 00 00 00 00 00 00 |ine.............|
00000310 00 00 00 00 00 00 00 d0 30 12 49 b5 fc 07 00 d0 |........0.I.....|
00000320 53 00 70 70 6c 65 5f 53 63 72 61 74 63 68 02 00 |S.pple_Scratch..|
00000330 d8 7a ae 78 ff 7f 00 00 8c 07 40 00 00 00 00 00 |.z.x......@.....|
00000340 09 41 70 70 6c 65 5f 55 46 53 00 00 00 00 00 00 |.Apple_UFS......|
00000350 00 00 00 00 00 00 00 d0 00 00 00 00 00 00 00 d0 |................|
00000360 09 00 ae 78 ff 7f 00 00 8c 07 40 00 00 00 00 00 |...x......@.....|
00000370 0a 41 70 70 6c 65 5f 48 46 53 58 00 00 00 03 00 |.Apple_HFSX.....|
00000380 d8 7a ae 78 ff 7f 00 00 8c 07 40 00 00 00 00 00 |.z.x......@.....|
00000390 09 41 70 70 6c 65 5f 49 53 4f 00 00 00 00 05 00 |.Apple_ISO......|
000003a0 d8 7a ae 78 ff 7f 00 00 8c 07 40 00 00 00 00 00 |.z.x......@.....|
000003b0 09 41 70 70 6c 65 5f 4b 46 53 00 00 00 00 07 00 |.Apple_KFS......|
000003c0 d8 7a ae 78 ff 7f 00 00 8c 07 40 00 00 00 00 00 |.z.x......@.....|
000003d0 0c 41 70 70 6c 65 5f 50 72 6f 44 4f 53 00 0d 00 |.Apple_ProDOS...|
000003e0 d8 7a ae 78 ff 7f 00 00 8c 07 40 00 00 00 00 00 |.z.x......@.....|
000003f0 0c 46 72 65 65 42 53 44 20 55 46 53 32 00 0f 00 |.FreeBSD UFS2...|
00000400Some results this time . . .
OK there's no boot loader code in LBA 0 and the PMBR is intact. But I am really confused by the GPT header from this hexdump, compared to what the gpt command is showing. The gpt command is showing five partitions (EFI System Partition is hidden so to you it seems like four partitions), but the hexdump from disk3 show a bogus GPT header. This is really weird. You haven't rebooted have you? The number of each disk can easily change between reboots, or when you disconnect/reconnect devices. What was disk3 before won't necessarily be disk3 next time.
Can you download and install GPT fdisk, and type this command:
sudo gdisk -l /dev/diskX
Use diskutil list to make sure you get the X value right for this 3TB Seagate.
No, I haven't rebooted and have double-checked as well. Here are the results (I've already downloaded gdisk the other day).
Code:
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *3.0 TB disk3
1: EFI 209.7 MB disk3s1
2: Apple_HFS BC clone 150.0 GB disk3s2
3: Apple_HFS JR MacHD TM 700.0 GB disk3s3
4: Apple_HFS WD JR BB Clone 1.7 TB disk3s4
5: Apple_HFS JR MacHD Clone 499.3 GB disk3s5
Giacomos-MacMini:~ giacomoraucci$ sudo gdisk -l /dev/disk3
Password:
GPT fdisk (gdisk) version 0.8.6
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/disk3: 732566645 sectors, 2.7 TiB
Logical sector size: 4096 bytes
Disk identifier (GUID): 36E5B7FA-382E-4BA0-9CD1-6F22A61F1BE3
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 732566639
Partitions will be aligned on 8-sector boundaries
Total free space is 131072 sectors (512.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 6 51205 200.0 MiB EF00 EFI System Partition
2 51206 36672301 139.7 GiB AF00 BootCamp backup
3 36705070 207603509 651.9 GiB AF00 JR MacHD TM
4 207636278 610613085 1.5 TiB AF00 WD JR BB Clone
5 610645854 732533871 465.0 GiB AF00 JR MacHD Clone
Last edited:
Logical sector size: 4096 bytes
Wow, I wonder if that's for real or a bug. What is the model of this disk according to:
Code:
diskutil info /dev/disk3Did you repartition this drive with Disk Utility? How? Did you click on the drive, go to the Partition tab, and change the number of partitions from Current to 4 partitions?
What is the model of this disk
Code:
diskutil info /dev/disk3
Device Identifier: disk3
Device Node: /dev/disk3
Part of Whole: disk3
Device / Media Name: Seagate Backup+ Desk Media
Volume Name: Not applicable (no file system)
Mounted: Not applicable (no file system)
File System: None
Content (IOContent): GUID_partition_scheme
OS Can Be Installed: No
Media Type: Generic
Protocol: USB
SMART Status: Not Supported
Total Size: 3.0 TB (3000592977920 Bytes) (exactly 5860533160 512-Byte-Blocks)
Volume Free Space: Not applicable (no file system)
Device Block Size: 4096 Bytes
Read-Only Media: No
Read-Only Volume: Not applicable (no file system)
Ejectable: Yes
Whole: Yes
Internal: No
OS 9 Drivers: No
Low Level Format: Not supportedDid you repartition this drive with Disk Utility? How? Did you click on the drive, go to the Partition tab, and change the number of partitions from Current to 4 partitions?
Yes, I used Mac OS Disk Utility. And, yes, I changed current to 4 partitions. If I remember the current partition was FAT32 (but I'm not 100% sure on the fAT32).
Code:Device Block Size: 4096 Bytes
I'm going to go out on a limb and propose the hang you're getting with this drive attached is an Apple firmware bug, specifically with the CSM-BIOS, due to both logical and physical sector being 4096 bytes. That's a new event in computing. In fact this is the first drive I've heard of shipping with 4096 logical sectors.
Since the invention of the hard drive, physical sectors on the drive have been 512 bytes. Each sector has an address number. When BIOS starts up, it asks the drive for the first sector, and it expects to get back 512 bytes of data.
A few years ago the hard drive industry moved to 4096 physical sector disks for various reasons (google is your friend), but they used a layer in the firmware to report the logical sectors as 512 bytes still. So when software or BIOS asked for a particular sector address, it got back only 512 bytes even though the sector was 4096 bytes. In effect each physical sector has eight addresses, 512 bytes each.
It's been known that 4096 logical sector disks would come out, that eliminate this 512 byte emulation layer. Both kinds of 4096 physical sector disks are referred to as AF (Advanced Format) disks. The ones with 512 byte emulation are 512e disks. The ones without it, are 4Kn disks. So this is looking like you have a 4Kn disk, and the part of the EFI firmare that emulates BIOS (the Compatibility Support Module) isn't exactly understanding what to do with that, because it's getting 4096 bytes instead of the 512 bytes it's expecting - that's my theory.
Anyway, the short term solution is to either disconnect the drive to boot Windows; or use a VM for Windows; or return the drive for a different 3TB drive that's 512e.
Last edited:
And, yes, I changed current to 4 partitions. If I remember the current partition was FAT32 (but I'm not 100% sure on the fAT32).
Do me a favor and try this:
Code:
sudo dd if=/dev/disk3 skip=8 count=1 2>/dev/null | hexdump -CIf I'm right and this is a 4Kn drive, that will get me the GPT header.
sudo dd if=/dev/disk3 skip=8 count=1 2>/dev/null | hexdump -C
Below is the hex dump you requested. I understand about the 4K vs. 512, I was somewhat reluctant to buy anything over 2 TB, but that's history now. I do have a few questions from your previous posting. Although replacing the Seagate is an option as well as removing the USB cable, I'd still like to get your take on the following alternatives:
- If I repartitioned the Seagate and created a NTFS or FAT32 partition, will that also solve this problem?
- Also, is there a way to modify the MBR record so that I don't get the infinite loop?
Code:
sudo dd if=/dev/disk3 skip=8 count=1 2>/dev/null | hexdump -C
00000000 45 46 49 20 50 41 52 54 00 00 01 00 5c 00 00 00 |EFI PART....\...|
00000010 55 68 e9 85 00 00 00 00 01 00 00 00 00 00 00 00 |Uh..............|
00000020 74 14 aa 2b 00 00 00 00 06 00 00 00 00 00 00 00 |t..+............|
00000030 6f 14 aa 2b 00 00 00 00 fa b7 e5 36 2e 38 a0 4b |o..+.......6.8.K|
00000040 9c d1 6f 22 a6 1f 1b e3 02 00 00 00 00 00 00 00 |..o"............|
00000050 80 00 00 00 80 00 00 00 ae 2d 9e 7c 00 00 00 00 |.........-.|....|
00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
00000200FWIW, I'm still having a hard time understanding why BootCamp is attempting to boot from a non-bootable volume, but I understand that it's a (new) scenario not encountered before.
[*]If I repartitioned the Seagate and created a NTFS or FAT32 partition, will that also solve this problem?
Doubtful. The firmware isn't hanging because the disk has HFSJ partitions. This hang occurs right at boot time, right? You see nothing?
I suppose it could be the Windows boot manager or boot loader that's seeing this drive, and that's what's hanging. But I'd expect that's gotten a lot of testing already, even though such drives are really rare still. I think this is an Apple firmware issue but even that's speculative.
[*]Also, is there a way to modify the MBR record so that I don't get the infinite loop?
No. But, there's an off chance that it's possible the firmware is becoming confused because there's so much superfluous garbage being returned by the drive. Maybe if those sectors were zero'd out and recreated cleanly, the extra space would report zeros instead of garbage. It could be worth a shot.
Code:sudo dd if=/dev/disk3 skip=8 count=1 2>/dev/null | hexdump -C 00000000 45 46 49 20 50 41 52 54 00 00 01 00 5c 00 00 00 |EFI PART....\...|
Yep. So this is definitely a 4Kn drive.
FWIW, I'm still having a hard time understanding why BootCamp is attempting to boot from a non-bootable volume, but I understand that it's a (new) scenario not encountered before.
All disks are scanned by the firmware. When you choose the Windows option for booting, that activates the CSM (the BIOS interface between EFI and Windows) and it might be that this CSM-BIOS implementation is doing its own device scan. Upon finding a drive that reports 4096 byte sectors, it's not inconceivable it's hanging.
BIOS normally scans devices, but I'm very unclear whether a CSM does this itself, or if it just asks EFI for data it already has about attached devices. I've pinged the author of gdisk, he knows more about the technical aspects of these things. Maybe he'll reply.
Maybe if those sectors were zero'd out and recreated cleanly, the extra space would report zeros instead of garbage. It could be worth a shot.
Should I try it or wait on the gdisk reply first? Of course, would need your help on which unix cmd(s) to issue.
Should I try it or wait on the gdisk reply first? Of course, would need your help on which unix cmd(s) to issue.
Since I don't have a 4Kn disk, I can't test this, but there's a feature in gdisk that will let you "zap" the MBR and GPT, and on a 4Kn disk this should zero all of the information in those sectors. The way I'd go about it would be to do this with gdisk in interactive mode, interactive meaning you type the letters in the sequence below followed by return. You can use ? to get a menu of the current list of options, and the quit command quits without saving changes, except when it warns you saying yes will obliterate the GPT and MBR - once you say yes to that, those structures are gone.
I'd start with a new Terminal window.
Code:
sudo gdisk /dev/disk[B][U]X[/U][/B]
p
b
3tbseagate_gdisk_partition.bin[p displays the current GPT to the screen serves as a backup-backup; b creates a gdisk backup file for the GPT, filename is just a suggestion. File is saved in your home directory, the one you launched gdisk in.]
------
Code:
x
z
y
y[This takes you to the expert menu, zaps the GPT, yes to confirm and yes to also erase the MBR. gdisk quits after this.]
------
Code:
sudo gdisk /dev/disk[B][U]X[/U][/B][There'll be some message about the lack of a partition table and that it's creating new entries. That's normal.]
------
Code:
r
l
<exactly the same filename as used above>
w
yThis will go to the recovery menu, load the backup file, and then write the GPT back to the disk. A protective MBR is also created.
------
Sorta type A, but you could do
Code:
sudo gdisk -l /dev/disk[B][U]X[/U][/B]To confirm/deny this zero'd those sectors, or at least the MBR one, you can do:
Code:
sudo dd if=/dev/disk[B][U]X[/U][/B] bs=4096 count=1 2>/dev/null | hexdump -CAnd post that, there shouldn't be more than a few lines if this works.
And before you quit Terminal or reboot, I recommend you go to the Terminal menu and choose "Export Text As" and save the terminal text somewhere. That way the printed backup and all the steps are recorded in case something's gone wrong.
And then finally you can also see if you're still getting the same hang on a reboot.
Unable to boot Windows when Seagate HD connected
Posting by murphychris.
And post that, there shouldn't be more than a few lines if this works./QUOTE]
Code:sudo dd if=/dev/disk3 bs=4096 count=1 2>/dev/null | hexdump -C
Here's the results from the above command:
Code:sudo dd if=/dev/disk3 bs=4096 count=1 2>/dev/null | hexdump -C 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 fe |................| 000001c0 ff ff ee fe ff ff 01 00 00 00 74 14 aa 2b 00 00 |..........t..+..| 000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 00000200 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00001000
Unfortunately, got the same results, system hangs when attempting to boot Windows with Seagate drive connected. However, I did notice one difference, when I booted Windows w/o Seagate, then connected the Seagate HD, I got 3 prompts in succession to reformat Drive H, Drive I, Drive J. My guess is that it's referring to 3 of the 4 Seagate partitions. Also, on the Mac side, all of the partition's contents look ok, when viewing via Finder.
I've included as an attachment the Terminal Output, assuming I did the attachment correctly.
Attachments
Unfortunately, got the same results, system hangs when attempting to boot Windows with Seagate drive connected.
The erase worked. The only thing in LBA 0 now is the PMBR.
How are you choosing Windows (System Preferences, or option key boot manager at the startup chime)? Try both, maybe there's a difference in behavior. Exactly when does the hang occur? This is before you see any indication Windows is booting? At the hang is there a cursor on a black screen or anything?
However, I did notice one difference, when I booted Windows w/o Seagate, then connected the Seagate HD, I got 3 prompts in succession to reformat Drive H, Drive I, Drive J.
That's well AFTER Windows has booted though, right?
It sorta sucks that Windows wants to reformat these partitions. They're designated by partition type GUID as being for HFSJ, so long as Windows doesn't know what that GUID is, it shouldn't ask. It should only ask if it recognizes the partition type GUID, but doesn't recognize the file system. But even OS X does this, if the GUID is for linux, and the partition is formatted ext4 or whatever, OS X wants to format it. Stupid.
How are you choosing Windows (System Preferences, or option key boot manager at the startup chime)?
Primarily through Mac's Toolbar "Restart in Windows" icon; however, I think the same thing will happen via System Preferences or a cold boot that goes directly to Windows based on previous (Windows) shutdown. But I can confirm that again with this new MBR.
The hang occurs before any indication of Windows booting, after the Mac OS "chime". I don't see any cursor, just a blank screen.Exactly when does the hang occur? This is before you see any indication Windows is booting? At the hang is there a cursor on a black screen or anything?
However, I did notice one difference, when I booted Windows w/o Seagate, then connected the Seagate HD, I got 3 prompts in succession to reformat Drive H, Drive I, Drive J.
That's well AFTER Windows has booted though, right?
That's correct, after a successful Windows boot (w/o Seagate connected), I then would connect the Seagate USB cable to the 4-port USB hub. The 3 successive popups would appear, following the typical "usb" sound.
On a separate note, I've looked at the previous (negative) reviews on Amazon web-site against this Seagate HD, similar problems with the 4k. Also contacted Amazon (since I purchased it thru them), asking when my 30-day expiration is in order to get the full refund. They will give me an extension. They encouraged me to contact Seagate to determine if they can fix the problem. The Amazon POC stated the following as part of the chat:
This gives us additional time to troubleshoot, only if you have an interest of pursuing this. I'm ok either way. You've helped a lot in solving the problem and narrowing down on the solution. Thank you.Yes, it looks like customers are experiencing some problems with the Harddrive. In this case, the best option would be to contact the Manufacturer, Seagate. In case they couldn't fix this, Please contact us. We'll be more than happy to help you with the return. Here's the contact number for the Seagate: 1-800-SEAGATE (1-800-732-4283).
On another note, I kinda' owe Apple Tech Support a reply since I have Applecare with my Mac-Mini. Are you ok if I share this exchange with them? Apple Tech Support seemed to right it off quickly as a Microsoft problem and not a Mac OS problem since I was able to boot Mac OS (from my perspective, I thought it too premature to discount BOOTCAMP without additional troubleshooting/symptoms).
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.