Thanks for all your replies.
As far as I can tell there are no errors reported using fsck or smartctl or nvme
and the firmware is the correct and newest version so no problems there.
The following are the messages that appear but only taken from my phone and copied from the photo (lots of scrolling errors repeating over).
I thought these new drives were supposed to last longer than older moving HDD but obviously not
I guess its time to buy a new drive : (
EXT4-fs (nvme0n1p2): Remounting filesystem read-onty
EXT4-fs error (device nvme01p2): ext4_journal_check_start:83: comm systemd-journal: Detected aborted Jounal
[633582.907324] EXT4-fs error (device nvme0n1p2): _ext4_find_entry:1683: inode #5898248: comm ntpd: reading directory iblock 0
[633582 908250] EXT4-fs (nvme0n1p2) : Remounting filesystem read-only
EXT4-fs (nvme0n1p2): Remounting filesystem read-only
EXT4-fs error (device nvme0n1p2) : ext4_journal.check_start:83: comm systemd-journal: Detected aborted journal
[633582.912099] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
EXT4-fs error (device nvme0n1p2): ext4_journal-check_start:83: comm systemd-journal: Detected aborted journal
[633582.916126] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
(633583.797550) EXT4-fs error (device nvme0n1p2) in ext4_setattr:5628: —— Journal has aborted
(633583. 798466) EXT4-fs (nvme0n1p2): Remounting filesystem read-only
EXT4-fs error (device nvme01p2): ext4_journal_check_start:83: comm systemd-journal: Detected aborted Jounal
EXT4-fs (nvme@nip2): Remounting filesystem read-only
EXT4-fs error (device nvme0n1p2): _ext4_find_entry:1683: inode #1966081: comm cron: reading directory Iblock 0
EXT4-fs (nvme@nip2): Remounting filesystem read-only
EXT4-fs error (device nvme0n1p2) in ext4_setattr:5628: —— Journal has aborted
EXT4-fs (nvme@nip2): Remounting filesystem read-only