You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

WARNING: Boot Camp Assistant can reformat wrong drive

This is a notification to users of a bug in Mac OS X Lion. On Macs that do not have internal optical drives (Mac Mini or MacBook Air), the Boot Camp Assistant 4.0.1 can potentially reformat the wrong external storage device in a case where the user has multiple external volumes, when creating the Windows Installer from a Windows 7 .ISO disk image file. (In my case the disk image was on an external drive that Boot Camp Assistant reformated due to this bug.)


This is how I produced this issue:


I have a friend's brand new Mac Mini 2011 with 10.7.1. I wanted to create a Boot Camp parition, so I started Boot Camp Assistant.


On the Mac Mini the Boot Camp Assistant gives you three options: (1) Create a bootable USB volume, (2) Download and burn the Apple drivers to CD/DVD, and (3) Install Windows on your Boot Camp Partition. Option (1) is new to Lion as mentioned by Apple here:

  • Support for the Windows 7 ISO installer
  • Install Windows with an installation disc you provide or, on Mac computers that do not have an optical drive, with a USB flash drive that contains a Windows 7 ISO image downloaded from Microsoft. The Boot Camp Assistant will offer to create this image on supported computers.


Apple's website does not say that you MUST install from a USB drive and not a DVD, and the Boot Camp Assistant screen does not say you can't either. Since I have an external LaCie DVD-RAM drive, I figured that I should just install Windows the old fashioned way -- from the DVD.


So, I unchecked Option (1) and used Boot Camp Assistant to create a new partition on the internal drive, on which to install Windows 7. The partition itself was successfully created on the internal hard drive of the Mac Mini. I burned the Apple drivers to CD using an external USB LaCie DVD-RAM drive. Next I inserted the Windows 7 disk into the external DVD drive, and pressed Continue to restart the Mac and install Windows. However the computer just showed a green screen with the text saying basically, "No bootable volume found."


At this point I don't know why it would not boot up from the Windows 7 disc that was in the DVD-RAM drive, since that disc worked fine on my Mac Pro for creating the Boot Camp partition, and evidently it is OK with installing from a USB stick. I even tried my friend's Windows 7 disc that he had brought, which was the same version, but it also failed.


So after hard-restarting the Mini, we got the ISO file and a 16GB USB stick and proceeded to try it the other way. The ISO file had been downloaded onto a USB hard drive that had two partitions: an HFS+ partition and a FAT-32 partition. They were called "Velcro" and "Velcro DOS." We used my Mac Pro to copy the ISO file onto that USB hard drive, then attached that drive to the Mac Mini along with the 16GB USB stick that was called "SIXTELN."


We opened Boot Camp Assistant and checked all three options. It asks you to select the Windows 7 ISO file, and I did select it on my external volume called "Velcro." Then it asks to choose which device to create the installation partition on. I selected "SIXTELN" to reformat and made sure that was the correct volume when it reminded me that I would lose all my data. So I hit "Continue" and then what happened next is that it formatted the wrong drive.


Boot Camp Assistant creates a volume called WININSTALL from which the Mac will boot, and from which Windows will be installed.


Let me resummarize for those of you who cannot accept the fact that this could actually be possible.


I attached my USB hard disk which two partitions, one Mac HFS+ and the other FAT 32 (entitled "Velcro" and "VelcroWin" respectively). Then I inserted the USB stick, a 16GB SanDisk Cruzer called "SIXTELN." The Mac HFS+ volume "Velcro" contained the Windows 7 ISO file, which I selected in Boot Camp Assistant to use for creating the startup USB disk. Next, I selected the USB stick "SIXTELN" as the device to reformat and use for creating the bootable Windows 7 installer. I then double-checked that I had selected the correct device, and even "SIXTELN" in the Finder to make sure there were no files on it that I couldn't stand losing. I clicked Continue to proceed, and was presented with a warning that "SIXTELN" would be erased and all its files deleted. I pressed "continue" and then I was confounded as the WININSTALL volume that was created showed 322 GB available, and an error message appeared in Boot Camp Assistant saying that it could not continue.


That was when I realized the truth:


Boot Camp Assistant had erased the entire USB hard disk including both both partitions, one of which contained the Windows 7 ISO file that I had selected to install from! The installation could not complete because it could not find the Windows 7 ISO file anymore! The software never warned me it was going to erase the Volume entitled "Velcro" nor "VelcroWin". It shouldn't have done so anyway, since the ISO file was on "Velcro"!


Software should never delete a file it is planning to read from, then try to read from it. Ever. For example, Disk Utility will not allow you to reformat your startup volume, because it's impossible, since Disk Utility depends on files that are on the startup volume! Boot Camp Assistant should not ever reformat the volume containing the Windows ISO file that has been selected to install from.


I suspect an error in the code of Boot Camp Assistant (like using the wrong variable) resulted in the software formatting the wrong drive. I'm certain, because I had named the volume for installation, "SIXTEEN" and when I selected it, I switched to the finder to open it and look at its contents, then switched back. Then it said basically, "Are you sure you want to reformat the volume, SIXTEEN, which will delete all its contents?" And I said yes to this.


From what I have read on these forums today, many people have had many problems trying to install Windows 7 onto MacBook Airs and Mac Minis due to their lack of DVD drives. There are a ton of bugs in Boot Camp Assistant and this whole process is confusing and not clearly documented. Personally with all due respect, in the case of MacBook Airs then I can understand the omission of a DVD drive. But in the case of Mac Mini, I cannot understand it at all. Macs are supposed to be simple to use; read this other thread and witness the complexity that users have had to go through just to get Boot Camp running on a MacBook Air or Mac Mini.


Further I cannot understand why Apple makes Macs that require booting from a USB stick to install Windows 7, but that do not allow users to simply install from an external USB DVD drive. If you're going to remove the DVD drive from the computer then at least give users an alternative solution that is not buggy.


EDIT: fixed some typos.


EDIT 2: see this thread about how to properly install Windows 7 on Lion if you have a Mac Mini or MacBook Air without the optical drive, without a DVD drive. An external DVD drive will not work.

Mac mini, Mac OS X (10.7.1)

Posted on Oct 2, 2011 9:00 PM

Reply
7 replies

Oct 3, 2011 1:42 AM in response to DaddieMac

Here is the console log (you can see where it seems to fail doing an init device, and it fails opening some hidden files on the USB stick "SIXTELN"... no idea why but yeah, instead of reformatting the USB stick, it reformatted the hard drive that contained the installation ISO! > . < Major bug!!


10/2/11 3:30:39.400 PM fseventsd: check_vol_last_mod_time:XXX failed to get mount time (25; &mount_time == 0x103202538)

10/2/11 3:30:39.400 PM fseventsd: log dir: /Volumes/VELCRO DOS/.fseventsd getting new uuid: D8053E69-89F3-4BF5-A766-55F73C20DAC1

10/2/11 3:30:40.000 PM kernel: 0 0 AppleUSBCDC: start - initDevice failed

10/2/11 3:30:40.000 PM kernel: USBMSC Identifier (non-unique): 20044324430F0462021A 0x781 0x5530 0x100

10/2/11 3:32:49.000 PM kernel: 0 0 AppleUSBCDC: start - initDevice failed

10/2/11 3:32:49.000 PM kernel: USBMSC Identifier (non-unique): 20044324430F0462021A 0x781 0x5530 0x100

10/2/11 3:32:50.264 PM fseventsd: could not open <</Volumes/SIXTELN/.fseventsd/fseventsd-uuid>> (No such file or directory)

10/2/11 3:32:50.264 PM fseventsd: log dir: /Volumes/SIXTELN/.fseventsd getting new uuid: 6C1CC756-2685-41A3-B0BE-C4BD30562672

10/2/11 3:33:25.689 PM fseventsd: could not open <</Volumes/WININSTALL/.fseventsd/fseventsd-uuid>> (No such file or directory)

10/2/11 3:33:25.689 PM fseventsd: log dir: /Volumes/WININSTALL/.fseventsd getting new uuid: 143D94D3-FED5-4F64-A447-4DE32CF4D7E5

10/2/11 3:33:25.734 PM fseventsd: Events arrived for /Volumes/WININSTALL after an unmount request! Re-initializing.

10/2/11 3:33:25.734 PM fseventsd: creating a dls for /Volumes/WININSTALL but it already has one...

10/2/11 3:33:27.903 PM coreservicesd: Received request to reset fmod watch. Latest received id is 1271309975403. Latest sent id is 1271309975403

10/2/11 3:33:27.995 PM fseventsd: disk logger: failed to open output file /Volumes/WININSTALL/.fseventsd/636573aada3c21a8 (No such file or directory). mount point /Volumes/WININSTALL/.fseventsd

10/2/11 3:33:27.995 PM fseventsd: disk logger: failed to open output file /Volumes/WININSTALL/.fseventsd/636573aada3c21a8 (No such file or directory). mount point /Volumes/WININSTALL/.fseventsd

10/2/11 3:33:30.745 PM fseventsd: check_vol_last_mod_time:XXX failed to get mount time (25; &mount_time == 0x103202538)

10/2/11 3:33:30.745 PM fseventsd: log dir: /Volumes/WININSTALL/.fseventsd getting new uuid: 0922C1AC-FB9C-48FB-B5C7-990E7CDCDBA1

10/2/11 3:33:30.746 PM fseventsd: Events arrived for /Volumes/WININSTALL after an unmount request! Re-initializing.

10/2/11 3:33:30.746 PM fseventsd: creating a dls for /Volumes/WININSTALL but it already has one...

10/2/11 3:33:30.898 PM fseventsd: disk logger: failed to open output file /Volumes/WININSTALL/.fseventsd/636573aada3c21bc (No such file or directory). mount point /Volumes/WININSTALL/.fseventsd

10/2/11 3:33:30.898 PM fseventsd: disk logger: failed to open output file /Volumes/WININSTALL/.fseventsd/636573aada3c21bc (No such file or directory). mount point /Volumes/WININSTALL/.fseventsd

10/2/11 3:33:30.898 PM fseventsd: failed to unlink old log file /Volumes/WININSTALL/.fseventsd/636573aada3c21bc (No such file or directory)

10/2/11 3:33:30.898 PM fseventsd: failed to unlink old log file /Volumes/WININSTALL/.fseventsd/636573aada3c21bc (No such file or directory)

10/2/11 3:33:30.898 PM fseventsd: unmounting: failed to remove log dir /Volumes/WININSTALL/.fseventsd (No such file or directory)

10/2/11 3:33:33.263 PM fseventsd: could not open <</Volumes/WININSTALL/.fseventsd/fseventsd-uuid>> (No such file or directory)

10/2/11 3:33:33.263 PM fseventsd: log dir: /Volumes/WININSTALL/.fseventsd getting new uuid: 771C1046-9404-4B80-95E1-4D2B91FC1F76

10/2/11 3:34:40.521 PM diskmanagementd: DM ->T-[DMToolBootPreference setDiskForBootPreference:path:isOS9:nextOnly:]: inDisk=0x106685c30=disk0s2=Shoggoth inPath=/System/Library/CoreServices inIsOS9=0 inNextOnly=0

10/2/11 3:34:40.522 PM diskmanagementd: DM ->T-[DMToolBootPreference runBlessToEnsureBootFilesInCoreServicesForDisk:]: inDiskUDS=0x106685c30=disk0s2=Shoggoth

10/2/11 3:34:40.522 PM diskmanagementd: DM ..T-[DMToolBootPreference runBlessToEnsureBootFilesInCoreServicesForDisk:]: launching /usr/sbin/bless (

"--folder",

"/System/Library/CoreServices",

"--bootefi"

)

Oct 11, 2011 2:17 AM in response to DaddieMac

OK So now I know I was not alone. The below post from my thread on MacRumors forum proves that I was not at fault in this, as some of you had tried to blame me in a thread that Apple deleted. Obviously there IS a bug in Bootcamp Assistant and it CAN and WILL reformat external USB hard drives... BE CAREFUL!!!


-daddiemac



> > >

I have the same experience, I tried to install Windows 7 using bootcamp assistant 4 into my new macbook air 2011. My windows 7 iso file was stored in one of two partition of my external 500 GB hard drive. I was also using a 8GB usb drive to store the "windows drivers" which supposedly downloaded during the installation process.


I plugged the external hard drive in one MBA's usb slot and the usb on another slot, initiated the process.


I think the process happens for around 10 minutes or so when an error message showed up. I thought the problem was simply failure to mount/copy the iso file to the usb drive. But I then realized that my entire 2 partition 500 GB external hard drive was wiped clean into a single wininstall partition.


I am now on my second days running a hard drive recovery program in windows trying to get my data back.

Sep 20, 2012 7:47 AM in response to DaddieMac

hi, thanks for your post, I have had the same problem, and now my external Hard disk is with the second data recovery company, as the first couldnot do the job and retrieve my data. I will try your software and hope for the best. Thank you, I also thought it was me, and my fault but your post made me feel a little better, so thank you

Sep 20, 2012 9:23 AM in response to nmwe999

I am trying to get this bug correctly documented for Apple to fix it. Can you please describe in great detail precisely all the steps you did leading up to it happening? Any minor detail could be important, please try to be thorough. Maybe we can help Apple fix this weird bug and save someone else like us from the same terrible fate. Thanks!

Dec 7, 2012 12:29 PM in response to DaddieMac

This is just insanely ridiculous!


Same happened to me just now:


500 GByte hard drive with Windows 7 iso-file in it (NTFS).

16 GByte thumb drive.


I don't even know how Boot Camp was able to write into the NTFS drive. Usually it's not allowed in Mac OS.


I'm running Recuva on the hard drive, lets see what happens.


I thought my inexperience with Mac OS was the cause but apparently not.

WARNING: Boot Camp Assistant can reformat wrong drive

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.