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 1746340
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.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
Status in linux package in Ubuntu:
Incomplete
Bug 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
