Symptoms
Chromebook can read a USB stick but fails to write new files even with free space.
Use the following observations to establish that this is the specific failure described here, rather than an unrelated outage or different account:
- Failing behavior: Chromebook can read a USB stick but fails to write new files even with free space.
- Comparison to run: Compare drive format and write permissions with a separate known-good test drive.
- Pass condition: A harmless file is written, reopened and deleted from the permitted drive.
Why It Happens
A user session, managed school profile and Android container can have different access to the same hardware or files.
Treat these as competing hypotheses, not confirmed diagnoses. Their implications are different:
- Media mounted read-only after filesystem error — investigate this first only if the local state or controlled comparison supports it.
- External drive has physical write lock — a second layer that may survive a simple restart and requires a targeted check.
- Managed policy blocks removable writes — investigate when the first two paths do not account for the observed behavior.
Before Making Changes
Back up the drive before any repair or formatting; never bypass school device controls. ChromeOS separates device capabilities, user-profile settings, Android app access and organization policy. A feature working in one profile does not prove the same permission exists elsewhere. Write down the working configuration and, if available, export settings or create a test-only copy before changing account permissions, routes or file locations.
Make one change at a time, note the original value, and repeat the exact same test after each change. If the new outcome is worse, restore that single setting; a full reset would erase evidence and can create additional problems.
Problem-Specific Diagnosis
Begin with this controlled observation: Compare drive format and write permissions with a separate known-good test drive. Record the result and time; a vague report such as “sometimes fails” cannot distinguish the three hypotheses.
| Check | What to do | What the result tells you |
|---|---|---|
| Compare a working path | Compare drive format and write permissions with a separate known-good test drive. | If one controlled route works, the failed route is probably specific to a setting, permission, device, or service rather than a total outage. |
| Check the local state | Check drive write-protect switch and storage format. | This can expose or rule out media mounted read-only after filesystem error without changing several settings together. |
| Inspect the deeper layer | Inspect ChromeOS storage diagnostics and filesystem integrity warnings. | Use the evidence to separate external drive has physical write lock from managed policy blocks removable writes; do not assume either is proven. |
If the local comparison is inconclusive, keep the current system unchanged while checking whether external drive has physical write lock is consistent with the evidence. If not, investigate managed policy blocks removable writes rather than applying every possible fix.
Use Beginner for reversible checks; use Advanced only when the comparison indicates a deeper fault. Chromebook can read a USB stick but fails to write new files even with free space. Run a harmless test and write down the time, device/account, current status indicators and the exact difference from normal behavior. Compare drive format and write permissions with a separate known-good test drive. Do not erase logs or reset the device yet. Check drive write-protect switch and storage format. Confirm the relevant account, cable, selected output, permission or status before saving changes. If it is already correct, leave it alone and proceed; do not force a change just to try something. Copy an existing nonprivate file to another safe location to check read access. Change only this one condition after recording the old value. If it does not improve the result, restore the former value rather than layering additional guesses on top. A harmless file is written, reopened and deleted from the permitted drive. Repeat the same comparison used in step one. Record what improved, what remains unchanged and whether a reconnect or normal app restart changes the result. Stop here if the expected outcome is stable. Consider media mounted read-only after filesystem error, external drive has physical write lock and managed policy blocks removable writes separately. Compare evidence from the working and failing paths, and avoid interpreting a green status indicator as end-to-end proof. Compare drive format and write permissions with a separate known-good test drive. Inspect ChromeOS storage diagnostics and filesystem integrity warnings. Focus on logs, state, permissions, protocol negotiation or version support relevant to this failure. Do not collect or share credentials, account tokens or unrelated private content. Verify organizational removable-storage policy with the device administrator. Use an isolated or test-only configuration where possible. Keep an explicit rollback path; do not weaken security, replace backup originals or bypass equipment protection to make one test pass. A harmless file is written, reopened and deleted from the permitted drive. Observe the behavior through the original trigger again. If the change does not produce this measurable result, undo that change and escalate with the recorded facts, rather than repeating disruptive reset attempts.Step-by-Step Troubleshooting
Capture the failing state
Check the first reversible condition
Apply the lowest-risk targeted fix
Retest and document
Distinguish the competing root causes
Inspect the deeper system layer
Run a second independent isolation test
Validate stability and rollback readiness
Solution Checklist
Common Mistakes to Avoid
- Treating media mounted read-only after filesystem error as certain before running the comparison: Compare drive format and write permissions with a separate known-good test drive.
- Trying several changes at once, such as modifying external drive has physical write lock and managed policy blocks removable writes simultaneously, which makes the successful change impossible to identify.
- Ignoring the safety boundary: Back up the drive before any repair or formatting; never bypass school device controls.
- Assuming that a status label or progress indicator guarantees the actual action completed; verify the outcome independently.
How to Verify the Fix
A harmless file is written, reopened and deleted from the permitted drive.
- Repeat the original failing action under equivalent conditions: Chromebook can read a USB stick but fails to write new files even with free space.
- Run the control again: Compare drive format and write permissions with a separate known-good test drive.
- Check the positive pass condition: A harmless file is written, reopened and deleted from the permitted drive.
- Recheck after a normal restart, reconnection or scheduled cycle only when it is safe and relevant.
A single passing attempt is useful but may conceal intermittent failures. Record whether the fix survives the triggering condition without requiring a daily workaround.
If the Problem Continues
Use the deeper comparison rather than repeating the first steps: Inspect ChromeOS storage diagnostics and filesystem integrity warnings. Verify organizational removable-storage policy with the device administrator.
Give Chromebook support the hardware model, ChromeOS version, whether the device is managed, and the exact difference between guest and affected profiles.
If the issue affects money, alarms, shared business records, or protective power equipment, stop risky experiments and use the official administrator, provider or manufacturer channel.
Prevent Recurrence
- Keep a record of the previously failing condition: Compare drive format and write permissions with a separate known-good test drive.
- Preserve the corrected behavior: A harmless file is written, reopened and deleted from the permitted drive.
- Maintain ChromeOS updates through supported channels, eject external drives, and keep work or school device policies documented.
- Review configuration or hardware changes that could reintroduce media mounted read-only after filesystem error.
Official Resources
Google Chromebook Help — Open, save, or delete files on your Chromebook — External storage compatibility and data-preserving checks.
Frequently Asked Questions
Does this symptom prove media mounted read-only after filesystem error?
No. Start with the controlled comparison: Compare drive format and write permissions with a separate known-good test drive. Only treat media mounted read-only after filesystem error as a candidate until the evidence supports it.
What if the first two checks do not change anything?
Move to a different layer rather than repeating the same action: Inspect ChromeOS storage diagnostics and filesystem integrity warnings. That helps determine whether external drive has physical write lock or managed policy blocks removable writes fits the symptoms.
How do I know the repair actually worked?
Use this outcome, not just an on-screen status message: A harmless file is written, reopened and deleted from the permitted drive. Keep a record of the working state for future troubleshooting.