=== ssh07322 is now known as ssh0732
[11:11] <andypandy> Hello. I am trying to upgrade my EOL Ubuntu Server according to https://help.ubuntu.com/community/EOLUpgrades but when I attempt to run the ./impish upgrade script I get errors messages.
[11:11] <andypandy> Unable to init server: Could not connect: Connection refused
[11:11] <andypandy> (impish:4244): Gtk-CRITICAL **: 13:09:11.291: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed
[11:45] <tomreyn> --frontend=DistUpgradeViewText   (as suggested in #ubuntu)  seems to have helped
=== andypandy_ is now known as andypandy
[13:29] <aaal> how to re-install / recover (default) grub?
[13:29] <aaal> is it apt install grub-common or grub2-common?
[13:33] <tomreyn> aaal: depends on how you're booting / which architecture. is this amd64 with uefi booting?
[13:33] <tomreyn> which ubuntu release?
[13:34] <aaal> amd64 
[13:34] <aaal> not sure if uefi, it's kvm
[13:34] <tomreyn> echo -n 'This system booted via: '; [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS 
[13:34] <aaal> release is 1804 or 2004
[13:34] <tomreyn> lsb_release -ds
[13:35] <tomreyn> if you'll run these commands you'll have the exact answers
[13:35] <aaal> bios
[13:35] <aaal> 1804
[13:36] <tomreyn> just a notice: free support for 18.04 will end mid last year
[13:37] <aaal> im not sure but the culpit may be me installing ubuntu-server which replaced grub with grub-ec2 and then maybe some error, yes i will jump to 2204
[13:37] <tomreyn> is this an ec2 instance then?
[13:37] <aaal> it's not aws so no?
[13:38] <tomreyn> okay, i was just wondering because you mentioned grub-ec2
[13:39] <aaal> yes, it was my mistake doing any of it
[13:39] <aaal> i tried to install grub2-common but got some error /dev missing (im in chroot
[13:40] <tomreyn> i think it'll be best to purge all grub* packages and install grub-pc
[13:41] <tomreyn> then grub-install to the boot disk
[13:47] <aaal> grub-probe: error: cannot find a device for / (is /dev mounted?)
[13:47] <aaal> but it should be
[13:48] <aaal> anyway grub-pc is what  i was looking for
[13:49] <aaal> nvm about the error
[13:55] <tomreyn> aaal: well that's not a good sign if grub can't find the root device
[13:56] <aaal> mount -o rbind /dev /mnt/dev etc
[13:56] <aaal> there's hope
[13:56] <tomreyn> ? is this a chroot?
[13:57] <aaal> yes
[13:59] <tomreyn> then you probably don't need grub in the first place
[14:00] <aaal> i mean i have to chroot to rescue my install
[14:00] <aaal> no?
[14:00] <tomreyn> oh this system currently won't boot. i wasn't aware of that.
[14:00] <aaal> yes i dungoofed
[14:01] <aaal> grub install to drive NOT partition yes?
[14:02] <tomreyn> yes, grub no longer supports installation to partitions other than a dedicated bios_grub partituon on gpt.
[14:02] <tomreyn> https://help.ubuntu.com/community/LiveCdRecovery
[14:03] <tomreyn> https://help.ubuntu.com/community/Grub2/Installing
[14:03] <aaal> ok done no errors
[14:04] <tomreyn> i forgot to tell you to also run update-grub.
[14:04] <aaal> ok
[14:04] <aaal> https://bpa.st/4IEQ
[14:05] <aaal> looks like it should boot yes?
[14:06] <aaal> https://bpa.st/VTXQ
[14:06] <tomreyn> it doesn't say that it won't
[14:07] <aaal> https://bpa.st/2CHA 
[14:07] <aaal> did update-gr
[14:08] <aaal> i think that was it..?
[14:08] <tomreyn> if grub.cfg actually refers to these kernels and grub is installed on the bios boot device then is should work
[14:12] <aaal> quit chroot but can't umount /dev/ says it's busy
[14:13] <aaal> unmounted sys and proc fine
[14:16] <aaal> nvm
=== PeGaSuS is now known as James
=== James is now known as PeGaSuS