/srv/irclogs.ubuntu.com/2022/08/20/#ubuntu-server.txt

=== ssh07322 is now known as ssh0732
andypandyHello. 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
andypandyUnable to init server: Could not connect: Connection refused11:11
andypandy(impish:4244): Gtk-CRITICAL **: 13:09:11.291: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed11:11
tomreyn--frontend=DistUpgradeViewText   (as suggested in #ubuntu)  seems to have helped11:45
=== andypandy_ is now known as andypandy
aaalhow to re-install / recover (default) grub?13:29
aaalis it apt install grub-common or grub2-common?13:29
tomreynaaal: depends on how you're booting / which architecture. is this amd64 with uefi booting?13:33
tomreynwhich ubuntu release?13:33
aaalamd64 13:34
aaalnot sure if uefi, it's kvm13:34
tomreynecho -n 'This system booted via: '; [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS 13:34
aaalrelease is 1804 or 200413:34
tomreynlsb_release -ds13:34
tomreynif you'll run these commands you'll have the exact answers13:35
aaalbios13:35
aaal180413:35
tomreynjust a notice: free support for 18.04 will end mid last year13:36
aaalim 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 220413:37
tomreynis this an ec2 instance then?13:37
aaalit's not aws so no?13:37
tomreynokay, i was just wondering because you mentioned grub-ec213:38
aaalyes, it was my mistake doing any of it13:39
aaali tried to install grub2-common but got some error /dev missing (im in chroot13:39
tomreyni think it'll be best to purge all grub* packages and install grub-pc13:40
tomreynthen grub-install to the boot disk13:41
aaalgrub-probe: error: cannot find a device for / (is /dev mounted?)13:47
aaalbut it should be13:47
aaalanyway grub-pc is what  i was looking for13:48
aaalnvm about the error13:49
tomreynaaal: well that's not a good sign if grub can't find the root device13:55
aaalmount -o rbind /dev /mnt/dev etc13:56
aaalthere's hope13:56
tomreyn? is this a chroot?13:56
aaalyes13:57
tomreynthen you probably don't need grub in the first place13:59
aaali mean i have to chroot to rescue my install14:00
aaalno?14:00
tomreynoh this system currently won't boot. i wasn't aware of that.14:00
aaalyes i dungoofed14:00
aaalgrub install to drive NOT partition yes?14:01
tomreynyes, grub no longer supports installation to partitions other than a dedicated bios_grub partituon on gpt.14:02
tomreynhttps://help.ubuntu.com/community/LiveCdRecovery14:02
tomreynhttps://help.ubuntu.com/community/Grub2/Installing14:03
aaalok done no errors14:03
tomreyni forgot to tell you to also run update-grub.14:04
aaalok14:04
aaalhttps://bpa.st/4IEQ14:04
aaallooks like it should boot yes?14:05
aaalhttps://bpa.st/VTXQ14:06
tomreynit doesn't say that it won't14:06
aaalhttps://bpa.st/2CHA 14:07
aaaldid update-gr14:07
aaali think that was it..?14:08
tomreynif grub.cfg actually refers to these kernels and grub is installed on the bios boot device then is should work14:08
aaalquit chroot but can't umount /dev/ says it's busy14:12
aaalunmounted sys and proc fine14:13
aaalnvm14:16
=== PeGaSuS is now known as James
=== James is now known as PeGaSuS

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!