Partitions ... have been written, but we have been unable to inform the kernel of the change

General system Kernel, boot, graphics & hardware
1

Partitions … have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should probably reboot now before making further changes.

This is happening in both gparted & gnome-disk-utility on all of my disks (OS, data1, data2, etc…). Rebooting and then using either program results in the same error.

I’ve never had this error before, and I don’t want all of my harddrives ruined. What should I do?

Screenshot_2020-09-12_22-02-40
Screenshot_2020-09-12_22-02-401764×718 478 KB

2

Right now there is a libparted problem. See: Gparted - Libparted error

2 Likes
3

You typically get that error when you haven’t unmounted a disk prior to making changes. If you did that, and still getting it, :man_shrugging:

2 Likes
4

I just updated the kernel today :sob:

I hope this doesn’t brick my disks…

5

From what I’ve been reading, this is a 5.8.X kernel problem. There are GIT reports that the up-coming 5.9.X kernel does not have this…so hang tight.

4 Likes
6

Thread already here here.

It won’t break the disk, nor is there actually a problem with Disk or Gparted. Those messages as far as I can tell are erroneous ones created by the kernel update.

3 Likes
8

@AlienProber

I used an older EndeavourOS live cd, and that version of gparted needed to run e2fsck before it made any changes.

I ran e2fsck on my drives and found several superblock errors. One partition of one drive was completely erased.

Be cautious.

9

Temporarily run the LTS kernel until this gets fixed. That worked for me.
Use AKA to install the LTS kernel if you don’t already have it installed.

Pudge

2 Likes
10

Or simply:

sudo pacman -S linux-lts linux-lts-headers
2 Likes
11

completely unrelated. This is a kernel issue. Gparted itself has not had an update since long before this kernel update.

12

@Kresimir,

Thank you for the exact command. I’ll try that later today after work.

13

Don’t worry your selves its all fixed today with Arch testing soon be in stable just a Kernel update that’s all.

3 Likes
14

I can confirm @mandog 's comment: linux 5.8.9.arch2-1 fixes this issue.

1 Like
15

no it is NOT in 5.8.9 Stable kernel ( unless you have added these patch for Archlinux )
it will be added to next version 5.8.10

this actually breaks libparted & dm raid if not patched

2 Likes
16

Didn’t say anything about it being stable :wink: . Just tested the mentioned kernel from “Testing” and can confirm the message that’s been bothering some posters here is gone.

Did not check if something else breaks instead … :upside_down_face:

1 Like
17

Thanks much appreciated.

18

No issue with Gparted with 5.8.9-zen2-1-zen (from Testing repo).

1 Like
19

Now I just need to have that update available for me through official repos :sweat_smile:

1 Like
20

Patience is a virtue!

Something I unfortunately lack :sweat_smile:

2 Likes
21

Same here.
Funny how people complain when there is a kernel update every day and also complain when these updates stop :laughing:

3 Likes