Chkdsk run everytime I start Windows Vista under Bootcamp in Snow Leopard

Question

Level 1

108 points

Chkdsk run everytime I start Windows Vista under Bootcamp in Snow Leopard

I have Windows Vista 32 bits installed on bootcamp partition and it work fine in 10.5.

Now I have upgrade my MBP (early 2008) to Snow Leopard, and upgrade WIndows Bootcamp drivers to version 3.0 from Snow Leopard DVD. Both installation were completed and run fine.

The problem I have now is: Whenever I used Mac OS, shut down, then restart the WIndows Vista by pressing Option key at Macbook Pro startup, Chkdsk will run evry time, checking integrity of the Windows boot partition. I have to wait for more than 20 minutes before Chkdsk fix all errors, then reboot, and press Options key to get back into WIndows Vista without Chkdsk running.

When I shut down Windows, and restart without goinb into Snow Leoprad, the boot process go OK without Chkdsk running.

But whenever I shut fown Winodws and use Snow Leopard, then get back in to startup Windows, Chdsk run again. This is very annoyingm, and never occured in 10.5

During Chkdsk session, the following errors occured and being fixed:

Deleting index entry ._501 in index $I30 of file 9028
Deleting index entry 501 in index $I30 of file 9028

and after all process finished, Chkdsk stated that: There is a blank space that allocated as used, and has been fixed.

Can any friend advise me what cause this problem? and How to correct it?

I understanfd that the ._501 is in .Trashes folder on Windows partiton. It must be altered wwhen I use Snow Leopard, and must have to do with Trash in Mac OSX 10.6.

Can any friend advise me how to solve this problem? Thank in advance

MacBook PRO Early 2008, Mac OS X (10.6)

Posted on Sep 7, 2009 2:58 AM

Reply

Answer 1

Purd Author

Level 1

108 points

Sep 7, 2009 6:05 AM in response to Purd

The problem is repeatable. The same index and file to be deleted by Chkdsk remain unchanged every time I boot Windows under bootcamp after using Mac OS. If I reboot Windows many many times without using Mac OS, the error never occur.

It must be Mac OSX Snow Leopard that is the culprit. Can any friend give me solution of how to solve this problem?

When I try booting Windows in Parallels the boot is OK

Reply

Answer 2

The hatter

Level 9

61,031 points

Sep 7, 2009 6:35 AM in response to Purd

Seems like Parallels is at least partially responsible. Otherwise, without 3rd party NTFS driver, Mac OS won't write to Vista otherwise, and read-only.

What if you don't use Parallels? is it up to date and okay? checked their forums?

Can Parallels run a chkdsk or verify of the filesystem?

Reply

Answer 3

Purd Author

Level 1

108 points

Sep 7, 2009 7:18 AM in response to The hatter

The same problem occured even if I don't use Parallels. My Parallels is the latest version that is Snow Leopard compatible.

When I have shut down Windows, then boot into Mac OSX, use it, then shut down, and resatrt Windows, Chkdsk will run as stated before.

But if I shut down Windows, and restart WIndows again, Chkdsk won't run I the boot is OK. I have Paragon NTFS for Mac (latest version) instal;led on my system since 10.5 and it work fine until Snow Leopard

Any suggestion?

Reply

Answer 4

The hatter

Level 9

61,031 points

Sep 7, 2009 8:17 AM in response to Purd

Check with Paragon; try without their drive. Drivers are one thing that regularly needs update.

Paragon means that Spotlight is going to run on Vista volume. You can minimize by putting Vista in its privacy list.

Reply

Answer 5

Airbaal

Level 1

0 points

Sep 18, 2009 9:54 AM in response to The hatter

I have the same problem. I am running Windows 7 RTM on a bootcamped drive, and have Snow Leopard. I never even boot into OS X and have NO programs installed in OS X. But every time I restart Windows, I get that message. I also tend to hibernate my Windows 7 PC a lot, and reboot every week or two...

Reply

Answer 6

Sep 20, 2009 11:54 AM in response to Purd

In OS X run disk utility. Select your Windows and run both repair disk and verify disk utilities. Then boot up to windows. This worked for me.

Reply

Answer 7

The hatter

Level 9

61,031 points

Sep 20, 2009 1:17 PM in response to Thomas Low

Disk Utility won't repair NTFS. And you should realize that Windows Vista and later require NTFS. Plus, Windows is best left to repair its own drives.

Maybe you used XP and FAT is only way you could repair Windows from mac os.

Reply

Answer 8

Sep 30, 2009 10:41 PM in response to Purd

Hey I'm having the same problem and the check shows my Windows drive to be "NOT dirty". Any idea how to fix this problem?

Reply

Answer 9

Nov 14, 2009 2:12 PM in response to Purd

Hi,

the same here. I don't have Parallels. Every time I restart Windows after a Snow Leopard session the computer runs a chkdsk, that in my case last more than 1 hour (MacBook Pro Unibody, Windows 7, HD 500gb 7200rpm).
This is very, very annoying.

Regards

Reply

Answer 10

The hatter

Level 9

61,031 points

Nov 14, 2009 2:59 PM in response to oscarbrt01

Is it an issue with 500GB drives in some Macs? an issue with using MacDrive or MacFuse (or other 3rd party NTFS driver in Mac OS)?

Reply

Answer 11

jayarr

Level 1

5 points

Nov 15, 2009 8:57 AM in response to The hatter

You might want to run a tool like Disk Warrior to analyze/fix problems with the hard drive, if they are detected.

Reply

Answer 12

Nov 15, 2009 9:24 AM in response to Purd

I had the same problem and was reasonably confident that the disc was actually okay and did not benefit from repeated checking. You can instruct Windows on boot to ignore a drive by typing in the following command after boot into a command window chkntfs /x c:

In the case above c: is the drive letter Windows is booting to. If there really is a serious issue that chkdsk is identifying and trying to fix for you this may not be the way to go. However if this helps you can always run chkdsk manually from time to time to verify that the disc is still okay.

SL also created this problem for me. After that and a host of other issues that I did not have the time or patience to to battle with I reinstalled Leopard and have been happy with the decision.

Reply