Still issues with Vertex on Mac with 1.3

[vhs]

My Vertex became unusable with Firmware 1.1, by locking up when the disk load increased (~ 5-10 minutes). I replaced the drive with the stock HD that came with the Mac, and no lockup after that.
Reflashed the drive yesterday with the 1.3 firmware, which went allright, but the drive has already locked up 2 times during use today (1st time the os was running spotlight indexer, the 2nd time it was booting windows in vmware).
Both times the os was still working, but no disk access anymore (and unfortunately also no log files) so I had to restart the computer.

[Tony]

RMA it

[SafariKC]

RMA it

I'm having this same issue on 2 different MacBook's with 2 different drives upgraded to 1.3. Every few minutes the machine seems to completely lock up. It's as if the drive is just "gone".

I have a feeing something horrible is going on between 10.5.7 and the 1.3 firmware.

I'll try calling support.. but i have a hard time believing that an RMA will fix this if it's happening across 2 seporate installs os OSX on 2 drives in my house.

Sigh!

[harshw]

I'm having this same issue on 2 different MacBook's with 2 different drives upgraded to 1.3. Every few minutes the machine seems to completely lock up. It's as if the drive is just "gone".

I have a feeing something horrible is going on between 10.5.7 and the 1.3 firmware.

I'll try calling support.. but i have a hard time believing that an RMA will fix this if it's happening across 2 seporate installs os OSX on 2 drives in my house.

Sigh!

Hi

I've heard of the occasional freeze but lockups every few minutes ??? What's in the logs ... and does unplugging/plugging the drive help (with the lid down) ?

Did the MacBooks sleep and wake and then this issue occurred ? Do you remember if the issue occurred with the MacBook freshly booted/restarted and not having slept even once ?

Also, do you have SafeSleep enabled ? ie Do a pmset -g | grep hibernatemode and see if hibernatemode is set to 3. If so, try setting it to 0. You'll need to do sudo pmset -a hibernatemode 3

[SafariKC]

Hi

I've heard of the occasional freeze but lockups every few minutes ??? What's in the logs ... and does unplugging/plugging the drive help (with the lid down) ?

Did the MacBooks sleep and wake and then this issue occurred ? Do you remember if the issue occurred with the MacBook freshly booted/restarted and not having slept even once ?

Also, do you have SafeSleep enabled ? ie Do a pmset -g | grep hibernatemode and see if hibernatemode is set to 3. If so, try setting it to 0. You'll need to do sudo pmset -a hibernatemode 3

Unfortunately I haven't gone back in the logs.. Right now i can't even use my machine.. i think this thing is toast.. i just tried to format and re-install OSX and it can't even make it through the install. The detailed install log doesn't show anything and we can't get access to the console from there. But it seems like the drive just disappears to the OS.

I haven't changed my sleep state settings on either machine. So they are system default. But the machines are locking up during active use. it will disappear in the middle of a SuperDuper for instance (when the drive is at full tilt) or disappear when I'm surfing the web.. or now.. installing an OS. I can try tweaking the sleep and hibernate settings on the other machine and see if it helps.

While i had rare issues with 1.10 the 1.30 firmware for me was when this got impossible to deal with. and I don't see a way back to an older firmware.

I'll give support a call today. I'm horribly discouraged here. I need to be able to trust my data... and right now the speed is awesome.. but i don't trust this thing. I know SSD's work great with OSX untweaked (apple ships them in their own machines). So i'm just baffled as to why this is hard. Admitted, i haven't spent a huge amount of time troubleshooting, log scraping, calling support up until now... but we shouldn't even have to.

[zsnow]

Unfortunately I haven't gone back in the logs.. Right now i can't even use my machine.. i think this thing is toast.. i just tried to format and re-install OSX and it can't even make it through the install. The detailed install log doesn't show anything and we can't get access to the console from there. But it seems like the drive just disappears to the OS.

I haven't changed my sleep state settings on either machine. So they are system default. But the machines are locking up during active use. it will disappear in the middle of a SuperDuper for instance (when the drive is at full tilt) or disappear when I'm surfing the web.. or now.. installing an OS. I can try tweaking the sleep and hibernate settings on the other machine and see if it helps.

While i had rare issues with 1.10 the 1.30 firmware for me was when this got impossible to deal with. and I don't see a way back to an older firmware.

I'll give support a call today. I'm horribly discouraged here. I need to be able to trust my data... and right now the speed is awesome.. but i don't trust this thing. I know SSD's work great with OSX untweaked (apple ships them in their own machines). So i'm just baffled as to why this is hard. Admitted, i haven't spent a huge amount of time troubleshooting, log scraping, calling support up until now... but we shouldn't even have to.

i have the same freeze issue with my new macbook pro os install.
my is not vertex but use the same controller. I tried install windows , looks fine.

[SafariKC]

i have the same freeze issue with my new macbook pro os install.
my is not vertex but use the same controller. I tried install windows , looks fine.

Maybe i'll just switch to windows for the rest of my macbooks life.. who needs all that macy goodness?

[zsnow]

Maybe i'll just switch to windows for the rest of my macbooks life.. who needs all that macy goodness?

i like to be able to still use mac. i will try clone the image and see if i can get through

[SafariKC]

i like to be able to still use mac. i will try clone the image and see if i can get through

I was kidding :-) I love OSX.. it needs to work.

I just re-imaged my drive, went into Vista off CD partitioned and ran the wiper.. then went back into OSX.. re-partitioned.. and am in the process of writing out a clone with SuperDuper back to my OCZ drive.

It's not going well at all:
Jun 12 17:14:34 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0xcbe09882 >= 0x0000251c)
Jun 12 17:14:34 KyBook kernel[0]: node=4580 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:34 KyBook kernel[0]:
Jun 12 17:14:34 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.
Jun 12 17:14:34 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0xcbe09882 >= 0x0000251c)
Jun 12 17:14:34 KyBook kernel[0]: node=4580 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:34 KyBook kernel[0]:
Jun 12 17:14:34 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.
Jun 12 17:14:34 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0xcbe09882 >= 0x0000251c)
Jun 12 17:14:34 KyBook kernel[0]: node=4580 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:34 KyBook kernel[0]:
Jun 12 17:14:34 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.
Jun 12 17:14:34 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0xcbe09882 >= 0x0000251c)
Jun 12 17:14:34 KyBook kernel[0]: node=4580 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:34 KyBook kernel[0]:
Jun 12 17:14:34 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.
Jun 12 17:14:34 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0xcbe09882 >= 0x0000251c)
Jun 12 17:14:34 KyBook kernel[0]: node=4580 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:34 KyBook kernel[0]:
Jun 12 17:14:34 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.
Jun 12 17:14:34 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0xcbe09882 >= 0x0000251c)
Jun 12 17:14:34 KyBook kernel[0]: node=4580 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:34 KyBook kernel[0]:
Jun 12 17:14:34 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.
Jun 12 17:14:34 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0xcbe09882 >= 0x0000251c)
Jun 12 17:14:34 KyBook kernel[0]: node=4580 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:34 KyBook kernel[0]:
Jun 12 17:14:34 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.
Jun 12 17:14:34 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0xcbe09882 >= 0x0000251c)
Jun 12 17:14:34 KyBook kernel[0]: node=4580 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:34 KyBook kernel[0]:
Jun 12 17:14:34 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.
Jun 12 17:14:34 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0xcbe09882 >= 0x0000251c)
Jun 12 17:14:34 KyBook kernel[0]: node=4580 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:34 KyBook kernel[0]:
Jun 12 17:14:34 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.
Jun 12 17:14:34 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0xcbe09882 >= 0x0000251c)
Jun 12 17:14:34 KyBook kernel[0]: node=4580 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:34 KyBook kernel[0]:
Jun 12 17:14:34 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.
Jun 12 17:14:34 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0xcbe09882 >= 0x0000251c)
Jun 12 17:14:34 KyBook kernel[0]: node=4580 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:34 KyBook kernel[0]:
Jun 12 17:14:34 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.
Jun 12 17:14:35 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0x89504e47 >= 0x0000251c)
Jun 12 17:14:35 KyBook kernel[0]: node=4741 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:35 KyBook kernel[0]:
Jun 12 17:14:35 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.
Jun 12 17:14:35 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0x89504e47 >= 0x0000251c)
Jun 12 17:14:35 KyBook kernel[0]: node=4741 fileID=4 volume=KyBook device=/dev/disk0s2
Jun 12 17:14:35 KyBook kernel[0]:
Jun 12 17:14:35 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook, fsck will be forced on next mount.


Every single file is having a horrible time writing.

I went back in time and saw this is what was happening before as well.

Jun 10 23:07:17 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook SSD, fsck will be forced on next mount.
Jun 10 23:07:17 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0x2c0a0fc8 >= 0x0000bb00)
Jun 10 23:07:17 KyBook kernel[0]: node=9042 fileID=4 volume=KyBook SSD device=/dev/disk0s2
Jun 10 23:07:17 KyBook kernel[0]:
Jun 10 23:07:17 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook SSD, fsck will be forced on next mount.
Jun 10 23:07:17 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0x2c0a0fc8 >= 0x0000bb00)
Jun 10 23:07:17 KyBook kernel[0]: node=9042 fileID=4 volume=KyBook SSD device=/dev/disk0s2
Jun 10 23:07:17 KyBook kernel[0]:
Jun 10 23:07:17 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook SSD, fsck will be forced on next mount.
Jun 10 23:07:18 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0x89504e47 >= 0x0000bb00)
Jun 10 23:07:18 KyBook kernel[0]: node=779 fileID=4 volume=KyBook SSD device=/dev/disk0s2
Jun 10 23:07:18 KyBook kernel[0]:
Jun 10 23:07:18 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook SSD, fsck will be forced on next mount.
Jun 10 23:07:18 KyBook kernel[0]: hfs_swap_BTNode: invalid forward link (0x89504e47 >= 0x0000bb00)
Jun 10 23:07:18 KyBook kernel[0]: node=779 fileID=4 volume=KyBook SSD device=/dev/disk0s2
Jun 10 23:07:18 KyBook kernel[0]:
Jun 10 23:07:18 KyBook kernel[0]: HFS: Runtime corruption detected on KyBook SSD, fsck will be forced on next mount.


and the magic continues... I put in a support case.. and called OCZ.. the guy who i can talk to evidently is out at lunch. I hope to hear back from him soon but will probably call shortly again.. i can't be without my machine for much longer.. and once i take this drive out and go back to my other drive it'll be hard to do any form of real time troubleshooting.

Anyone know if there's a way to go back to an older firmware? I'd love to do a full install (with integrated wipe) of 1.10 again and see if this is all artifacts of the "quick" 1.30 firmware push.

KC

[SafariKC]

OCZ just reached out.. they are going to RMA both of my 250's. I still can't help but think there's something we can do to fix this in firmware.. but i'm glad they are going to swap out the drives... from what i hear they have been really good at that for folks having issues.

Anyone on the mac version of the drive having issueS? Maybe there is some kind of difference?

[harshw]

Unfortunately I haven't gone back in the logs.. Right now i can't even use my machine.. i think this thing is toast.. i just tried to format and re-install OSX and it can't even make it through the install. The detailed install log doesn't show anything and we can't get access to the console from there. But it seems like the drive just disappears to the OS.

I haven't changed my sleep state settings on either machine. So they are system default. But the machines are locking up during active use. it will disappear in the middle of a SuperDuper for instance (when the drive is at full tilt) or disappear when I'm surfing the web.. or now.. installing an OS. I can try tweaking the sleep and hibernate settings on the other machine and see if it helps.

While i had rare issues with 1.10 the 1.30 firmware for me was when this got impossible to deal with. and I don't see a way back to an older firmware.

I'll give support a call today. I'm horribly discouraged here. I need to be able to trust my data... and right now the speed is awesome.. but i don't trust this thing. I know SSD's work great with OSX untweaked (apple ships them in their own machines). So i'm just baffled as to why this is hard. Admitted, i haven't spent a huge amount of time troubleshooting, log scraping, calling support up until now... but we shouldn't even have to.

Format the drive in Windows. As FAT32 or NTFS ... doesn't matter. And then reformat it under OSX ... put in the Install CD; choose Disk Utility, create a single GUID partition. And reinstall OSX from scratch. Dont worry ... it can pick up info from your SuperDuper clone and do a migration. But don't clone stuff back ... do a re-install ( with the reformat )

And please post your partition table ... you'll need to do a sudo fdisk /dev/rdisk0 from a Terminal prompt

[TheBrew]

Half a year ago I bought a unibody MacBook 13" and installed a 120GB Vertex SATA II in it. Everything has been snappy and nice right up until now:

I decided to buy the new unibody MacBook Pro 13" that Apple released on june 8th.

Installing the drive in this notebook has been (and still is..) hell. I've spend 3 days trying to figure out what's wrong (must have tried to install Leopard 1.5.7 20 times).

Clean wipe of the drive, and yet I still have unstable installs - It just stops at some percent and stays there. I've been able to complete an install of Leopard one time - just to have it hang after a little while using the system. But the installing is the best test - fails 90% of the time.

What I've tried:

* Updated to latest firmware (1.30 ..boy was that b.. with the serialno. bug and need for different firmwares)
* Alt+Cmd+PR (Reset PRAM)
* Format in Winblows, re-create a GUID partition instead through the Leo-installer and let it reformat it.
The formatting in Windows actually had it install 100% - but died while transfering my old settings at the next reboot.
* Works every time with regular SATA HDD.

Funny thing though: If I plug the SSD into a USB-dock and install to that: no problems..

So I wonder if the problem is the controller, driver, or firmware?

Any good ideas for me to try?

..next up, will try a Snow Leopard install..

Cheers - and thanks for a good forum

[TheBrew]

Hm. Could be related to the fact that the new unibody MacBook Pro is crippled down to SATA I..

http://forums.macrumors.com/showthread.php?t=718516

[megasupermax]

Half a year ago I bought a unibody MacBook 13" and installed a 120GB Vertex SATA II in it. Everything has been snappy and nice right up until now:

I decided to buy the new unibody MacBook Pro 13" that Apple released on june 8th.

Installing the drive in this notebook has been (and still is..) hell. I've spend 3 days trying to figure out what's wrong (must have tried to install Leopard 1.5.7 20 times).

Clean wipe of the drive, and yet I still have unstable installs - It just stops at some percent and stays there. I've been able to complete an install of Leopard one time - just to have it hang after a little while using the system. But the installing is the best test - fails 90% of the time.

What I've tried:

* Updated to latest firmware (1.30 ..boy was that b.. with the serialno. bug and need for different firmwares)
* Alt+Cmd+PR (Reset PRAM)
* Format in Winblows, re-create a GUID partition instead through the Leo-installer and let it reformat it.
The formatting in Windows actually had it install 100% - but died while transfering my old settings at the next reboot.
* Works every time with regular SATA HDD.

Funny thing though: If I plug the SSD into a USB-dock and install to that: no problems..

So I wonder if the problem is the controller, driver, or firmware?

Any good ideas for me to try?

..next up, will try a Snow Leopard install..

Cheers - and thanks for a good forum

I'm having the exact same issue.... this has to be fixed

[soleblaze]

I'll also say that I've had this issue, although I did eventually get it installed (It hung up every 15% or so for a couple of minutes the second time I tried the install). Now I occasionally get the beachball freezes. I'm also going to try installing the new Snow Leopard to see if that helps.