I've hit this "bug". I've a nice Clevo ODM based laptop and luckily I
have two nvme drives in it so it's not a show-stopper for me but obv.
it's a concern. I have an Intel one which is the boot drive and a
Samsung one which is the data drive. I have a dual-boot setup. So two
data points to note. The Intel nvme works in both Windows and Linux. The
Samsung works in Windows, but not in Linux. When I say that it doesn't
work in Linux I should say that the system brings the drive up, I can
mount it read-write, everything looks good but as soon as I try and
write files to it it craps out with nothing written:
[369.798910] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x10
[369.798916] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[369.798918] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[369.870912] nvme :01:00.0: enabling device ( -> 0002)
[369.871064] nvme nvme0: Removing after probe failure status: -19
[369.890931] nvme0n1: detected capacity change from 1953525168 to 0
Output of `dmesg` attached.
** Attachment added: "omg_dmesg_b0rked.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5641705/+files/omg_dmesg_b0rked.txt
--
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:
Confirmed
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/
