1021
Storage / Re: Chkdsk log formatter
« on: October 27, 2018, 11:49:14 pm »
It might be possible that it will still start. But you will no longer be able to run chkdsk to clear up any potential errors because chkdsk.exe will abort operation if it finds something wrong with the transaction log.
That's really unfortunate (I think it would be better if chkdsk completely wiped the transaction log if it gets corrupted).
But now you might have some lurking errors. I had the very same, including these unexpected system restart. I never realized there was something wrong with my JFS partition (because the transaction log was fine) until I finally ran chkdsk /F:3 from another partition. A whole bunch of errors turned up and I had about 400 MB of crosslinked files (fortunately, that was basically a source file tree that I had cloned from a GITHUB repo which I could just reget).
But after that, the JFS partition was in an errorfree state.
The only thing I can suggest is that you save the files to another partition/media and reformat the JFS partition.
That's really unfortunate (I think it would be better if chkdsk completely wiped the transaction log if it gets corrupted).
But now you might have some lurking errors. I had the very same, including these unexpected system restart. I never realized there was something wrong with my JFS partition (because the transaction log was fine) until I finally ran chkdsk /F:3 from another partition. A whole bunch of errors turned up and I had about 400 MB of crosslinked files (fortunately, that was basically a source file tree that I had cloned from a GITHUB repo which I could just reget).
But after that, the JFS partition was in an errorfree state.
The only thing I can suggest is that you save the files to another partition/media and reformat the JFS partition.