From slitt at troubleshooters.com Wed Mar 1 08:50:18 2023 From: slitt at troubleshooters.com (Steve Litt) Date: Wed, 1 Mar 2023 01:50:18 -0500 Subject: Runit init system discussed at GoLUG, Wednesday, 3/1/2023, 7pm Eastern Standard Message-ID: <20230301015018.79ea477b@mydesk.domain.cxm> Hi all, At the Wednesday, 3/1/2023 online GoLUG meeting, Steve Litt will discuss the ins and outs of the runit init system. He'll cover the benefits and drawbacks of runit, and how its features compare to each of the several other Free Software init systems. And of course, the definition of an init system and how it works will be discussed. Time: Wednesday, 3/1/2023 at 7PM Eastern Standard time Location: https://meet.jit.si/golug SteveT Steve Litt GoLUG Publicity Coordinator From borissh1983 at gmail.com Wed Mar 1 08:56:26 2023 From: borissh1983 at gmail.com (borissh1983 at gmail.com) Date: Wed, 01 Mar 2023 08:56:26 +0200 Subject: Help ! /lib64/libglib-2.0.so.0: file too short References: Message-ID: <3631154.TCx7iinzDu@beast> On Tuesday, 28 February 2023 18:09:53 IST Aharon Schkolnik wrote: > Don't know what happened, but my system fails to boot with the above error > message. > > I am clueless. > > Anyone have any ideas? > You got either a bad installation , corrupted package, corrupted filesystem or hardware error. What you can and should do , disconnect the drive and rescue all what you can by copying the data out. chroot to it , and reinstall libglib2.0-0. hopefully it was just a flash error (and not a hardware error). From aschkolnik at gmail.com Wed Mar 1 09:36:33 2023 From: aschkolnik at gmail.com (Aharon Schkolnik) Date: Wed, 1 Mar 2023 09:36:33 +0200 Subject: Help ! /lib64/libglib-2.0.so.0: file too short In-Reply-To: <3631154.TCx7iinzDu@beast> References: <3631154.TCx7iinzDu@beast> Message-ID: Pretty sure was corrupted file system (maybe connected to electrical issues). Managed to save /home. Reinstalled Fedora. Long night. Most everything seems to be working. Only issue so far is that GRUB doesn't find my Windows installation. Thanks for the help. On Wed, 1 Mar 2023 at 08:59, wrote: > On Tuesday, 28 February 2023 18:09:53 IST Aharon Schkolnik wrote: > > Don't know what happened, but my system fails to boot with the above > error > > message. > > > > I am clueless. > > > > Anyone have any ideas? > > > > You got either a bad installation , corrupted package, corrupted > filesystem or hardware error. > > What you can and should do , disconnect the drive and rescue all what you > can by copying the data out. > chroot to it , and reinstall libglib2.0-0. hopefully it was just a flash > error (and not a hardware error). > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From borissh1983 at gmail.com Wed Mar 1 12:03:53 2023 From: borissh1983 at gmail.com (borissh1983 at gmail.com) Date: Wed, 01 Mar 2023 12:03:53 +0200 Subject: Help ! /lib64/libglib-2.0.so.0: file too short References: <3631154.TCx7iinzDu@beast> Message-ID: <1996012.KKdSJh6eHA@beast> On Wednesday, 1 March 2023 9:36:33 IST Aharon Schkolnik wrote: > Pretty sure was corrupted file system (maybe connected to electrical > issues). > > Managed to save /home. > > Reinstalled Fedora. > > Long night. > > Most everything seems to be working. > > Only issue so far is that GRUB doesn't find my Windows installation. > does osprober able to find it ? if not , perhaps that fs had been also corrupted, you may be able to fix it via ntfsfix /dev/xxx and then mount -o remove_hibernatefile -t ntfs-3g /dev/xxx I strongly recommend you to check your smart logs. From aschkolnik at gmail.com Wed Mar 1 21:27:22 2023 From: aschkolnik at gmail.com (Aharon Schkolnik) Date: Wed, 1 Mar 2023 21:27:22 +0200 Subject: Interesting Grub issue Message-ID: Hi. I have both Fedora and Windows 10 installed on my computer. I can boot either using bios settings. I have grub installed, and can boot to it. The grub menu shows me 3 linux kernels and UEFI firmware. It does not show me Windows. In the attached grub.cfg file there is the following entry: ### BEGIN /etc/grub.d/30_os-prober ### menuentry 'Windows Boot Manager (on /dev/sdc3)' --class windows --class os $menuentry_id_option 'osprober-efi-3C10-1AFF' { insmod part_gpt insmod fat set root='hd2,gpt3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt3 --hint-efi=hd2,gpt3 --hint-baremetal=ahci2,gpt3 3C10-1AFF else search --no-floppy --fs-uuid --set=root 3C10-1AFF fi chainloader /efi/Microsoft/Boot/bootmgfw.efi } The entry is there, but it doesn't show when the machine boots/ Any ideas? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: grub.cfg Type: application/octet-stream Size: 7490 bytes Desc: not available URL: From aschkolnik at gmail.com Thu Mar 2 17:35:46 2023 From: aschkolnik at gmail.com (Aharon Schkolnik) Date: Thu, 2 Mar 2023 17:35:46 +0200 Subject: Interesting Grub issue [Solved] Message-ID: So, it turns out that I have two directories (each on their own mount point): /boot /boot/efi The attached grub.cfg was from /boot/efi -missing the windows entry The correct grub.cfg was in /boot - including the missing windows entry That makes sense since I ran grub2-mkconfig -o /etc/grub2-efi.cfg, and /etc/grub2-efi.cfg is linked to /boot/grub2/grub.cfg So, the file in /etc is linked to the file in /boot but the boot process uses the file in /boot/efi (/boot/efi/EFI/fedora) I would think that on a efi system, the file in /etc should be linked to the file in /boot/efi Sound like a bug? Any idea how I ended up with bot /boot and /boot/efi Any reason not to change the link? Any reason not to delete /boot/grub2 and leave /boot/efi? On Wed, 1 Mar 2023 at 21:27, Aharon Schkolnik wrote: > Hi. > > I have both Fedora and Windows 10 installed on my computer. > I can boot either using bios settings. > I have grub installed, and can boot to it. > The grub menu shows me 3 linux kernels and UEFI firmware. > It does not show me Windows. > In the attached grub.cfg file there is the following entry: > > ### BEGIN /etc/grub.d/30_os-prober ### > menuentry 'Windows Boot Manager (on /dev/sdc3)' --class windows --class os > $menuentry_id_option 'osprober-efi-3C10-1AFF' { > insmod part_gpt > insmod fat > set root='hd2,gpt3' > if [ x$feature_platform_search_hint = xy ]; then > search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt3 > --hint-efi=hd2,gpt3 --hint-baremetal=ahci2,gpt3 3C10-1AFF > else > search --no-floppy --fs-uuid --set=root 3C10-1AFF > fi > chainloader /efi/Microsoft/Boot/bootmgfw.efi > } > > The entry is there, but it doesn't show when the machine boots/ > > Any ideas? > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shachar at shemesh.biz Thu Mar 2 18:38:32 2023 From: shachar at shemesh.biz (Shachar Shemesh) Date: Thu, 2 Mar 2023 18:38:32 +0200 Subject: Interesting Grub issue [Solved] In-Reply-To: References: Message-ID: <9bd3d21c-2b9d-475f-2dc6-f94556326912@shemesh.biz> An HTML attachment was scrubbed... URL: From rabin at rabin.io Thu Mar 2 22:09:47 2023 From: rabin at rabin.io (Rabin Yasharzadehe) Date: Thu, 2 Mar 2023 22:09:47 +0200 Subject: Interesting Grub issue [Solved] In-Reply-To: References: Message-ID: Not sure where I found this, and I have this in my efi/grub file, but you can chain the EFI grub.cfg to the one you're generating (just make sure to change the uuid for the disk) ``` #/boot/efi/EFI/fedora/grub.cfg search --no-floppy --fs-uuid --set=dev 38b0586f-2715-4493-a548-e12902f1b68d set prefix=($dev)/grub2 export $prefix configfile $prefix/grub.cfg ``` -- Rabin On Thu, 2 Mar 2023 at 17:36, Aharon Schkolnik wrote: > So, it turns out that I have two directories (each on their own mount > point): > /boot > /boot/efi > > The attached grub.cfg was from /boot/efi -missing the windows entry > The correct grub.cfg was in /boot - including the missing windows entry > > That makes sense since I ran grub2-mkconfig -o /etc/grub2-efi.cfg, and > /etc/grub2-efi.cfg is linked to /boot/grub2/grub.cfg > > So, the file in /etc is linked to the file in /boot but the boot process > uses the file in /boot/efi (/boot/efi/EFI/fedora) > > > I would think that on a efi system, the file in /etc should be linked to > the file in /boot/efi > > Sound like a bug? > > Any idea how I ended up with bot /boot and /boot/efi > > Any reason not to change the link? > > Any reason not to delete /boot/grub2 and leave /boot/efi? > > On Wed, 1 Mar 2023 at 21:27, Aharon Schkolnik > wrote: > >> Hi. >> >> I have both Fedora and Windows 10 installed on my computer. >> I can boot either using bios settings. >> I have grub installed, and can boot to it. >> The grub menu shows me 3 linux kernels and UEFI firmware. >> It does not show me Windows. >> In the attached grub.cfg file there is the following entry: >> >> ### BEGIN /etc/grub.d/30_os-prober ### >> menuentry 'Windows Boot Manager (on /dev/sdc3)' --class windows --class >> os $menuentry_id_option 'osprober-efi-3C10-1AFF' { >> insmod part_gpt >> insmod fat >> set root='hd2,gpt3' >> if [ x$feature_platform_search_hint = xy ]; then >> search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt3 >> --hint-efi=hd2,gpt3 --hint-baremetal=ahci2,gpt3 3C10-1AFF >> else >> search --no-floppy --fs-uuid --set=root 3C10-1AFF >> fi >> chainloader /efi/Microsoft/Boot/bootmgfw.efi >> } >> >> The entry is there, but it doesn't show when the machine boots/ >> >> Any ideas? >> >> _______________________________________________ > Linux-il mailing list > Linux-il at cs.huji.ac.il > http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il > -------------- next part -------------- An HTML attachment was scrubbed... URL: