This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM hangs during boot sometimes - "udev: starting version 147"

Hi,

I have a problem with my UTM 9.403-4 (now) since about three months. When I reboot the UTM it hangs and shows "Sophos UTM - Press F2 for details" on the screen often. The UTM doesn't recognize any keypress or power-off button in this state. I have to unplug the power cord and plug it in again. Mostly the UTM boot fine after that. Sometimes it hangs again for one or two more times.

Today I rebooted the UTM and pressed F2 right after the "Sophos UTM" screen appeared. I had "luck" because the UTM hung again. But now I saw the boot log and where the UTM hung:

"udev: starting version 147" is the last entry on the screen. No idea what it means, if this is the problem (because at the end there is a green "done") or if the following action is the problem.
I reproduced this hang two times to be sure, that the error occur at the same point every time.

When the UTM boots up fine, it runs without any problems.

Today I re-installed the UTM (but import my old configuration) and reseted the BIOS setting, but the problem occured again after the second reboot. :(

Has anyone a idea what this could be and how to solve it?

Thank you!

Jas Man



This thread was automatically locked due to age.
  • Must have to do with ACPI because....

    1. I found a article in the Internet which described this problem. But in this article the system hung every boot at the same point. The solution was to enable ACPI in the BIOS.

    2. I found the boot log in the WebAdmin interface. After a successfull boot the next entry after "udev..." is "ACPI: Requesting acpi_cpufreq"


    Was there a change regarding ACPI in the Linux distribution of the UTM? I never had this problem since I have my UTM running (about 1 year).

  • The problem did not occur anymore since the last three months. Hope that it was solved by Sophos. Hope that it was solved by Sophos in one of the last updates... :)