Boot hang after updating and setting up Iscsi with 4.15.0-72 generic kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Hi All,
Host Server - Dell PowerEdge R630, Dual Xeon E5-2650 v4, 768GB Memory, ESX 6.5.0
I created a VM with 1vCPU, 2GB Memory, 16GB Hard drive.
I installed Ubuntu Server 16.04.2 (latest ISO I had on hand), installed fine.
I then ran apt-get update, apt-get upgrade... upgrade failed as repos were out of date. I then ran do-distribution
--I don't want to mislead anyone - I can't remember if I rebooted or not at this point.
After this, I setup an Iscsi initiator to an external target, added to fstab, formatted and confirmed all working.
I then rebooted, and... nothing!
No ping, no ssh or anything... Control + Alt + Del did not work, looked like it had frozen. The last line was starting SSH, but the previous line was the Iscsi initiator. At this point, I figured network is down and ISCSI is hanging as it can't connect/maybe I messed up the ISCSI mount.
I then went to GRUB and did advanced, I did the recovery console for kernel 4.15.0-72 generic which lead to a kernel panic: https:/
I then went through the options again and selected 4.4.0-62 generic, and it booted fine, and after about 2 seconds at the recovery menu, further ISCSI related text came up: https:/
I went to the shell as root, deleted the line from fstab, and rebooted, but, it hang again at the same point.
I then went to advanced, booted normally to 4.4.0-62 generic, and, it went through without any issue what so ever.
Messing around with kernels puts me out of my depth... happy to give further info or do more diagnostics if required, however, due to it working in a different kernel and nothing out of the ordinary - I believe this to be a bug.
This is on Ubuntu 18.04.3 LTS / Release 18.04
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Dec 3 01:35 seq
crw-rw---- 1 root audio 116, 33 Dec 3 01:35 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=
InstallationDate: Installed on 2019-12-02 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.173.12
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic
Uname: Linux 4.4.0-62-generic x86_64
UpgradeStatus: Upgraded to bionic on 2019-12-02 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/05/2016
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: VMware Virtual Platform
dmi.product.
dmi.sys.vendor: VMware, Inc.
no longer affects: | intel-microcode (Ubuntu) |
Sorry, I'm new here - I was searching for related bugs to not create a duplicate and it appears to automatically got the intel microcode tag... I can't confirm it is related or not to that.
p.s. I put the Iscsi target back in fstab, rebooted and selected the old kernel - it booted and mounted without any issue at all.