I'd like to start a new thread regarding file system corruption that is being caused by PDM. I have twice suffered catastophic failures on the volume on which the VM 'disk' is run from (in my case it was a RAID, but it also occurs on a single disk setup). It seems there was an acknowledgement from the Parallel's team back in April 2006 from "ms@parallels" stating: 3. Kernel panic is main reason of the FS corruption. and Tim Sargent promised that the issue would be fixed prior to a production release. However, it seems that this bug has persisted into b1970. I don't know if it has been fixed yet in any of the beta builds - they're not recommended for use on production machines. What has been common across the posts that I've found in my seach is that after the file system's corruption takes place (by PDM), that Apple's Disk Utility reports "Invalid sibling links" when trying to repair the volume. I have organized related posts below to highlight relevant information for the correct diagnosis and resolution of this bug. I am unable to use the product on any volume that I can't risk 'expected' (random in my case) and complete disk failure. I would hope that Paralles will see this post and spend some time to investigate - (my bug reports go unanswered)... Contrary to the "3. Kernel panic is main reason of the FS corruption" acknowledgment from ms@parallels, I've only (ever) had one kernel panic - and it was when I tried to install the orginal release b1940. I haven't ever had another, despite the two disk corruptions. So while "Kernel panic is main reason of the FS corruption", it's not the only one. I have also never slept my Mac (or the drives), or paused the XP Pro VM. Mac runs 24/7, Parallels was opened, VM launched, used and then Start-->Shut Down, finally quiting PDM after successful shut down on every use. In my particular case, the VM 'disk' was on a RAID 0 stripe, and both times the bug manifested, the RAID was completely hosed. Disk Warrior4 let me manully recover everything but the PDM .hdd file the second time the FS corruption happened (wasn't available back in Nov. when I first had the problem), but was unable to rebuild the (RAID) volume's directory - it had to be destroyed and rebuilt. Other users reporting the same bug: April 7, 2006 - Sean Dudley November 23, 2006 - syates21 December 21, 2006 - mbohnen January 2, 2005 - fidel January 31, 2007 - bitjunky (my post) February 21, 2007 - mckinney February 25, 2007 - illovich If you have experienced a complete failure of your Mac OS boot disk (most common install) or another disk that contains your VM .hdd file(s), please reply to this post with your hardware info, and anything you think may be pertinent to this discussion. Hopefully Parallels will chime in to offer their current thoughts on this problem.
