Ever since the Windows 10 upgrade was announced as free I have tried off and on to install it in a copy of my Windows 7 Virtual Machine (that I run on my Mac). At least I can get on with work and life while trying major OS upgrades that way. Unfortunately it’s not worked until finally I got somewhere today.
1. Switch your hard drives and DVD drive to IDE not SCSI.
2. Don’t worry if you missed the Windows 10 free upgrade deadline. Use your Windows 7/8 product key or the ‘assistive technologies’ upgrade.
For some reason VMware Fusion that I’m running defaults new Hard Drives to SCSI, though you can change the (emulated) connection type to IDE or SATA. It appears that Windows 10 doesn’t really like SCSI. Whenever I tried to install – either through ISO or running an upgrade assistant I got an error or else it would let me choose a keyboard layout then only give troubleshooting options and insist on shutting down or restarting the PC, without actually installing windows. Then it would revert to Windows 7, sometimes reporting error 0xc1900101 – 0x20017.
This turns out to be driver-related and probably was the SCSI issue.
A friend had a troublesome external Hard drive that wouldn’t work. It wouldn’t mount in Mac OS X, having some corruption issues and being an NTFS format drive.
Disk Utility helpfully said:
Verify and Repair volume “xxxxxxxx”Repairing file system.** /usr/local/bin/ntfsfix has been disabled because of volume corruption issues.
** If you still want to try fixing your volume, use /usr/local/bin/ntfsfix from the command line…
File system check exit code is 250.Updating boot support partitions for the volume as required.Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
Plugging it into my Windows 7 Virtual Machine didn’t let me do anything to fix it.
So I tried running sudo /usr/local/bin/ntfsfix as suggested (I had used Disk Utility’s ‘info’ function to identify the drive as /dev/disk5s1), only to encounter this:
dyld: Library not loaded: /usr/local/lib/libntfs.9.dylib
Referenced from: /usr/local/bin/ntfsfix
Reason: image not found
I updated various ports I thought might help but to no avail. Finally I looked inside /usr/local/lib/ and discovered that I have a file called libntfs.9.0.0.dylib but not libntfs.9.dylib. I typed
ln -s libntfs.9.0.0.dylib libntfs.9.dylib
to create a link to the file where the ntfsfix program expected it and thereafter the ntfsfix command works as it should. Something seems to have broken in OS X 10.10 Yosemite, but it just requires a quick link to work.
That said, I haven’t managed to resurrect the volume yet. Posting this because I got no helpful hits reporting the dyld (Dynamic Loader) error above.