palica

what is the output of boot-update with un/mounted boot what versions of grub, boot-update do you have what gets displayed when you type configfile /grub/grub.cfg in grub prompt

how do you know it can't find kernel? ever tried to do manual grub start. selecting root device and loading the kernel ... grub> set root=(hd0,msdos1) #probably, I am just guessing here, but tab complete works in grub grub> linux /kernel real_root=/dev/mapper/funtoo grub> initird /initrd grub> boot these lines are just guesses take a look at grub.cfg and make note of those lines. Or just try ls (hd<TAB><TAB> should autocomplete to something sane like hd0,msdos1)/ so for example ls (hd0,msdo1)/ should list some files if it is /boot (sda1) if it sees the files there all you are missing is grub.cfg which gets lost somewhere. I think you just need to make sure /boot is mounted then. what is the output of boot-update when /boot not mounted?

did you forcibly unmount /boot? if yes, then don't do it. if you don't want your /boot mounted then modify your script to mount /boot before running the stuff and reinstalling grub. reinstalling grub is not needed on regular basis (only after grub version update), all you need to modify is /boot/grub/grub.cfg, but also only if your kernels change. correct your /etc/fstab it is actually all working as it should be. what is probably going on here is if /boot is not mounted then grub-install installs and makes a reference to /boot that is on / (root partition) putting all the files there etc, with no error - which is ok. when boot-update is run it mounts /boot over the /boot directory that is containing the install of grub and puts the grub.cfg there with reference to /boot on separate partition. setting the root device for grub to /boot that doesn't contain a correct grub installation, because it got installed to root partition and not /boot partition. But this is also expected. to check my theory run ls -alF /boot when boot mounted and when not mounted. To sum up - it works as expected, if you want to run regularly this script that reinstalls grub and does all the fancy things... , make sure boot is mounted.

quickpkg - grabs the files already on your system and packs them to a tbz2 archive. emerge --buildpkg(only) - emerges the package and packs an archive from the build directory. The only difference is if the files on your system were already modified, then you will pack modified files with quickpkg, emerge will always generate files as they get installed on your system (vanilla so to say). so recompile = emerge pack what is already installed = quickpkg since you are grabbing a fresh stage3 direct from the build server, you can generate packages from what is already installed and save time, if you are unsure and have time emerge --buildpkg will also work. mkdir vs install no difference, just a preference I think.

I tried to be polite (see the please) . It is hard to help "Advanced members" if all they paste is output from other commands that don't point to a better problem description or solution. Your emerge @world did give us some more information about the system status, thou, but that was probably not intentional on your part and pure luck :) Sometimes even "Newbies" have good ideas and even the fix. What you can do is download a stage3 and chroot as if you were installing a new funtoo (following the steps of Chrooting in Install article on the funtoo wiki) and then creating binary packages of @system packages. Steps to resurrect: download stage3 chroot to stage3 quickpkg --include-config y @system exit chroot locate packages in $chroot/var/cache/portage/packages/ copy them to your /var/cache/portage/packages on your hosed system emerge -avk1 @system You should see a lot of binary packages being emerge (if that doesn't work, try installing gcc, binutils and glibc first with separate emerge -avk1 gcc ... commands) By now you should have your system working again. If not, wait for Oleg or BDFL to reply. Over and out.

that is the new theme for icons if you wish to switch themes - you will find it in Preferences :)

noauto = doesn't mount it automatically so if you have the whole time noauto there it just won't get mounted, because that is how it is designed.

try putting quotes in fstab for your labels

this is my setup, using labels. separate /boot, noauto is not set in fstab, boot gets mounted by openrc. still unable to reproduce.

I think it is ok to discuss here. You can probably directly open an issue on github. Had to disable profile-info in /etc/report.conf and then it reports. I have elasticsearch with kibana running here http://elk.liguros.net there you can check the results or data being submitted.

so to sum up: grub install ok lvm is not the culprit (those warning can be ignored /run/lvm/lvmetad.socket ...) /boot not being automounted from openrc is causing the problem unable to reproduce in virtualbox, boot gets mounted. After reboot what do you get when running mount |grep boot try rebuilding openrc, when that doesn't help, then I don't know.

completely unrelated to your issues and also non critical (just a warning that can be ignored and possibly fixed by the script maintainers) bcowan told you to rebuild these instead you tried @revdep-rebuild and @world - do as being told, please. note I will not work probably as: You system is hosed. You have 2 options: find a funtoo computer that is ok and build binary packages for at least gcc binutils glibc (if you don't have a computer download a fresh stage3 and chroot into it and build those packages there), then use these packages to restore a sane build environment on your box. (instructions can be found here https://www.funtoo.org/System_resurrection) reinstall or try doing that what bcowan proposed (emerge -v1 gcc, emerge -v1 binutils, emerge -v1 glibc, followed by eselect gcc list and set the right profile and follow the instructions printed on screen regarding sourcing /etc/profile) if that doesn't work only options 1, and 2 are left

enable RC_LOG in /etc/rc.conf reboot and paste /var/log/rc.log

did you run boot-update? it looks you don't have /boot/grub/grub.cfg generated, do you?

Grub reports: Installation finished. No error reported. paste screenshot of grub error upon boot.

paste output of blkid please

you need to copy your running kernel config for example with zcat /proc/config.gz > .config and then make oldconfig should work let me know if that was the problem

Bugs can be reported on bugs.funtoo.org. With the steps to reproduce. I encourage you to read through this as it can be used also for "How to file a good bug report" :)

cat /etc/fstab

harmless :) https://bugs.funtoo.org/browse/FL-4598?jql=text ~ "openrc"

make sure portage owns the distfiles directory and change it accordingly also for git3-src drwxr-xr-x 1 portage portage 274506 28. led 21.50 /var/cache/portage/distfiles/

looks like permission problems. steps to reproduce? are you running as root? can you write to /var/cache/portage/distfiles? what are permissions on that dir? is portage able to write there? those are all questions you could avoid answering when you would read this :)

This is probably the best to start and use to convert to runit. https://wiki.gentoo.org/wiki/Runit#Runit_as_the_init_system Let us know how it went. I have never tried it personally.

sci-misc/boinc-7.8.4::science-kit installs just fine on my test box.

[ebuild N ] sci-mathematics/rstudio-1.1.383::science-kit USE="-dedicated -server" 207,262 KiB compiled for me without problems. If you are still experiencing problems let us know. When possible supplying also ebuild.log.