Using new fog kernel for client but got an error.

[yusrijamal]

Hi.

I got a machine DELL Optiplex 7440 which is not compatible with current kernel in fog 1.2.0. So what I did was download the latest kernel bzImage, bzImage32, init.xz and init_32.xz.

Now, when i did fog compatiility, both disk and network is passed. (network was fail on the old kernel).

But now i got other error.

“EXT4-fs (ram0): couldn’t mount as ext3 due to feature incompatibilities.
sd 5:0:0:0 alua: Attach failed (-22)
sd 5:0:0:0 [sdb] No caching mode page found
sd 5:0:0:0 [sdb] Assuming drive cache: write through
Starting logging: OK”

I tried few tips regarding ext4/3 but no luck. Seem like the second error message is different and I can t find similar error.

Anyone can help me?

[george1421]

You will want the latest kernel but the original 1.2.0 stable inits (virtual hard drive). The trunk version of the inits are not compatible with 1.2.0 stable because they expect additional information to be loaded that is not in 1.2.0 stable.

Your other option is to upgrade to the trunk version. Just be aware that this is a dev version and a bit unstable at times. I can say for absolute that the 7440/7240 works with the trunk version of FOG 1.2.0.

[Tom Elliott]

I don’t know that I understand this.

How is the message you’re seeing an error? It’s just informative.

@george1421 is correct, updating to a newer kernel should fix this for you, but even still, this is not an error that should be preventing things from happening.

[Sebastian Roth]

@yusrijamal said:

EXT4-fs (ram0): couldn’t mount as ext3 due to feature incompatibilities

That’s because we use ext4 in the newer inits but FOG 1.2.0 does not pass a kernel option to tell it so. This is just a warning and does not harm anything!

sd 5:0:0:0 alua: Attach failed (-22)

Read through this. Guess this can be ignored as well.

sd 5:0:0:0 [sdb] No caching mode page found

The message is harmless I reckon but I still wonder why it says sdb (second hard drive)?!?

Please do as advised. Try newer kernel with old init files. If that does not work you can still look into properly upgrading to trunk version to be able to image that new hardware.