I’ve got two problems very much related to mounting USB filesystems on a hAP AX3 I’m using for pihole and an SMB share. I had stopped and ejected the smb file share, then unplugged it from the usb hub (usb1). This is where the problems began. Pihole mounts on usb2 and the SMB share to usb3. This is a new SMB share formatted from the AX3 using exfat filesystem.
1: After replugging in the SMB share the filesystem doesn’t mount on usb3
2: The pihole is mounting normally in usb2 but when I look in files they all show under usb3:
3: The filesystem I was sharing from usb3 is not mounting, although it was formatted on the AX3.
Export of the disks
/disk
# mountpoint usb2 taken by usb2
set usb3 media-interface=bridge1
/disk settings
set auto-media-interface=lo
How can I get the usb2 to show files in usb2 as expected? I believe this is preventing my SMB share from mounting on usb3 and mounting. Also, when I do an /export in terminal it seems to hang on the container, and smb shares, then the request will time out.
Which physical devices are you using?
By any chance SANDISK USB sticks?
There have been reports of those having issues in getting the same order at each connection/reconnection, cannot say if related to your issue.
However, getting the SMB share to mount is still an issue. USB3 is showing up as a disk, at least.
But usb4 doesn't really exist in the drives:
> /disk/print
Flags: E - EMPTY, B - BLOCK-DEVICE; M - MOUNTED
Columns: SLOT, MOUNT-POINT, MODEL
# SLOT MOUNT-POINT MODEL
0 E usb1
1 BM usb2 usb2 USB SanDisk 3.2Gen1
;;; mount failed: Invalid argument
2 B usb3 Space keys USB 3.0 Device
Invalid argument mount error is from internal mount process, not related to some config parameter in ROS. Linux kernel fails to mount drive for some reason.
If you can mount drive on some other system this means there is some issue in ROS, could be related to Linux kernel driver for particular usb drive model, Linux kernel on ROS is not very recent.
From your screenshot you have autosupout files, which means something is crashing internally in ROS. Better send them to support by opening ticket as suggested above.
IF the issue is the known one, the only thing that you can do is cycle the USB AFTER the boot of the router.
For some reasons some SANDISK USB sticks attempt to "negotiate" (or whatever) at each power on whether to expose the USB 2.0 or the USB 3.x interface and this sometimes confuses routerOS detection of the device.
It seems to be a timing issue of some kind, a workaround is issueing a USB reboot with a script, when the deivce is not detected correctly, example:
The solution - as said - is to try a non-SANDISK usb stick.
JFYI most USB sticks use "third party" controllers (like Physon, Alcor, Skymedi, SMI, etc.), SANDISK is an exception and develops their own controller chips (and usually the quality of Sandisk sticks is excellent) that have their own peculiarities.
Given the data hasn't been on the disk for long, I reformatted, and this time to ext4 instead of exfat. After the reformat the drive happily mounted and I'm moving data there again.
I believe this to be 99.99% user error on my part clicking on stuff as I'm new to this. Live and learn.
Since reformatting to ext4, I've been using robocopy to move my data to the SMB share and it's working better than the exfat filesystem.
Previously with exfat I noticed several large files could not successfully copy and robocopy would barf with an error 59. Now it appears the copying is going very well with no issues. So far so good.
