1 |
On 13/09/2020 11:17, Peter Humphrey wrote: |
2 |
> Morning all, |
3 |
> |
4 |
> My ~amd64 system uses partitions 1 to 18 on /dev/nvme0n1, and it has two SATA |
5 |
> disks as well, for various purposes. Today, after I'd taken the system down |
6 |
> for its weekly backup (I tar all the partitions to a USB disk) and started up |
7 |
> again, invoking gparted to look around, libparted spat out a list of |
8 |
> partitions from 19 to 128 which, it said, "have been written but we have been |
9 |
> unable to inform the kernel of the change..." |
10 |
> |
11 |
> I remerged gparted, parted, libparted and udisks, then booted another system |
12 |
> and ran fsck -f on all the partitions from 4 to 18 - those that this system |
13 |
> uses - and rebooted. No change - the same complaint from libparted. |
14 |
> |
15 |
> I get a similar complaint about /dev/sda. |
16 |
> |
17 |
> Those errors are repeated once. |
18 |
> |
19 |
> Is this a terminal condition? I could repartition and restore from backup, but |
20 |
> I hope someone can offer a clue before I resort to that. |
21 |
> |
22 |
You're using the wrong tool to try and fix it. There's clearly something |
23 |
wrong with your partition TABLE, and you're using a tool that fixes the |
24 |
partition CONTENTS. |
25 |
|
26 |
Use gparted (or gdisk) on the DISK, and that should sort things out. |
27 |
Check whether it thinks those partitions exist or not, and then get it |
28 |
to write a new partition table to clean things up. |
29 |
|
30 |
Cheers, |
31 |
Wol |