| 1 |
I'm backing up my partitions maps to avoid such problems, I've had them before on spinning rust. Also backing up the headers of luks partitions, loose those and your' really sunk! |
| 2 |
|
| 3 |
--"Fascism begins the moment a ruling class, fearing the people may use their political democracy to gain economic democracy, begins to destroy political democracy in order to retain its power of exploitation and special privilege." Tommy Douglas |
| 4 |
|
| 5 |
|
| 6 |
|
| 7 |
|
| 8 |
Sep 13, 2020, 06:26 by peter@××××××××××××.uk: |
| 9 |
|
| 10 |
> On Sunday, 13 September 2020 12:40:47 BST antlists wrote: |
| 11 |
> |
| 12 |
>> You're using the wrong tool to try and fix it. There's clearly something |
| 13 |
>> wrong with your partition TABLE, and you're using a tool that fixes the |
| 14 |
>> partition CONTENTS. |
| 15 |
>> |
| 16 |
> |
| 17 |
> Yes, I was clutching at straws, rather. |
| 18 |
> |
| 19 |
>> Use gparted (or gdisk) on the DISK, and that should sort things out. |
| 20 |
>> Check whether it thinks those partitions exist or not, and then get it |
| 21 |
>> to write a new partition table to clean things up. |
| 22 |
>> |
| 23 |
> |
| 24 |
> Gparted 0.31.0 on my rescue CD finds no problems. Parted in this system doesn't |
| 25 |
> offer a checking tool, but gdisk does and it reports "no problems". Gparted |
| 26 |
> 1.1.0 in this system still reports the errors, but only once now on each disk |
| 27 |
> (so what's changed there? Beats me). |
| 28 |
> |
| 29 |
> Udisks was upgraded on 13 August and I may not have used gparted since then, |
| 30 |
> but reverting to the previous version hasn't helped. All the other packages I |
| 31 |
> mentioned have not been changed for months. |
| 32 |
> |
| 33 |
> So I'm still left wondering what to do. I'm happy that the hardware isn't on |
| 34 |
> the blink, anyway. |
| 35 |
> |
| 36 |
> -- |
| 37 |
> Regards, |
| 38 |
> Peter. |
| 39 |
> |
Archives