i was googling the problem a bit and i was curious, will it boot if you remove the raid card?
just trying to understand the source of the panic.

@Sebastian-Roth i understand the reasoning for not updating it. i’m hoping to have a chance to help with testing by the end of the week.

@george1421 i only brought it up because we’re updating ztsd for this build anyway, so i figured “why not have the latest one?”

@Sebastian-Roth FYI zstd 1.4.3 is out. it’s a just a bug-fix upgrade, and a bug that’s probably not relevant to our use case, but we should probably upgrade anyway.

@jondeong Just an FYI: the update to dev-branch would have updated the KERNEL RAMDISK SIZE for you to what is going to be the new size requirement. that was almost certainly the cause of the kernel panic.

@dolf FOG is image deployment software, not backup software. resizable is the default because that’s the most useful and common type of image capture to be used for FOG’s intended purpose. While, yes, FOG can be used to backup systems, it is not it’s intended purpose and we have encouraged people for years to not use it as such.

@Mokerhamer if you’re really wanting to push things to the limit, you might be interested in helping out with testing/development here: https://forums.fogproject.org/topic/13206/the-future-of-partclone-and-therefore-fog-as-it-is/105

the newest version of partclone will allow us to save images without checksums, decreasing the captured data slightly and increasing compress-ability. my initial testing says it will be about a 10% improvement on compression.

@george1421 i just want to chime in that those speeds seem completely normal to me. that’s what i was getting on a regular basis before i switched the VM host for my FOG server.

@george1421 all of what you said is true, but it just emphasizes the importance of benchmarking compression. with all of the variables that can come into play, the one thing you can usually rely on being consistent among peoples setups is 1GbE to the end client.

the maximum transfer rate on gigabit is well established, but what’s important is end result speed of writing to disk, and that’s what we can effect with compression methods.

btw, i wasn’t being grumpy. i just like to highlight how fast Fog can be. it’s one of Fog’s killer features that other methods can’t beat. (if anyone has seen a faster deployment method than Fog, please let me know.)