Bug 26838

Summary:	Bootloader not detected on non-volatile memory SSD drive
Product:	Mageia	Reporter:	Joseph Wang <joequant>
Component:	RPM Packages	Assignee:	Mageia tools maintainers <mageiatools>
Status:	NEW ---	QA Contact:
Severity:	major
Priority:	Normal	CC:	mageia
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakxtools-18.31-1.mga8.src.rpm	CVE:
Status comment:
Attachments:	test script

Description Joseph Wang 2020-06-20 20:04:16 CEST

Description of problem:

When I have a boot disk which is a nvm SSD drive, the kernel install does not
rerun the bootloader

The reason is that the /dev/nvme0n1 is not recognized as a hard disk


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. install a kernel on a nvm device
2. you get a bootloader not detected error
3.

Comment 1 Martin Whitaker 2020-06-21 10:20:34 CEST

Please provide the output of

  fdisk -l /dev/nvme0n1

and

  blkid /dev/nvme0n1*

Assignee: bugsquad => mageiatools
Keywords: (none) => NEEDINFO
CC: (none) => mageia

Comment 2 Joseph Wang 2020-06-21 14:40:35 CEST

(base) [joe@big-apple ~]$ sudo fdisk -l /dev/nvme0n1
[sudo] joe 的密碼：
Disk /dev/nvme0n1: 953.89 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: Samsung SSD 960 PRO 1TB                 
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: 0x29329c96

所用裝置       可開機      Start       結束       磁區   Size Id 類型
/dev/nvme0n1p1 *            2048  301783039  301780992 143.9G 83 Linux
/dev/nvme0n1p2         301785088 2000409263 1698624176   810G  5 延伸
/dev/nvme0n1p5         301787136 1951877119 1650089984 786.8G 83 Linux
/dev/nvme0n1p6        1951879168 2000408575   48529408  23.1G 82 Linux 交換區/ S
(base) [joe@big-apple ~]$ sudo blkid /dev/nvm
/dev/nvme0n1    /dev/nvme0n1p2  /dev/nvme0n1p6  
/dev/nvme0n1p1  /dev/nvme0n1p5  
(base) [joe@big-apple ~]$ sudo blkid /dev/nvme0n1*
/dev/nvme0n1: PTUUID="29329c96" PTTYPE="dos"
/dev/nvme0n1p1: UUID="bb5c3530-8482-46fc-89d7-ed3058fb5a58" UUID_SUB="23b457bb-84f4-4d04-b0c9-3f809b48794f" BLOCK_SIZE="4096" TYPE="btrfs" PTTYPE="dos" PARTUUID="29329c96-01"
/dev/nvme0n1p2: PTUUID="34fae1ad" PTTYPE="dos" PARTUUID="29329c96-02"
/dev/nvme0n1p5: LABEL="/home" UUID="b65f0178-859a-4089-b7a5-a37d1ad948c9" UUID_SUB="717672f8-8e6e-4c58-b472-186ffb3070ab" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="29329c96-05"
/dev/nvme0n1p6: UUID="bfdd7ebe-9bed-4040-9342-4f94a3f9b257" TYPE="swap" PARTUUID="29329c96-06"

Comment 3 Martin Whitaker 2020-06-21 20:53:53 CEST

Created attachment 11708 [details]
test script

I can't reproduce this issue when emulating your setup in VirtualBox. I'm assuming you are using GRUB2.

Please run the attached test script by (as root):

  LC_ALL=C perl detect.pl >& detect.log

and attach the resulting log file.

(the script is just an extract of the bootloader detection code with some extra debug output)