4.15.0-15-generic can't find root device

Bug #1766770 reported by Barry Price
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This is on a Hewlett-Packard ProLiant DL380 G7, with a Smart Array P410i RAID controller containing a RAID 1+0 array of four SATA hard drives.

It's running Ubuntu 16.04 with the linux-image-generic-hwe-16.04-edge packages installed.

The root partition consists of a simple ext4 filesystem on /dev/sda1, which is on the RAID array

There is a more complex secondary mount involving mdraid and bcache intended to be mounted at /srv - but we're seeing problems before that comes into play.

Booting into the last 4.13 kernel (4.13.0-39-generic) works fine.

Booting into the latest 4.15 kernel (4.15.0-15-generic) results in the root device not being found, and a stacktrace before an initramfs prompt: https://pastebin.ubuntu.com/p/JnTXQ5YP9W/
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Apr 25 03:37 seq
 crw-rw---- 1 root audio 116, 33 Apr 25 03:37 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
IwConfig: Error: [Errno 2] No such file or directory
MachineType: HP ProLiant DL380 G7
Package: linux (not installed)
PciMultimedia:

ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=dd30f756-2a4d-43e5-b49c-dfbafbceea9d ro console=ttyS1,38400 nosplash
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-39-generic N/A
 linux-backports-modules-4.13.0-39-generic N/A
 linux-firmware 1.157.17
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial
Uname: Linux 4.13.0-39-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm
_MarkForUpload: True
dmi.bios.date: 08/16/2015
dmi.bios.vendor: HP
dmi.bios.version: P67
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrP67:bd08/16/2015:svnHP:pnProLiantDL380G7:pvr:cvnHP:ct23:cvr:
dmi.product.family: ProLiant
dmi.product.name: ProLiant DL380 G7
dmi.sys.vendor: HP

Revision history for this message
Barry Price (barryprice) wrote :
Revision history for this message
Barry Price (barryprice) wrote :
Revision history for this message
James Troup (elmo) wrote :

This appears to be a regression in the HPSA driver. In the 4.13 kernel, the following hpsa output is seen:

  https://paste.ubuntu.com/p/Bq9ktJWtBm/

And the HW RAID volume ends up as /dev/sda. In 4.15, the HW RAID is not found and one of the SSD volumes ends up as /dev/sda/

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1766770

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: artful
Revision history for this message
James Troup (elmo) wrote :

William Grant points out:

 commit 8b834bff1b73dce46f4e9f5e84af6f73fed8b0ef
 Date: Tue Mar 13 17:42:39 2018 +0800
     scsi: hpsa: fix selection of reply queue

     Since commit 84676c1f21e8 ("genirq/affinity: assign vectors to all
     possible CPUs") we could end up with an MSI-X vector that did not have
     any online CPUs mapped. This would lead to I/O hangs since there was no
     CPU to receive the completion.

Our 4.15 does not have that commit, but does have the referenced one.

Revision history for this message
Barry Price (barryprice) wrote : CRDA.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
Barry Price (barryprice) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : Lspci.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : Lsusb.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : ProcEnviron.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : ProcModules.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : UdevDb.txt

apport information

Revision history for this message
Barry Price (barryprice) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Barry Price (barryprice) wrote :

I've confirmed this issue on a second G7 with the same model of RAID controller but a simpler disk setup (no bcache or mdraid):

https://pastebin.ubuntu.com/p/bK5xQrXZmD/

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.