Register for the iXsystems Community to get an ad-free experience and exclusive discounts in our eBay Store.

TrueOS lo0 is not up on Trident 19.6 boot

Joined
May 11, 2019
Messages
19
Thanks
0
#1
Hi, this issue is still opened from my previous topic, being helped by JG in understanding what went wrong after the last system upgrade which left some functionalities broken/unavailable.
After sending the command "ifconfig lo0 127.0.0.1 up" in a terminal as root, everything comes back working fine.
But this is limited to the opened session, I lose it on next reboot.
I would need a kind help from who could tell how to get the lo0 up permanently.
Thank you
 
Joined
May 11, 2019
Messages
19
Thanks
0
#3
Project Trident Information
--------------------------------------
OS Version: TOS-19.06
Build Date: Wed Jun 26 18:16:40 CEST 2019
Boot Type: UEFI
--------------------------------------
TrueOS Sources Used:
Base Repository: https://github.com/trueos/trueos
Base Commit Branch or Tag: v2019062000
Ports Repository: https://github.com/trueos/trueos-ports
Ports Commit Branch or Tag: 8bcaaa24672bb45f4df9044200668b0b7c833c01
--------------------------------------
System Specs:
Boot Method: UEFI
Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
Physical CPUs: 4
Physical Memory: 15.87 GB
--------------------------------------
X11 Information:
X11 Configuration File: /usr/local/etc/X11/xorg.conf
X11 Driver Running: modesetting
radeon
--------------------------------------
GPU Information:
vgapci0@pci0:0:2:0: class=0x030000 card=0x80c2103c chip=0x16168086 rev=0x09 hdr=0x00
vendor = 'Intel Corporation'
device = 'HD Graphics 5500'
class = display
subclass = VGA
vgapci1@pci0:13:0:0: class=0x038000 card=0x80c2103c chip=0x66601002 rev=0x83 hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]'
device = 'Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile]'
class = display
--------------------------------------
Network Device Information
re0@pci0:7:0:0: class=0x020000 card=0x80c2103c chip=0x813610ec rev=0x07 hdr=0x00
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL810xE PCI Express Fast Ethernet controller'
class = network
subclass = ethernet
 

Rod Myers

FreeNAS Aware
Joined
Feb 9, 2015
Messages
77
Thanks
25
#6
did you pay attention to the upgrade notice?

sounds like you did not, which is why your /etc was overwritten
 
Joined
May 11, 2019
Messages
19
Thanks
0
#7
Hi Rod, I had considered your question on my previous topic where you had highlighted I did not pay attention to that notice, but the correct situation has been recovered after followed the specific suggestions received there. As far as I can tell, this issue is the only oddity to be corrected.
Thanks
 

groenveld

FreeNAS Aware
Joined
May 10, 2019
Messages
94
Thanks
28
#8
Hi Rod, I had considered your question on my previous topic where you had highlighted I did not pay attention to that notice, but the correct situation has been recovered after followed the specific suggestions received there. As far as I can tell, this issue is the only oddity to be corrected.
Thanks
Easy way to debug...
Revert back to your pre-19.06 BE where lo0 is correctly configured on boot.
# beadm activate WORKING-BE
# shutdown -r now
Confirm lo0 is correctly configured, then...
# pkg upgrade pkg sysup
Then update to 19.07...
# sysup -update


John
groenveld@acm.org
 

groenveld

FreeNAS Aware
Joined
May 10, 2019
Messages
94
Thanks
28
#9
A near worthless datapoint:
I have one stationary workstation with an IP address assigned via /etc/rc.conf that fails to configure its network interface on boot.
This system was upgraded via an updated sysup.

When I can get on console I'll be able to provide more worth.
John
groenveld@acm.org
 

Rod Myers

FreeNAS Aware
Joined
Feb 9, 2015
Messages
77
Thanks
25
#10
A near worthless datapoint:
I have one stationary workstation with an IP address assigned via /etc/rc.conf that fails to configure its network interface on boot.
This system was upgraded via an updated sysup.

When I can get on console I'll be able to provide more worth.
John
groenveld@acm.org
On the upgrade from 1906 and earlier, there was an announcement in the GUI client, where you need to for update sysup, so it WOULD NOT overwrite the /etc folder
 
Joined
May 11, 2019
Messages
19
Thanks
0
#11
Easy way to debug...
Revert back to your pre-19.06 BE where lo0 is correctly configured on boot.
# beadm activate WORKING-BE
# shutdown -r now
Confirm lo0 is correctly configured, then...
# pkg upgrade pkg sysup
Then update to 19.07...
# sysup -update
ok now its fine! I did step-by-step what you wrote above, and all is working, including lo0 connection.
Thank you
 
Joined
May 11, 2019
Messages
19
Thanks
0
#12
On the upgrade from 1906 and earlier, there was an announcement in the GUI client, where you need to for update sysup, so it WOULD NOT overwrite the /etc folder
Ok Rod, I understood that I should have paid attention to that notice, and now everything is working as it is supposed to, after applied John's indications.
My hint to devs (as a basic user) for next time is : find a way to disable the upgrade by GUI if you're sure it won't go right, many ones like me could miss the notice. For those ones, better doing nothing and let them inform on separate way how to upgrade, otherwise they will upgrade anyway, and spend days in understanding what's wrong.
This in my humile opinion.
Thanks
 

Rod Myers

FreeNAS Aware
Joined
Feb 9, 2015
Messages
77
Thanks
25
#14
well, if you all would care to assist in the future, I'm sure it would be greatly appreciated.

But sine this is a 3 man operation, one has to prioritize items. Hand holding is not in the top 100 of things to do
 
Top