[02:34] Gigi was added by: Gigi [04:01] must be 10 years since i was on irc! hello to you all.... [04:02] does anyone run isyncr ? [06:42] So I did those ppa backport updates or installs on my 19.04. And ever since I shut down my computer, I cannot boot into the OS anymore. There is no grub on my harddive anymore so I cannot boot in any other way or access the shell. So I am kind of dumbfounded on what to do. And I don't want to reinstall as I've got too many important f [06:42] iles saved on my OS. Granted I could just access another OS and backup the files, but at the same time I use this OS quite a bit. So any help would be appreciated. [07:42] @Jessedavid4 backports on 19.04? The backports were only meant for the 18.04 release to gain the LTS status and receive updates until 2021. [08:55] @Jessedavid4 [So I did those ppa backport updates or installs on my 19.04. And ever since I sh …], Ah yes. But was having trouble with audio. So Erik said to add them to my 19.04 [14:26] M_aD: The backports are open for 19.04 as well. [14:28] @Jessedavid4 [Ah yes. But was having trouble with audio. So Erik said to add them to my 19.04], I highly doubt the backports would've done that. Had you customized your grub or added anything else? [14:30] I guess it doesn't matter. We need to get your system operational. Do you have any other OSs installed, as in, do you dual-boot? [14:32] Eickmeyer: thanks, understood [18:16] Windows dual booted on another hard drive. [18:32] Is there a way I can get grub via access to my windows? It's windows 8.1 if that makes a difference. I feel if I can get grub on there, it may fix the problem. [18:34] And correction. It does boot to it, I just no video. And cannot access pointer or keyboard commands. Tried moving around sata chords in different slots (to see if that was the error). And can also try my nvidia gpu to see if it may be a direct graphics related issue. [18:35] Have you tried: during boot hold down shift key? [18:41] Well during boot, I usually just go directly to bios and then select the hard drive I want to use... Kind of my current "grub menu" for selecting OS's. [18:43] The screen isn't black when I boot in either. It's Led black. So it's acting as it isn't there, but it should be past the boot and somewhat on the log in, or just before. [18:48] Press Ctrl + Alt + T to open the terminal window. In the terminal window type the following command: sudo os-prober and press Enter. If you see it detect Windows 10 then all you have to do is type the command sudo update-grub and press Enter. It will add new entries to the grub menu and update it. [18:49] Its worth a shoot, dont do any harm , probing for partition. [18:50] then you dont have to change in bios, since it will write to the bootloader you just booted in. [18:50] studiobot: ^ [18:51] I did that shift, and after that third time for a quick moment it said "loading grub" [18:51] But then went back into the blank screen. I then tried to do the commands you said [19:14] cjoke: studiobot is an IRC <=> Telegram bridge, so you'd want to ping someone with @name where name is the name given inside the . [19:29] Eickmeyer: yea, it got wierd, so I did check studiobot, and did figure that out lol. So I can talk to @Jessedavid4 by putting @before_nickname ? [19:34] I got it, its like routin messages between different chatprotocols. [19:35] cjoke: Exactly. :) [21:37] upgrading to the latest kernel and the terminal window is frozen at 22% "Unpacking linux-headers-5.0.0-21 (5.0.0-21.22) ..." [21:37] eveyrthing except that terminal window is still working [21:37] kinda scared to close it and try again lol [21:41] sakrecoer: in another terminal do ls /boot how many kernels do you have in there? Have you run out of diskspace? [21:42] 2 kernels in there 5.0.0.-19 and 20 [21:42] I guess I should ask if you have efi (or whatever it is... the new bios stuff) [21:42] legacy boot [21:43] df -h [21:43] shows how much room on / [21:43] (use %) [21:43] 21.9 Gb [21:43] 4% of boot used [21:43] wait.. [21:43] that seems small [21:44] seems i am on efi [21:44] /dev/sda1 234M 7,6M 226M 4% /boot/efi [21:46] ya, but there is room on it [21:47] puh... i'm so dumb. i'm in the middle of a production with deadline tomorrow lol [21:48] is there a /boot/grub/grub.conf [21:48] it [21:48] no [21:48] /boot/grub/grub.conf [21:48] sorry grubcfg [21:48] not there [21:48] grub.cfg [21:49] yes that one is [21:49] what is the date /time on it? [21:49] jul 12th [21:49] I think you should be safe to kill that terminal [21:50] It seems update-grub has not been run yet [21:50] Thanks OvenWerks <3 i'll give it a try... appreciate your assistance wether this works or not :) [21:51] you will likely need to run an apt install -f at some point [21:51] but I would wait till after your deadline [21:51] when you mentioned disk space, i think it could be my drive... it has been giving me attitudes lately... [21:52] should i kill the dpkg process? [21:52] when something stops in the middle of an unpack drive is a good suspect [21:52] I would [21:52] tail /var/log/syslog show anything interesting? [21:53] like failed read/write/seek [21:53] (or dmesg) [21:54] not that i can see [21:54] Those are the normal things I get for a failing drive [21:55] doesn't seem to be that... [21:56] what does the -f flag stand for in apt install? [21:57] fix [21:57] nice :) [21:57] manz thanks OvenWerks [21:57] many even [21:57] It takes whatever install you were part way through and continues [21:57] YW [21:58] need to dive back into that work for tomorrow... [21:58] cya! o/ [21:59] o/ [22:02] ItzSwirlz was added by: ItzSwirlz [22:02] hello === JTa1 is now known as JTa