Jump to content

Should I really “eject” USB/flash/thumb drives?

FoxYolk
Go to solution Solved by Eigenvektor,
4 minutes ago, Helpful Tech Witch said:

this is only if you have that on iirc

flash drives by default dont have write caching akaik, which is why you can pull and go. 

Right.

 

The eject feature essentially goes back to mechanical drives. Ejecting the drive allows it to move its head into the parked position. It should also be able to do this in the case of sudden power loss, but why risk it?

 

On top of that, a mechanical drive often has its own write cache. Ejecting the drive allows the drive can commit anything to disk, before being unplugged. Sudden loss of power could lead to data loss.

 

On a modern system it should generally be safe to unplug a drive, especially when the drive is idle.

When you pull a drive or something, windows will say you should eject it. Is it really necessary? 

Link to comment
Share on other sites

Link to post
Share on other sites

Windows may cache writes to a drive for performance reasons. So if you pull it without ejecting first, it might be in the middle of a write, which could lead to corrupt data.

Remember to either quote or @mention others, so they are notified of your reply

Link to comment
Share on other sites

Link to post
Share on other sites

I still recall being at a hotel lobby, downloading anime onto my USB drive, not ejecting it, and going upstairs only to find the file corrupted and unwatchable.

You can enable a setting that disables the caching. Here are some instructions I found that tell how to do that. But remember it is per drive, so each USB drive would need the setting.

Link to comment
Share on other sites

Link to post
Share on other sites

3 minutes ago, Eigenvektor said:

Windows may cache writes to a drive for performance reasons. So if you pull it without ejecting first, it might be in the middle of a write, which could lead to corrupt data.

this is only if you have that on iirc

flash drives by default dont have write caching akaik, which is why you can pull and go. 

I could use some help with this!

please, pm me if you would like to contribute to my gpu bios database (includes overclocking bios, stock bios, and upgrades to gpus via modding)

Bios database

My beautiful, but not that powerful, main PC:

prior build:

Spoiler

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, Avaviel said:

I still recall being at a hotel lobby, downloading anime onto my USB drive, not ejecting it, and going upstairs only to find the file corrupted and unwatchable.

You can enable a setting that disables the caching. Here are some instructions I found that tell how to do that. But remember it is per drive, so each USB drive would need the setting.

oh, okay

Link to comment
Share on other sites

Link to post
Share on other sites

4 minutes ago, Helpful Tech Witch said:

this is only if you have that on iirc

flash drives by default dont have write caching akaik, which is why you can pull and go. 

Right.

 

The eject feature essentially goes back to mechanical drives. Ejecting the drive allows it to move its head into the parked position. It should also be able to do this in the case of sudden power loss, but why risk it?

 

On top of that, a mechanical drive often has its own write cache. Ejecting the drive allows the drive can commit anything to disk, before being unplugged. Sudden loss of power could lead to data loss.

 

On a modern system it should generally be safe to unplug a drive, especially when the drive is idle.

Remember to either quote or @mention others, so they are notified of your reply

Link to comment
Share on other sites

Link to post
Share on other sites

By default Windows will set removable drives to not cache writes, so once the copy window disappears all writes should be committed. You can change that to improve performance but then you need to use eject.

 

BUT some drives have internal cache, and may be lying to Windows that "the transfer is done" while they still need to clear their own cache. Used to have one that was terrible about that, but at least had an LED to signal its status. Even after finishing the copy and/or ejecting successfully the LED might have been blinking for another 10-20s and you'd get corruption if removed before.

Should be pretty rare nowadays, this was an early USB3 flash drive.

F@H
Desktop: i9-13900K, ASUS Z790-E, 64GB DDR5-6000 CL36, RTX3080, 2TB MP600 Pro XT, 2TB SX8200Pro, 2x16TB Ironwolf RAID0, Corsair HX1200, Antec Vortex 360 AIO, Thermaltake Versa H25 TG, Samsung 4K curved 49" TV, 23" secondary, Mountain Everest Max

Mobile SFF rig: i9-9900K, Noctua NH-L9i, Asrock Z390 Phantom ITX-AC, 32GB, GTX1070, 2x1TB SX8200Pro RAID0, 2x5TB 2.5" HDD RAID0, Athena 500W Flex (Noctua fan), Custom 4.7l 3D printed case

 

Asus Zenbook UM325UA, Ryzen 7 5700u, 16GB, 1TB, OLED

 

GPD Win 2

Link to comment
Share on other sites

Link to post
Share on other sites

1 hour ago, Eigenvektor said:

Right.

 

The eject feature essentially goes back to mechanical drives. Ejecting the drive allows it to move its head into the parked position. It should also be able to do this in the case of sudden power loss, but why risk it?

 

On top of that, a mechanical drive often has its own write cache. Ejecting the drive allows the drive can commit anything to disk, before being unplugged. Sudden loss of power could lead to data loss.

 

On a modern system it should generally be safe to unplug a drive, especially when the drive is idle.

That's odd, considering none of my mechanical external hard drives have even had the option to eject before unplugging them.

CPU: Ryzen 9 5900 Cooler: EVGA CLC280 Motherboard: Gigabyte B550i Pro AX RAM: Kingston Hyper X 32GB 3200mhz

Storage: WD 750 SE 500GB, WD 730 SE 1TB GPU: EVGA RTX 3070 Ti PSU: Corsair SF750 Case: Streacom DA2

Monitor: LG 27GL83B Mouse: Razer Basilisk V2 Keyboard: G.Skill KM780 Cherry MX Red Speakers: Mackie CR5BT

 

MiniPC - Sold for $100 Profit

Spoiler

CPU: Intel i3 4160 Cooler: Integrated Motherboard: Integrated

RAM: G.Skill RipJaws 16GB DDR3 Storage: Transcend MSA370 128GB GPU: Intel 4400 Graphics

PSU: Integrated Case: Shuttle XPC Slim

Monitor: LG 29WK500 Mouse: G.Skill MX780 Keyboard: G.Skill KM780 Cherry MX Red

 

Budget Rig 1 - Sold For $750 Profit

Spoiler

CPU: Intel i5 7600k Cooler: CryOrig H7 Motherboard: MSI Z270 M5

RAM: Crucial LPX 16GB DDR4 Storage: Intel S3510 800GB GPU: Nvidia GTX 980

PSU: Corsair CX650M Case: EVGA DG73

Monitor: LG 29WK500 Mouse: G.Skill MX780 Keyboard: G.Skill KM780 Cherry MX Red

 

OG Gaming Rig - Gone

Spoiler

 

CPU: Intel i5 4690k Cooler: Corsair H100i V2 Motherboard: MSI Z97i AC ITX

RAM: Crucial Ballistix 16GB DDR3 Storage: Kingston Fury 240GB GPU: Asus Strix GTX 970

PSU: Thermaltake TR2 Case: Phanteks Enthoo Evolv ITX

Monitor: Dell P2214H x2 Mouse: Logitech MX Master Keyboard: G.Skill KM780 Cherry MX Red

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, dizmo said:

That's odd, considering none of my mechanical external hard drives have even had the option to eject before unplugging them.

Because they are not marked 'removable'. If they are hot-swapable, you'd have the same 'Eject' choice.

Link to comment
Share on other sites

Link to post
Share on other sites

1 hour ago, Kilrah said:

By default Windows will set removable drives to not cache writes, so once the copy window disappears all writes should be committed. You can change that to improve performance but then you need to use eject.

 

BUT some drives have internal cache, and may be lying to Windows that "the transfer is done" while they still need to clear their own cache. Used to have one that was terrible about that, but at least had an LED to signal its status. Even after finishing the copy and/or ejecting successfully the LED might have been blinking for another 10-20s and you'd get corruption if removed before.

Should be pretty rare nowadays, this was an early USB3 flash drive.

 

2 hours ago, Eigenvektor said:

Right.

 

The eject feature essentially goes back to mechanical drives. Ejecting the drive allows it to move its head into the parked position. It should also be able to do this in the case of sudden power loss, but why risk it?

 

On top of that, a mechanical drive often has its own write cache. Ejecting the drive allows the drive can commit anything to disk, before being unplugged. Sudden loss of power could lead to data loss.

 

On a modern system it should generally be safe to unplug a drive, especially when the drive is idle.

2 hours ago, Helpful Tech Witch said:

this is only if you have that on iirc

flash drives by default dont have write caching akaik, which is why you can pull and go. 

1 hour ago, dizmo said:

That's odd, considering none of my mechanical external hard drives have even had the option to eject before unplugging them.

I think I started a heated argument...

Link to comment
Share on other sites

Link to post
Share on other sites

2 hours ago, dizmo said:

That's odd, considering none of my mechanical external hard drives have even had the option to eject before unplugging them.

I no longer have one, but mine had the option, same a my current external SSD

Remember to either quote or @mention others, so they are notified of your reply

Link to comment
Share on other sites

Link to post
Share on other sites

I would recommend using the Windows cache, and using eject before removing the drive ( as otherwise the data may be corrupted, or not finished writing )

simply because it’s faster to do that.
Not using Windows write cache is just slow.

 

as for the media, I would recommend, using GPT and NTFS, or ReFS ( do note the compatibility issue with older OS ). 
as MBR ones can get corrupted easily in my expirients.   

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

On 10/4/2023 at 10:37 PM, kokosnh said:

I would recommend using the Windows cache, and using eject before removing the drive ( as otherwise the data may be corrupted, or not finished writing )

simply because it’s faster to do that.
Not using Windows write cache is just slow.

 

as for the media, I would recommend, using GPT and NTFS, or ReFS ( do note the compatibility issue with older OS ). 
as MBR ones can get corrupted easily in my expirients.   

 

 

Oh, okay

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×