Samsung SSD corruption (fsck needed)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
Ubuntu 4.13.0-
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_
lz@lz:/var/log$ dmesg
[62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_
[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_
[62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_
[62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_
[62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_
[62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_
[62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_
[62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_
[62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_
[63285.618078] audit: type=1400 audit(151719556
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:/
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:/
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/
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=
ProcVersionSign
RelatedPackageV
linux-
linux-
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:
dmi.product.family: 1A586752
dmi.product.name: Blade Stealth
dmi.product.
dmi.sys.vendor: Razer
Changed in linux (Ubuntu): | |
assignee: | nobody → Kai-Heng Feng (kaihengfeng) |
tags: | added: patch |
Changed in linux (Ubuntu): | |
assignee: | Kai-Heng Feng (kaihengfeng) → nobody |
tags: | added: cscc |
Would it be possible for you to test the latest upstream kernel? Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Please test the latest v4.15 kernel[0].
If this bug is fixed in the mainline kernel, please add the following tag 'kernel- fixed-upstream' .
If the mainline kernel does not fix this bug, please add the tag: 'kernel- bug-exists- upstream' .
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
Thanks in advance.
[0] http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v4.15