/srv/irclogs.ubuntu.com/2022/04/30/#lubuntu.txt

bob5config table fw_platformsize runtime systab00:07
bob5efivars fw_vendor runtime-map vars00:07
bob5sudo parted-l is huge00:07
bob5partition table is GPT00:08
arraybolt3OK good.00:08
arraybolt3That's all I need to know from those.00:08
bob5the motherboard is set to both UEFI and legacy boot. I tried running it in either of them and it didn't help00:09
bob5running in both was best as it showed all options in boot menu00:09
arraybolt3OK.00:09
bob5the motherboard would detect "ubuntu" but it stayed broken no matter what I did00:09
arraybolt3What all different operating systems do you have on there?00:09
bob5only lubuntu now00:10
bob5I use to have windows lubuntu and mint00:10
bob5w7*00:10
arraybolt3Oh OK. You have an EFI partition near the very beginning of the drive, right?00:11
bob5I just opened a fiel from the partition that was restored from the usb and it works well00:12
bob5yes I have a 200mb Ext4 sda100:12
bob5bios-grub flag is unchecked (checking it didn't fix it before)00:13
arraybolt3OK. And your BIOS is telling you that it can't find any OS when you try to boot?00:13
bob5No it lists the HDD and ubuntu as boot options00:13
bob5after that it would either say cannot read or write outsie hd0 or no OS found or maybe a 3rd options and entering grub rescue mode00:14
arraybolt3And both options result in an error message about no OS?00:14
bob5yes I could test it again now but I'm sure I've tried it00:14
arraybolt3OK! Good to know. Then I think you don't even have to reinstall the bootloader. I think you just need to regenerate the configuration.00:14
arraybolt3Can you do "ls /mnt" real quick? It should be empty.00:14
bob5I mean the option would change depending on what I did to try to get it to work00:14
bob5nothing happened00:15
arraybolt3That's fine. You're description sounds like the bootloader is working, but can't find the operating systems. This is very easy to fix.00:15
arraybolt3Good. So, mount your EFI partition using "sudo mount <path to EFI partition> /mnt".00:16
bob5right now the disk has the following: EFI, unallocated(u) 800mb, Shrinked OS part, u, backup of original size OS part, u, restored shrink OS part00:16
bob5, u00:16
arraybolt3That's fine. Just mount the EFI partition.00:17
arraybolt3(You can use "lsblk" to find your EFI partition.)00:17
bob5ok /dev/sda1 worked00:18
arraybolt3OK. Can you tell me the results of "ls /mnt/boot"?00:18
bob5no such file or dir00:18
arraybolt3Perfect. Do "sudo mkdir /mnt/boot00:18
arraybolt3Then do "sudo mkdir /mnt/boot/grub"00:19
arraybolt3Let me know whenever those are done.00:20
bob5done00:27
bob5I'd appreciate for my learning that you tell me what the commands do00:28
arraybolt3ls tells you the contents of a folder.00:28
arraybolt3mkdir makes a folder.00:29
arraybolt3lsblk tells you what block devices (usually disk drives) are in your system.00:29
arraybolt3So what we're doing right now is creating extra folders in your UEFI partition, where we'll get to put the GRUB configuration.00:29
arraybolt3This should enable your system to boot.00:30
arraybolt3OK, so, I'm doing some research, 'cause I'm realizing my setup is a bit weird, and I'd like things to just continue to work as normal for you once this is done. You're still restoring the backup partition, right?00:31
bob5No the backup partition was restored00:37
bob5and It works00:37
bob5so I have both the /home/ folder backup and a partition backup on USBs00:37
bob5by works I mean I can access and open files from it00:38
arraybolt3OK. I've almost finished getting the final solution made, hang tight for just a sec...00:38
bob5I'm going to fix my table I'll be back00:42
arraybolt3OK. I think I've got everything figured out, I'm doing one final test to be sure, if it works, I'll give you the commands.00:43
arraybolt3Alright, whenever you're back, I'm ready.00:52
bob5lol01:07
bob5rdy01:07
arraybolt3OK. "sudo grub-mkconfig -o /mnt/boot/grub/grub.cfg"01:08
arraybolt3That should generate the boot configuration file and enable your system to boot again. We're not quite done yet, though.01:08
bob5.01:10
bob5 /usr/sbin/grub-probe: error: failed to get canonical path of '/cow'01:11
arraybolt3Duh... what? Are you sure you didn't make a typo?01:11
bob5yeah01:12
bob5the prior command was sudo mkdir /mnt/boot/grub01:13
arraybolt3Crud. I've never seen that error before in my life.01:13
arraybolt3And that command runs perfectly on my system..01:14
arraybolt3I'm looking up what the error means.01:15
arraybolt3Oh I see why it's gone berzerk. 01:16
arraybolt3Hold on, I think I've got the solution. I'm almost there.01:17
arraybolt3OK, so the error appears to be because grub-mkconfig is getting confused because of our directory setup.01:21
arraybolt3Can you tell me the "/dev/sd<whatever>" of your main partition?01:22
arraybolt3It's /dev/sda3 right?01:22
bob5sda401:24
arraybolt3OK. And /dev/sda1 is your EFI partition, correct?01:24
bob5wouldn't mind booting to sda 201:24
bob5yes01:24
arraybolt3OK. Try this:01:24
arraybolt3sudo umount /dev/sda101:25
arraybolt3sudo mount /dev/sda2 /mnt01:25
bob5sda1 and sda3 are shrinked versions so I would have to extent them later01:25
arraybolt3sudo mount /dev/sda1 /mnt/boot/efi01:25
arraybolt3sudo chroot /mnt01:25
arraybolt3sudo grub-mkconfig -o /boot/efi/boot/grub/grub.cfg01:25
arraybolt3exit01:25
arraybolt3That should get the mounts all in the way that grub-mkconfig wants, and then let it make the config file.01:26
bob5last command gave sudo: grub: command not found01:26
bob5oh wait01:27
arraybolt3Probably did a space rather than a dash01:27
arraybolt3(You'll notice the new "chroot" command - this gives you a shell that believes the root directory is whatever directory you tell it. This makes it so that grub-mkconfig can find all the files it expects.)01:28
bob5 /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).01:29
arraybolt3How'd it go? Did it print some output about "sourcing configuration files" and "found initrd" and stuff like that?01:29
bob5no01:29
bob5just gave what I wrote01:29
bob5maybe it would be easier to edit mount points in KDE01:30
arraybolt3Oh I just saw that. Argh, forgot that about chroots...01:30
bob5nvm01:30
arraybolt3OK, so type "exit", then do "sudo mount --bind /dev /mnt/dev"01:31
arraybolt3Then do "sudo chroot /mnt" again.01:31
arraybolt3Then do "sudo grub-mkconfig -o /boot/efi/boot/grub/grub.cfg" again.01:32
bob5it's doing lots of stuff now01:35
arraybolt3That's a good sign!01:35
bob5cannot find list of partitions01:35
arraybolt3Hmm. OK, sounds like we need to do another bind mount. Do "exit".01:36
arraybolt3OK, my research is failing me. Bear with me while I get a test environment set up, this shouldn't take long.01:37
arraybolt3OK, getting my test stuff booted.01:38
zobUploaded file: https://uploads.kiwiirc.com/files/1f8b72e2ccf6de42e9816cc3d2215e23/pasted.txt01:39
arraybolt3Got it! Here's the command sequence (assuming you did the "exit" already). I'll look at your file first.01:41
arraybolt3Oh wait, wrong guy's file.01:41
arraybolt3@bob3 Command sequence:01:41
arraybolt3@bob5 Command sequence:01:41
arraybolt3sudo mount --bind /proc /mnt/proc01:41
bob5no that's also me01:41
arraybolt3sudo mount --bind /sys /mnt/sys01:41
arraybolt3sudo chroot /mnt01:41
arraybolt3grub-mkconfig -o /boot/efi/boot/grub/grub.cfg01:41
arraybolt3OK, I'll look at it.01:41
zobgot a bunch of fails will give u txt01:42
arraybolt3Yeah, that's similar to what I saw. The command sequence fixed it, but I'll look at what fails you got this time.01:42
zoboh wait it did find them01:42
arraybolt3Do you see "found linux image" in the output?01:42
zobUploaded file: https://uploads.kiwiirc.com/files/8cc35c915b38e688efe7df528cf2dbc7/pasted.txt01:42
zobyes!01:43
arraybolt3Uh... you may have missed the "sudo mount --bind /proc /mnt/proc" part.01:43
arraybolt3Do this:01:43
arraybolt3exit01:43
arraybolt3sudo mount --bind /proc /mnt/proc01:43
zobI did miss it01:43
arraybolt3sudo chroot /mnt01:43
arraybolt3Now do grub-mkconfig again.01:43
arraybolt3Upload the results when it's done and I'll tell you if it's good.01:44
zobshouldn't i do the sys part first?01:44
arraybolt3If you already did the sys part, you don't need to do it again.01:44
arraybolt3And it doesn't matter what order you do the "mound --bind" commands in.01:44
arraybolt3As long as you do them before the chroot.01:45
zobthink we got it01:45
arraybolt3What's the output look like? (It's probably good.)01:45
zobnow I'll have to delete all but one of the isntalls to not get confused01:45
zobUploaded file: https://uploads.kiwiirc.com/files/8ed29f41c21c82d1e8897d80d3716135/pasted.txt01:46
arraybolt3OK, there's one last step before everything's done.01:46
arraybolt3Looks good!01:46
zobWhen we're done I'd like a summary of what to do in the future for my notes01:46
zobif it happens again01:46
arraybolt3Alright, reboot, **remove the live ISO**, and boot into the fixed system.01:46
arraybolt3And yes, I'd be happy to give you a summary.01:47
bob5ok when I boot all I get is ubuntu followed by STA xxxxx whatever the drive name is01:48
bob5dman01:48
arraybolt3Does selecting an option in the menu do anything?01:48
arraybolt3Or are you stuck at a "/dev/sdXY clean" something or other prompt?01:48
bob5ubuntu gave " error file '/boot/grub/i386-pc/normal.mod' not found, entering rescue mode... grub rescue>01:48
bob5I don't recall if EFI was fresh or was after running boot-repair01:49
arraybolt3And confusingly, I'm not seing /dev/sda2 as an option to boot from in your grub-mkconfig output.01:49
arraybolt3Oh, wait, i386-pc : the thing's trying to boot in BIOS mode. Change it to EFI mode and try again.01:49
arraybolt3We just did a bunch of repairs for EFI, and now it's trying to boot with BIOS - that won't work.01:50
bob5holy shit I see something for the first time01:50
arraybolt3Anything good?01:50
bob5There's an additional bios option for storage boot option control01:50
bob5it was set to legacy only01:50
arraybolt3Yep, that's what it looked like.01:50
bob5noo same error01:50
bob5I set it to UEFI first01:51
arraybolt3Even in EFI mode? And the error says "i386-pc" in it?01:51
bob5yes01:51
arraybolt3OK, so this part will be interesting. Boot the live ISO again. We're going to do a manual bootloater install. (I've run into this same sort of thing on my systems.)01:51
bob5What should the mobo do? uefi only?01:52
bob5I could try uefi only for both options01:52
arraybolt3Yes, UEFI only. Actually, do that first before booting the live ISO.01:52
arraybolt3Your system keeps booting a BIOS copy of GRUB, when it needs a UEFI copy for the fixes we did to work.01:52
arraybolt3Once you've got UEFI only set, reboot without the live ISO.01:53
bob5reboot and select proper boot device01:53
arraybolt3Select your hard drive.01:53
bob5will select it now instead of leaving it to auto01:53
arraybolt3Do you get a GRUB menu or a desktop?01:53
bob5only option now is ubuntu and I get same error01:54
bob5It worked with UEFI before it stopped working01:54
bob5I had a menu where I could choose lubuntu mint or windows01:54
arraybolt3Yeah, sounds like something's gone awry with your bootloader. Really, at this point, it might be best to reinstall from scratch, since your system has a LOT of really weird config on it, but if we want to repair it still, we can install the bootloader.01:55
bob5bootloader is something in the EFI?01:55
arraybolt3Sorta. It's a mini-OS that your system boots first, and it finds Linux and boots it.01:55
arraybolt3It should be in your EFI partition.01:55
arraybolt3(While we're at this, we should change the EFI partition to fat32 - I've never seen an EXT4 EFI partition before, so I wonder if that's part of the problem.)01:56
arraybolt3OK, so boot into the live ISO. It has everything we need.01:56
arraybolt3Once you're in the live ISO, open KDE Partition Manager, and reformat the EFI partition to fat32. Make sure to set the "boot" flag on it when you do that.01:57
bob5the thing about KDE is the only flag option is "bios-grub"01:59
arraybolt3Hmm, that's odd. You're right-clicking the EFI partition, clicking Reformat, and selecting "fat32", right?01:59
bob5Buit I can download gnome-disk-utility01:59
arraybolt3Ugh, that's awful. Use "GParted". "sudo apt install gparted"02:00
arraybolt3I mean, if you're used to gnome-disk-utility, do whatever works for you, I just find it confusing and easy to make mistakes in.02:00
bob5where do I find this irc channel?02:03
arraybolt3https://lubuntu.me/links/02:04
arraybolt3It's near the top of the page.02:04
bob5it's not lubuntu.net or lubuntu.me02:04
arraybolt3Lubuntu.me.02:04
bob5got it02:05
arraybolt3Lubuntu.net is an unofficial site that the Lubuntu devs have tried to get taken down. There's a whole fight over it in a bug report.02:05
bob5is it malicious?02:05
arraybolt3Dunno, but it's incorrect for sure.02:05
zoblibparted error: the backup gpt table is corrupt, but the primary appears OK so that will be used02:06
arraybolt3I think some former Lubuntu guy made it, and then when he left the team, he didn't let the site down. I could be wrong (probably someone else in this channel has better details)02:06
zobI remember I checked these before and only the header was corrupted02:06
zobthen after restoring header from ehader backup all were good02:06
arraybolt3Oy! That's... possibly part of your problem.02:06
zobboth aprtition priamry and backup were always good02:06
zobso this is news02:06
arraybolt3I'm guessing you've been messing with this system's partitions a lot?02:06
zoba lot02:07
zobI didn't save my instructions to fix this02:07
arraybolt3Yeah, it *might* be fixable at this point, but you have plenty of backups. I'd recommend reinstalling from scratch and then restoring from one of your home backups. That will be far more effective and probably much faster than any repair we can do at this point.02:07
arraybolt3Also, if you like messing with new operating systems like I do, you should look into virtualization. Once you're system is working again, do "sudo apt install virt-manager" and enjoy.02:09
zobIf I overwrite the new install aprtition with the backup, will it work?02:09
zobno I had another use case02:09
arraybolt3No, erase disk and install Lubuntu. If your apps don't work, we can mess with the partition backups, but otherwise, erasing the whole disk is the best bet (we need to fix that partition table error you got earlier)02:09
arraybolt3(and just overwriting a partition probably won't fix it, but erasing the disk should)02:10
arraybolt3(Also, anything involving multiple operating systems is leaps and bounds easier using virt-manager. It allows you to split one system into multiple virtual computers, each running its own OS. You can run two, three, or more operating systems at the same time using it.)02:10
zobI'm aware but I only need 1 os02:11
arraybolt3oh OK.02:11
zobI was able to fix and verify that partition and header were fixed before02:11
zobso shouldn't I do this instead02:12
zobit sounds to me like you said onyl way to fix partition table is to wipe and reinstall02:12
arraybolt3The problem is, something got your partition table messed up, and I don't know what. Trying to repair something that's this scrambled *might* work, but it's not as safe as just starting afresh. You'll still have your home backups to make your apps work.02:12
zobhey it says the backup is fine02:13
zobso just copy backup to primary02:13
zoberr backup is corrupt but primary ok*02:14
bob5going to use this https://www.rodsbooks.com/gdisk/repairing.html02:15
arraybolt3I've never messed with partition table backups before, so I don't know what it's going to do. You probably know more than I do about this particular part of what you're doing.02:15
bob5It's start with checking the status here if ur curious https://askubuntu.com/questions/386752/fixing-corrupt-backup-gpt-table02:16
zoboh got it's worse than last time02:19
zobUploaded file: https://uploads.kiwiirc.com/files/27c3da25203d1bdf9d244d08d8338a36/pasted.txt02:19
zobgoing to put this here for posterity02:19
zobIt was all fixed before we talked...02:19
arraybolt3That's really odd, because nothing that we did should have messed with the partition table... except for your copying the backup partition, but that doesn't seem like something that would do **this**.02:20
arraybolt3I wonder if your main hard drive is failing. What brand is it and how long have you been using it?02:20
arraybolt3@zob @bob5 Well, I hate to say it, but I have to go. I probably won't be on again for most of tomorrow, but if we run into each other again, I'd be happy to offer what help I can!02:29
zobUploaded file: https://uploads.kiwiirc.com/files/a91cf09b6da472dc0c00750f4ba4b579/pasted.txt02:30
zobfixed it02:30
zobit's seagate and I thought about this too now :(02:30
bob5I'll try a fresh wipe and install in the meantime02:35
bob5https://askubuntu.com/questions/386752/fixing-corrupt-backup-gpt-table02:42
bob5manual recovery:02:45
bob5sudo mount --bind /proc /mnt/proc02:45
bob5sudo mount --bind /sys /mnt/sys02:45
bob5sudo chroot /mnt02:45
bob5grub-mkconfig -o /boot/efi/boot/grub/grub.cfg02:45
bob5ls /mnt02:46
bob5sudo mkdir /mnt/boot02:47
bob5sudo mkdir /mnt/boot/grub02:47
bob5sudo grub-mkconfig -o /mnt/boot/grub/grub.cfg02:47
bob5sudo umount /dev/sda102:54
bob5sudo mount /dev/sda2 /mnt02:54
bob5sudo mount /dev/sda1 /mnt/boot/efi02:54
bob5sudo chroot /mnt02:54
bob5sudo grub-mkconfig -o /boot/efi/boot/grub/grub.cfg02:55
zobsudo mount /dev/sda1 /mnt/boot/efi02:55
zoboh I give up03:00
bob5it could be an usntable psu...03:24
bob58Any experts in remote hacking BIOS?15:41
tomreynbob58: wrong channel15:47
tomreyn!topic15:47
ubottuPlease read the channel topic whenever you enter, as it contains important information. To view it at any time after joining, simply type /topic15:47
=== root is now known as Guest6581

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