Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Prompted for / during bootup
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Mon Mar 13, 2017 4:29 pm    Post subject: Prompted for / during bootup Reply with quote

Hi guys. I've built Gentoo many, many times but this is my first time with a NVMe PCI Flash Memory card. Everything is fine but I get this prompt during bootup:

https://postimg.org/image/bcx7wc0vn/

Basically I'm prompted for the root block device, because apparently it can't find the device uuid anywhere - except the one it displays is the correct one. If I just hit "Enter" it continues and boots just fine.

Any ideas?
Thanks!

PS [/url]I would attach grub.cfg and .config but I don't see the option to attach files anymore...?
_________________
Just when you think you know the answers, I change the questions.

AMD64 Phenom-II 6-core, 440Gb Intel SSD NVMe, 4Tb SATA II, 20576Mb, 1Gb Ethernet, GeForce GTS 950, x64
MacBook, ESX servers, many other toys
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43178
Location: 56N 3W

PostPosted: Mon Mar 13, 2017 7:09 pm    Post subject: Reply with quote

phil_r,

It sounds like the kernel tries to mount root before everything is ready.
Does adding rootwait to the kernel command line in grub.cfg have any effect?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Mon Mar 13, 2017 7:18 pm    Post subject: Reply with quote

@Neddy - I will check on that tonight and get back to you!
_________________
Just when you think you know the answers, I change the questions.

AMD64 Phenom-II 6-core, 440Gb Intel SSD NVMe, 4Tb SATA II, 20576Mb, 1Gb Ethernet, GeForce GTS 950, x64
MacBook, ESX servers, many other toys
Back to top
View user's profile Send private message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Tue Mar 14, 2017 1:03 am    Post subject: Reply with quote

No success with the rootwait, sadly.
_________________
Just when you think you know the answers, I change the questions.

AMD64 Phenom-II 6-core, 440Gb Intel SSD NVMe, 4Tb SATA II, 20576Mb, 1Gb Ethernet, GeForce GTS 950, x64
MacBook, ESX servers, many other toys
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43178
Location: 56N 3W

PostPosted: Tue Mar 14, 2017 9:07 am    Post subject: Reply with quote

phil_r,

In a way, I'm pleased about that. rootwait makes the kernel check that the root filesystem is there before it tries to mount it.
It avoids the panic when root isn't ready and waits forever instead.
That it didn't fix it, shows that its not that.

Unfortunately, I'm out of ideas. I don't have a NVMe PCI Flash Memory card to experience the problem first hand.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Tue Mar 14, 2017 5:14 pm    Post subject: Reply with quote

I've never had this issue before with a regular (/dev/sdX) type drive. But I also had to build an initramfs for this, which I've never had to do before either. So I'm sure I'm just missing a simple step somewhere - but it is weird that it identifies the UUID of the / filesystem, prompts for the same one and then simply works if I just let it continue...
_________________
Just when you think you know the answers, I change the questions.

AMD64 Phenom-II 6-core, 440Gb Intel SSD NVMe, 4Tb SATA II, 20576Mb, 1Gb Ethernet, GeForce GTS 950, x64
MacBook, ESX servers, many other toys
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43178
Location: 56N 3W

PostPosted: Tue Mar 14, 2017 6:03 pm    Post subject: Reply with quote

phil_r,

That rootwait will be applied to the initrd, not the real root.

Why do you need an initrd?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Tue Mar 14, 2017 6:24 pm    Post subject: Reply with quote

Without the initrd, it kernel panics about 2 seconds into the boot up process.
_________________
Just when you think you know the answers, I change the questions.

AMD64 Phenom-II 6-core, 440Gb Intel SSD NVMe, 4Tb SATA II, 20576Mb, 1Gb Ethernet, GeForce GTS 950, x64
MacBook, ESX servers, many other toys
Back to top
View user's profile Send private message
cboldt
l33t
l33t


Joined: 24 Aug 2005
Posts: 833

PostPosted: Tue Mar 14, 2017 6:48 pm    Post subject: Reply with quote

Have you tried using that UUID in /etc/fstab? Or perhaps you already have, and the "drive" isn't ready when fstab is processed.

"UUID=" goes in place of the "/dev/sd?" place, that is, it would be the first field in the fstab line.

Edit to add, you might get satisfaction with the kernel boot parm "root=" too.

From /usr/src/*/init/do_mounts.c :

Code:
 *      6) PARTUUID=00112233-4455-6677-8899-AABBCCDDEEFF representing the
 *         unique id of a partition if the partition table provides it.
 *         The UUID may be either an EFI/GPT UUID, or refer to an MSDOS
 *         partition using the format SSSSSSSS-PP, where SSSSSSSS is a zero-
 *         filled hex representation of the 32-bit "NT disk signature", and PP
 *         is a zero-filled hex representation of the 1-based partition number.


Combining that with the instructions in /usr/src/*/Documentation/kernel-parameters.txt :

Code:
        root=           [KNL] Root filesystem
                        See name_to_dev_t comment in init/do_mounts.c.


... I'd try the kernel boot parm "root=PARTUUID=xxxxxxxxxxx"
Back to top
View user's profile Send private message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Tue Mar 14, 2017 7:28 pm    Post subject: [Solved] Prompted for / during bootup Reply with quote

@cboldt:

I did have it in fstab, it didn't make a difference.

Setting:
root=PARTUUID=xxxxxxxxxxx (insert partuuid here)

had no effect, however when I did:
root=UUID=xxxxxxxxxxx (insert uuid here)

seems to of cracked the problem - it boots without stopping now.

Thank you all for the guidance!
_________________
Just when you think you know the answers, I change the questions.

AMD64 Phenom-II 6-core, 440Gb Intel SSD NVMe, 4Tb SATA II, 20576Mb, 1Gb Ethernet, GeForce GTS 950, x64
MacBook, ESX servers, many other toys
Back to top
View user's profile Send private message
cboldt
l33t
l33t


Joined: 24 Aug 2005
Posts: 833

PostPosted: Tue Mar 14, 2017 7:34 pm    Post subject: Reply with quote

Appreciate the feedback. Funny how the kernel docs can be ever so slightly misleading, and real world experience is mighty useful. You might be able to get rid of your initramfs too - I'm sure that it (initramfs startup) has to find rootfs on its own, without reference to /etc/fstab ... but I'm not clear on why you found the need for an initramfs in the first place. Not that it matters, once you have the thing booting, you are probably happy to "leave it alone"!

Oh, one other thought. The kernel boot parm structure may change over time. The instruction to use PARTUUID is from a 4.9.6 kernel, and from the source code, the kernel is looking for that exact string.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43178
Location: 56N 3W

PostPosted: Tue Mar 14, 2017 7:54 pm    Post subject: Reply with quote

phil_r,

You only need an initrd if your kernel cannot boot without some help from user space.
You must configure everything needed to boot as <*>, not <M> since you can't load modules until root is mounted and if you need modules to mount root, well ... don't do that.

UUID and PARTUUID refer to different block structures.
PARTUUID is a partition reference. UUID is a filesystem reference.
The kernel can mount root by PARTUUID but not by UUID. root=UUID= needs the user space mount tool and an initrd.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Tue Mar 14, 2017 8:41 pm    Post subject: Reply with quote

I don't know what to tell you...

All critical functions are compiled in, not modules. The NVM driver, the filesystem drivers, PCI related things all compiled in.

Without the intird, it didn't boot. With it, it does.

Using PARTUUID failed. UUID worked (and yes I got the right values from /dev/disk/by-uuid | by-partuuid)


I can play with it more and try to narrow it down some but for right now, at least it boots without help.
_________________
Just when you think you know the answers, I change the questions.

AMD64 Phenom-II 6-core, 440Gb Intel SSD NVMe, 4Tb SATA II, 20576Mb, 1Gb Ethernet, GeForce GTS 950, x64
MacBook, ESX servers, many other toys
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43178
Location: 56N 3W

PostPosted: Tue Mar 14, 2017 8:49 pm    Post subject: Reply with quote

phil_r,

The non initrd panic message would be useful.
You cannot use root=UUID= without an initrd though.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
cboldt
l33t
l33t


Joined: 24 Aug 2005
Posts: 833

PostPosted: Tue Mar 14, 2017 9:09 pm    Post subject: Reply with quote

I also wonder what is in the initramfs.

Neddy - appreciate the heads up that UUID and PARTUUID are different. They indeed are. I ran blkid here, and UUID is associated with the filesystems. PARTUUID is 8 hex digits, followed by a hyphen and two more hex digits. My partition scheme is NOT GPT, and I don't use EFI.

Another "root=" parameter scheme that is supposed to work is to give the major/minor device as a four digit hex value, or major:minor separated by a colon, I assume in that case that major and minor are decimal.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43178
Location: 56N 3W

PostPosted: Tue Mar 14, 2017 9:45 pm    Post subject: Reply with quote

cboldt,

That's the MSDOS DiskID, from the disk label followed by the partition number.
Look in fdisk.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
cboldt
l33t
l33t


Joined: 24 Aug 2005
Posts: 833

PostPosted: Tue Mar 14, 2017 10:03 pm    Post subject: Reply with quote

Yep, it is the same, "Disk identifier: 0x9af1d243" - get rid of the leading 0x hex identifier, and it becomes PARTUUID on (that device) on my system, after adding the hyphen and partition number.
Back to top
View user's profile Send private message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Wed Mar 15, 2017 2:10 pm    Post subject: Reply with quote

I'm currently using a 4.9.13 kernel. I'll compile a 4.10 kernel with no initrd and boot that, however I'm at work so although I can compile the kernel I won't be able to snap the error for several hours.

Thank you for continuing to work with me on this.
_________________
Just when you think you know the answers, I change the questions.

AMD64 Phenom-II 6-core, 440Gb Intel SSD NVMe, 4Tb SATA II, 20576Mb, 1Gb Ethernet, GeForce GTS 950, x64
MacBook, ESX servers, many other toys
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43178
Location: 56N 3W

PostPosted: Wed Mar 15, 2017 2:18 pm    Post subject: Reply with quote

phil_r,

Working on other broken Gentoos saves us breaking our own :)
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Thu Mar 16, 2017 4:04 am    Post subject: Reply with quote

So this is what I get if I boot with a kernel and no initramfs generated:

http://pasteboard.co/JXK5iJjXm.jpg

Some snippets of /dev that might be useful to you:

Code:

undertaker ~ # fdisk -l /dev/nvme0n1
Disk /dev/nvme0n1: 372.6 GiB, 400088457216 bytes, 781422768 sectors
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: B228C256-738C-4FE8-B442-F57937CFBE91

Device             Start       End   Sectors  Size Type
/dev/nvme0n1p2    206848   2303999   2097152    1G Linux filesystem
/dev/nvme0n1p3   2304000  69412863  67108864   32G Linux swap
/dev/nvme0n1p4  69412864 174270463 104857600   50G Linux filesystem
/dev/nvme0n1p5 314574848 314779647    204800  100M EFI System
/dev/nvme0n1p9 519278592 781422591 262144000  125G Linux filesystem
undertaker ~ # ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 15 Mar 15 22:54 1fc078c4-aa4b-4550-9591-e43126725a9b -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 Mar 15 22:54 3aa9cea9-3bfd-445b-8700-c07b7c2ceb6a -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 10 Mar 15 22:54 74e4f678-7ac2-41c6-afa8-fc4fc25b52c8 -> ../../sda1
lrwxrwxrwx 1 root root 10 Mar 15 22:54 8A5A45E95A45D31D -> ../../sdb1
lrwxrwxrwx 1 root root 15 Mar 15 22:54 930A-A1D2 -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 15 Mar 15 22:55 b38edddc-5109-47f4-ba69-d491be55dbd8 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Mar 15 22:54 d411aeab-18dc-4908-a29d-efb719ef803f -> ../../nvme0n1p9
undertaker ~ # ls -l /dev/disk/by-partuuid
total 0
lrwxrwxrwx 1 root root 15 Mar 15 22:54 06a4bc61-e778-4eb2-8571-e519632892ec -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 15 Mar 15 22:54 140d2f66-02ab-47f6-96e0-329cc06e55df -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 10 Mar 15 22:54 3af3e5fd-ac08-47fb-a901-157d65c0c067 -> ../../sda1
lrwxrwxrwx 1 root root 15 Mar 15 22:54 487e3589-2991-4a0e-9f00-ef0c86078807 -> ../../nvme0n1p9
lrwxrwxrwx 1 root root 15 Mar 15 22:54 6f72714e-3423-4181-93fe-11a90e3cda7e -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 10 Mar 15 22:54 9bd86715-01 -> ../../sdb1
lrwxrwxrwx 1 root root 15 Mar 15 22:55 a0dcb1da-d705-4f48-b85b-c22dd6062cbf -> ../../nvme0n1p2


Root is /dev/nvme0n1p4. sda1 is a internal sata that I use for /home and sdb1 is just an external usb I happened to have plugged in.

My grub.cfg is pretty much the standard apart from me adding the root=UUID=3aa9cea9-3bfd-445b-8700-c07b7c2ceb6a. As I said earlier if I use the partuuid it (still) doesn't boot.

If it helps, I put my kernel config on Dropbox - https://www.dropbox.com/s/hhzzq2lpj94ujsp/kernelconfig?dl=0


Any of that help?
_________________
Just when you think you know the answers, I change the questions.

AMD64 Phenom-II 6-core, 440Gb Intel SSD NVMe, 4Tb SATA II, 20576Mb, 1Gb Ethernet, GeForce GTS 950, x64
MacBook, ESX servers, many other toys
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43178
Location: 56N 3W

PostPosted: Thu Mar 16, 2017 10:08 am    Post subject: Reply with quote

phil_r,

You can't just throw away the initrd. You need to change a few kernel options from <M> to <*> too.
The initrd is a temporary root filesystem in a file. It holds all the kernel modules so that they can be loaded before the real root is mounted.
The unknown-block(0,0) at the top of the image shows that the kernel cannot talk to your HDD at all, probably because it needs some modules from the initrd.

root=UUID= needs the initrd as it uses /bin/mount to mount root. You must either use the root=PARTUUID= or /dev/nvme0n...
That usually leads to different numbers in the panic statement unknown-block(0,0).

You don't say what filesystem you use on root.
Code:
CONFIG_XFS_FS=m
CONFIG_BTRFS_FS=m
are modules. They won't work.
Code:
CONFIG_EXT3_FS=y
CONFIG_EXT4_FS=y
CONFIG_JBD2=y
will be OK

Everything else looks good.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
cboldt
l33t
l33t


Joined: 24 Aug 2005
Posts: 833

PostPosted: Thu Mar 16, 2017 12:26 pm    Post subject: Reply with quote

Just to make the point pedantically (thinking more of other readers, not you), whatever the kernel needs to recognize the NVMe PCI Flash Memory card must be built into the kernel, for root=PARTUUID to work. That covers more than the filesystem!

Edit to add -- the opening screen tells us that "All critical functions are compiled in, not modules." isn't true. Something is missing from the kernel. The major,minor designation of 0,0 would be something different.

What do you get from `ls -l /dev/nvme0n1p4`?
Back to top
View user's profile Send private message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Thu Mar 16, 2017 3:03 pm    Post subject: Reply with quote

@Neddy - root is ext4. /home is xfs. I learned that lesson a long time ago :-)

If you see something that should be compiled in rather than a module please let me know.

@cboldt - The NVMe driver is compiled in.

Code:
undertaker ~ # ls -l /dev/nvme0n1p4
brw-rw---- 1 root disk 259, 3 Mar 15 22:54 /dev/nvme0n1p4


I assume the 259,3 is what you're looking for?
_________________
Just when you think you know the answers, I change the questions.

AMD64 Phenom-II 6-core, 440Gb Intel SSD NVMe, 4Tb SATA II, 20576Mb, 1Gb Ethernet, GeForce GTS 950, x64
MacBook, ESX servers, many other toys
Back to top
View user's profile Send private message
cboldt
l33t
l33t


Joined: 24 Aug 2005
Posts: 833

PostPosted: Thu Mar 16, 2017 3:25 pm    Post subject: Reply with quote

Yep, 259,3 is what I was looking for. Try "root=259:3" as a boot parameter. That is one of the forms that is spelled out in the kernel Documentation. Another form is a hex representation, but with major=259 (>0xff), this deviates from the four (hex) digit example. The hex representation would have five digits, "10403"

We can't tell what has to be compiled in, that isn't, but the fact that the kernel reports inability to find the root at 0,0 is a symptom that the device is itself unknown to the kernel.
.
Once it's up, show us the output of `lsmod`. Maybe there is something other than "the device driver itself," which you haven't specified yet. My kenel config is set like so ...

Code:
CONFIG_NVME_CORE=m
CONFIG_BLK_DEV_NVME=m
# CONFIG_BLK_DEV_NVME_SCSI is not set
# CONFIG_NVME_TARGET is not set
CONFIG_NVMEM=m


So I could have "the device" NVMe set in the kernal as CORE capability only, then "the device" NVMe-block set as a module, etc

Edit OOPS - 0259 is 0x103, not 0x104. The kernel docs say, when representing the root device in hex, as a kernel boot parameter, omit the leading 0x. I use it here just to communicate. root=10303
Back to top
View user's profile Send private message
phil_r
Apprentice
Apprentice


Joined: 14 Mar 2006
Posts: 218
Location: Lincoln, NE, USA

PostPosted: Thu Mar 16, 2017 3:42 pm    Post subject: Reply with quote

Don't forget, the original issue here is that without root=UUID in grub.cfg my system won't boot unless I supply the UUID during boot-up (which it defaults to so all I have to is hit ENTER). If I do that the system boots fine so there can't be too much wrong with the kernel. I'm not worried about needing an initrd or not or anything like that. I do have a bootable system but it's a tad kludgy. I don't mind having to have the extra parameter in grub.cfg, it's just strange to me that I never needed to do that with a rotational hard drive. Once everything is booted, it's all rock solid.
_________________
Just when you think you know the answers, I change the questions.

AMD64 Phenom-II 6-core, 440Gb Intel SSD NVMe, 4Tb SATA II, 20576Mb, 1Gb Ethernet, GeForce GTS 950, x64
MacBook, ESX servers, many other toys
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Goto page 1, 2  Next
Page 1 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