| 1 |
On Sunday, 13 September 2020 12:40:47 BST antlists wrote: |
| 2 |
|
| 3 |
> You're using the wrong tool to try and fix it. There's clearly something |
| 4 |
> wrong with your partition TABLE, and you're using a tool that fixes the |
| 5 |
> partition CONTENTS. |
| 6 |
|
| 7 |
Yes, I was clutching at straws, rather. |
| 8 |
|
| 9 |
> Use gparted (or gdisk) on the DISK, and that should sort things out. |
| 10 |
> Check whether it thinks those partitions exist or not, and then get it |
| 11 |
> to write a new partition table to clean things up. |
| 12 |
|
| 13 |
Gparted 0.31.0 on my rescue CD finds no problems. Parted in this system doesn't |
| 14 |
offer a checking tool, but gdisk does and it reports "no problems". Gparted |
| 15 |
1.1.0 in this system still reports the errors, but only once now on each disk |
| 16 |
(so what's changed there? Beats me). |
| 17 |
|
| 18 |
Udisks was upgraded on 13 August and I may not have used gparted since then, |
| 19 |
but reverting to the previous version hasn't helped. All the other packages I |
| 20 |
mentioned have not been changed for months. |
| 21 |
|
| 22 |
So I'm still left wondering what to do. I'm happy that the hardware isn't on |
| 23 |
the blink, anyway. |
| 24 |
|
| 25 |
-- |
| 26 |
Regards, |
| 27 |
Peter. |
Archives