View previous topic :: View next topic |
Author |
Message |
Hu Administrator
Joined: 06 Mar 2007 Posts: 21706
|
Posted: Sun Mar 13, 2022 4:58 pm Post subject: |
|
|
todd93 wrote: | It appears to want kernel options set in order to proceed. | No. You are warned that Portage may not work properly with the Kconfig options you have. You then get an error when pam fails to build. The pam error does not appear to be connected to the Kconfig checks.
You cannot umount swap, but you can swapoff it. |
|
Back to top |
|
|
figueroa Advocate
Joined: 14 Aug 2005 Posts: 2965 Location: Edge of marsh USA
|
Posted: Sun Mar 13, 2022 5:04 pm Post subject: |
|
|
What did you boot from? This was a 1 GB swap partition. My guess is that the OS has it automatically "mounted" (not really mounted) as swap. Try:
Code: | swapoff -v /dev/sdd3 |
But, if you really re-did the partitions, you may need to reboot from your boot media. _________________ Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
Back to top |
|
|
todd93 l33t
Joined: 30 Oct 2006 Posts: 620 Location: Missouri
|
Posted: Sun Mar 13, 2022 5:08 pm Post subject: |
|
|
figueroa wrote: | What did you boot from? This was a 1 GB swap partition. My guess is that the OS has it automatically "mounted" (not really mounted) as swap. Try:
Code: | swapoff -v /dev/sdd3 |
But, if you really re-did the partitions, you may need to reboot from your boot media. |
I'm using the MX Linux livecd... I actually got swapoff to work, partitions redone, reformatted, now I'm ready to do a fresh install! |
|
Back to top |
|
|
todd93 l33t
Joined: 30 Oct 2006 Posts: 620 Location: Missouri
|
Posted: Sun Mar 13, 2022 9:00 pm Post subject: |
|
|
Ok, we're slowly, but surely getting there... I have another problem now, I configured/compiled the kernel, but I can't get it to copy over to /boot/...
Code: | # make install
sh ./arch/x86/boot/install.sh 5.15.26-gentoo \
arch/x86/boot/bzImage System.map "/boot"
cat: write error: No space left on device
make: *** [arch/x86/Makefile:262: install] Error 1
|
I followed the guide in the handbook for partition sizes, etc... Not sure why it's saying this, unless I didn't allocate enough space, but there should be plenty... |
|
Back to top |
|
|
figueroa Advocate
Joined: 14 Aug 2005 Posts: 2965 Location: Edge of marsh USA
|
Posted: Sun Mar 13, 2022 9:25 pm Post subject: |
|
|
Let's see your new partition layout (from the chroot) and a couple of other things; output of:
cat /etc/fstab
df
lsblk
fdisk -l /dev/sdd
ls -l /boot
How do you plan to boot? _________________ Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
Back to top |
|
|
todd93 l33t
Joined: 30 Oct 2006 Posts: 620 Location: Missouri
|
Posted: Sun Mar 13, 2022 9:32 pm Post subject: |
|
|
Absolutely!
Code: | # cat /etc/fstab
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed); notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
#
# NOTE: Even though we list ext4 as the type here, it will work with ext2/ext3
# filesystems. This just tells the kernel to use the ext4 driver.
#
# NOTE: You can use full paths to devices like /dev/sda3, but it is often
# more reliable to use filesystem labels or UUIDs. See your filesystem
# documentation for details on setting a label. To obtain the UUID, use
# the blkid(8) command.
#LABEL=boot /boot ext4 noauto,noatime 1 2
#UUID=58e72203-57d1-4497-81ad-97655bd56494 / ext4 noatime 0 1
#LABEL=swap none swap sw 0 0
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0 |
Code: | # df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdd3 475209732 5693864 445303032 2% /
cgroup 12 0 12 0% /sys/fs/cgroup
devtmpfs 8159400 4 8159396 1% /dev
tmpfs 4118600 0 4118600 0% /dev/shm
tmpfs 1639872 3140 1636732 1% /run
/dev/sdd1 2000 1997 3 100% /boot |
Code: | # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 1.7G 1 loop
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 500M 0 part
├─sda2 8:2 0 464.4G 0 part
└─sda3 8:3 0 858M 0 part
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 512M 0 part
├─sdb2 8:18 0 244M 0 part
└─sdb3 8:19 0 930.8G 0 part
├─ubuntu--vg-root 254:0 0 926.8G 0 lvm
└─ubuntu--vg-swap_1 254:1 0 3.9G 0 lvm
sdc 8:32 0 931.5G 0 disk
├─sdc1 8:33 0 100M 0 part
└─sdc2 8:34 0 931.4G 0 part
sdd 8:48 0 465.8G 0 disk
├─sdd1 8:49 0 256M 0 part /boot
├─sdd2 8:50 0 4G 0 part [SWAP]
└─sdd3 8:51 0 461.5G 0 part /
sde 8:64 1 0B 0 disk
sdf 8:80 1 0B 0 disk
sdg 8:96 1 0B 0 disk
sdh 8:112 1 0B 0 disk
sdi 8:128 1 0B 0 disk
sdj 8:144 1 0B 0 disk
sdk 8:160 1 0B 0 disk
sdl 8:176 1 0B 0 disk
sdm 8:192 1 0B 0 disk
sdn 8:208 1 0B 0 disk
sr0 11:0 1 1024M 0 rom
sr1 11:1 1 1.8G 0 rom |
Code: | # fdisk -l /dev/sdd
Disk /dev/sdd: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 850
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 0F839E6E-C08A-EE4D-A2D0-B133DD50F141
Device Start End Sectors Size Type
/dev/sdd1 2048 526335 524288 256M EFI System
/dev/sdd2 526336 8914943 8388608 4G Linux swap
/dev/sdd3 8914944 976773134 967858191 461.5G Linux filesystem |
Code: | ls -l /boot
total 1996
-rwxr-xr-x 1 root root 2043904 Mar 13 20:47 vmlinuz-5.15.26-gentoo |
I was planning on installing Grub on the MBR of /dev/sda (Windows drive), unless there's a better option... I'm willing to do whatever works best.
Thanks |
|
Back to top |
|
|
figueroa Advocate
Joined: 14 Aug 2005 Posts: 2965 Location: Edge of marsh USA
|
Posted: Sun Mar 13, 2022 9:58 pm Post subject: |
|
|
Well, sdd1 is very small (too small) and set to be EFI. Also, your kernel seems very large, much larger than mine. It sounds like you are not going to use EFI, in which case you don't really need a separate /boot partition. I would suggest deleting the sdd1 partition for now, put boot into the system root.
Everything in your /etc/fstab is commented out.
Are you other disks also MBR? Mine are. If I've made some wrong assumptions, ignore me. _________________ Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
Back to top |
|
|
todd93 l33t
Joined: 30 Oct 2006 Posts: 620 Location: Missouri
|
Posted: Sun Mar 13, 2022 10:04 pm Post subject: |
|
|
figueroa wrote: | Well, sdd1 is very small (too small) and set to be EFI. Also, your kernel seems very large, much larger than mine. It sounds like you are not going to use EFI, in which case you don't really need a separate /boot partition. I would suggest deleting the sdd1 partition for now, put boot into the system root.
Everything in your /etc/fstab is commented out.
Are you other disks also MBR? Mine are. If I've made some wrong assumptions, ignore me. |
Well, I'm not sure if I will use EFI or not, I hear it's better some way... Of course, this system is getting some age on it. So I'm not sure if it's even possible to use with this system. I know the other drive I boot from is MBR (I think, I actually need to investigate that.).
My kernel is probably too large, but I'm not sure how to reduce it in size, I probably have far too much built into it... Back in the day, I used Pappy's seeds, but I don't think that's a thing anymore |
|
Back to top |
|
|
figueroa Advocate
Joined: 14 Aug 2005 Posts: 2965 Location: Edge of marsh USA
|
Posted: Mon Mar 14, 2022 12:11 am Post subject: |
|
|
Pappy's seeds are still two major and sticky threads in the forums here: https://forums.gentoo.org/viewforum-f-51.html
You can overcome a lot of the hard part in the beginning by emerging sys-kernel/gentoo-kernel-bin. This will get you up and running and you can work on a custom kernel once a system is up and running.
Your system BIOS setup will show you whether EFI/uEFI/UEFI is even an option. Unless you are already using UEFI, I don't recommend it at this point. UEFI booting and GPT drive partitioning kind of go hand-in-hand like BIOS booting and MBR partitioning go hand-in-hand. But, this is a tangential thing to getting your new Gentoo system installed. _________________ Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Mon Mar 14, 2022 2:31 am Post subject: |
|
|
CaptainBlood wrote: | pjp wrote: | I'm not aware of any package that fails to compile due to kernel settings, although some may exist. | IIRCis one of them.
Most packages installing in /lib/modules/x.y.z-alphanumeric/ should check matching kernel config file settings prior to building, when well designed.may be another I'm aware of.
Both with activated Code: | CONFIG_TRIM_UNUSED_KSYMS | as source of build failure: Code: | * Checking for suitable kernel configuration options... [ ok ]
* Checking for suitable kernel configuration options...
* CONFIG_TRIM_UNUSED_KSYMS: should not be set. But it is. | Thks 4 ur attention, interest & support. | Check, yes, but fail to build? I rarely have a kernel config in place and have never perceived a problem (lucky me I guess?). But I don't have vhba or r8168 (I did have one system with a realtek NIC, but not in current use). Based on my experience, it seemed that programs compile successfully despite having only partial or no functionality until the kernel settings were enabled. If not, then I've checked the "learn something new" box for he day. _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
todd93 l33t
Joined: 30 Oct 2006 Posts: 620 Location: Missouri
|
Posted: Tue Mar 15, 2022 11:11 pm Post subject: |
|
|
figueroa wrote: | Pappy's seeds are still two major and sticky threads in the forums here: https://forums.gentoo.org/viewforum-f-51.html
You can overcome a lot of the hard part in the beginning by emerging sys-kernel/gentoo-kernel-bin. This will get you up and running and you can work on a custom kernel once a system is up and running.
Your system BIOS setup will show you whether EFI/uEFI/UEFI is even an option. Unless you are already using UEFI, I don't recommend it at this point. UEFI booting and GPT drive partitioning kind of go hand-in-hand like BIOS booting and MBR partitioning go hand-in-hand. But, this is a tangential thing to getting your new Gentoo system installed. |
I appreciate all the help you're providing... I've hit a major snag, though... I realized that I don't boot efi, I use a bios boot... So I redid my partitions for bios boot, but when I tried to install grub, it failed, because it was looking for efi. So, should I start over, reformat the /root drive, and get the install working that way? Or is it easier just to fix what I have to use bios boot?
I do have to apologize, I don't have any time during the week to work on this, so my time is a little limited. |
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 4236 Location: Bavaria
|
Posted: Tue Mar 15, 2022 11:52 pm Post subject: |
|
|
todd93 wrote: | So I redid my partitions for bios boot, [...] |
If that means you have either:
- a free space at beginning (=before the first partition) of minimum 2048 KB (2MB), OR
- an extra partitions (not mounted) for grub2 AND set "bios_grub" flag. PARTED: "set X bios_grub on" (Alternatively, you can use gdisk and set its type code to EF02)
?
THEN ...
todd93 wrote: | [...] but when I tried to install grub, it failed, because it was looking for efi |
Be sure you have in your /etc/portage/make.conf: GRUB_PLATFORMS="pc"
todd93 wrote: | So, should I start over, reformat the /root drive, and get the install working that way? Or is it easier just to fix what I have to use bios boot? |
If it doesnt work, it is (always) helpful togive us the exact error message.
todd93 wrote: | I do have to apologize, I don't have any time during the week to work on this, so my time is a little limited. |
No need to apologize ... we will answer also when we have time
P.S.: See also here: https://wiki.gentoo.org/wiki/GRUB2#BIOS_with_MBR |
|
Back to top |
|
|
figueroa Advocate
Joined: 14 Aug 2005 Posts: 2965 Location: Edge of marsh USA
|
Posted: Wed Mar 16, 2022 2:02 am Post subject: |
|
|
There shouldn't be any need to start over. Let us know what your NEW partition layout is like (and a few other things) you did back on 3/13. i.e.
cat /etc/fstab
df
lsblk
fdisk -l /dev/sda (added)
fdisk -l /dev/sdd
ls -l /boot
emerge -pv sys-boot/grub (added) _________________ Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
Back to top |
|
|
todd93 l33t
Joined: 30 Oct 2006 Posts: 620 Location: Missouri
|
Posted: Wed Mar 16, 2022 10:10 pm Post subject: |
|
|
figueroa wrote: | There shouldn't be any need to start over. Let us know what your NEW partition layout is like (and a few other things) you did back on 3/13. i.e. |
Okay, we're having some success! I have Grub installed! I have the new layout:
Code: | # cat /etc/fstab
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed); notail increases performance of ReiserFS (at the expense of storage
# efficiency). It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#
# <fs> <mountpoint> <type> <opts> <dump/pass>
# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
#
# NOTE: Even though we list ext4 as the type here, it will work with ext2/ext3
# filesystems. This just tells the kernel to use the ext4 driver.
#
# NOTE: You can use full paths to devices like /dev/sda3, but it is often
# more reliable to use filesystem labels or UUIDs. See your filesystem
# documentation for details on setting a label. To obtain the UUID, use
# the blkid(8) command.
#LABEL=boot /boot ext4 noauto,noatime 1 2
#UUID=58e72203-57d1-4497-81ad-97655bd56494 / ext4 noatime 0 1
#LABEL=swap none swap sw 0 0
#/dev/cdrom /mnt/cdrom auto noauto,ro 0 0
/dev/sda2 /mnt/windows ntfs-3g users 0 0
/dev/sdb1 /mnt/ubuntu vfat users 0 0
/dev/sdc2 /mnt/oldwin ntfs-3g users 0 0
/dev/sdd1 /boot vfat defaults,noatime 0 2
/dev/sdd2 none swap sw 0 0
/dev/sdd3 / ext4 noatime 0 1
/dev/cdrom /mnt/cdrom auto noauto,ro 0 0 |
Code: | # df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdd3 475209732 6260752 444736144 2% /
cgroup 12 0 12 0% /sys/fs/cgroup
devtmpfs 8159404 4 8159400 1% /dev
tmpfs 4118600 0 4118600 0% /dev/shm
tmpfs 1639876 3144 1636732 1% /run
/dev/sdd1 258094 49676 208418 20% /boot |
Code: | # lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 1.7G 1 loop
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 500M 0 part
├─sda2 8:2 0 464.4G 0 part
└─sda3 8:3 0 858M 0 part
sdb 8:16 0 931.5G 0 disk
├─sdb1 8:17 0 512M 0 part
├─sdb2 8:18 0 244M 0 part
└─sdb3 8:19 0 930.8G 0 part
├─ubuntu--vg-root 254:0 0 926.8G 0 lvm
└─ubuntu--vg-swap_1 254:1 0 3.9G 0 lvm
sdc 8:32 0 931.5G 0 disk
├─sdc1 8:33 0 100M 0 part
└─sdc2 8:34 0 931.4G 0 part
sdd 8:48 0 465.8G 0 disk
├─sdd1 8:49 0 256M 0 part /boot
├─sdd2 8:50 0 4G 0 part [SWAP]
└─sdd3 8:51 0 461.5G 0 part /
sde 8:64 1 0B 0 disk
sdf 8:80 1 0B 0 disk
sdg 8:96 1 0B 0 disk
sdh 8:112 1 0B 0 disk
sdi 8:128 1 0B 0 disk
sdj 8:144 1 0B 0 disk
sdk 8:160 1 0B 0 disk
sdl 8:176 1 0B 0 disk
sdm 8:192 1 0B 0 disk
sdn 8:208 1 0B 0 disk
sr0 11:0 1 1024M 0 rom
sr1 11:1 1 1.8G 0 rom |
Quote: |
fdisk -l /dev/sda (added) |
Code: | # fdisk -l /dev/sda
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 850
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x366d2ddb
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 1026047 1024000 500M 7 HPFS/NTFS/exFAT
/dev/sda2 1026048 975009923 973983876 464.4G 7 HPFS/NTFS/exFAT
/dev/sda3 975011840 976769023 1757184 858M 27 Hidden NTFS WinRE |
Code: | # fdisk -l /dev/sdd
Disk /dev/sdd: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 850
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc651cc85
Device Boot Start End Sectors Size Id Type
/dev/sdd1 2048 526335 524288 256M 83 Linux
/dev/sdd2 526336 8914943 8388608 4G 82 Linux swap / Solaris
/dev/sdd3 8914944 976773167 967858224 461.5G 83 Linux |
Code: | # ls -l /boot/
total 38010
-rwxr-xr-x 1 root root 235070 Mar 16 16:44 config-5.15.25-gentoo-dist
drwxr-xr-x 6 root root 512 Mar 16 16:54 grub
-rwxr-xr-x 1 root root 22291467 Mar 16 16:44 initramfs-5.15.25-gentoo-dist.img
-rwxr-xr-x 1 root root 5801542 Mar 16 16:44 System.map-5.15.25-gentoo-dist
-rwxr-xr-x 1 root root 10591712 Mar 16 16:44 vmlinuz-5.15.25-gentoo-dist |
Quote: |
emerge -pv sys-boot/grub (added) |
This one I omitted, as I did make some changes, re-emerged Grub and got it to install properly, without error... I am including the grub.cfg output, I am fuzzy on how to make the proper Grub entry for Windows booting (sda). I would also like to note that I installed the genkernel to get up and running, and will at a later time build a custom kernel as per your advice.
Thanks again for all the help!
Code: | # cat /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd3,msdos3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos3 --hint-efi=hd3,msdos3 --hint-baremetal=ahci3,msdos3 bb114566-68e9-47bc-9d8d-7dd64deaa260
else
search --no-floppy --fs-uuid --set=root bb114566-68e9-47bc-9d8d-7dd64deaa260
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Gentoo GNU/Linux' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-bb114566-68e9-47bc-9d8d-7dd64deaa260' {
load_video
if [ "x$grub_platform" = xefi ]; then
set gfxpayload=keep
fi
insmod gzio
insmod part_msdos
insmod fat
set root='hd3,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1 99FC-DE47
else
search --no-floppy --fs-uuid --set=root 99FC-DE47
fi
echo 'Loading Linux 5.15.25-gentoo-dist ...'
linux /vmlinuz-5.15.25-gentoo-dist root=UUID=bb114566-68e9-47bc-9d8d-7dd64deaa260 ro
echo 'Loading initial ramdisk ...'
initrd /initramfs-5.15.25-gentoo-dist.img
}
submenu 'Advanced options for Gentoo GNU/Linux' $menuentry_id_option 'gnulinux-advanced-bb114566-68e9-47bc-9d8d-7dd64deaa260' {
menuentry 'Gentoo GNU/Linux, with Linux 5.15.25-gentoo-dist' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.15.25-gentoo-dist-advanced-bb114566-68e9-47bc-9d8d-7dd64deaa260' {
load_video
if [ "x$grub_platform" = xefi ]; then
set gfxpayload=keep
fi
insmod gzio
insmod part_msdos
insmod fat
set root='hd3,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1 99FC-DE47
else
search --no-floppy --fs-uuid --set=root 99FC-DE47
fi
echo 'Loading Linux 5.15.25-gentoo-dist ...'
linux /vmlinuz-5.15.25-gentoo-dist root=UUID=bb114566-68e9-47bc-9d8d-7dd64deaa260 ro
echo 'Loading initial ramdisk ...'
initrd /initramfs-5.15.25-gentoo-dist.img
}
menuentry 'Gentoo GNU/Linux, with Linux 5.15.25-gentoo-dist (recovery mode)' --class gentoo --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.15.25-gentoo-dist-recovery-bb114566-68e9-47bc-9d8d-7dd64deaa260' {
load_video
if [ "x$grub_platform" = xefi ]; then
set gfxpayload=keep
fi
insmod gzio
insmod part_msdos
insmod fat
set root='hd3,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd3,msdos1 --hint-efi=hd3,msdos1 --hint-baremetal=ahci3,msdos1 99FC-DE47
else
search --no-floppy --fs-uuid --set=root 99FC-DE47
fi
echo 'Loading Linux 5.15.25-gentoo-dist ...'
linux /vmlinuz-5.15.25-gentoo-dist root=UUID=bb114566-68e9-47bc-9d8d-7dd64deaa260 ro single
echo 'Loading initial ramdisk ...'
initrd /initramfs-5.15.25-gentoo-dist.img
}
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ### |
|
|
Back to top |
|
|
figueroa Advocate
Joined: 14 Aug 2005 Posts: 2965 Location: Edge of marsh USA
|
Posted: Thu Mar 17, 2022 3:06 am Post subject: |
|
|
If you are using grub-mkconfig to setup /boot/grub/grub.cfg, add the following:
Code: | GRUB_DISABLE_OS_PROBER=false |
to /etc/default/grub
This will cause "grub-mkconfig -o /boot/grub/grub.cfg" os-prober to find and setup all other bootable OSes. You will need to emerge sys-boot/os-prober for this to work if you don't already have it. This usually works. _________________ Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
Back to top |
|
|
todd93 l33t
Joined: 30 Oct 2006 Posts: 620 Location: Missouri
|
Posted: Sat Mar 19, 2022 1:47 am Post subject: |
|
|
Ok, got it to work, now I am able to boot into Windows 10, and 7 (didn't realize that I still had a bootable Windows 7 lol).
Attempted to boot the kernel, but it was unsuccessful. I was able to get a pic of the screen with my phone, but I can't post it on the forum, and I'm not sure what image sharing site is acceptable to use here, but it failed to boot while attempting to load removable discs that aren't there, then gave me an option of "repair filesystem#".
I will remind, I did use genkernel with the hopes of getting up and running, then I plan on building a custom kernel.
Thanks
Todd |
|
Back to top |
|
|
figueroa Advocate
Joined: 14 Aug 2005 Posts: 2965 Location: Edge of marsh USA
|
Posted: Sat Mar 19, 2022 3:21 am Post subject: |
|
|
Well done.
Take any removable disks out of the /etc/fstab (if there are any), or alternatively, connect them. Beware of "repairing the filesystem." If you put an image somewhere, be sure to post the full URL and not some short version. Many of us won't click on funky looking links. _________________ Andy Figueroa
hp pavilion hpe h8-1260t/2AB5; spinning rust x3
i7-2600 @ 3.40GHz; 16 gb; Radeon HD 7570
amd64/23.0/split-usr/desktop (stable), OpenRC, -systemd -pulseaudio -uefi |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54300 Location: 56N 3W
|
Posted: Sat Mar 19, 2022 10:13 am Post subject: |
|
|
todd93,
Nothing that needs a sign in. Many users prefer to avoid Java too.
Youtube works if we need to see several screen fulls scroll.
However videos are a bit hit and miss due to the 30Hz video frame rate and asynchronous screen update.
If you get a kernel panic, tell us the full text. Its one line above the register dump.
Something like
Kernel Panic! Unable to mount root filesystem ... unknown-block(x,y) x and y are important here.
or
Kernel Panic! Tried to kill init.
Or even Loading initrd .... Then no more. That's becoming popular. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
todd93 l33t
Joined: 30 Oct 2006 Posts: 620 Location: Missouri
|
Posted: Sat Mar 19, 2022 10:25 am Post subject: |
|
|
Thank you all for the kind help... I will link to the image hosted at imgbb, if the link poses a problem, please let me know. I will also have a look at my fstab to see if there could be a minor problem there, my guess is that it's probably one line that I overlooked.
https://i.ibb.co/XVgxRmq/1st-boot.jpg |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54300 Location: 56N 3W
|
Posted: Sat Mar 19, 2022 10:37 am Post subject: |
|
|
todd93,
The kernel and initrd loaded. Something failed and its dropped you to the busybox shell in the initrd.
Ignore the prompt. Repairing Filesystem is the last thing to try. It often does more harm than good.
We really needed to see several screenfuls above. A video may or may not help.
Meanwhile, use that shell to look around. Maybe we can work out what went wrong?
What is your root device?
Does it appear in
Depending an what it is you way need to look in subdirectories.
Is it mounted?
orwill show it if so.
If its not mounted, can you mount it by hand somewhere?
busybox mount requires the -t option to give the filesystem type.
If its mounted, does it look like a root filesystem or possibly its your /boot? _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
todd93 l33t
Joined: 30 Oct 2006 Posts: 620 Location: Missouri
|
Posted: Sat Mar 19, 2022 1:28 pm Post subject: |
|
|
A video I can do, I'll have to boot into the live media I'm using and chroot in to provide the rest of the info, so bear with me!
https://youtu.be/ipbKfF8ba28 |
|
Back to top |
|
|
todd93 l33t
Joined: 30 Oct 2006 Posts: 620 Location: Missouri
|
Posted: Sat Mar 19, 2022 1:44 pm Post subject: |
|
|
Something happened that has caused /dev/sdd3 to be unmountable... I'm not sure what, but observe:
Code: | # mount /dev/sdd3 /mnt/gentoo
mount: /mnt/gentoo: cannot mount; probably corrupted filesystem on /dev/sdd3. |
This is output from the LiveCD that I'm using, trying to mount the drive in order to chroot in. I'm not sure what I could have done to have caused this error, as I was only messing with Grub and got it to fully install, and work properly. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54300 Location: 56N 3W
|
Posted: Sat Mar 19, 2022 1:57 pm Post subject: |
|
|
todd93,
There is not a lot useful there. At 18 sec there is a frame that contains Quote: | You might want to save /run/initramfs/rdsosreport.tet to a USB stick or /boot after mounting them and attach it to a bug report. |
Ahh ... just before that at 4.301704 in the boot is Code: | EXT4-fs (sdd3): VFS: Found ext4 filesystem with invalid superblock checksum. Run e2fsck? |
Is /dev/sdd3 your Gentoo root filesystem?
Is it supposed to be ext4?
If the answers are yes and yes, boot the live media and run
As there are backup superblocks, if the others are OK, that will fix it. If not, your root is not recoverable.
fsck is generally dangerous as when its faced with an inconsistency, it has to guess which information is correct. hence, it can make a bad situation worse.
In your case, it's the superblock that's the first problem, that's relatively safe to allow it to fix. Notice I say 'first' there may be other problems too.
There is no undo. If sdd3 contains valuable data, you need to make an image of it before you let fsck loose.
We could also try to mount /dev/sdd3 manually, using a backup superblock. If it works, that will fix the primary superblock, which is where your problem is. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
todd93 l33t
Joined: 30 Oct 2006 Posts: 620 Location: Missouri
|
Posted: Sat Mar 19, 2022 2:01 pm Post subject: |
|
|
NeddySeagoon wrote: | todd93,
There is not a lot useful there. At 18 sec there is a frame that contains Quote: | You might want to save /run/initramfs/rdsosreport.tet to a USB stick or /boot after mounting them and attach it to a bug report. |
Ahh ... just before that at 4.301704 in the boot is Code: | EXT4-fs (sdd3): VFS: Found ext4 filesystem with invalid superblock checksum. Run e2fsck? |
Is /dev/sdd3 your Gentoo root filesystem?
Is it supposed to be ext4?
If the answers are yes and yes, boot the live media and run
As there are backup superblocks, if the others are OK, that will fix it. If not, your root is not recoverable.
fsck is generally dangerous as when its faced with an inconsistency, it has to guess which information is correct. hence, it can make a bad situation worse.
In your case, it's the superblock that's the first problem, that's relatively safe to allow it to fix. Notice I say 'first' there may be other problems too.
There is no undo. If sdd3 contains valuable data, you need to make an image of it before you let fsck loose.
We could also try to mount /dev/sdd3 manually, using a backup superblock. If it works, that will fix the primary superblock, which is where your problem is. |
Ok, appears to have worked, it mounted fine after that... The answers were "yes" to both questions on ext4... I'm going to boot the kernel again... Stay tuned! |
|
Back to top |
|
|
todd93 l33t
Joined: 30 Oct 2006 Posts: 620 Location: Missouri
|
Posted: Sat Mar 19, 2022 2:15 pm Post subject: |
|
|
Ok, that was successful, I've booted into the new kernel, and after changing net.eth0 to net.enp4s0, I have internet capability! I'm going to attempt to install a desktop environment and try to get this install done! Now I can ssh in from my phone and finish this! |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|