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