An Error detected, fails capture
-
This post is deleted! -
@Tom-Elliott @adam1972 Thank you so much for getting back to me…
the efsck shows clean…
Debug mode? This is what I see… I used the FOG menu item.
Should I be using a different option?
-
@adam1972 that is the debug shell, you can try the efsck command in debug mode then use the command ‘fog’ to step through the capture process
-
Hello eveyone
Anyone have any idea or suggestions?
I would prefer to have it shrunken than the full size if possible
-
@JJ-Fullmer Thank you for trying to help
If you notice the third image -->
I did, The blue colored prompt at the bottom of the image was the only thing that would happen after i had chopsen the “fog” option.I also did the efsck before hand (1st image)–>
-
@adam1972 you should run the e2fsck command FROM the blue window
and you should reschedule your task, but with the debug option.
-
@Tom-Elliott What do you mean from the “Blue Window”? I ran it from an external usb as /dev/sda2 is mounted with system files (and it was the only way I could find to do it with many many online searches).
I did reschedule the tak, I created one specifically with the debug -->
That is what i got… i chose the Fog option and it gave me a “Variable dump” from FOG… It states "Press [Enter] key to continue… which I did and all I get is a blue prompt…
-
@Tom-Elliott You mean like this?
This is the debug capture… with the FOG option selected… -
@adam1972 With the task in debug now, that you’ve done the e2fsck:
Now runfogfrom the blue prompt and it should run though the normal process just pausing as it goes along. -
@Tom-Elliott I did it before your response… I saw it was the same results as I had done through root using an external boot device… Oddly though, once it completed I restarted the job normally and it actually COMPLETED!!! THANK YOU SO MUCH!!!
-
@adam1972 So when you’re in a debug mode, or in a fog task in general, you’re booted into FOS (Fog Operating System) which is the same idea as booting from an external disc/drive. The idea being you’re not mounting and booting from your disks that you are capturing/deploying from/to. So after the efsck came back as clean from where FOS could see, it makes sense that it would work as expected right after.
This probably won’t happen every time you capture, if it does then there’s something you’re doing in preparing the image that is causing the dirty bit to be flagged on the disk, there is likely a way around that, I don’t know off the top of my head for Linux what that might be. But we can figure it out if the problem recurs. -
[[undefined-on, A adam1972, ]]
-
@JJ-Fullmer Good to know, thank you so much
