Added new drive but it's stuck as "read only file system"

Bought a new drive. Expected it would be easy to install...

Shouldn't need to use commands for something every day users should be able to complete, so I followed this GUI guide:

https://www.zdnet.com/article/how-to-automount-a-drive-in-linux-the-gui-way-with-gnome/

I managed to write a file on the drive from an application. However, later when I attempt to change the file it says it's a read-only file system:

sudo chmod 777 file_namechmod: changing permissions of file_name: Read-only file system

I get the same when trying to change the permissions for the mounted folder.

Interestingly when I open GParted I get an error for the new drive:

and the drive isn't shown in the drop down.

Disks application shows this:

Could someone please provide a simple solution where I am just using the GUI?

This is for Ubuntu 22.04

Updates from comments:

findmnt -T /media/ssdTARGET     SOURCE    FSTYPE OPTIONS/media/ssd /dev/sda1 ext4   ro,nosuid,nodev,relatime

and

findmnt --fstabTARGET      SOURCE                                                 FSTYPE OPTIONS/           UUID=3983f8b5-04f5-4eb4-8356-5f749f7cbaa6              ext4   errors=remount-ro/boot/efi   UUID=9450-FE9C                                         vfat   umask=0077none        /swapfile                                              swap   sw/media/ssd/ /dev/disk/by-uuid/c1189942-b1c5-432f-815b-cdcb40054877 auto   nosuid,nodev,nofail,x-gvfs-show

Another:

sudo fsck -y /dev/sda1 fsck from util-linux 2.37.2e2fsck 1.46.5 (30-Dec-2021)fsck.ext2: Input/output error while trying to open /dev/sda1The superblock could not be read or does not describe a valid ext2/ext3/ext4filesystem.  If the device is valid and it really contains an ext2/ext3/ext4filesystem (and not swap or ufs or something else), then the superblockis corrupt, and you might try running e2fsck with an alternate superblock:    e2fsck -b 8193 <device> or    e2fsck -b 32768 <device>