Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Inconsistency when booting new kernel
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
NathanZachary
Moderator
Moderator


Joined: 30 Jan 2007
Posts: 2496
Location: /home/zach

PostPosted: Thu Jun 27, 2019 2:31 am    Post subject: Reply with quote

The motherboard is an Intel DX58SO2 (no making fun of how old it is :P), and it has a "main" SATA controller as well as a Marvell eSATA controller:
Code:

# lspci | grep -i sata
00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller
02:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9123 PCIe SATA 6.0 Gb/s controller (rev 10)
08:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6111/6121 SATA II / PATA Controller (rev b2)


I'm going to give the 'root=partuuid=' option a try and see how it goes. If that fixes the problem, then great. I'll continue to delve into possible causes for the change, but it is more important to get it fixed. I don't see any reason to not go the partuuid route.
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---
Back to top
View user's profile Send private message
NathanZachary
Moderator
Moderator


Joined: 30 Jan 2007
Posts: 2496
Location: /home/zach

PostPosted: Thu Jun 27, 2019 3:01 am    Post subject: Reply with quote

Well using the 'root=PARTUUID=' kernel parameter fixed the problem. I've consistently booted several times now, and am confident that that was the issue as seen by the current mount output:
Code:

# mount -l | grep '/dev/sd'
/dev/sdf4 on / type ext4 (rw,noatime,discard)
/dev/sdg1 on /home/zach/stuff type ext4 (rw,noatime)
/dev/sda1 on /vmdrive type ext4 (rw,noatime)


In previous successful boots, /dev/sdb4 was the root volume. In this case, since it is /dev/sdf4, it would NOT have booted without the 'root=PARTUUID=' kernel parameter. I made that the standard going forward by finding the PARTUUID with gdisk:
Code:

# gdisk /dev/sdf
GPT fdisk (gdisk) version 1.0.4

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): i
Partition number (1-4): 4
Partition GUID code: 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem)
Partition unique GUID: EBC14D26-4071-489E-B14D-9EF2CAABE89F
First sector: 1579008 (at 771.0 MiB)
Last sector: 488395119 (at 232.9 GiB)
Partition size: 486816112 sectors (232.1 GiB)
Attribute flags: 0000000000000000
Partition name: 'rootfs'

Command (? for help): q


the PARTUUID is the "Partition unique GUID" code above, or in my specific case, 'EBC14D26-4071-489E-B14D-9EF2CAABE89F'. I then added that as an option within GRUB2:
Code:

# grep 'GRUB_CMDLINE_LINUX=' /etc/default/grub | grep -v '^#'
GRUB_CMDLINE_LINUX="root=PARTUUID=EBC14D26-4071-489E-B14D-9EF2CAABE89F"


and regenerated my grub.cfg with `grub-mkconfig -o /boot/grub/grub.cfg`. Now it shows on all kernel lines, overriding the first 'root=' line for all kernels:
Code:

# grep 'vmlinuz' /boot/grub/grub.cfg
   linux   /vmlinuz-5.0.13-gentoo root=/dev/sdf4 ro root=PARTUUID=EBC14D26-4071-489E-B14D-9EF2CAABE89F
      linux   /vmlinuz-5.0.13-gentoo root=/dev/sdf4 ro root=PARTUUID=EBC14D26-4071-489E-B14D-9EF2CAABE89F
      linux   /vmlinuz-5.0.13-gentoo root=/dev/sdf4 ro single root=PARTUUID=EBC14D26-4071-489E-B14D-9EF2CAABE89F
      linux   /vmlinuz-4.17.14-gentoo root=/dev/sdf4 ro root=PARTUUID=EBC14D26-4071-489E-B14D-9EF2CAABE89F
      linux   /vmlinuz-4.17.14-gentoo root=/dev/sdf4 ro single root=PARTUUID=EBC14D26-4071-489E-B14D-9EF2CAABE89F


So, the problem is resolved now, but I am going to continue to investigate to see if I can find what caused the change. I also noticed that the boot time on 5.0.13 is consistently ~6-8 seconds slower than with the previous 4.17.14 kernel that I was using. Anyway, thanks for all the help in tracking down the problem, and I am anxious to see whether or not it persists in the 5.1 kernels (once I am able to build the nvidia-drivers with one).

Cheers,
Nathan Zachary
_________________
“Truth, like infinity, is to be forever approached but never reached.” --Jean Ayres (1972)
---avatar cropped from =AimanStudio---
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7368

PostPosted: Thu Jun 27, 2019 8:15 am    Post subject: Reply with quote

NathanZachary wrote:
They are all SATA disks (OS drive is an SSD, and the other two are spinning disks).

What is important there, is are they all using the same controller?
kernel just do first seen, first served rules (which is actually as simple as that).

if you have controller1: loaded as module, with pciid1
and controller2: buildin kernel, with pciid3 (the point is not pciid3, the point is just showing an id higher than controller1)

kernel see buildin first (because it's build in)
and sda, sdb... are given to disks attach to controller2

if you have buildin controller1 driver (so both controller drivers are buildin), it's still first seen, but first seen is now the lowest pciids in the list:
kernel see controller1 first (because lowest pciid) and sda, sdb... are attach to it

I made a doc that you might like read times ago, trying to explains that: https://forums.gentoo.org/viewtopic-t-1007788.html

You must be in the case where your bios play with pciids (some bios do alter pciids depending on option set, and sometimes, even with something totally different, like enabling a network card or sound card...) and change pciids of controllers
Back to top
View user's profile Send private message
Anon-E-moose
Advocate
Advocate


Joined: 23 May 2008
Posts: 4402
Location: Dallas area

PostPosted: Thu Jun 27, 2019 9:15 am    Post subject: Reply with quote

Glad it's fixed, at least for booting.

With disks that may get reordered (from boot to boot) partuuid is the way to go, at least for grub, I like using labels in /etc/fstab (just because they're shorter)

Just curious, which disks are attached to which sata controllers.

And no, I don't make fun of running old stuff.
I usually keep my mb's/systems around for years.
:lol:
_________________
Asus m5a99fx, FX 8320 - nouveau, oss4, rx550 for qemu passthrough
Acer laptop E5-575, i3-7100u - i965, alsa
---both---
5.0.13 zen kernel, profile 17.1 (no-pie & modified) amd64-no-multilib
gcc 8.2.0, eudev, openrc, openbox, palemoon
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
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