[03:11] <wholesum> how do i rebuild grub? I can access the system partition (and the LVM) using the liveCD. it's 18.04.1.
[03:11] <wholesum> i've been struggling for the past 24 hrs, i'm afraid i'm going to lose my job...
[03:12] <wholesum> i already tried to use refind, reinstalling grub, and a lot of other things.
[03:27] <sarnold> wholesum: if you mean, how to ask grub to rebuild the menu, configuration, etc, then try 'update-grub' -- the /etc/default/grub file points there
[03:27] <wholesum> i'm in grub rescue now
[03:28] <wholesum> sarnold: you can see the grub info here (menuentry ubuntu, ignore above) https://pastebin.com/AuiAvrjY
[03:30] <sarnold> wholesum: you might have better success in #ubuntu -- many of the folks here haven't seen grub in years, but the #ubuntu folks help debug install problems a lot more often
[03:31] <wholesum> sarnold: what are you using? refind? i had better luck with that, but not enough to boot my system
[03:31] <wholesum> i can do away with grub, there is only one OS in the system
[03:32] <wholesum> BTW not a install problem. server has been running fine for almost 1 year. last night I rebooted and it told me no OS found
[03:33] <sarnold> wholesum: I've never needed to do anything like this, ever
[03:34] <sarnold> wholesum: refind is in universe, so it wouldn't be the preferred choice; efibootmgr is in main, it's probably the ubuntu preferred tool
[03:35] <wholesum> how would i go about configuring it from a live CD? set the boot order to use the partition where ubuntu is installed?
[03:39] <sarnold> you could chroot to the mounted path..
[03:40] <sarnold> it'd be something like: (untested) (pretend the instal;led system is mounted on /mnt/root) mount -obind /proc/ /mnt/root/proc ; mount -obind /sys/ /mnt/root/sys/ ; chroot /mnt/root /bin/bash
[03:50] <wholesum> will try!
[03:53] <wholesum> so once i have a shell inside the installed system i play with efibootmgr?
[04:06] <wholesum> sarnold: I'm in the shell for the installed system
[04:09] <wholesum> I cleaned up efibootmgr to have only a single entry: ubuntu
[04:29] <lotuspsychje> wholesum: why is your server not up to date to .2?
[04:30] <wholesum> lotuspsychje: didn't want an upgrade to bork it up and can't afford downtime on it...
[04:30] <lotuspsychje> wholesum: there are like tons of security updates out, and now your system is also borked
[04:31] <wholesum> it was fully up to date, on a daily basis
[04:31] <lotuspsychje> wholesum: is that an intel cpu?
[04:32] <wholesum> but on 18.04.1
[04:32] <wholesum> yes, i5
[04:32] <wholesum> disk is NVME SSD with secure boot
[04:32] <lotuspsychje> wholesum: we had several users reporting unable to boot on the new !mds
[04:33] <wholesum> whats the new !mds? i'm not using raid
[04:33] <lotuspsychje> wholesum: did you change uefi settings recently?
[04:33] <lotuspsychje> !mds
[04:33] <wholesum> ah yes, the new vuln
[04:33] <wholesum> uefi settings have not been changed in months...
[04:34] <lotuspsychje> wholesum: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620
[04:34] <wholesum> i am the single user on this machine, running only trusted apps. i am going to disable all mitigations later
[04:34] <lotuspsychje> maybe worth testing?
[04:35] <lotuspsychje> ill be out for breakfast first
[04:35] <wholesum> i doubt that's it, but i will look at it
[04:35] <wholesum> it's a lenovo box
[04:36] <wholesum> no cryptsetup
[05:06] <lotuspsychje> wholesum: you might also wanna browse https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bugs?orderby=importance&start=0
[05:06] <wholesum> thx and good morning
[05:06] <wholesum> :)
[05:06] <lotuspsychje> there's tons of grub installer bugs noticed recently
[05:06] <wholesum> i reinstalled from 18.04.2 server (not live)
[05:07] <wholesum> i have an image of the previous install system partition
[05:07] <lotuspsychje> ah
[05:08] <wholesum> i'm thinking about booting into the desktop live usb again, and copying this image over the (same size) current  system partition. do you think it would work?
[05:08] <wholesum> setting up everything again will take weeks...
[05:13] <lotuspsychje> wholesum: dont you have a backup of your configs, or can preserve your /home on a new installer?
[05:14] <wholesum> lotuspsychje: too many applications installed and configured, and 4 users. but i do have a backup of /home inside the img of the entire system partition
[07:57] <raddy> Hello Everybody
[07:59] <raddy> I am using ubuntu 16.04.5 in AWS
[07:59] <raddy> tmpfs has 377M free space
[08:00] <raddy> But it still says there is no free space
[08:00] <tomreyn> which tmpfs?
[08:01] <raddy> You mean ?
[08:01] <raddy> tmpfs           377M     0  377M   0% /run/user/1000
[08:02] <tomreyn> raddy: so you're trying to write to somewhere below /run/user/1000/ ?
[08:02] <raddy> I am trying write in /tmp/
[08:03] <tomreyn> then the above output is not relevant, try this:  df -h /tmp
[08:05] <raddy> Filesystem      Size  Used Avail Use% Mounted on
[08:07] <tomreyn> raddy: now repeat the line which wasn't transferred since it started with a slash. add a blank space as the first character
[08:09] <raddy> tomreyn: I don't get you, but I don't have separate /tmp file system
[08:11] <tomreyn> raddy: so how much free unallocated space do you have in / ?
[08:12] <tomreyn> raddy: alternatively, run this and post the url:  df -h /tmp 2>&1 | nc termbin.com 9999
[08:13] <raddy> 2.4Gb free space is available
[08:21] <tomreyn> raddy: that's not a lot. if it's an ext{2,3,4} file system, then 5% are reserved for the root user by default
[08:22] <tomreyn> 5% of the total file system
[08:22] <tomreyn> another explanation could be that all inodes are in use: df -hi /tmp
[08:30] <raddy> tomreyn: You nailed it. that is the issue
[08:34] <raddy> tomreyn: find . -type f | wc -l shows the /tmp/ has only 80 files
[08:35] <RoyK> tomreyn: df reports the available space after the 5% is subtracted. also, tmpfs doesn't have that. the reserved space can be tuned with tune2fs -m<something> /dev/sd<something>
[08:35] <raddy> But 512k inodes being shown as used
[08:37] <raddy> Please help
[08:38] <raddy> I got it
[08:39] <tomreyn> you'll need to create a new file system, specifying a higher amount of inodes (-I)
[08:40] <tomreyn> actually i didn'T explain this properly, read the man page, please
[08:41] <tomreyn> actually -N is what you'd need,-I just changes the inode size.
[14:04] <jamespage> coreycb, sahid: train milestone 1 is next week so we should make a plan to upload snapshots to eoan
[14:05] <coreycb> jamespage: sounds good
[19:44] <jiffe> so I'm trying to install ubuntu 18.04 on a desktop, it installs find but doesn't boot, no grub menu or anything I just get a flashing cursor in the top right
[19:44] <jiffe> boot order is correct, its booting from hd
[19:45] <lordcirth> jiffe, you are installing Ubuntu desktop or server ISO? EFI or BIOS?
[19:46] <jiffe> ubuntu server, not sure about the later let me check
[19:53] <jiffe> yeha looks like bios, nothing about uefi in here
[19:53] <jiffe> or efi
[19:53] <jiffe> this is an old P4 machine
[20:02] <lordcirth> jiffe, pentium 4? 32 or 64bit?
[20:03] <jiffe> 64 bit
[20:06] <jiffe> I see people having success with something similar running boot-repair from a live cd
[22:03] <tomreyn> jiffe: which installer did you use (.iso filename)? and which version of the installer? were there any warnings or errors while installing?
[22:05] <tomreyn> also, with hardware this old (with known unfixed security bugs), you'll want the latest firmware available to be installed, i'd say. did you check you have that?