In case of a “Memory is insufficient!” Error, you need to update first to the intermediate firmware version, and then to the latest one. We also watch it on the link above. For example, when I stitched the DES-3200 C1 on 4.46, then the intermediate version was 4.38.000.
If it does not work, then the problem is more likely with a tftp server or a firewall that can block access.
To check the availability of ip, you can ping directly from the switch:
At the time of firmware upgrade, it is not possible that the power to the switch has disappeared, otherwise it may not start.
When the firmware file is uploaded to the switch – we will reload it with the command:
The switch will boot with the new firmware version, the configuration in my case has not been changed.
Switch DES-3200-28F from version 4.46 to 4.48 I updated the firmware as follows:
2) Register a static IP address to the computer, for example 192.168.88.254
3) Connect the Ethernet cable to the router through the ETH1 port with the computer using the switch or directly.
4) Run the NetInstall application. Click the “Net booting” button, check “Boot Server” enabled and enter the IP address from the same subnet where the computer is located, for example 192.168.88.200, its NetInstall will temporarily assign it to the router. Any firewall on the computer must be disabled.
5) When the router is disconnected from the mains, press the “reset” button and continue to turn it on, wait for about half a minute until the NetInstall program displays a new device in the device list.
6) In “Packages”, click the “Browse” button and specify the directory with the firmware. In the list of devices (Routers/Drives) select a router, in the bottom of the list, tick the firmware to be downloaded to the router and click “Install”. The firmware is downloaded to the router and the status will be written “Waiting for reboot”, after which, instead of the install button, there will be a reboot button, and you will need to click it.
The router will boot with the new firmware. If there are any problems with the loading of the router, you can try to reset it to the standard settings by holding the reset button, or if there is a display, select “Restore settings” and enter the standard pin code 1234. Alternatively, restore via Netinstall with the tick “Keep Old Configuration” and indicating below your “Configure script”.
Updating the MikroTik firmware is easy enough, just open the web-interface of the device or WinBox, select “System” – “Packages” from the menu and click “Check For Updates”, if a new firmware is found, then click “Download & Upgrade”. The device will download the firmware from the official website and starts from it.
To flash MikroTik devices not to the newest version, or when the device does not have access to the Internet, I propose the following:
1) Download the firmware from the official website https://www.mikrotik.com/download
2) Connect via WinBox (not through the web interface!), Select “Files” in the menu, a window will appear, just drag the firmware file with the *.npk extension and wait for the file to upload.
3) Reload the router. It will have to start with a new firmware.
To downgrade the firmware version, you need to perform steps 1 and 2, then connect to the device via telnet and run the command:
On the test, I installed a clean Ubuntu Server 18.04, during the installation, the system automatically split the disk into one main /dev/sda1, which already had /boot files.
Since I did not have a system with /boot on a separate partition, I transferred it to a separate one and described the process in this article – Transfer /boot from a main partition to a separate partition
Today, I’ll give an example of moving /boot from a shared partition to a separate partition.
For the test, you can connect a new disk or use the first partition on any disk, for example, with a size of 512MB.
Once I noticed the following error in the file /var/log/proftpd/proftpd.log:
error: unable to open passwd file ‘/etc/proftpd/ftpd.passwd’: Permission denied
As it turned out, the rights to the file were 440 and the owner and group were specified as root
Let’s look in the file /etc/proftpd/proftpd.conf, from which user ProFTPd works, by default from the user proftpd:
Just in case, we will specify the correct rights to the files (if they are other, then ProFTPd may not start):