Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 7 subscribers
  • Views 3352 views
  • Users 0 members are here
Options
Suggested
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

Error during installation on ESXi

Jeff x

How can I determine the cause of this error:

/user/bin/tee: /dev/ttyS0: Input/output error

I get this when installing on ESXi 7.x. I do NOT get this error when I do a test install in VMWare Workstation 17.x.

Even with the error, the installation on ESXi continues and the resulting VM seems to be functioning without issue.



This thread was automatically locked due to age.
  • 0

    The /dev/ttyS0 is a serial port.  Do you need that?  I disable them, lol.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • 0 in reply to Amodin

    There's no physical serial port on the box nor is there one specified in the VM's virtual hardware settings.

    --------------------------------------------------------------------
    Sophos UTM 9.719-3 - Home User
    Virtual machine on Dell Optiplex 3070
    i3-9100 @ 3.60 GHz, 16 GB RAM
    --------------------------------------------------------------------

  • 0 in reply to Jeff x

    Are there no COM ports on it?  What hardware are you putting UTM on?

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • 0 in reply to Amodin

    Dell Optiplex 3070 SFF, no COM ports. ESXi is installed on the box.

    --------------------------------------------------------------------
    Sophos UTM 9.719-3 - Home User
    Virtual machine on Dell Optiplex 3070
    i3-9100 @ 3.60 GHz, 16 GB RAM
    --------------------------------------------------------------------

  • 0 in reply to Jeff x

    You can try:

    • Press [Alt]+[F2] to bring up the console window.
    • At the command prompt type cd /usr/lib and press [Enter].
    • At the next prompt type bootstrap --install and press [Enter]. 

    That should bypass hardware detection and install UTM.  Do it when your installer starts.

    ESXi might also be your issue.  I used to love that barebones OS, but I went to Proxmox and had so much better luck with things working.

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • 0 in reply to Amodin

    The installation completes even with that error. It's been running for several hours without any issues so I guess that error is nothing to worry about but I was hoping there was a way to find out what's causing it.

    This is the first time that I've installed the UTM in a virtual environment. I like the fact that I can now remotely install Sophos but I'm seeing CPU spikes which I don't get with fresh, bare metal installs even on much older, slower hardware. I don't have any other VM's on this box and I used pass-through for the NICs but it still feels wrong to put ESXi out on the edge ¯\_(ツ)_/¯

    --------------------------------------------------------------------
    Sophos UTM 9.719-3 - Home User
    Virtual machine on Dell Optiplex 3070
    i3-9100 @ 3.60 GHz, 16 GB RAM
    --------------------------------------------------------------------

  • 0 in reply to Jeff x

    Not a fan of that myself, I prefer a dedicated machine for my firewall.  I'll VM the hell out of a lot, but not my security.  ;)

    OPNSense 64-bit | Intel Xeon 4-core v3 1225 3.20Ghz
    16GB Memory | 500GB SSD HDD | ATT Fiber 1GB
    (Former Sophos UTM Veteran, Former XG Rookie)

  • 0 in reply to Amodin

    Speak of the devil... www.bleepingcomputer.com/.../

    --------------------------------------------------------------------
    Sophos UTM 9.719-3 - Home User
    Virtual machine on Dell Optiplex 3070
    i3-9100 @ 3.60 GHz, 16 GB RAM
    --------------------------------------------------------------------

  • 0 in reply to Jeff x

    Those infected probably hadn't secured the management access of their esxi server.

Unfiltered HTML