Comment 23 for bug 1746340
Revision history for this message
| Kai-Heng Feng (kaihengfeng) wrote Re: [Bug 1746340] Re: Samsung SSD corruption (fsck needed) | #23 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Kai-Heng
> On 31 Jan 2018, at 1:38 PM, Lucas Zanella <email address hidden> wrote:
>
> Thank you for your answer. I'm desperated. I just installed debian
> therefore I'm not going to able to do it right now, but I have output
> from the last time I was using Ubuntu.
>
> I tried nvme_core.
> Then I've put it to 0, which didn't work too. Well, with 0 it didn't
> generate errors while using, but while trying to update my machine,
> which always happens too, so I don't know anymore. I remember seeing
> ATSP Disabled at the output, but the error always happens when I try to
> update my software…
I’d like to see the output of `sudo nvme get-feature -f 0x0c -H /dev/nvme0` when you use nvme_core.
>
> Shouldn't this bug be already fixed? Or not in my kernel? I could pay to
> get to the bottom of this, because I need my computer so much right now
> and this bug is happening every day and I can't continue my work!
This is more likely to a low level NVMe/PCIe issue. If possible, please try to upgrade the firmware for the NVMe.
>
> The last kernel I had on ubuntu was 4.13.0-26-generic, now I'm on debian
> and I have 4.9.0-4.
You’ll get hit by this issue (again) once next Debian release uses newer kernel.
>
> sudo nvme list
> Node SN Model Namespace Usage Format FW Rev
> ---------------- -------
> /dev/nvme0n1 S33UNX0J324060 SAMSUNG MZVLW512HMJP-00000 1 25,30 GB / 512,11 GB 512 B + 0 B CXY7501Q
>
> NVME Identify Controller:
> vid : 0x144d
> ssvid : 0x144d
> sn : S33UNX0J324060
> mn : SAMSUNG MZVLW512HMJP-00000
> fr : CXY7501Q
> rab : 2
> ieee : 002538
> cmic : 0
> mdts : 0
> cntlid : 2
> ver : 10200
> rtd3r : 186a0
> rtd3e : 4c4b40
> oaes : 0
> oacs : 0x17
> acl : 7
> aerl : 3
> frmw : 0x16
> lpa : 0x3
> elpe : 63
> npss : 4
> avscc : 0x1
> apsta : 0x1
> wctemp : 341
> cctemp : 344
> mtfa : 0
> hmpre : 0
> hmmin : 0
> tnvmcap : 512110190592
> unvmcap : 0
> rpmbs : 0
> sqes : 0x66
> cqes : 0x44
> nn : 1
> oncs : 0x1f
> fuses : 0
> fna : 0
> vwc : 0x1
> awun : 255
> awupf : 0
> nvscc : 1
> acwu : 0
> sgls : 0
> subnqn :
> ps 0 : mp:7.60W operational enlat:0 exlat:0 rrt:0 rrl:0
> rwt:0 rwl:0 idle_power:- active_power:-
> ps 1 : mp:6.00W operational enlat:0 exlat:0 rrt:1 rrl:1
> rwt:1 rwl:1 idle_power:- active_power:-
> ps 2 : mp:5.10W operational enlat:0 exlat:0 rrt:2 rrl:2
> rwt:2 rwl:2 idle_power:- active_power:-
> ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
> rwt:3 rwl:3 idle_power:- active_power:-
> ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
> rwt:4 rwl:4 idle_power:- active_power:-
>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https:/
>
> Title:
> Samsung SSD corruption (fsck needed)
>
> Status in linux package in Ubuntu:
> Confirmed
>
> 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:/
> different nvme_core.
> 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:/
> corruption-
>
> 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=
> ProcVersionSign
> RelatedPackageV
> linux-restricte
> linux-backports
> 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
>
> To manage notifications about this bug go to:
> https:/