I have only 8 hours to fix it!
I moved the hard disk to a more proper server hardware, but nsdc dind’t start. I moved it back to old hardware – and it still doesn’t start.
I’m afraid to resolve it: what if it is going to overwrite something else? I also noticed that I don’t have br0 interface but only brdef.
Is there a way to rename it to br0?
I found that some time ago I enabled Nethserver Config backup. So, I restored it. All services are running well. All interfaces are OK. Br0 is back. Users list is back. But, the windows machines can’t find domain controller to login. Admin tools on windows say that “server is not operational”.
Well… actually, now that I’m recalling how I installed Nethserver…
Yes! I installed in on the latest AMD Ryzen CPU/Motherboard. It was an adventure:
Have two HDDs in your Ryzen PC
HDD 1 – install modern UBUNTU
Install VirtualBox (don’t forget to enable virtualization in BIOS)
Find out HDD2 path (for me it was /dev/sda )
Add your user to two groups: disk and virtualbox
reboot
Create a linking virtualbox file to physical HDD2
Create a virtual machine without Storage
Add physical HDD2 in virtualbox
Install NethServer on physical HDD2 in virtualbox
Install new kernel in NethServer
Shutdown
Remove Ubuntu HDD and leave only NethSever/VirtualBox HDD2
Boot NethServer on Ryzen!
So… yeah… Virtualization is cool… But my real server hardware (not the desktop Ryzen thing) is real server MB+ server CPU + server RAM + server case + server power supply… I have to move to it. And I’d prefer to do it without virtualization. It’s an entry level server hardware, so slowing it down even more with virtualization is not an option.
Using an entry level server is not an issue, I have several customers using such an environment, I also have 1 of 3 Proxmox at home also on an 8 year old HP Proliant ML110 (also entry level server).
I recently installed Proxmox, NethServer, OPNsense and a LXC with Debian on a Quad Core Atom! And I was impressed how swift everything worked. If you had asked me two months earlier, I’d have said: no way!
Maybe you don’t know it, but certain tasks can run faster virtualized than on native.
An example, install any Linux on your hardware, and compile the whole Linux kernel.
It will take it’s time, sure.
Then install any virtualizer Host on the same hardware, and inside install again your same Linux, but now virtualized.
This will also take it’s time, but will be faster than above, running natively on the same hardware…
Usually 5-15% faster!
Why is this so?
Two levels of caching, is one reason, there are more…
Disaster recovery on native hardware: Always issues with NICs, Controllers for Disk.
Virtualization: Rock-Solid and fast disaster recovery, on almost ANY hardware.
Move a fussy Windows from AMD to Intel - you get a nice blue screen.
Using Proxmox, I can migrate from AMD to Intel and back Intel to AMD - no issues!
Windows doesn’t even notice the difference of architures nor requires a new registration!
Some small advantages, and the main reasons why almost no knowledgeable person would suggest native installs anymore!
Just to finalize my adventure:
I was able not only to restore my strangely broken server settings (if you take your HDD and place it in a different hardware and then return it back – your configuration will be broken), but also successfully moved to the new hardware.
Configuration backup allowed me to specify what my new network interface was and corrected all … I mean ALL related configs with appropriate NIC name and MAC address. It was so good… now I know how to change the hardware.
Thank you for such a thoughtful config backup/restore procedure!
don’t wait so much time in front of the screen while restoring
