RB450G + ROS 5.14 + microSD = strange problem

Dear RouterOS community,

I have a big problem with my RouterBoard since I have update from RouterOS 5.7 to 5.13.
I noticed if I copy some files to the microSD card (1 GB Kingston) via SMB, after a reboot, all copied files are gone. If I do the same via FTP, after the reboot the files can be found on the card. In some cases the router cannot mount the card and the micro-sd folder is not visible in the file manager. This strage issue was not there in 5.7
I tired to update to the latest ROS 5.14 if it solves this problem, but I noticed that the copied files are cannot be found on the card after rebooting even if I copy them via FTP.
I suspect that changes are not written physically to the card before shutting down the system.
I tried a different microSD card, a 1 GB Samsung one, but the situation is the same.

Is my RouterBoard dying or is this a software issue? I tried cleaning my card’s and the router’s pins with a special contact cleaner spray to make sure that the card contacts properly. Of course, I have disconnected the board from the power source and used an ESD protector wrist strap.

If you would like to reproduce the problem, follow these steps:

  1. Install the latest RouterOS
  2. Connect to the router via FTP
  3. Copy some files to the microSD card
  4. Reboot the router
  5. After booting, check if the files are on the card

Another method for 5.13 via SMB:

  1. Create an SMB share on the microSD, for example: /micro-sd/smb
  2. Connect to this share and copy some files
  3. Reboot the router
  4. Check the files

In my case these steps bring up the problem.

I think the problem is identical to that one discussed in this topic: http://forum.mikrotik.com/t/rb433ah-and-micro-sd-card/41804/1

I have made some screenshots.
rb450g_after_smb_copy.PNG
rb450g_after_smb_copy_stores.PNG
rb450g_after_smb_copy_reboot.PNG

Another screenshots
rb450g_after_copy_manager.PNG
rb450g_after_reboot.PNG
rb450g_smb_setup.PNG

And I made supout.rif files.
supout_after_smb_copy.zip (226 KB)
supout_after_copy.zip (223 KB)
supout_after_reboot.zip (220 KB)

I found another symptom. If I create an SMB share in the root of the microSD and copy files to it, these files are not deleted after rebooting the router, but if I create a sub-folder it is deleted after a reboot including all its contents. So probably there is a problem with folder handling. The situation is exactly the same if I create the sub-folder via FTP. I made two supout.rif files (before and after the reboot).
supout_after_reboot.zip (198 KB)
supout_before_reboot.zip (202 KB)

Any update ? I appear to see the same issue on 4 different routers.

Soft Reboot will make the microSD disappear from the /system store

Power Reboot brings them back.

I have sent two supout.rif files last week and am still awaiting a response :slight_smile:

Still no updates and no response from support for me.

Edit: I just got an answer from the support:

Hello,

Sorry for the late response. The problem is found and we are working to fix it.

Regards,
Janis Becs

I also received a response yesterday and have provided some more info to Mikrotik on microSD model.

Mine are Sandisk C4 sdhc 4 & 8 GB models




If the post was helpful please give Karma :slight_smile:

Well I have had confirmation from Mikrotik support that the Sandisk C4 4 & 8 GB do not work for them either and no promise of a fix due to a hw limitation currently.

Same issue - fine on power up but gone after a soft reboot.

I tried a C2 1 GB and that worked ok so off to buy older slower microSD’s for me. :frowning:




If the post was helpful please give Karma :slight_smile:

There are two problems with similar symptoms in this topic:

  • The problem with lost sub-folders and files after reboot is software related and will be fixed in one of the next RouterOS releases.
  • The other problem with SanDisk SDHC Class 4 memory card initialization after reboot cannot be fixed in near future.

Unfortunately 5.15 didn’t fix issue with disappearing folders. When it is planned to make it work?

We will fix it for v5.16. Issue is confirmed.

Unfortunately it is not resolved in 5.16. Problem persists.

The problem is fixed in RouterOS v5.17.

Yes, it is fixed in 5.17. Thank you!