HT204435: Mac OS X: About file system journaling
Learn about Mac OS X: About file system journaling
-
All replies
-
Helpful answers
-
Nov 18, 2015 1:20 PM in response to Andrew9813by Andrew9813,Thank You all for your help i just double checked over the diskutil list and i chose the wrong identifier disk0s2 and my drive identifier was disk1 and now my hard drive is not journaled.
-
Nov 18, 2015 1:30 PM in response to Andrew9813by Barney-15E,Once again, stop typing in what you did and what came back and instead copy and paste it from the terminal. You don't have to take a screen shot. Just select the text, copy, and paste into a reply.
If you really used disk0s2, that is an odd reply as that is what you would have gotten from using just disk0.
Volume disk0s2 is the startup volume which cannot be disabled, at least while booted that drive. I don't know if it is possible at all.
Given that the volume is CoreStorage, it also may not be possible to disable. I'm trying to determine that, now.
do you no how to reenable disable journaling with the disk utility app.
There isn't a way in the current Disk Utility.
-
Nov 18, 2015 1:32 PM in response to Andrew9813by Barney-15E,Andrew9813 wrote:
Thank You all for your help i just double checked over the diskutil list and i chose the wrong identifier disk0s2 and my drive identifier was disk1 and now my hard drive is not journaled.
Then that answers both of my questions.
-
Nov 18, 2015 1:34 PM in response to Barney-15Eby Andrew9813,Yes I know how to enable journal command In disk utility app and terminal.
-
Nov 18, 2015 1:42 PM in response to Andrew9813by R C-R,Andrew9813 wrote:
Thank You all for your help i just double checked over the diskutil list and i chose the wrong identifier disk0s2 and my drive identifier was disk1 and now my hard drive is not journaled.
FWIW, I think you got the error message when using /dev/disk0s2 because your startup disk is set up using Core Storage (a way of creating virtual disks from one or more physical ones). Because of that, the physical disk "Apple_CoreStorage Macintosh HD 499.2 GB disk0s2" does not contain a file system, just like the error message said. The virtual disk "Apple_HFS Macintosh HD +498.9 GB disk1" does, which is why using "disk1" as the identifier works.
Confusing, is it not?
(Edited for typos)
-
Nov 18, 2015 1:55 PM in response to R C-Rby Andrew9813,Yeah I found it a bit confusing.
Hopefully they implement the file + option to disable and enable journaling in the disk utility app.
-
Nov 18, 2015 2:10 PM in response to Andrew9813by R C-R,Andrew9813 wrote:
Hopefully they implement the file + option to disable and enable journaling in the disk utility app.
They probably won't, since a journaled file system is resistant to data loss caused by system problems. You should not disable journaling on an HFS+ file system unless absolutely necessary.
-
Nov 18, 2015 2:13 PM in response to R C-Rby Andrew9813,I Only do temporarily to scan my computer for viruses with product called fixmestick. Enable when done scanning.
-
Nov 18, 2015 2:25 PM in response to Andrew9813by Barney-15E,Andrew9813 wrote:
I Only do temporarily to scan my computer for viruses with product called fixmestick. Enable when done scanning.
Perhaps you should ask them to make a product that doesn't require you to alter your system in order to work?
Does it ever really find anything that needs to be cleaned?
-
Nov 18, 2015 2:33 PM in response to Barney-15Eby Andrew9813,Hasn't found anything yet.
for the fixmestick that the only way for the usb fixmestick program to scan Mac computer.
-
Nov 18, 2015 3:05 PM in response to Andrew9813by R C-R,Andrew9813 wrote:
I Only do temporarily to scan my computer for viruses with product called fixmestick. Enable when done scanning.
From http://support.fixmestick.com/hc/en-us/articles/203456925-How-to-disable-and-re- enable-filesystem-journaling-on-Mac you do not need to disable journaling to scan them, just to "clean" them. Also note the following from that support article:
On the newest Mac OS X El Capitan, the option to disable journaling is unavailable. You will still be to run a scan on El Capitan, but you won't be able to clean your Mac. We are sorry about this and our engineers are currently working on a solution.
So more to the point, why even consider using a product like that when the maker tells you it can't "clean" a Mac running El Capitan?
To begin with, El Capitan has robust anti-malware capabilities built into it, including the new System Integrity Protection feature (SIP, for short), which make it very unlikely any malware could find its way onto your Mac or do any damage to it (unless you do something foolish like installing software from untrusted sources). Beyond that, there is some danger that booting your Mac from what is in effect a third party operating system that may not be designed for SIP compatibility could compromise that if it could "clean" the Mac.
-
Nov 18, 2015 3:13 PM in response to R C-Rby Andrew9813,I Found that same article about El Capitan. I may not use the product anymore since you said about SIP and I use trusted sources.
Thank You for your help today.
-
Dec 27, 2015 6:30 AM in response to Barney-15Eby el0n_mu$k,Does it ever really find anything that needs to be cleaned?
Fixmestick found three files in /library/Mail/.../Messages/:
- Trojan-Downloader.Win32.Updatre.eii
- Trojan-Downloader.Win32.Updatre.eii
- HEUR:Trojan.Win32.Generic
If fixmestick is still unable to clean user library, i will fix it manually. Hopefully it works. Are you sure that these files don't have an impact on my mac?
-
Dec 27, 2015 6:39 AM in response to el0n_mu$kby BobHarris,The "Win32" identification says it is a Windows trojan.
-
Jan 18, 2016 1:50 PM in response to [GoldenDrake]by glenn.randall09,Reformat the disk using diskutil
diskutil eraseDisk HFS+ Name /dev/disk4
If you want it journaled, use JHFS+ instead.