I haven't given up yet, but it's very possible this is the case. It may ultimately be that because USB is loaded so late in the kernel boot process, anything more than just basic login capability is a lost cause. My Mikrotik gear is the most reliable stuff in the house, so it makes sense to use this as the pivot point (I even use this for my VPN rather than a VPN container in unRAID). You may ask "what is the point since you can just walk up to the monitor and login via keyboard" but if I'm away from home and my unRAID server barfs, the ability to connect to it via serial through my Mikrotik router using Serial Terminal means I can kick it in the pants even without fancy stuff like an iLO card. I am still looking into whether I can get kernel events posted to the USB serial console but for now this should help anyone who would like to restart their unRAID server even if network connectivity gets lost due to a NIC module errors or macvlan callbacks that kill the network stack.
PUTTY FOR MAC SERIAL CONSOLE DRIVER
There's a couple of issues with even trying to do this, including the fact that the USB driver loads quite late in the boot order and so you won't see a whole bunch of boot messages anyway. What it won't do is let you see kernel messages via the serial port. Note that my device is ttyUSB0 and it's set to 115200 baud rate as I'm connecting from a Mikrotik router. Getting the ability to login via the USB to serial adapter only requires the addition to the /boot/config/go file as follows:
PUTTY FOR MAC SERIAL CONSOLE UPDATE
To update this topic for those using USB serial adapters (which I assume is realistically most of us), so far I have not managed to get kernel boot and shutdown messages to show but you can at least get the ability to login via the USB serial port.Įssentially, you don't need the "SERIAL 0 115200" line, nor the changes to the "append" line" at all to get the ability to login via the USB serial adapter. If the system refuses to boot, you'll need to reconnect the keyboard/monitor and poke around in the bios to look for a setting called "Halt on error" and disable it (depending on your specific bios it may be called something else) Again, you should see the entire boot process (starting with the unRAID boot menu) using Putty. If you want to run headless, disconnect the keyboard and monitor and reboot. You should be able to login using either the connected keyboard (if there is one) or using Putty. When you reboot the system, you should see the entire boot process on both the connected monitor (if there is one) and on the serial connection using Putty. The whole section will look something like this (it could be different depending on what other customizations you have made) label unRAID OSĪppend initrd=/bzroot console=ttyS0,115200 console=tty0 At the top of the Global Configuration section add: SERIAL 0 115200įind the "append" line in the "label unRAID OS" area and add this to the end of the line: console=ttyS0,115200 console=tty0.In the unRAID webgui, go to Main -> Boot Device -> Flash -> Syslinux Configuration.Sed -i -e "s/^#ttyS0/ttyS0/" /etc/securetty It won't hurt anything though) # setup serial console (Note that the line that mentions /etc/securetty is not needed from somewhere around 6.8.3+. Add the following lines to the end of your /boot/config/go script using a good text editor like Notepad ++ (be sure to save the file with unix line endings, not Windows).Once you've got the basic connection working, let's make it permanent.
0 kommentar(er)
