Ubuntu fails and requires a hard reboot. This appears to be due to the file system becoming readonly.

Bug #1955863 reported by Michael Duckwitz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
udisks2 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu fails and requires a hard reboot. This appears to be due to the file system becoming readonly.

This has happened many times over the past few months. Tonight, these were the programs being used when the system died.
    1. Gnome Terminal 3.38.1
    2. Evolution 3.40.4-1
    3. Gnome Files 40.2
    4. Firefox Browser 95.0.2 (64-bit)
    5. Chromium Browser Version 96.0.4664.110 (Official Build) snap (64-bit)
    6. Rythmbox 3.4.4
    7. Code42 Crashplan 8.8.1 running in the background, may or may not have been performing a backup
    8. LibreOffice: Writer and Calc
         Version: 7.2.3.2 / LibreOffice Community
         Build ID: 20(Build:2)
         CPU threads: 8; OS: Linux 5.13; UI render: default; VCL: gtk3
         Locale: en-US (en_US.UTF-8); UI: en-US
         Ubuntu package version: 1:7.2.3-0ubuntu0.21.10.1
         Calc: threaded

When I attempt to shutdown or reboot, the screen changes to a non-graphical display with unending errors about the file system.

My system is up-to-date and I’m using Wayland.

> lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 21.10
Release: 21.10
Codename: impish

> uname -a
Linux aBrux 5.13.0-22-generic #22-Ubuntu SMP Fri Nov 5 13:21:36 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

> ls -a /var/crash/
. ..

Visiting https://errors.ubuntu.com/user/ID I get “No errors have been reported from this system”.

/etc/default/apport does have “enabled=1” and it’s not commented out.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: udisks2 2.9.4-1
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Uname: Linux 5.13.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 71-bh-permissions.rules 60-brother-brscan4-libsane-type1.rules 60-brother-libsane-type1-inst.rules 70-snap.gimp.rules 70-snap.snap-store.rules 70-snap.chromium.rules 70-snap.core.rules 99-jlink.rules 70-snap.pinta.rules 70-snap.firefox.rules 70-snap.zoom-client.rules 71-ti-permissions.rules
Date: Mon Dec 27 21:42:42 2021
InstallationDate: Installed on 2021-10-17 (72 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: Dell Inc. Inspiron 7506 2n1
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=1868a1bf-d176-4a48-8969-65c754214a81 ro quiet splash vt.handoff=7
SourcePackage: udisks2
Symptom: storage
Title: No permission to access files on storage device
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/01/2021
dmi.bios.release: 1.8
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 0G72HV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd10/01/2021:br1.8:svnDellInc.:pnInspiron75062n1:pvr:rvnDellInc.:rn0G72HV:rvrA00:cvnDellInc.:ct31:cvr:sku09DE:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7506 2n1
dmi.product.sku: 09DE
dmi.sys.vendor: Dell Inc.

Revision history for this message
Michael Duckwitz (duckwitz) wrote :
affects: ubuntu → udisks2 (Ubuntu)
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709

(FYI: A file-system flipping to RO (read-only) is usually the result of the system detecting errors & flipping to RO prevents dataloss. You should read your systemd journal logs for clues; but the usual cause is hardware issues; such as power; failing disks etc.)

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.