DEC3860 mini-USB Console

[Mbl]

Hmmm just checked one of the latest backup files and have found this:

Code Select Expand

<disableconsolemenu>1</disableconsolemenu>

Looks like I have disabled console once in the past (even if I don't why I should have done this  ::) )

[Patrick M. Hausen]

Shouldn't that just present a login prompt instead of the menu?

Franco?

[Mbl]

Shouldn't that just present a login prompt instead of the menu?

Franco?

Yes you're probably right. But I don't even get the promt

[Mbl]

Hmmm just checked one of the latest backup files and have found this:

Code Select Expand

<disableconsolemenu>1</disableconsolemenu>

Looks like I have disabled console once in the past (even if I don't why I should have done this  ::) )

@Franco, is there a way (hack) to enable console without web or SSH access?

[franco]

Look, login(1) doesn't work. Whether it lets you auto-login or prompt for a user/password both of these things don't work if login(1) doesn't have a console to attach to. It could even be that the /etc/login.conf is trashed which is rare but it can happen. Manual recovery or troubleshoot of damaged file systems is difficult. Reinstall from an image with config import is a quick and easy recovery mechanism.

Still the question is if 22.4 serial stick behaves the same way and if maybe a 21.10 stick would not have these issues (different FreeBSD version).

And to stress that point: the "serial" image use is important here.


Cheers,
Franco

[Patrick M. Hausen]

You could still boot single user and try to find out what's disabling the login prompt. You'll need quite a bit of FreeBSD experience, though, and I doubt this can be solved by question/answer ping pong via the forum in a reasonable amount of time.

Booting from an install/live medium to check if the serial console works *at all* is probably a good idea. And a way to a rescue procedure - boot into live mode, manually mount the installed system drive, copy the config.xml and look for hints what went wrong. Then sanitize the XML config, reinstall, reimport ...

[Mbl]

Thanks for your replay Franco - very appreciated!

I have booted from serial USB image and console works well.

I know whats wrong on the config.xml to make the system working again. So would it not be possible to mount the local disk into the USB life environment or single user (as pmhausen mentioned), make manual changes on config.xml and boot again from local disk?

What type of device should I look at for the local disk on the DEC3860?

[franco]

When having booted the stick go to console (option 8) and type

# opnsense-importer -m

It'll list the devices to attach to and mount it for you and execute  a shell for manual repair. It's going to tell you where the disk is mounted. Inside that directory under $DIR/conf/config.xml is the file to edit. Then type "exit" and reboot the stick. If it was the config.xml change the system should come back fine.

If not there are backups under $DIR/conf/backup/ that might help shed some light on what change was done when.

In any case fingers crossed. :)


Cheers,
Franco

[Mbl]

System up and running!  :)

I have SSH and web access to the firewall again.

Strange that console is still not working. In config.xml I have chnaged

Code Select Expand

<disableconsolemenu>1</disableconsolemenu> to "0". Looking at the GUI (see attached print screen) it should be enabled from my point of view.

BIOS has been set to UART Configuration Options --> UART 0 Legacy Options. Going to remove "hw.uart.console" and reboot and will report back...

[Mbl]

Was to fast.

Code Select Expand

hw.uart.console does not even exist on my system

[franco]

USB-base serial ports setting is wrong. This is for directly connected USB consoles, not adapters that expose USB connectivity.

Pretty sure that's the issue (image defaults to off).


Cheers,
Franco

[Mbl]

USB-base serial ports setting is wrong.

This did the trick. It's working now...

Thanks again for your superbe support!

[franco]

Yay, happy to help :)


Cheers,
Franco