Bump:
PC: Lenovo Legion Y520-15IKBN
SSD: Samsung SM951 M.2 PCIe SSD Drive (MZ-HPV256)
---
lshw relevant parts:
computer
description: Notebook
product: 80WK (LENOVO_MT_80WK_BU_idea_FM_Lenovo Y520-15IKBN)
vendor: LENOVO
version: Lenovo Y520-15IKBN
I just want to say that after 2 years I remembered I had an SSD with
different brand tham Samsung, a Kingston one. I installed it on my razer
and it worked perfectly for days, I did several SSD stress tests and no
errors.
The error is defintely with Samsung AND linux. And it's not a faulty SSD
I thought I could help in some way with more information. By the way,
I've found the solution and my SSD works fine right now. You may want to
take a lookt at https://bugzilla.kernel.org/show_bug.cgi?id=201685.
Comment #294 (https://bugzilla.kernel.org/show_bug.cgi?id=201685#c294),
in particular,
Ramon,
Please file a separate bug since it's platform specific.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this
I also had this problem of it working for a year, then I update it and
it stops working. Then I roll back the kernel and it won't work again
Enviado via ProtonMail móvel
Mensagem Original
Ativo 7 de mar de 2020 10:17, Ramon Fontes escreveu:
> I have a Dell Inspiron 14 5000
I have a Dell Inspiron 14 5000 Series-5480. The most strange thing is
that I bought my laptop about 1 year ago and I've installed Ubuntu
18.04.1 with kernel 4.15.0-65-xxx (default installation) and everything
worked as expected. However, the same problem happened with any other
kernel version
Ramon, which hardware is yours? Razer?
Enviado via ProtonMail móvel
Mensagem Original
Ativo 6 de mar de 2020 16:34, Ramon Fontes escreveu:
> BTW, pcie_aspm=off and nvme_core.default_ps_max_latency_us=5500 didn't
> work.
>
> --
> You received this bug notification because you
BTW, pcie_aspm=off and nvme_core.default_ps_max_latency_us=5500 didn't
work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage
Hello all!
I'm experiencing the same problem with an adata SU800NS38. My SSD works
fine with the 4.17.0-041700-generic kernel version but unfortunately
this is the only kernel version it works perfectly. In addition to try
other kernel versions such as 4.x, I also tried 5.0 - 5.5. The disk
No I have a laptop from a XMG, it is a German brand.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
Juan, which hardware you're on? Razer?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
an update on this:
it was actually pcie_aspm=off what helped to solve the problem.
I think the problem is related to the power management of PCIe ports.
Without pcie_aspm=off I started seeing errors like the following ones:
- [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on
Hi Kai-Heng Feng, please note that after I installed Qubes, I never ever
had the problem again. It may be useful in the debug process, and maybe
the way Xen, PCIe and Linux work together in Qubes can give a hint on
what's happening. Thank you for all your help to this day.
--
You received this
Can you please attach `sudo nvme id-ctrl /dev/nvme0`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go
Hi, yes I also am trying to install onto the razer blade stealth like a
lot of the other people above which have the SAMSUNG MZVLB256HAHQ-0
nvme ssd. Getting the I/O Error and have tried most of the fixes
mentioned above, but no luck, and I would rather continue using Windows
instead of Qubes.
Craigums Carlonious,
Is the system exact the same?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
It's 2020, is there still no solution to this problem? Getting this
error with ubuntu 18 LTS and 19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
Thank Lucas.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
non nvme SSDs are pretty slow, like 8 times slower. Stick with NVME and
if nothing works install Qubes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck
Thank you. My SSD is LITEON CA3-8D512, not Samsung. So, would i buy
another type of SSD? non nvme?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
The other 2 good brands I know are Corsair and WD Black. Don't buy
Samsung, the majority of people with this problem have Samsung
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Thank Lucas, i think i will buy another type of SSD. Do you have any
suggestion?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage
Hu trong lu. I indeed bought a new SSD because I thought mine was
faulty. However I bought one of the same brand (Samsung). I didn't have
the idea of buying another brand. Anyways, the brand new SSD also has
the problem.
For my case it definitely is not a hardware problem. With Linux the
problem
Hi Lucas, do you have tried with new SSD? I don't think this is the hw issue.
My SSD Power Cycles is only 807. Eventually, if not having any other solution,
i think i will buy new SSD, do you know which type of SSD would work properly
with linux?
Smartctl output:
sudo smartctl -t long -a
Hi trong luu, I didn't test it, but I think that it depends on the way
VMware virtualizes access to the disk. There may be multiple ways, one
of which will work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Lucas, is it ok if installing window and using ubuntu in VMware?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about
After running cat /sys/module/nvme_core/parameters/default_ps_max_latency_us
command and output is 0.
sudo nvme get-feature -f 0x0c -H /dev/nvme0n1p2
get-feature:0xc (Autonomous Power State Transition), Current value:
Autonomous Power State Transition Enable (APSTE): Disabled
Hi
try:
cat /sys/module/nvme_core/parameters/default_ps_max_latency_us
sudo nvme get-feature -f 0x0c -H /dev/nvme0
please read carefully the link provided. the info is there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Juan, i have tried with your suggest many time but the problem still
happens. I also tried with nvme_core.default_ps_max_latency_us=0 but no hope.
I'm not sure the APST be disabled. How to check APST status when system booted?
For anyone struggling with this hideous bug, try the following:
add "nvme_core.default_ps_max_latency_us=250" in /etc/default/grub, for
example:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pcie_aspm=off
nvme_core.default_ps_max_latency_us=250"
then run "update-grub"
My laptop has been running
I think other SSD type is last option. But, i really want find out root
cause of the problem. As my understanding, system booted up with Opts:
errors=remount-ro. Then something went wrong, system switched to ro mode
to protect file system. Do you have checked system log, have any
abnormal log?
Hi trong luu, for me the error happened every day, which is why I ended
up using Qubes. It's the only way that I could find except for Windows
You can try older kernels but it didn't work for me. Remember that
downloading older ubuntus will still give you a recent kernel, you have
to downgrade by
The error still happens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
I switched to recovery mode and run: mount -o remount,rw /. The problem
no longer appears, it seem be fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption
Thank Lucas,
It just happened to my laptop. I will try find out the solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage
Hi tronglx,
I didn't try Arch but I THINK I tried Manjaro which is based on it. If I
did it didn't work. I remember trying lots of linux and all of them
failed.
Qubes OS works because it doesn't use linux kernels directly because it
uses Xen microkernel, so somehow it excludes the bug. You can
Thank Lucas, do you have tried with arch linux? Qubes OS is very strange
with me. I'm developer and os community is very importance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Hi tronglx, the only way I found was to install Qubes OS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go
Hi lucas, i have the same problem. My laptop is matebook x pro 2018 and
nvme LITEON CA3-8D512. My working is on linux and it is an unpleasant
experience. Currently, when issue occurs, i power off/on my laptop (one
times or more) and it can work normally in a few hours. Do you have any
another
Hi Juan, what computer you are in?
If you really want to use your computer with linux the only way that it
solved for me was to use Qubes OS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
I have exactly the same drive:
/dev/nvme0n1 S444NY0K600040 SAMSUNG MZVLB256HAHQ-0
1 81.09 GB / 256.06 GB512 B + 0 B EXD7101Q
and exactly the same problem.
I filled a bug before deactivating AER (pci=noaer)
Hi, I didn't find the root of the problem, **BUT**...
Using Qubes OS I was able to run for more than 7 days without any
problems! It normally would occur in the first hour of usage.
I guess Qubes's Xen drivers proxy the pcie requests and therefore the
failing NVME/PCIE drivers aren't used. So it
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage
I've been using NVMe M.2 Samsung Pro 960 for 18 months and never had a problem.
Ubuntu 16.04.6 LTS, Kernel 4.14.114 LTS, Skylake 6700HQ, nVidia 970m
UEFI, GPT, AHCI (Intel Raid off), Secure Boot off
`/etc/fstab`:
UUID=b40b3925-70ef-447f-923e-1b05467c00e7 / ext4
Disable ASPM. Only compile tested.
** Patch added: "lp1746340.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5273733/+files/lp1746340.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Kai-Heng Feng, I just installed kernel 5.1.1 and the error still
happens
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage
I tried the Ubuntu 19.04 installer and I couldn't even install it
because of IO errors. Does the installer of Ubuntu 19.04 uses the new
kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Lucas,
Do you still have this issue on mainline kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go
Hi,
a little update from my side: It seems that faulty memory was the reason
for the data corruptions in my case. I have replaced the memory module
and everything seems to work fine now. I was quite surprised though that
the memory was defective since I did test it carefully for many hours
with
Hi Kai-Heng Feng, do you have any news on this problem? It'd be great to
know.
Than you so much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
Just tried Ubuntu 19 today and the problem persists (can't even install
ubuntu because it gives io error)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck
My issue has been resolved by upgrading the firmware of my SSD from
SBFKB1C2 to SBFKB1C3.
https://askubuntu.com/questions/1107053/ubutnu-18-04-ssd-sometimes-
freeze-for-seconds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I too am having an SSD corruption issue with Ubuntu 18.04, same exact
symptoms. I have a Kingston 480gb SSD, not nvme, connected over SATA. My
PC is a desktop, I have attached the output of lspci -vvnn. I have to do
manual fsck every 1.5 weeks or so. When I am using my PC, it will freeze
up
Here is the iotop log I mentioned above (attached)
** Attachment added: "iotop.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5241595/+files/iotop.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Any news on this problem? Im still having it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
lspci -vvnn:
04:00.0 Non-Volatile memory controller [0108]: Sandisk Corp WD Black NVMe SSD
[15b7:5001] (prog-if 02 [NVM Express])
Subsystem: Marvell Technology Group Ltd. WD Black NVMe SSD [1b4b:1093]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping-
I should probably mention that while it is installed in my laptop it is
not currently being used as I had to revert to using an ordinary HDD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
lshw output:
*-storage
description: Non-Volatile memory controller
product: Sandisk Corp
vendor: Sandisk Corp
physical id: 0
bus info: pci@:04:00.0
version: 00
width: 64 bits
Here is the output of lspci -vvnn on my computer. It's from the 256GB version
of the samsung NVMe.
On my systems I've never had any corruption problems, even moving large (60GB+)
VM files and installing OS on ext4 multiple times. Currently running stock LM
19. Hope this helps.
** Attachment
Then I'm puzzled. I'll retest later with WD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
The kernel doesn't do anything special for 144d:a808, it's for
144d:a804.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications
My Samsung is indeed [144d:a808]. I'll check WD later on - it's not connected
at this time.
I was not able to reproduce this bug using Clear Linux current kernel
(4.18.16-645).
I checked kernel https://people.canonical.com/~khfeng/lp1785715/ with no
nvme-core.default_ps_max_latency_us=
My Samsung is indeed [144d:a808]. I'll check WD later on - it's not connected
at this time.
I was not able to reproduce this bug using Clear Linux current kernel
(4.18.16-645).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If you use Samsung (144d:a804) or Sk Hynix (1c5c:1285), please try
kernel in [1].
[1] https://people.canonical.com/~khfeng/lp1785715/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
What's the PCI ID for EVO 970 and WD Black?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
Attachment contains error from dmesg output. For me reproduction steps
are: write large (>10G) amount of data to NVMe ssd.
** Attachment added: "nvme-heavy-write-error.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+attachment/5204874/+files/nvme-heavy-write-error.txt
--
I have the WD Black 256 Gb drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
I can confirm that bug with two different NVMe drivers - Samsung EVO970
and WD Black in 4.18.0-10-generic and in 4.15.0-20-generic kernels.
H270 Intel chipset on the motherboard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I may try that. Are we sure it's a kernel bug though? I can't remember
having this problem when I used Solus OS for a while. But I may not have
used for long enough since I discovered it didn't support Jack2 and was
pretty much unusable to me.
--
You received this bug notification because you
Ok Christian, thanks for the info. You can try the kernel for now, and I
also read that using ubuntu with brtfs system instead of ext4 also
solves the problem, you could try
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Lucas! Thanks for the reply. No, I had no problems during
installation. The computer just shuts down at random intervals to a
black screen with all kinds of EXT4-fs errors and reports that the file
system is read only. Often the disk isn't even recognized at reboot, so
I have to boot into a
Hi Ole Christian. First, did you have any problems in the ubuntu
installation? In mine I had to try to install several times until it
installed without any disk errors.
Also, you can try this kernel https://people.canonical.com/~khfeng/pm961
-disable-aspm/ with this kernel parameter "nvme-
I have this bug (MSI laptop, Ubuntu Studio 18.04) and it's getting quite
annoying to be honest. If there's anything I can do to help remedy the
situation within reasonable time (I'm about to reinstall) then let me
know.
--
You received this bug notification because you are a member of Ubuntu
I have tried two things:
(1) Fresh install, Ubuntu 18.04 (about ten days ago), ext4. No errors
during the installation. However, when installing stuff via apt
afterwards (or upgrading), I got many errors along the lines described
above (e.g., "compressed data is corrupt... unexpected end of file
Fabian, did you have any problems installing ubuntu? Mine would give
disk errors about 7/10 times I tried to install. I had to try many times
until no error appeared.
I'd like to try btrfs but I don't have the time to do it right now. I
also had problems with apt, but when upgrading the system.
To add to my previous comment, I've been running ext4 all the time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about
I have had the same issues with Ubuntu 18.04 and a Samsung MZ-V7E1T0
1000GB M.2 PCI Express 3.0 and the default installation (ext4): Plenty
of errors, especially when upgrading/installing packages via apt.
I have reinstalled the whole system. Instead of the standard journaling
file system (ext4),
Stumbled onto this bug from somewhere else, and noticed that it seems I
have the same samsung SSD drive SM961/PM961 (Same output on lspci --vvnn
regarding the NVMe as Lucas posted,). However, for me it has worked
without any problems on stock ubuntu 18.04 / mint / kubuntu
installations. Perhaps it
I'm also running the ASPM patch and haven't had problems for the last
month or so. Any idea when this will get merged?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD
Hello Lucas, thank you for response. Yes, badly setted kernel parameters
can cause very serious problems. Additionally, I can comfirm, that
problem is not bounded only on Samsung NVME SSD, but It occurs on Intel
SSD-6 series as well. It looks like, that problem is in ASPM SSD Driver
- kernel
It's worth saying that the ASPM patch + 1500 kernel parameter worked for
me for over a month without giving me one single error. After update to
18.04 now I see the error every 2 or 3 days. Actually, in the middle of
the update process to 18.04 it gave the error right on the initramfs
update,
Hello Lucas, thank you for response. Yes, badly setted kernel parameters
can cause very serious problems. Additionally, I can comfirm, that
problem is not bounded only on Samsung NVME SSD, but It occurs on Intel
SSD-6 series as well. It looks like, that problem is in ASPM SSD Driver
- kernel
Hi hariprasad. If possible, you could try our patched kernel which
disables ASPM: https://people.canonical.com/~khfeng/pm961-disable-
aspm/. It worked for me but only when I added the nvme-
core.default_ps_max_latency_us=1500 kernel parameter. Maybe you can try
some day. We're still investigating
Hello, my Ubuntu Linux was 8-9 months out of order v. 17.10, and later
18.04. I did many installations and tests, changed SSD M.2 four times
(recognized reclamation), changed the whole NUC7i7BNH (recognized
reclamation). Log Issue on Intel. Finally I installed Fedora 28. and
NVME M.2 SSD is in
I also have the same issue on a Razer Blade 2017 - 7500U model. My
system has the exact same drive in it. I have just installed the
4.18.0-3 kernel linked above and will post here if I run into the issue
again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Could you send me the patch (and should I use the aspm patch together
with it?)
Another information that you might find useful: I've been using for 30
days without any problems on the main machine (only one incident inside
the virtual machine), so today I decided to finally conclude all the
Lucas,
I've found that the PCIe common clock may be the culprit here.
Please try the kernel [1].
[1] https://people.canonical.com/~khfeng/quirk-no-commclk/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi hariprasad. nvme-core.default_ps_max_latency_us=1500 and ASPM
disabling by kernel patching worked for me, at least for the main
machine (my virtual machines inside this main machine still give the
error after some time). I've been using the patch for almost a month
without incidents. I had the
There is an issue, wich can be our problem. it looks like, that
workaround is to disable TRIM. https://blog.algolia.com/when-solid-
state-drives-are-not-that-solid/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Additionally, i can comfirm, that problem is not bounded only on Samsung
NVME SSD, but It occurs on Intel SSD as well. It looks like, that
problem is a SSD Driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm. I have the same problems since 10.11. 2017. Some hours system
works and suddenly there are serious SSD problems. I changed SSD rour times
(reclamation) and I did recamation odf a new Computer one times.
HW: Intel NUC7i7BNH (Intel i7), Samsung EVO 960 M.2 NVMe, OPM Crucial 16GB.
Can you attach the error? Maybe use something else like virtual box to
see if KVM is the culprit?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
I've tested the new kernel with this parameter for 10 days and the error
didn't happen, which is a record. So I decided to open a VM yesterday
and it handled good for like 12 hours, they I went to sleep and grabbed
the computer again and the error had happened inside and outside the VM.
I don't
No the user uses an XPS 9560. I think remove io_queue_depth parameter
should be safe.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage
Should I take nvme.io_queue_depth=64 out? I didn't experience the
problem again yet, just right after the first boot with the new kernel.
However I still experience the error inside the VMs.
I'm adding nvme-core.default_ps_max_latency_us=1500 now.
Is this an user of Razer Blade Stealth? Would be
So the ASPM is indeed disabled:
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
Can yo try disabling the deepest power state under this kernel? i.e. use
"nvme-core.default_ps_max_latency_us=1500".
--
You received this bug notification because you are a member of Ubuntu
FWIW there's another user says that disabling ASPM fixes this issue for
him.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage
I just compiled the kernel and it presented the error just minutes after
the first boot.
A reminder: my kernel parameters are still like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash button.lid_init_state=open
nvme.io_queue_depth=64"
Here's the output you wanted:
00:00.0 Host bridge
No, just use the patch in #120.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746340
Title:
Samsung SSD corruption (fsck needed)
To manage notifications about this bug go to:
1 - 100 of 206 matches
Mail list logo
