- Joined
- Aug 27, 2010
- Messages
- 140
- Motherboard
- GA-X58A-UD3R
- CPU
- XEON X5650
- Graphics
- GeForce GTX 260 + 9500GT
- Mac
- Classic Mac
- Mobile Phone
Good old ga-x58a-ud3. Upgraded from Sierra to High Sierra today.
I have a spare with a CCC backup of Sierra in case I have to revert from High Sierra. That drive has its own bootable EFI partition with Clover, and another partition for data. (3 total: EFI, Sierra Backup, and Data)
The problem: After upgrading to HS the drive doesn't mount. I keep seeing the message "The disk you inserted was not readable by this computer", and hitting initialize doesn't seem to do anything.
The drive still shows up on clover, the bootable sierra backup loads fine. I'm wondering if High Sierra has any additional protections to prevent the partitions to mount (like detected system files or the other EFI partition). Diskutil can see the HD, but doesn't show any of the partitions. I never had this issue on Sierra, Yosemite or any other previous OSX.
I have a third drive with just data, no EFI or system files that show up fine, so I really don't believe it is a driver issue.
Any clue of what might be causing this, and more importantly, how to solve it?
Thanks folks!
I have a spare with a CCC backup of Sierra in case I have to revert from High Sierra. That drive has its own bootable EFI partition with Clover, and another partition for data. (3 total: EFI, Sierra Backup, and Data)
The problem: After upgrading to HS the drive doesn't mount. I keep seeing the message "The disk you inserted was not readable by this computer", and hitting initialize doesn't seem to do anything.
The drive still shows up on clover, the bootable sierra backup loads fine. I'm wondering if High Sierra has any additional protections to prevent the partitions to mount (like detected system files or the other EFI partition). Diskutil can see the HD, but doesn't show any of the partitions. I never had this issue on Sierra, Yosemite or any other previous OSX.
I have a third drive with just data, no EFI or system files that show up fine, so I really don't believe it is a driver issue.
Any clue of what might be causing this, and more importantly, how to solve it?
Thanks folks!