Why your SDA1 partition becomes read-only and how to fix it

When you plug a USB drive or external storage into your Raspberry Pi, the system sometimes mounts it as read-only — meaning you can open files but cannot create, edit, or delete anything on it. This happens most often with the SDA1 partition, which is usually the first partition on an external drive. The read-only state protects your data if the drive disconnects suddenly, but it also locks you out of organizing your files the way you need to.

You can change SDA1 back to read-write in about five minutes using the command line. The fix involves remounting the partition with write permissions, and optionally fixing any file system errors that may have triggered the read-only state in the first place.

Key Takeaways

  • A read-only partition usually means the file system has errors or the drive was not safely removed from another computer.
  • You can remount SDA1 as read-write using a single command: sudo mount -o remount,rw /media/pi/[partition-name]
  • If remounting fails, run sudo fsck.ext4 -y /dev/sda1 to repair file system errors before trying again.
  • Always unmount the drive safely before unplugging it to prevent the read-only state from happening again.

Finding where your SDA1 partition is mounted

Before you can change the permissions, you need to know the exact path where the partition is mounted on your Raspberry Pi. Open a terminal window and type this command:

lsblk

This shows all connected storage devices and their mount points. Look for sda1 in the left column — it will have a path listed on the right side, usually something like /media/pi/USB-DRIVE or /mnt/external. Write down that full path; you will need it in the next step. If you see sda1 listed but no mount point appears next to it, the partition is not currently mounted and you will need to mount it first before changing permissions.

Remounting the partition as read-write

Once you have the mount path, type this command into the terminal, replacing [mount-path] with the actual path you found in the previous step:

sudo mount -o remount,rw [mount-path]

For example, if your mount path is /media/pi/USB-DRIVE, the command would be:

sudo mount -o remount,rw /media/pi/USB-DRIVE

Press Enter and wait for the prompt to return. If the command completes without an error message, the partition is now read-write and you can create and edit files on it. Try opening a file manager and creating a test folder on the drive to confirm it worked.

If you see an error message instead — especially one mentioning "read-only file system" — the partition has file system errors that must be repaired before it will accept write commands. Move to the next section.

Repairing file system errors if remounting fails

A read-only state that persists after remounting usually means the file system itself has detected errors and locked itself to prevent data loss. You can repair these errors using the fsck tool, which checks and fixes the partition. First, unmount the partition completely:

sudo umount [mount-path]

Then run the repair command on the unmounted partition:

sudo fsck.ext4 -y /dev/sda1

The -y flag tells fsck to automatically fix errors without asking you to confirm each one. The process may take a few minutes depending on the drive size. When it finishes, you will see a summary of what was repaired. After fsck completes, remount the partition as read-write using the command from the previous section.

If fsck reports that the partition is not an ext4 file system, it may be formatted as FAT32 or NTFS instead. In that case, file system errors are less common, and the read-only state usually comes from the drive being unplugged unsafely from another computer. Remounting as read-write should work once you try again.

Preventing read-only errors in the future

The easiest way to avoid this problem is to safely eject the drive before unplugging it. In the file manager, right-click the drive and select Eject or Safely Remove. This tells the Raspberry Pi to finish all pending writes and close the connection cleanly. Only unplug the drive after the system confirms it is safe to remove.

If you frequently move the drive between computers, consider formatting it as exFAT instead of ext4. ExFAT works on Windows, Mac, and Linux, and is less prone to read-only states when moved between systems. You can reformat the drive using the Raspberry Pi's file manager or the command line, though this will erase all existing data.

Checking if the fix worked

After remounting or repairing, verify that the partition is truly read-write by creating a test file. Open the file manager, navigate to the SDA1 partition, right-click in an empty area, and select Create Document or New Folder. If the option appears and the file or folder is created successfully, the partition is now writable. Delete the test file afterward to keep the drive clean.

If you still cannot create files, check that you are using the correct mount path and that the partition is actually mounted. Run lsblk again to confirm the mount point has not changed, then try the remount command once more.

Frequently Asked Questions

What does read-only mean on a storage drive?

Read-only means the operating system will let you open and copy files from the drive, but will not let you create new files, edit existing ones, or delete anything. This state protects data if the drive is disconnected unexpectedly, but it also prevents you from organizing or modifying your files.

Will remounting as read-write erase my files?

No. Remounting only changes the permission state — it does not touch any data on the drive. All your files remain exactly as they are. If you run fsck to repair file system errors, it may move corrupted files to a lost-and-found folder, but it will not delete intact files.

Can I use this method on other partitions like SDA2 or SDB1?

Yes. The same commands work for any partition. Just replace sda1 with the partition you need to fix, and use the correct mount path. Always verify the partition name with lsblk before running fsck to avoid repairing the wrong drive.

What if the partition is not showing up in lsblk at all?

The drive may not be recognized by the Raspberry Pi, or it may be failing. Try unplugging it and plugging it into a different USB port. If it still does not appear, the drive may need to be formatted or replaced. You can also try connecting it to another computer to see if it is recognized there.

Do I need to do this every time I plug in the drive?

No. Once you fix the partition and safely eject it before unplugging, it should stay read-write. The read-only state returns only if the drive is unplugged without ejecting, or if new file system errors develop. Safely ejecting every time prevents the problem from recurring.