[Bug 1877388] Re: If DVD drive is present system very often fails to start-up

Thu May 7 14:34:55 UTC 2020

It occurred to me as I was filing this that perhaps I should've searched
existing bugs for "failed to unmount /cdrom" - none of these sound the
same, but perhaps related?

https://bugs.launchpad.net/ubuntu?field.searchtext=failed+to+unmount+%2Fcdrom&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1877388

Title:
  If DVD drive is present system very often fails to start-up

Status in plymouth package in Ubuntu:
  New

Bug description:
  Whenever I power down, upon next boot the system just hangs with
  Ubuntu at the bottom of the screen and the circle above going around
  and around forever.

  It happens nearly every ime I power down, but not every single time.
  Rebooting rather that powering down works quite often.

  At first when thing hung I would just hard power off by holding down
  the power key.  Then I'd use the live usb I installed with to run
  Disks app.  More often than not the vfat W95 FAT32 partition at sda1
  was damaged. The first repair would fail. The second repair would
  succeed.  And then I'd be able to boot into my system again.

  After chatting about it a little with EriC^^ in #ubuntu on IRC I
  learned how to do Alt+Fn+PrtSc S, U, B or S, U, O.  Sometimes just
  doing either of those on the hang screen would result in it booting up
  fine next time.  Sometimes not.

  After installing 20.04 (a fresh install on a brand new Samsung 860 EVO
  1TB sdd hard drive) I copied back all the files in my home direct that
  I'd backed from 18.04, including hidden files.  This confused Firefox
  so I had to delete related folders and then unintall and reinstall to
  stop Firefox being confused.  This might have nothing whatsoever to do
  with this issue, just mentioning it just in case something else is
  similarly confused.  EriC^^ suggested I try adding another user and
  seeing if the issue went away.  On the first test (and some but not
  all subsequent tests) it did seem that TestUser could power down and
  reboot fine. But actually it didn't seem that different.

  I powered down, rebooted, used live usb to repair Disk over and over
  again for hours trying to find a pattern as to when it happened and
  when it didn't, but failed to find any fixed pattern.

  Eventually at one point it was taking a while to power down (or
  reboot, I forget) and so I hit Esc and spotted that it had failed to
  unmount /cdrom  ...

  ... so then I thought I'd try completely removing my DVD/CDRW drive
  and that made the issue go away.

  Before filing this I put the DVD drive back in (but haven't since
  rebooted), so not sure if apport has picked up it's details or not?
  Perhaps I'll need to re-file the bug after booting with it present?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: plymouth 0.9.4git20200323-0ubuntu6
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  7 15:09:23 2020
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2020-04-26 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
       |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
       |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
           |__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
  MachineType: LENOVO 4384WCV
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET81WW (1.41 )
  dmi.board.name: 4384WCV
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvr6MET81WW(1.41):bd10/26/2010:svnLENOVO:pn4384WCV:pvrThinkPadT510:rvnLENOVO:rn4384WCV:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T510
  dmi.product.name: 4384WCV
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1877388/+subscriptions