| 2018-01-30 20:18:27 |
Lucas Zanella |
bug |
|
|
added bug |
| 2018-01-30 20:29:13 |
Joseph Salisbury |
linux (Ubuntu): importance |
Undecided |
High |
|
| 2018-01-30 20:29:20 |
Joseph Salisbury |
tags |
blade corruption razer samsung ssd stealth |
blade corruption kernel-da-key razer samsung ssd stealth |
|
| 2018-01-30 20:30:04 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2018-01-30 23:20:47 |
Lucas Zanella |
tags |
blade corruption kernel-da-key razer samsung ssd stealth |
apport-collected artful blade corruption kernel-da-key razer samsung ssd stealth wayland-session |
|
| 2018-01-30 23:20:48 |
Lucas Zanella |
description |
Ubuntu 4.13.0-21.24-generic 4.13.13
I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though.
I notice the error when I try to save something on disk and it says me that the disk is in read-only mode:
lz@lz:/var/log$ touch something
touch: cannot touch 'something': Read-only file system
lz@lz:/var/log$ cat syslog
Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
lz@lz:/var/log$ dmesg
[62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.377374] Aborting journal on device nvme0n1p2-8.
[62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
[62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin"
Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then.
Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates.
I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke?
I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu.
My Samsung 512gb SSD is:
SAMSUNG MZVLW512HMJP-00000, FW REV: CXY7501Q
on a Razer Blade Stealth.
I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk-corruption-fsck-needed-probably-samsung-ssd-bug-afte
Please help me, as I need this computer to work on lots of things :c |
Ubuntu 4.13.0-21.24-generic 4.13.13
I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though.
I notice the error when I try to save something on disk and it says me that the disk is in read-only mode:
lz@lz:/var/log$ touch something
touch: cannot touch 'something': Read-only file system
lz@lz:/var/log$ cat syslog
Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
lz@lz:/var/log$ dmesg
[62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.377374] Aborting journal on device nvme0n1p2-8.
[62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
[62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin"
Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then.
Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates.
I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke?
I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu.
My Samsung 512gb SSD is:
SAMSUNG MZVLW512HMJP-00000, FW REV: CXY7501Q
on a Razer Blade Stealth.
I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk-corruption-fsck-needed-probably-samsung-ssd-bug-afte
Please help me, as I need this computer to work on lots of things :c
---
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: lz 1088 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
InstallationDate: Installed on 2018-01-30 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Razer Blade Stealth
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=0ca062da-7e8f-425a-88b1-1f784fb40346 ro quiet splash button.lid_init_state=open nvme_core.default_ps_max_latency_us=0
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
RelatedPackageVersions:
linux-restricted-modules-4.13.0-21-generic N/A
linux-backports-modules-4.13.0-21-generic N/A
linux-firmware 1.169.1
Tags: wayland-session artful
Uname: Linux 4.13.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/12/2017
dmi.bios.vendor: Razer
dmi.bios.version: 6.00
dmi.board.name: Razer
dmi.board.vendor: Razer
dmi.chassis.type: 9
dmi.chassis.vendor: Razer
dmi.modalias: dmi:bvnRazer:bvr6.00:bd01/12/2017:svnRazer:pnBladeStealth:pvr2.04:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
dmi.product.family: 1A586752
dmi.product.name: Blade Stealth
dmi.product.version: 2.04
dmi.sys.vendor: Razer |
|
| 2018-01-30 23:20:50 |
Lucas Zanella |
attachment added |
|
AlsaInfo.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045881/+files/AlsaInfo.txt |
|
| 2018-01-30 23:20:51 |
Lucas Zanella |
attachment added |
|
CRDA.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045882/+files/CRDA.txt |
|
| 2018-01-30 23:20:54 |
Lucas Zanella |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045883/+files/CurrentDmesg.txt |
|
| 2018-01-30 23:20:55 |
Lucas Zanella |
attachment added |
|
IwConfig.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045884/+files/IwConfig.txt |
|
| 2018-01-30 23:20:57 |
Lucas Zanella |
attachment added |
|
JournalErrors.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045885/+files/JournalErrors.txt |
|
| 2018-01-30 23:20:58 |
Lucas Zanella |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045886/+files/Lspci.txt |
|
| 2018-01-30 23:20:59 |
Lucas Zanella |
attachment added |
|
Lsusb.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045887/+files/Lsusb.txt |
|
| 2018-01-30 23:21:01 |
Lucas Zanella |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045888/+files/ProcCpuinfo.txt |
|
| 2018-01-30 23:21:02 |
Lucas Zanella |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045889/+files/ProcCpuinfoMinimal.txt |
|
| 2018-01-30 23:21:04 |
Lucas Zanella |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045890/+files/ProcEnviron.txt |
|
| 2018-01-30 23:21:06 |
Lucas Zanella |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045891/+files/ProcInterrupts.txt |
|
| 2018-01-30 23:21:07 |
Lucas Zanella |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045892/+files/ProcModules.txt |
|
| 2018-01-30 23:21:09 |
Lucas Zanella |
attachment added |
|
PulseList.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045893/+files/PulseList.txt |
|
| 2018-01-30 23:21:11 |
Lucas Zanella |
attachment added |
|
RfKill.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045894/+files/RfKill.txt |
|
| 2018-01-30 23:21:14 |
Lucas Zanella |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045895/+files/UdevDb.txt |
|
| 2018-01-30 23:21:16 |
Lucas Zanella |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/1746340/+attachment/5045896/+files/WifiSyslog.txt |
|
| 2018-01-30 23:22:14 |
Lucas Zanella |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2018-02-15 15:26:20 |
Kai-Heng Feng |
linux (Ubuntu): assignee |
|
Kai-Heng Feng (kaihengfeng) |
|
| 2018-06-15 09:02:47 |
Kai-Heng Feng |
attachment added |
|
0001-ASPM-quirk-for-SM-PM-EVO-961.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5152931/+files/0001-ASPM-quirk-for-SM-PM-EVO-961.patch |
|
| 2018-06-15 12:25:43 |
Ubuntu Foundations Team Bug Bot |
tags |
apport-collected artful blade corruption kernel-da-key razer samsung ssd stealth wayland-session |
apport-collected artful blade corruption kernel-da-key patch razer samsung ssd stealth wayland-session |
|
| 2018-06-15 12:25:44 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Joseph Salisbury |
| 2018-09-17 08:27:40 |
Andreas Gnau |
bug |
|
|
added subscriber Andreas Gnau |
| 2018-09-28 19:29:24 |
Fabian |
bug |
|
|
added subscriber Fabian |
| 2018-10-02 17:59:02 |
Janne Peltonen |
bug |
|
|
added subscriber Janne Peltonen |
| 2018-10-24 12:25:26 |
pleban |
attachment added |
|
nvme-heavy-write-error.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5204874/+files/nvme-heavy-write-error.txt |
|
| 2018-10-25 11:02:44 |
Janne Peltonen |
attachment added |
|
lspci -vvnn output https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5205324/+files/debug.txt |
|
| 2018-12-11 18:50:37 |
Alexnader Johansson |
bug |
|
|
added subscriber Alexnader Johansson |
| 2019-02-23 04:18:51 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Terry Rudd |
| 2019-02-25 16:19:30 |
Richard Grieves |
attachment added |
|
lspci.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5241594/+files/lspci.txt |
|
| 2019-02-25 16:20:06 |
Richard Grieves |
attachment added |
|
iotop.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5241595/+files/iotop.log |
|
| 2019-02-25 16:20:45 |
Richard Grieves |
bug |
|
|
added subscriber Richard Grieves |
| 2019-02-27 21:28:12 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2019-04-08 15:18:29 |
Dan Streetman |
removed subscriber Dan Streetman |
|
|
|
| 2019-06-27 06:43:28 |
Kai-Heng Feng |
attachment added |
|
lp1746340.patch https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5273733/+files/lp1746340.patch |
|
| 2019-07-17 14:55:38 |
Kai-Heng Feng |
linux (Ubuntu): assignee |
Kai-Heng Feng (kaihengfeng) |
|
|
| 2019-07-24 20:21:40 |
Brad Figg |
tags |
apport-collected artful blade corruption kernel-da-key patch razer samsung ssd stealth wayland-session |
apport-collected artful blade corruption cscc kernel-da-key patch razer samsung ssd stealth wayland-session |
|
| 2019-12-18 09:29:24 |
trong luu |
bug |
|
|
added subscriber trong luu |
| 2020-05-03 18:49:18 |
Ramon Fontes |
bug watch added |
|
https://bugzilla.kernel.org/show_bug.cgi?id=201685 |
|
| 2023-01-16 13:35:10 |
Anthony Durity |
attachment added |
|
omg_dmesg_b0rked.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5641705/+files/omg_dmesg_b0rked.txt |
|
