Your drive is ancient and dying - not quite dead yet but well on its way. It could fail completely AT ANY MOMENT.

Your only option is to replace it. ASAP. The urgency of replacing this drive can not be overstated.

The easiest way will be to replace it with a new drive of the exact same size and use ddrescue to make a bit copy of the entire old drive to the new drive.

However, since it's 6.5 years old, you may want to take advantage of the fact that newer SSDs come in far larger capacities for reasonable prices. In that case, it's probably easiest to start from scratch. The old SSD is still readable, so you should be able to copy the data off of it. Or start with a ddrescue clone of it and use gparted or something to expand the partitions & filesystems once you've copied it.

While you're at it, if you can physically fit another drive in the system, I recommend adding a second identical drive as a btrfs RAID-1 mirror drive so that you have at least some redundancy. One of the main points of using a filesystem like btrfs or zfs is error detection and correction. Without redundancy, you get error detection but not error correction. I don't know if you already have a 2nd drive in that btrfs pool or not because you haven't shown the underlying SSD(s), just the /dev/mapper nodes.

NOTE: if you can not replace the drive immediately, at least make a backup if your not already making regular backups (which you should because RAID and RAID-like filesystems are NOT a substitute for backups). At least you'll have a backup of your data while you're deciding what to buy and waiting for it to arrive.

Hardware is replacable. Lost data is not.

Your drive is ancient and dying - not quite dead yet but well on its way. It could fail completely AT ANY MOMENT.

Your only option is to replace it. ASAP. The urgency of replacing this drive can not be overstated.

The easiest way will be to replace it with a new drive of the exact same size and use ddrescue to make a bit copy of the entire old drive to the new drive.

However, since it's 6.5 years old, you may want to take advantage of the fact that newer SSDs come in far larger capacities for reasonable prices. In that case, it's probably easiest to start from scratch. The old SSD is still readable, so you should be able to copy the data off of it. Or start with a ddrescue clone of it and use gparted or something to expand the partitions & filesystems once you've copied it.

While you're at it, if you can physically fit another drive in the system, I recommend adding a second identical drive as a btrfs RAID-1 mirror drive so that you have at least some redundancy. One of the main points of using a filesystem like btrfs or zfs is error detection and correction. Without redundancy, you get error detection but not error correction. I don't know if you already have a 2nd drive in that btrfs pool or not because you haven't shown the underlying SSD(s), just the /dev/mapper nodes.

NOTE: if you can not replace the drive immediately, at least make a backup if you're not already making regular backups (which you should because RAID and RAID-like filesystems are NOT a substitute for backups). At least you'll have a backup of your data while you're deciding what to buy and waiting for it to arrive.

Hardware is replacable. Lost data is not.

Your drive is ancient and dying - not quite dead yet but well on its way. It could fail completely AT ANY MOMENT.

Your only option is to replace it. ASAP. The urgency of replacing this drive can not be overstated.

The easiest way will be to replace it with a new drive of the exact same size and use ddrescue to make a bit copy of the entire old drive to the new drive.

However, since it's 6.5 years old, you may want to take advantage of the fact that newer SSDs come in far larger capacities for reasonable prices. In that case, it's probably easiest to start from scratch. The old SSD is still readable, so you should be able to copy the data off it. Or start with a ddrescue clone of it and use gparted or something to expand the partitions & filesystems once you've copied it.

While you're at it, if you can physically fit another drive in the system, I recommend adding a second identical drive as a btrfs RAID-1 mirror drive so that you have at least some redundancy. One of the main points of using a filesystem like btrfs or zfs is error detection and correction. Without redundancy, you get error detection but not error correction. I don't know if you already have a 2nd drive in that btrfs pool or not because you haven't shown the underlying SSD(s), just the /dev/mapper nodes.

NOTE: if you can not replace the drive immediately, at least make a backup if your noy already making regular backups (which you should because RAID and RAID-like filesystems are NOT a substitute for backups). At least you'll have a backup of your data while you're deciding what to buy and waiting for it to arrive. Hardware is replacable. Lost data is not.

Your drive is ancient and dying - not quite dead yet but well on its way. It could fail completely AT ANY MOMENT.

Your only option is to replace it. ASAP. The urgency of replacing this drive can not be overstated.

The easiest way will be to replace it with a new drive of the exact same size and use ddrescue to make a bit copy of the entire old drive to the new drive.

However, since it's 6.5 years old, you may want to take advantage of the fact that newer SSDs come in far larger capacities for reasonable prices. In that case, it's probably easiest to start from scratch. The old SSD is still readable, so you should be able to copy the data off of it. Or start with a ddrescue clone of it and use gparted or something to expand the partitions & filesystems once you've copied it.

While you're at it, if you can physically fit another drive in the system, I recommend adding a second identical drive as a btrfs RAID-1 mirror drive so that you have at least some redundancy. One of the main points of using a filesystem like btrfs or zfs is error detection and correction. Without redundancy, you get error detection but not error correction. I don't know if you already have a 2nd drive in that btrfs pool or not because you haven't shown the underlying SSD(s), just the /dev/mapper nodes.

NOTE: if you can not replace the drive immediately, at least make a backup if your not already making regular backups (which you should because RAID and RAID-like filesystems are NOT a substitute for backups). At least you'll have a backup of your data while you're deciding what to buy and waiting for it to arrive.

Hardware is replacable. Lost data is not.