to day after long years ago, again met the famous GMal error. But this time not -04 but 02. what is the difference. I have read what Todd tell us about error -04. solution for this is installing windows 10 64 bit 1809_1776_379 again and after that ISR 2.4 Then loading the .arx file. costs lots of time. is there a better solution for this ?
The only time I've seen this error (10 years back) I could not fix it... (it lead to a corrupt partition)
Pandlouk, i know you where busy with that error. I Thought Raxco has found a solution for this in the update to version 2.4. So the only thing we can do , start whole over again. But we have the .arx files, and that helps shorten the time. Frits
did this happen after an w10 upgrade? Have you tried uninstalling (program only), reinstalling and reimporting/updating the snapshot from the archive? Panagiotis
Panagiotis, or this happens after a W10 update, i don't know. It is to long ago. I do know, i regulary update W10. Now i have version .503 Uninstalling the prgr was impossible, then i had to have access it first. Could i do that via the CLI ? When i could have access to the Instantrecovery control , it is possible. Couldd i have this .exe file on a other USB appart to run it.? In my opinion it is not possible. Frits
I don't know if it can be uninstalled from the command line. By the way raxco has published a complete list of code errors ftp://ftp.raxco.com/pub/Download/InstantRecovery/UserGuides/InstantRecovery_Error_Codes.pdf File System Error: GMAL-02 Invalid MFT record The MFT attribute offset has overflowed the record. The likely cause is a corrupt file system resolution = Run CHKDSK /F /R Panagiotis
Panagiotis, never know that Raxco published such a list. SO THANKS VERY MUCH. I did't know it could give so much errors. so excecuting CHKSK on a separate repair disk could solve the problem. I do have a repair disk EASYRE for Windows 10. But this EASYRE could not work together with ISR. i think the vectors for all the windows snapshots are on a other place. So i have to use a seperate CD with CHKDSK on it. I could also use the W10 installation disk , and jump to CLI , and find CHKDSK there. But finally I do hope , it takes years for GMAL errors to popup. thanks ! Frits Egelie
looked to CHKDSK: /F Fixes errors on the disk. /R Locates bad sectors and recovers readable information (implies /F, when /scan not specified). Will this also work with SSD drives. Bad sectors could also be repaired with Spinrite 6.0.
Frits, I ususally run chkdsk /f .It is enough to locate and fix file problems, unless I suspect that files disappeard from the partition Yes it works in ssds too. Spinrite is way to slow for my taste.
I know for years now of the existence of chkdsk, but never used it. I thought that the Gmal error was a sort of buffer overflow error. So, never thought on file error or something else. So, Gmal errors could be repaired with CHKDSK. ( some of them) Frits
