Complete folders keep disappearing on my SSD

[machete143]

Hi,
I've just bought a new Mac Pro 15" with an 512GB SSD.
I mainly use my Mac for developing PHP Frameworks and I've been using an Mac Pro (early 09) before. I've installed all the neccessities (php55, mysql5, ...) via port but there's a really weird issue:

Dependencies installed just keep disappearing randomly - it's mostly the same folder (vendor/zendframework) but it has hit random folders in that directory. I notice this immediately because my applications stop working - but I've not modified anything there nor have I deleted stuff in there.

I've searched all my file structure in superuser mode ( find * | grep xyz ; locate xyz ) but the files are just freaking gone.

I've run the disk utility and checked for errors (there where none), repaired the disk (there was nothing to repair) and checked for invalid permissions (there are many invalid permissions, which is weird, because the mac is like 2 days old).

I have really no clue why this keeps happening (it's like the 5th time now) and I'm not sure if other parts of the FS are affected as well (there's not a lot of stuff on my mac yet).

The files are kept in:

/Library/WebServer/Documents/workspace/[projectname]/src/vendor/

Does anyone have any idea? Or should I just send this thing back. It really seems to me as if it's a problem with the SSD.

all the best and a merry xmas

----------

Okay something weird is happening. Normally the disk utility would show a green line saying something like "Volme XYZ seems to be okay". This works fine with a partition called "Recovery HD".
But when I do this check on "Macintosh HD" the tests stops at "File für extended attributes is being checked" (roughly translated from german. The original says: "Datei für erweiterte Attribute wird überprüft"). I don't get that green line telling me that everything is okay!

The log looks like this:

2013-12-25 14:36:22 +0100: Partitionstabelle für „APPLE SSD SM0512F Media“ überprüfen und reparieren
2013-12-25 14:36:22 +0100: Reparatur wird gestartet:
2013-12-25 14:36:22 +0100: Voraussetzungen überprüfen
2013-12-25 14:36:22 +0100: Die Partitionsliste überprüfen
2013-12-25 14:36:22 +0100: Partitionstabelle wird bei Bedarf an die Größe der gesamten Festplatte angepasst
2013-12-25 14:36:22 +0100: Nach einer EFI-Systempartition suchen
2013-12-25 14:36:22 +0100: Die Größe der EFI-Systempartition überprüfen
2013-12-25 14:36:22 +0100: Das Dateisystem der EFI-Systempartition überprüfen
2013-12-25 14:36:22 +0100: Alle Loader-Speicherplätze von HFS-Datenpartitionen überprüfen
2013-12-25 14:36:22 +0100: Startpartitionen werden überprüft
2013-12-25 14:36:22 +0100: Startpartition disk0s3 wird überprüft
2013-12-25 14:36:22 +0100: Dateisystem prüfen
2013-12-25 14:36:23 +0100: HFS+ Volume (Journaled) überprüfen.
2013-12-25 14:36:23 +0100: Zusatzdatei für Dateiaufbau wird überprüft.
2013-12-25 14:36:23 +0100: Katalog wird überprüft.
2013-12-25 14:36:23 +0100: Multi-Link-Dateien werden überprüft.
2013-12-25 14:36:23 +0100: Kataloghierarchie wird überprüft.
2013-12-25 14:36:23 +0100: Datei für erweiterte Attribute wird überprüft.
2013-12-25 14:36:23 +0100: Volume-Bitmap wird überprüft.
2013-12-25 14:36:23 +0100: Informationen des Volumes werden überprüft.
2013-12-25 14:36:23 +0100: Unbenutzte Blöcke trimmen
2013-12-25 14:36:23 +0100: Das Volume „Recovery HD“ ist anscheinend in Ordnung. ( < the green line)
2013-12-25 14:36:23 +0100: Reparatur des Volumes abgeschlossen.
2013-12-25 14:36:23 +0100: Boot-Support-Partitionen nach Bedarf für das Volume aktualisieren.
2013-12-25 14:36:23 +0100: Boot-Support-Loader überprüfen
2013-12-25 14:36:23 +0100: Partitionen des physischen Core-Speicher-Volume überprüfen
2013-12-25 14:36:23 +0100: boot.ini-Dateien von Windows werden nach Bedarf aktualisiert
2013-12-25 14:36:23 +0100: Die Partitionstabelle ist anscheinend in Ordnung.
2013-12-25 14:36:23 +0100: 

2013-12-25 14:36:29 +0100: Volume „Macintosh HD“ überprüfen
2013-12-25 14:36:29 +0100: Überprüfung wird gestartet:
2013-12-25 14:36:29 +0100: Dateisystem prüfen
2013-12-25 14:36:29 +0100: Live-Verifizierung durchführen.
2013-12-25 14:36:29 +0100: HFS+ Volume (Journaled) überprüfen.
2013-12-25 14:36:29 +0100: Zusatzdatei für Dateiaufbau wird überprüft.
2013-12-25 14:36:29 +0100: Katalog wird überprüft.
2013-12-25 14:36:36 +0100: Multi-Link-Dateien werden überprüft.
2013-12-25 14:36:36 +0100: Kataloghierarchie wird überprüft.
2013-12-25 14:36:46 +0100: Datei für erweiterte Attribute wird überprüft.
2013-12-25 14:36:48 +0100: Informationen des Volumes werden überprüft.
2013-12-25 14:36:48 +0100: Repariert:
2013-12-25 14:36:48 +0100:

----

After doing the same check multiple times on "Macintosh HD" I finally got that green line - this looks like the SSD / HDD is broken, doesn't it?

 

[Mr. Retrofire]

It is possible that some software is not compatible with Mavericks. If you have additional file system drivers or anti virus software on your machine, remove the software, restart and see what happens!

What says the S.M.A.R.T. information in Disk Utility? See also:
http://support.apple.com/kb/PH7029

 

[murphychris]

If you're reproduced this since the most recent reboot, post the results from 'sudo dmesg'. And the easier of a.) creating a Fedora 20 live desktop USB stick using 'sudo dd if=<pathtoISO> of=/dev/diskX bs=32k' where X is the number for the USB stick which can be found with 'diskutil list'. This command will destroy all data on the USB stick. Once you see the Fedora Media option choose that, and then navigate the following menu to, I think, Troubleshooting, and choose the option to use basic video. Navigate around to get to Utilities then to the Terminal application and issue 'su' to get to root, then 'yum install smartmontools' to install smartmontools. Note that it goes away on reboot, it's not being installed to persistent storage. You'll need an ethernet connection to avoid dealing with wireless firmware installation. Next, 'smartctl -x /dev/sda' which will spit out a pile of information about the drive that can be copy/pasted into gedit, save it out as a text file, and using FireFox you can attach it to this forum thread. The advantage of this adventure is that the linux kernel has full SATA passthrough and so in addition to SMART info we also get PHY Event counters which might be revealing.

The alternative, option b.) is to install XCode and MacPorts and build yourself smartmontools on OS X. But no PHY Event counters.

Thing is, if it were bad RAM or a flakey drive, I'd expect chaos. The manifestation of problems would be inconsistent. And you'd almost certainly have massive file system corruption. It does seem more likely some process is cleaning up files.