Hello, I have used PW since beta 1 and i think that it's a nice product. I have read some of the comments on this forum about HD corruption and it too happened to me. All i had to do was boot off from the OS X Install Disc and do a HD repair and it was all set. Well this morning i was using PW and compiling something from DarwinPorts and surfing the web and a whole bunch of other things and PEEEW! i got a kernel panic. So i held down the power button until it rebooted and then i tried to boot the system again. No go....no mouse or anything on the blue background. So then i tried Single User Mode with a fsck -fy and it kept whining about invalid record count. I thought that this was because i was booting off fromthe HD and not the CD...maybe something with a mounted HD can't be checked properly? So i booted off from the OS X Install Disc and went into Disk Utility and tried to run a repair volume from there. No Go! Same error and a pop up saying that the disk is trashed. So i'm reinstalling as we speak. Unfortunately i didn't save the kernel panic log...i hit the erase button before thinking... So i ask you fellow testers: 1) Have you had this happen to you as well? 2) Has anyone noticed the HD corruption talked about in these forums? 3) Is there some user error that i performed? Final Note: I have prepaid for the final version. I love this product and stand behind it. I am not complaining, just expressing concerns because i hadn't ran into such a serious problem before. I do understand this is beta and i did have everything backed up. No sweat! Thanks for listening, -Levi System: Macbook Pro 1.83GHZ/1GB/80GB
Next time you boot into single-user mode and use fsck, if you receive an error then re-run fsck and continue re-running until you receive a Filesystem OK reply. It may take fsck several runs to fix all the errors. However, if you find that continually re-running does not result in the filesystem being fully repaired or if you receive a message that fsck cannot repair an error, then you know that the problem is too serious for fsck to fix.
I was in the process of installing xp when I receieved an OSX error that I was out of disk space (or memory, I remember it being ambiguous) and to quit an application. Parallels then gave me a fatal error. I reality I still had more than 30GB free. The machine would not boot correctly, I had only the "progress circle", but no login prompt. When I booted from firewire I ran Disk Utility and got all sorts of errors! I will now send the du log and para-log to parallels, but I am extremely concerned!
