Output from os-prober showing non existent entries

I get this output when installing packages from Pamac:

Found Manjaro Linux on /dev/mapper/luks-95a9c47a-ede8-438c-a436-9e117a7636a9
Found Debian GNU/Linux 10 (buster) on /dev/mapper/luks-95a9c47a-ede8-438c-a436-9e117a7636a9
Found Debian GNU/Linux 10 (buster) on /dev/mapper/luks-95a9c47a-ede8-438c-a436-9e117a7636a9
Found Ubuntu 20.04.3 LTS on /dev/mapper/luks-95a9c47a-ede8-438c-a436-9e117a7636a9

How do remove the entries under Manjaro?

please change title ! it’s not pamac

grub (or other ?) found some linux and you want remove theses entries

It’s at you to uninstall these linux (remove theses partition…)

The problem is that those partitions don’t exist.

I guess it’s the result of os-prober while updating grub during kernel update.

I fail to see the real issue here.

Problem is that those installs don’t exist.

Type here the result of sudo os-prober.

/dev/mapper/luks-95a9c47a-ede8-438c-a436-9e117a7636a9:Manjaro Linux:Manjaro:linux:btrfs:UUID=529d3098-72b8-4134-a612-a89662ab4bda:subvol=timeshift-btrfs/snapshots/2021-09-24_21-54-12/@
/dev/mapper/luks-95a9c47a-ede8-438c-a436-9e117a7636a9:Debian GNU/Linux 10 (buster):Debian:linux:btrfs:UUID=529d3098-72b8-4134-a612-a89662ab4bda:subvol=timeshift-btrfs/snapshots/2021-09-24_21-54-12/@/var/lib/docker/btrfs/subvolumes/417c3b90a80e137aa667e1d23635d52ed3449d5239b9a992e438bc85a041413a
/dev/mapper/luks-95a9c47a-ede8-438c-a436-9e117a7636a9:Debian GNU/Linux 10 (buster):Debian1:linux:btrfs:UUID=529d3098-72b8-4134-a612-a89662ab4bda:subvol=timeshift-btrfs/snapshots/2021-09-25_23-56-01/@/var/lib/docker/btrfs/subvolumes/b5fead9f541aa310e70c07ae06f8b9a26e99d9642500b6280f3312d66182f77e
/dev/mapper/luks-95a9c47a-ede8-438c-a436-9e117a7636a9:Ubuntu 20.04.3 LTS:Ubuntu:linux:btrfs:UUID=529d3098-72b8-4134-a612-a89662ab4bda:subvol=timeshift-btrfs/snapshots/2021-09-25_23-56-01/@/var/lib/docker/btrfs/subvolumes/e6d3d878a86e63fbad81e4ce26fa9dd1eb43e28b509884556c2134c68dcf8dbd


thes linux are in docker

I do not use docker anymore. How do I remove them?

Is os-prober even supposed to run after every package installation?

docker ps;  docker rm XXX  [ docker images ; docker rmi YYY ]

os-prober run after all kernel update

os-prober runs for me on every package transaction.

After each kernel update, it does sudo update-grub that you can also launch manually.
Within grub config, you get os-prober that is launched alongside.

As @papajoke said, it’s only for kernel related updates, so not as often that regular packages.

Edit: do you complete the update of all the packages? Or do you perform partial updating?

complete update

I don’t use either encryption, nor docker. I don’t know what happens during updates then.

If not using it anymore, I’d flush the docker containers (no idea how, though).

me to :rofl: GNU GRUB - Bugs: bug #53688, os-prober found dockers conteners... [Savannah]

I had an archlinux in /dev/sda10 (btrfs)
os-prober couldn’t find my archlinux but find my containers :upside_down_face:

If it wasn’t fixed since 2018 it probably won’t be fixed anytime soon.

Btrfs, LUKS, Docker…
Winning combo.

Not even close. Throw in a laptop with WiFi, hybrid AMD/Nvidia graphics, a touchpad, a Bluetooth dongle, a dual-boot setup with Windows 11, and a n00b who likes hardcore gaming through Steam and Lutris on triple monitors with a HDMI connection, and then you’ll be closer to winning the prize. :rofl:

But of course, btrfs with Docker containers on LUKS is a good start. :stuck_out_tongue:

I had no docker containers, volumes or images installed. Seems that os-prober was picking up the btrfs snapshots. I just removed the offending snapshots.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.