File system turns read only after waking Dell XPS 9370 laptop up from suspend
Multi tool use
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm running Ubuntu 18.04 on a Dell XPS 13 (9370). Recently my main file system has been turning read-only when I wake my laptop up from suspend (i.e. open the lid).
Relevant output from dmesg:
[95469.731682] OOM killer enabled.
[95469.731684] Restarting tasks ... done.
[95469.741792] [drm] RC6 on
[95469.763521] EXT4-fs error (device nvme0n1p3): __ext4_get_inode_loc:4618: inode #3408659: block 13631569: comm Xwayland: unable to read itable block
[95469.763529] Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write
[95469.763531] Aborting journal on device nvme0n1p3-8.
[95469.763535] Buffer I/O error on dev nvme0n1p3, logical block 57180160, lost sync page write
[95469.763536] JBD2: Error -5 detected when updating journal superblock for nvme0n1p3-8.
[95469.763538] EXT4-fs (nvme0n1p3): Remounting filesystem read-only
[95469.763541] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: IO failure
[95469.763543] EXT4-fs (nvme0n1p3): previous I/O error to superblock detected
[95469.763544] Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write
[95469.763546] EXT4-fs error (device nvme0n1p3) in ext4_dirty_inode:5945: IO failure
[95469.763548] EXT4-fs (nvme0n1p3): previous I/O error to superblock detected
[95469.763549] Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write
[95469.835805] EXT4-fs (nvme0n1p3): ext4_writepages: jbd2_start: 9223372036854775806 pages, ino 25579170; err -30
[95469.836523] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: Journal has aborted
[95469.836535] EXT4-fs (nvme0n1p3): previous I/O error to superblock detected
[95469.837801] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: Journal has aborted
[95469.842400] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: Journal has aborted
[95469.907749] PM: suspend exit
There seem to be some clear red flags there but how do I go about resolving these errors?
linux filesystems suspend
edited Aug 21 at 19:13
sourcejedi
20.1k42886
asked Aug 21 at 17:26
M. Berk
1011
add a comment |Â
up vote
0
down vote
favorite
I'm running Ubuntu 18.04 on a Dell XPS 13 (9370). Recently my main file system has been turning read-only when I wake my laptop up from suspend (i.e. open the lid).
Relevant output from dmesg:
[95469.731682] OOM killer enabled.
[95469.731684] Restarting tasks ... done.
[95469.741792] [drm] RC6 on
[95469.763521] EXT4-fs error (device nvme0n1p3): __ext4_get_inode_loc:4618: inode #3408659: block 13631569: comm Xwayland: unable to read itable block
[95469.763529] Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write
[95469.763531] Aborting journal on device nvme0n1p3-8.
[95469.763535] Buffer I/O error on dev nvme0n1p3, logical block 57180160, lost sync page write
[95469.763536] JBD2: Error -5 detected when updating journal superblock for nvme0n1p3-8.
[95469.763538] EXT4-fs (nvme0n1p3): Remounting filesystem read-only
[95469.763541] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: IO failure
[95469.763543] EXT4-fs (nvme0n1p3): previous I/O error to superblock detected
[95469.763544] Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write
[95469.763546] EXT4-fs error (device nvme0n1p3) in ext4_dirty_inode:5945: IO failure
[95469.763548] EXT4-fs (nvme0n1p3): previous I/O error to superblock detected
[95469.763549] Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write
[95469.835805] EXT4-fs (nvme0n1p3): ext4_writepages: jbd2_start: 9223372036854775806 pages, ino 25579170; err -30
[95469.836523] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: Journal has aborted
[95469.836535] EXT4-fs (nvme0n1p3): previous I/O error to superblock detected
[95469.837801] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: Journal has aborted
[95469.842400] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: Journal has aborted
[95469.907749] PM: suspend exit
There seem to be some clear red flags there but how do I go about resolving these errors?
linux filesystems suspend
edited Aug 21 at 19:13
sourcejedi
20.1k42886
asked Aug 21 at 17:26
M. Berk
1011
You might want to try a quick self-check withsmartctl -H /dev/nvme0. And there might be something insmartctl -l error /dev/nvme0. smartctl supports NVMe, although the support might still be experimental.
– sourcejedi
Aug 21 at 19:20
Some obvious search terms found 0 bugs in the Ubuntu tracker. bugs.launchpad.net/ubuntu/bionic/+source/… You could try reporting there (make sure to read the guidelines about required information). Especially if you found a kernel version that doesn't have the problem.
– sourcejedi
Aug 21 at 19:31
You should try seeing if one your older kernel updates avoids the problem (kernel versions in GRUB boot menu). I think, if it is a kernel regression within 18.04, it is a regression within the Ubuntu 4.15.0-x.y series. Ubuntu is on its own here; it's not related to any of the official linux-stable branches.
– sourcejedi
Aug 21 at 19:33
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm running Ubuntu 18.04 on a Dell XPS 13 (9370). Recently my main file system has been turning read-only when I wake my laptop up from suspend (i.e. open the lid).
Relevant output from dmesg:
[95469.731682] OOM killer enabled.
[95469.731684] Restarting tasks ... done.
[95469.741792] [drm] RC6 on
[95469.763521] EXT4-fs error (device nvme0n1p3): __ext4_get_inode_loc:4618: inode #3408659: block 13631569: comm Xwayland: unable to read itable block
[95469.763529] Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write
[95469.763531] Aborting journal on device nvme0n1p3-8.
[95469.763535] Buffer I/O error on dev nvme0n1p3, logical block 57180160, lost sync page write
[95469.763536] JBD2: Error -5 detected when updating journal superblock for nvme0n1p3-8.
[95469.763538] EXT4-fs (nvme0n1p3): Remounting filesystem read-only
[95469.763541] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: IO failure
[95469.763543] EXT4-fs (nvme0n1p3): previous I/O error to superblock detected
[95469.763544] Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write
[95469.763546] EXT4-fs error (device nvme0n1p3) in ext4_dirty_inode:5945: IO failure
[95469.763548] EXT4-fs (nvme0n1p3): previous I/O error to superblock detected
[95469.763549] Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write
[95469.835805] EXT4-fs (nvme0n1p3): ext4_writepages: jbd2_start: 9223372036854775806 pages, ino 25579170; err -30
[95469.836523] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: Journal has aborted
[95469.836535] EXT4-fs (nvme0n1p3): previous I/O error to superblock detected
[95469.837801] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: Journal has aborted
[95469.842400] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: Journal has aborted
[95469.907749] PM: suspend exit
There seem to be some clear red flags there but how do I go about resolving these errors?
linux filesystems suspend
edited Aug 21 at 19:13
sourcejedi
20.1k42886
asked Aug 21 at 17:26
M. Berk
1011
I'm running Ubuntu 18.04 on a Dell XPS 13 (9370). Recently my main file system has been turning read-only when I wake my laptop up from suspend (i.e. open the lid).
Relevant output from dmesg:
[95469.731682] OOM killer enabled.
[95469.731684] Restarting tasks ... done.
[95469.741792] [drm] RC6 on
[95469.763521] EXT4-fs error (device nvme0n1p3): __ext4_get_inode_loc:4618: inode #3408659: block 13631569: comm Xwayland: unable to read itable block
[95469.763529] Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write
[95469.763531] Aborting journal on device nvme0n1p3-8.
[95469.763535] Buffer I/O error on dev nvme0n1p3, logical block 57180160, lost sync page write
[95469.763536] JBD2: Error -5 detected when updating journal superblock for nvme0n1p3-8.
[95469.763538] EXT4-fs (nvme0n1p3): Remounting filesystem read-only
[95469.763541] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: IO failure
[95469.763543] EXT4-fs (nvme0n1p3): previous I/O error to superblock detected
[95469.763544] Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write
[95469.763546] EXT4-fs error (device nvme0n1p3) in ext4_dirty_inode:5945: IO failure
[95469.763548] EXT4-fs (nvme0n1p3): previous I/O error to superblock detected
[95469.763549] Buffer I/O error on dev nvme0n1p3, logical block 0, lost sync page write
[95469.835805] EXT4-fs (nvme0n1p3): ext4_writepages: jbd2_start: 9223372036854775806 pages, ino 25579170; err -30
[95469.836523] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: Journal has aborted
[95469.836535] EXT4-fs (nvme0n1p3): previous I/O error to superblock detected
[95469.837801] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: Journal has aborted
[95469.842400] EXT4-fs error (device nvme0n1p3) in ext4_reserve_inode_write:5761: Journal has aborted
[95469.907749] PM: suspend exit
There seem to be some clear red flags there but how do I go about resolving these errors?
linux filesystems suspend
linux filesystems suspend
edited Aug 21 at 19:13
sourcejedi
20.1k42886
asked Aug 21 at 17:26
M. Berk
1011
edited Aug 21 at 19:13
sourcejedi
20.1k42886
asked Aug 21 at 17:26
M. Berk
1011
edited Aug 21 at 19:13
sourcejedi
20.1k42886
edited Aug 21 at 19:13
sourcejedi
20.1k42886
edited Aug 21 at 19:13
sourcejedi
20.1k42886
20.1k42886
asked Aug 21 at 17:26
M. Berk
1011
asked Aug 21 at 17:26
M. Berk
1011
asked Aug 21 at 17:26
M. Berk
1011
1011
You might want to try a quick self-check withsmartctl -H /dev/nvme0. And there might be something insmartctl -l error /dev/nvme0. smartctl supports NVMe, although the support might still be experimental.
– sourcejedi
Aug 21 at 19:20
Some obvious search terms found 0 bugs in the Ubuntu tracker. bugs.launchpad.net/ubuntu/bionic/+source/… You could try reporting there (make sure to read the guidelines about required information). Especially if you found a kernel version that doesn't have the problem.
– sourcejedi
Aug 21 at 19:31
You should try seeing if one your older kernel updates avoids the problem (kernel versions in GRUB boot menu). I think, if it is a kernel regression within 18.04, it is a regression within the Ubuntu 4.15.0-x.y series. Ubuntu is on its own here; it's not related to any of the official linux-stable branches.
– sourcejedi
Aug 21 at 19:33
add a comment |Â
You might want to try a quick self-check withsmartctl -H /dev/nvme0. And there might be something insmartctl -l error /dev/nvme0. smartctl supports NVMe, although the support might still be experimental.
– sourcejedi
Aug 21 at 19:20
Some obvious search terms found 0 bugs in the Ubuntu tracker. bugs.launchpad.net/ubuntu/bionic/+source/… You could try reporting there (make sure to read the guidelines about required information). Especially if you found a kernel version that doesn't have the problem.
– sourcejedi
Aug 21 at 19:31
You should try seeing if one your older kernel updates avoids the problem (kernel versions in GRUB boot menu). I think, if it is a kernel regression within 18.04, it is a regression within the Ubuntu 4.15.0-x.y series. Ubuntu is on its own here; it's not related to any of the official linux-stable branches.
– sourcejedi
Aug 21 at 19:33
You might want to try a quick self-check with
smartctl -H /dev/nvme0. And there might be something in smartctl -l error /dev/nvme0. smartctl supports NVMe, although the support might still be experimental.– sourcejedi
Aug 21 at 19:20
You might want to try a quick self-check with
smartctl -H /dev/nvme0. And there might be something in smartctl -l error /dev/nvme0. smartctl supports NVMe, although the support might still be experimental.– sourcejedi
Aug 21 at 19:20
Some obvious search terms found 0 bugs in the Ubuntu tracker. bugs.launchpad.net/ubuntu/bionic/+source/… You could try reporting there (make sure to read the guidelines about required information). Especially if you found a kernel version that doesn't have the problem.
– sourcejedi
Aug 21 at 19:31
Some obvious search terms found 0 bugs in the Ubuntu tracker. bugs.launchpad.net/ubuntu/bionic/+source/… You could try reporting there (make sure to read the guidelines about required information). Especially if you found a kernel version that doesn't have the problem.
– sourcejedi
Aug 21 at 19:31
You should try seeing if one your older kernel updates avoids the problem (kernel versions in GRUB boot menu). I think, if it is a kernel regression within 18.04, it is a regression within the Ubuntu 4.15.0-x.y series. Ubuntu is on its own here; it's not related to any of the official linux-stable branches.
– sourcejedi
Aug 21 at 19:33
You should try seeing if one your older kernel updates avoids the problem (kernel versions in GRUB boot menu). I think, if it is a kernel regression within 18.04, it is a regression within the Ubuntu 4.15.0-x.y series. Ubuntu is on its own here; it's not related to any of the official linux-stable branches.
– sourcejedi
Aug 21 at 19:33
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f463925%2ffile-system-turns-read-only-after-waking-dell-xps-9370-laptop-up-from-suspend%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
You might want to try a quick self-check with
smartctl -H /dev/nvme0. And there might be something insmartctl -l error /dev/nvme0. smartctl supports NVMe, although the support might still be experimental.– sourcejedi
Aug 21 at 19:20
Some obvious search terms found 0 bugs in the Ubuntu tracker. bugs.launchpad.net/ubuntu/bionic/+source/… You could try reporting there (make sure to read the guidelines about required information). Especially if you found a kernel version that doesn't have the problem.
– sourcejedi
Aug 21 at 19:31
You should try seeing if one your older kernel updates avoids the problem (kernel versions in GRUB boot menu). I think, if it is a kernel regression within 18.04, it is a regression within the Ubuntu 4.15.0-x.y series. Ubuntu is on its own here; it's not related to any of the official linux-stable branches.
– sourcejedi
Aug 21 at 19:33