Read-only file system on a battery
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I have a 2021 Dell XPS 15 (9510) i7-11800H, 16 GB, 512 GB SSD, RTX 3050Ti, Windows 11 Pro.
I’ve updated the following components:
- replaced the RAM to 2x32 GB
- added a brand new Samsung 980 Pro to the second NVMe slot
On the secondary NVMe drive, I’ve installed Ubuntu 20.04 LTS.
Usually, I use Dell WD19TBS USB-C 180W to supply the power, Internet, external USB keyboard and mouse, and two monitors. When doing so, everything seems to be working perfectly for a long time whether working with Ubuntu or Windows.
However, when the laptop is running on battery, I’m observing Ubuntu freezes that happen anywhere between seconds to minutes after a reboot. The keyboard stops responding, the icons go missing, and I’m getting dropped to the terminal with the following messages appearing:
__ext4_
__ext4_
And after a few seconds, the following start to appear:
system-journald: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
system-journald: Failed to write entry (22 items, 750 bytes), ignoring: Read-only file system
It seems that disconnecting the docking station usually triggers the freeze immediately. When starting from a battery, it usually takes a few minutes before everything freezes.
The only way to recover is to do a power long-press. If I do this sequence a few times - boot, wait for hang, power long-press, boot again, usually at some point the Samsung 980 Pro is no longer visible in the BIOS. I need to boot into Windows, wait a bit, reboot again, and the drive appears and it’s possible to boot to Ubuntu
What I’ve tried:
update Ubuntu to 21.10
update to the latest kernel: 5.13.0-41-generic
update all drivers, including BIOS, from Windows using Dell SupportAssistant
update Samsung 980 Pro firmware through Samsung Magican
enabling Full Power Mode in Samsung Magician
check SMART report for Samsung, it’s all clear
change GRUB params, currently they look like this: GRUB_CMDLINE_
tried also default_
fsck from a live boot pendrive
It looks like the drive decides to go to a sleep at some point and does not wake up.
Windows works well both with docking station and battery, the Samsung NVMe is recognized by Samsung Magician.
Any hint what else can I check?
Thank you!
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/pcmC1D0p: pawel 3332 F...m pulseaudio
/dev/snd/
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2022-04-05 (24 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: Dell Inc. XPS 15 9510
NonfreeKernelMo
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.201.5
Tags: impish
Uname: Linux 5.13.0-41-generic x86_64
UpgradeStatus: Upgraded to impish on 2022-04-29 (0 days ago)
UserGroups: adm cdrom dip docker input lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/17/2022
dmi.bios.release: 1.9
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.0
dmi.board.name: 01V4T3
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.family: XPS
dmi.product.name: XPS 15 9510
dmi.product.sku: 0A61
dmi.sys.vendor: Dell Inc.
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
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 1971009
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.