Journaling suddenly disabled

[WaldMeister]

Hi,

 

I had Yosemite 10.10.4 installed on a Mac OS Extended (Journaled) partition.

During a reboot fsck started, stated that it could not check/restore the disk, and the notebook shut down.

 

I migrated my user account to an external installation, and see in disk utility that journaling is disabled. The option to enable it has been grayed out. Restoring the partition does not work.

 

Any idea how i can find out what happened, i only rebooted the normal way. And can i somehow change the partition flags or just reinstall? 

 

[WaldMeister]

Found a solution for this. 

sudo fsck_hfs -r /dev/disk0s2

Which returned the following:

** /dev/rdisk0s2
   Executing fsck_hfs (version hfs-285).
** Checking Journaled HFS Plus volume.
   The volume name is Yosemite
** Checking extents overflow file.
** Checking catalog file.
** Rebuilding catalog B-tree.
   Invalid node structure
(4, 19702)
** Rechecking volume.
** Checking Journaled HFS Plus volume.
   The volume name is Yosemite
** Checking extents overflow file.
** Checking catalog file.
   Missing thread record (id = 2568478)
   Incorrect number of thread records
(4, 20119)
   Incorrect number of thread records
(4, 20119)
** Checking multi-linked files.
** Checking catalog hierarchy.
   Missing thread record (id = 2568433)
   Invalid directory item count
   (It should be 0 instead of 3)
   Missing thread record (id = 2568446)
   Invalid directory item count
   (It should be 0 instead of 1)
   Missing thread record (id = 2568478)
   Invalid directory item count
   (It should be 1 instead of 3)
** Checking extended attributes file.
   Incorrect number of extended attributes
   (It should be 546647 instead of 546641)
** Checking volume bitmap.
   Volume bitmap needs minor repair for orphaned blocks
** Checking volume information.
   Invalid volume free block count
   (It should be 24306104 instead of 19336776)
   Volume header needs minor repair
(2, 0)
** Repairing volume.
GetCatalogRecord: No matching catalog thread record found
GetCatalogRecord: No matching catalog thread record found
GetCatalogRecord: No matching catalog thread record found
GetCatalogRecord: No matching catalog thread record found
GetCatalogRecord: No matching catalog thread record found
GetCatalogRecord: No matching catalog thread record found
** Rechecking volume.
** Checking Journaled HFS Plus volume.
   The volume name is Yosemite
** Checking extents overflow file.
** Checking catalog file.
** Checking multi-linked files.
** Checking catalog hierarchy.
** Checking extended attributes file.
** Checking volume bitmap.
** Checking volume information.
** The volume Yosemite was repaired successfully.

 

I still would like to know how to find out what happened.

 

Syslog lines before this all occurred: 

Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
May 27 16:02:49 lexhimself.nl emond[49558]: SetUpLogs: uid = 0 gid = 0
May 27 16:02:49 lexhimself.nl emond[49558]: SetUpLogs: opening /Library/Logs/EventMonitor/EventMonitor.error.log
May 27 16:02:49 lexhimself com.apple.xpc.launchd[1]: assertion failed: 14E26a: launchd + 83932 [099DDB51-875F-39F0-A880-93B7128E4687]: 0x11
May 27 16:02:49 lexhimself com.apple.xpc.launchd[1] (com.apple.emond): Service only ran for 0 seconds. Pushing respawn out by 10 seconds.
May 27 16:02:52 lexhimself kernel[0]: AppleSmartBattery::pollBatteryState: path = 1
May 27 16:02:52 lexhimself.nl powerd[53]: Failed to read current rating(0xe00002f0)
May 27 16:02:58 lexhimself.nl CoreServicesUIAgent[1430]: unexpected message <OS_xpc_error: <error: 0x7fff738ecc60> { count = 1, contents =
		"XPCErrorDescription" => <string: 0x7fff738ecf70> { length = 18, contents = "Connection invalid" }
	}>
May 27 16:02:59 lexhimself.nl emond[49590]: SetUpLogs: uid = 0 gid = 0
May 27 16:02:59 lexhimself.nl emond[49590]: SetUpLogs: opening /Library/Logs/EventMonitor/EventMonitor.error.log
May 27 16:02:59 lexhimself com.apple.xpÙÕù ¡c×ÿÿÿÿß1ã:
ûûª0w¨aQ%	House MD Seizoen 6 D 3.part073.rar
oO/Volumes/Opslag/alt.binaries.multimedia/House MD seizoen 8/`w¨`Q%	House MD Seizoen 6 D 3.part072.rarO/Volumes/Opslag/alt.b¨RQG%	House MD Seizoen 6 D 3.part058.rar¼O@/Volumes/Opslag/alt.binaries.multimedia/House MD seizoen 8/House MD Seizoen 6 D 3.part058.rarQw¨SQ%	House MD Seizoen 6 D 3.part059.rarÛO/Volumes/Opslag/alt.binaries.multimedia/House MD seizoen 8/Rw¨TQ%	House MD Seizoen 6 D 3.part060.rar2O/Volumes/Opslag/alt.binaries.multimedia/House MD seizoen 8/Sw¨UQ%	House MD Seizoen 6 D 3.part061.rarõO/Volumes/Opslag/alt.binaries.multimedia/House MD seizoen 8/Tw¨VQ%	House MD Seizoen 6 D 3.part062.rarZO/Volumes/Opslag/alt.binaries.multimedia/House MD seizoen 8/Uw¨WQ%	House MD Seizoen 6 D 3.part063.rarÇO/Volumes/Opslag/alt.binaries.multimedia/House MD seizoen 8/Vß2SQLite format 3@  µJã:µJ-âöûözÙ]%%tablehqx_decodershqx_decodersCREATE TABLE hqx_decoders (   file int UNIQUE,	data blob)7K%indexsqlite_autoindex_hqx_decoders_1hqx_decodersX-mtriggerdownloads_deletedownloadsCREATE TRIGGER downloads_delete DELETE ON downloads FOR EACH ROW BEGIN   DELETE FROM download_parts WHERE file = OLD.rowid;  DELETE FROM hqx_decoders WHERE file = OLD.rowid;ENDf3indexdownloads_group_idxdownloadsCREATE INDEX downloads_group_idx ON downloads (downloadgroup)Z1sindexdownloads_file_idxdownloadsCREATE INDEX downloads_file_idx ON downloads (file)w=tabledownloadsdownloadsCREATE TABLE downloads (   file int,   downloadgroup int,   newsgroup int,   name text,   size int,   parts int,   lastsegment int,   lastoffset int,   encoding int,   path text,   position int,   stringencoding int)S))ctableschema_versionschema_versionCREATE TABLE schema_version ( ver
	ß2pMay 27 18:47:26 localhost bootlog[0]: BOOT_TIME 1432745246 0
May 27 18:48:11 localhost syslogd[42]: Configuration Notice:
	ASL Module "com.apple.AccountPolicyHelper" claims selected messages.
	Those messages may not appear in standard system log files or in the ASL database.

Opslag is disk0s4.

[hodenhagen]

diskutil enableJournal /Volumes/YourDiskName/

[WaldMeister]

diskutil enableJournal /Volumes/YourDiskName/

Thanks, but this was not an option, somehow the partition was damaged on a reboot and the journaling was not recognized.