Urbackup changing root device even after uninstall

client
#1

Urbackup changes your root device to a DM device of its own creation, even after uninstalling, here are the offending lines:

 /usr/share/initramfs-tools/scripts/local-top/urbackup-setup-snapshot:34:echo "0 $RBD_SIZE linear $RBD 0" | dmsetup create root-98d1f8b1f435 2> /dev/kmsg
/usr/share/initramfs-tools/scripts/local-top/urbackup-setup-snapshot:36:echo "export ROOT=/dev/mapper/root-98d1f8b1f435" > /conf/param.conf

This had me going crazy. I couldn’t for the life of me figure out what was changing my root device mid-boot. It kept coming back after I removed the offending lines in the initrd and other boot scripts. I had to grep my whole boot volume looking for it. Especially confusing since I uninstalled the urbackup client from this computer months ago. This screws up the ubuntu update-grup script which sets the root volume in grub.cfg to the mapped volume, that doesn’t get mapped till after root is mounted, which causes boot to fail.

Edit: This was on Ubuntu 19.04

#2

Sry, yeah, I ran into that update-grub on kernel update problem myself as well (and improved the error somewhat in that case, but wasn’t able to make grub discover the real device).

Will definitely add a remove on uninstall…

I think the only proper solution is to have the whole thing integrated in grub and/or Debian/Ubuntu.

#3

It would be nice to maybe throw a “UrBackup setting root device to $devicename” or something like that into the system log so that if things do go screwy they’re easier to track down.

#4

@nixcamic @uroni How exactly did you end up fixing the issue with your root device. I seem to have run into the same thing on linux mint and i really dont know enough about the boot system to figure out how to fix it.

1 Like
#5

@PrimevalGod @nixcamic Did you guys get a solutin to this issue. I m stuck on this

#6

@Andile_Simelane I never got an answer to this. I did manage to fix my laptop unfortunately I don’t really know how.

1 Like