Hi everyone, 

I'm using an MTP1000 Unified panel with the last version of firmware and TIA Portal V20.

I'm currently doing deep archiving tests on a USB drive. I am using Traces for troubleshooting.

I recently noticed while testing that if I remove the USB stick from the screen and plug it back in, I can no longer write to it until I power the runtime off and on again. 

"I would like to know if there is a solution, as I don’t want to give my clients the possibility to stop the runtime."

Best regards ! 

Thanks for replies.

- Hi, try using EjectStorageMedium before removing.

I tested it, the answer is the same as if I'm not using it.

- However, the outcome may depend on how much time elapses between unplugging and replugging the storage medium. If you unplug the medium without ejecting it first, it will take some time for the mount service to detect this. If you plug it in again before then, though, automounting might fail.

The time is not a problem. When I unplug my device, errors traces is thrown immediately in the TraceViewer for the the mount service, so the detection is good.
Then, I waited some different amount of time, and the result is the same : automounting always fail. So I have to restart the runtime to force the re-mount of my USB stick.

Now, the question to understand is how automounting work exactly (of course, if you know something that I could use, it will be appriciated) ? 

Bye ! 

Stefan Arcularius

Hi,

Based on my observations, a panel reboot is needed to mount the storage device again once automounting fails.

Therefore, it is essential to properly unplug the storage medium to ensure that related services function correctly. However, in most cases, unplugging and replugging the medium does not cause any problems. It would be interesting to know why it seems to be such an issue in your case. Have you submitted a support request yet?

Kind regards
Stefan

I made many tests this morning, and my observations are the following ones (with TraceViewer): 

- First, I observed that after I created an eject button, the eject methode work randomly.

- Then, if the ejection worked well, the automounting failed more than worked when I re-plugged the USB stick. And, of course, I waited different time to simulate every posibilities.

- Finally, if the eject methode AND automounting worked, then sometimes an info that saying something like "State : NotWorking -> HealthGood" is thrown, but sometimes not. If not, then the USB stick is not detected...

I don't know if I'm doing something wrong. I know that random cannot exist in automation, but here I don't see any common points between my tests... 

I have to go like 3 weeks away, so I'll restart my testing task later.

Bye !