On Sun, Sep 13, 2020 at 8:17 PM Peter Humphrey <[email protected]> wrote:
> Morning all, > > My ~amd64 system uses partitions 1 to 18 on /dev/nvme0n1, and it has two > SATA > disks as well, for various purposes. Today, after I'd taken the system > down > for its weekly backup (I tar all the partitions to a USB disk) and started > up > again, invoking gparted to look around, libparted spat out a list of > partitions from 19 to 128 which, it said, "have been written but we have > been > unable to inform the kernel of the change..." > > I remerged gparted, parted, libparted and udisks, then booted another > system > and ran fsck -f on all the partitions from 4 to 18 - those that this > system > uses - and rebooted. No change - the same complaint from libparted. > I would start by dd ing an image of the entire disk, then making a copy to work on (keeping the original image as a backup) then running testdisk against the working copy image to see what it reports.
