You can make a difference in the Apple Support Community!

When you sign up with your Apple ID, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Can you "Eject" an external device with IpadOS?

Hi folks,

I am a 12.9" Gen5 Ipad Pro and an OWC Envoy Pro T3 M2 external storage device to store video files and edit directly with lumafusion.


The problem is, I am seeing some failures of video files and assume it to be somehow related to unplugging the drive as the failures have never happend on a PC, only the ipad.


Performance is fine and it does exactly what I would expect it to do, bar sometimes when I plug it back in, MP4 files are damaged.


I havent seen anything about having to eject USBC/T3 hardware, but that doesnt mean there isnt...


Any suggestions folk?

iPad Pro 12.9-inch, 3rd Gen, Wi-Fi, Cell

Posted on Sep 28, 2021 4:22 AM

Reply
Question marked as Top-ranking reply

Posted on Sep 28, 2021 4:36 AM

Apple hasn’t chosen to include a safe-eject option in iOS/iPadOS. There reasoning and design decisions for this (or any feature) are known only to Apple Engineering.


Providing your attached USB Storage device does not employ write-caching, you should be able to disconnected a USB Storage device wherever the device is not being actively written to; it follows that you should ensure that a file-write has completed prior to a device disconnect.


In more detail:


The type of flash storage device that you are using will have significant impact on “safe dismount” from your iPad. Simple flash storage devices can be dismounted provided that an active write isn’t occurring. More complex devices are a completely different proposition…


The technical cause is likely to be write-caching - this being a feature of the USB Storage (in this case SSD) device.


For most desktop computers, it is possible to configure an externally attached storage device either for performance (i.e., uses write-caching) or for Quick Removal. This determines how and when information is “written” to non-volatile storage.


When configured for Quick Removal, information from the host computer is written immediately to the storage medium. This has the advantage that you may disconnect the storage device from the host computer, without risk of corrupting the file-system, at any time that data is not being actively transmitted to the storage device. Whilst being a completely valid and useful method of managing data storage, for reasons beyond the immediate scope of this description, this method is less efficient and slower.


Alternatively, when write-caching is enabled, information from the host computer is “cached” in separate (high performance) volatile storage within the storage device - and when sufficient information has been received, a “block” of data is written in single write-cycle. Whilst being faster and more efficient, this method comes with the penalty of the host computer having to notify the storage device of a impending device-disconnection before it is disconnected. This warning ensures that the storage device will flush any pending data from its volatile cache-memory to non-volatile storage - and in so doing sets a “clean switch” on the flash filesystem and signals to the computer that it is safe to disconnect.


A drive configured for write-caching, upon connection to a host computer, is checked for the “clean switch”; if present, the storage device is “mounted” and made available to the operating system. By contrast, if the “clean switch” is not detected (this will occur if the storage device was disconnected prior to being notified of a “dismount”), the filesystem must be assumed to be potentially corrupt; pending data within the write-cache may not have been written to the drive.


So, the relevance of this to iPad is simple. iPad does not fully support devices that implement write-caching. iPadOS lacks the ability to inform the storage device of imminent disconnection of the storage device from the USB bus. iPad also lacks capability to detect and scan/repair corrupt storage devices.


In summary, now that you [hopefully] understand both the cause and effect, you will now understand that you can only reliably use USB storage devices that can be configured for Quick Disconnect operation - this having major significance to non-corruption of the filesystem and reduced data throughput.


The only “safe” dismount is to fully shut down the iPad before disconnecting.


I hope this information and insight proves to be helpful.

5 replies
Question marked as Top-ranking reply

Sep 28, 2021 4:36 AM in response to Evolution-Stu

Apple hasn’t chosen to include a safe-eject option in iOS/iPadOS. There reasoning and design decisions for this (or any feature) are known only to Apple Engineering.


Providing your attached USB Storage device does not employ write-caching, you should be able to disconnected a USB Storage device wherever the device is not being actively written to; it follows that you should ensure that a file-write has completed prior to a device disconnect.


In more detail:


The type of flash storage device that you are using will have significant impact on “safe dismount” from your iPad. Simple flash storage devices can be dismounted provided that an active write isn’t occurring. More complex devices are a completely different proposition…


The technical cause is likely to be write-caching - this being a feature of the USB Storage (in this case SSD) device.


For most desktop computers, it is possible to configure an externally attached storage device either for performance (i.e., uses write-caching) or for Quick Removal. This determines how and when information is “written” to non-volatile storage.


When configured for Quick Removal, information from the host computer is written immediately to the storage medium. This has the advantage that you may disconnect the storage device from the host computer, without risk of corrupting the file-system, at any time that data is not being actively transmitted to the storage device. Whilst being a completely valid and useful method of managing data storage, for reasons beyond the immediate scope of this description, this method is less efficient and slower.


Alternatively, when write-caching is enabled, information from the host computer is “cached” in separate (high performance) volatile storage within the storage device - and when sufficient information has been received, a “block” of data is written in single write-cycle. Whilst being faster and more efficient, this method comes with the penalty of the host computer having to notify the storage device of a impending device-disconnection before it is disconnected. This warning ensures that the storage device will flush any pending data from its volatile cache-memory to non-volatile storage - and in so doing sets a “clean switch” on the flash filesystem and signals to the computer that it is safe to disconnect.


A drive configured for write-caching, upon connection to a host computer, is checked for the “clean switch”; if present, the storage device is “mounted” and made available to the operating system. By contrast, if the “clean switch” is not detected (this will occur if the storage device was disconnected prior to being notified of a “dismount”), the filesystem must be assumed to be potentially corrupt; pending data within the write-cache may not have been written to the drive.


So, the relevance of this to iPad is simple. iPad does not fully support devices that implement write-caching. iPadOS lacks the ability to inform the storage device of imminent disconnection of the storage device from the USB bus. iPad also lacks capability to detect and scan/repair corrupt storage devices.


In summary, now that you [hopefully] understand both the cause and effect, you will now understand that you can only reliably use USB storage devices that can be configured for Quick Disconnect operation - this having major significance to non-corruption of the filesystem and reduced data throughput.


The only “safe” dismount is to fully shut down the iPad before disconnecting.


I hope this information and insight proves to be helpful.

Sep 28, 2021 6:13 AM in response to Evolution-Stu

You’re very welcome.


Unfortunately, despite optimistic and creative marketing by Apple, iPad and iPad Pro are not able to replicate functionality similar to that of a full PC or Mac computer. The iPad is, for many, as excellent companion device - but cannot be realistically considered a full replacement for a traditional computer. iPad’s capabilities are getting stronger with each hardware and iPadOS iteration - but still has a long way to go.


As you observe, the greatest and most expensive accessory hardware is not necessarily the “best” or more uselful.

Sep 28, 2021 6:08 AM in response to LotusPilot

Hi,

Thanks for the extremely detailed reply, it helps me understand the issue greatly and I learnt a few things too.

So this could well be one of those stuations where buying the best, wasnt the best thing to buy....


I bought this as its Thunderbolt 3 so totally compatible with all 4 of my different machine specifications. And my hub is Thunderbolt 4 so this made it all pretty futureproof. But I guess the compatability and NVMe speed comes with its own set of unexpected problems.


https://www.owcdigital.com/products/envoy-pro-fx


I suppose I could do a power down after the video editing is complete.

Far from ideal, but yeah, I guess I could.


Hopefully Apple will address tjhis issue one day as these super fast drives become more and more commonplace on their latest USBC-Thunderbolt 3/4 equipped machines.


Thanks for your time and knowledge.

Can you "Eject" an external device with IpadOS?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.