Installed XEN package and Mt went down

RouterOS Beginner Basics
1

I installed XEN package on MT 3.17. On reboot, xen started showing various error mesasages.

MT booted up but unfunctional. I can log in using console. Tried to disable xen package, it is marked as scheduled for isabling but reboot cannot execute. It reports thatit cannot stop various sevices and that is it.

Afer forceful reboot, it agains hows the same XEN errors and i get to the same point, xen is scheduled for disable, but reboot cannot be executed?

What to do?

2
  1. Power down the router… :open_mouth:
  2. Remove ALL wireless and sync hardware. (All un needed hardware , Ethernet as well)
  3. Restart the router and double check thet the package is schedualed to be disabled.
  4. Reboot the router and verify the package disables.
  5. Set the XEN package for removal and reboot the router. (verify removal)..
  6. Power down the router… :open_mouth:
  7. Reinstall the removed hardware.
    :sunglasses: Reboot the router and verify the settings…

All will be good…

It fixed my old Tyan P4 based system..

3

Thanks, I already fixed a problem by simply installing MT again on hard disk with option Save current configuration.

It did not save configuration (all options were reset), but it saved licence info, which was my main concern. I had configuration backup which I saved before installing package, so I just uploaded backup, restored it and router was functional again.

So, everyone to know, be careful with XEN package, it may crash your system to the ground.

4

Pedja, I had this same problem. Can you kindly explain it to me in a simple way? Is the (option Save current configuration) means this question: “do you want to keep old configuration?” ? Thanks!

5

Sorry for double post…thanks to Pedja’s posts so now my MT can live again. :smiley: the solution for this problem is: install the ROS using ROS CD with the same version and dont install the XEN package, when the installer ask you to “keep old configuration?” choose yes… and continue. your MT will run smooth again with the same license. I post this just to make the solution clearer. Thanks Pedja once again! Cheers!

6

No prob. I am glad I helped.

This licence locked to disk volume can be very frustration. One wrong step and you detroy the licence.

I have the other disk with licenced MT that was crashed because motherboard recognized it with wrong PIO. I am still looking for a way to handle it and not loose the licence.

7

save configuration is fixed in 3.18 on cdinstall and netinstall (fixed from 3.17)

wireless interfaces working on xen hosts (fixed from 3.17)

about loosing license - if configuration of sata differs then sof-id might change in some occasions, otherways, if you use cdinstall and netinstall you should not loose license.