** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694596
Title:
LiteOn NVMe issue
To manage notifications about this bug go to:
http
I swapped my Lite-On drive for a replacement Samsung drive that Dell
sent to me. As a result, I'm unable to help any further on this bug
report. I returned the Lite-On drive to Dell for further testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
After wiping out my Ubuntu installation with Windows 10 Pro and running
the firmware upgrade, I discovered that it was an upgrade to the version
I already have (48811QD). I also tried a separate DOS firmware upgrade
program that Dell sent to me by e-mail, with the same result:
Model: CX2-8B256-Q11
Dell asked me to apply the following firmware upgrade, which fixed some
problems on Windows:
LITEONIT Solid State Drive Firmware
http://www.dell.com/support/home/ca/en/cabsdt1/Drivers/DriversDetails?driverId=CWX68
The update program, though, works only on Windows. I'm waiting to find
out from Del
I am no expert on this area, but you probably also need to check the
integrity of dm-crypt layer and lvm layer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694596
Title:
LiteOn NVMe issue
To man
I opened a Service Request yesterday with Dell regarding my Lite-On CX2
NVMe Series drive. The workstation group escalated the support ticket to
their "High Complexity or Ubuntu" group and told me they would get back
to me by tomorrow (in 24-48 hours).
The last time this happened, there were 329 d
Also, can you attach the filesystem errors? Filesystems (EXT4, XFS,
etc.) are pretty robust nowadays.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694596
Title:
LiteOn NVMe issue
To manage notifi
Can you attach the output of `sudo nvme get-feature -f 0x0c -H
/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/1694596
Title:
LiteOn NVMe issue
To manage notifications about this bug go
My system is under warranty, so I'll find out in the next week what Dell
says about the problem. I don't see any way for me to upgrade the
firmware on the device:
http://www.liteonssd.com/en/pcie-ssd/item/client-pcie-ssd/CLIENT-
CX2-SERIES.html
I'm on firmware revision 48811QD, while you're on re
Hmm, eventually I still want to backport NVMe APST support to Xenial
(4.4) kernel - the reduction on energy consumption is quite huge.
My same LiteON NVMe works flawlessly for months with APST enabled, but
with a different firmware version -
NVME Identify Controller:
vid : 0x14a4
No, the errors stopped when I reverted to the Ubuntu 16.04 GA kernel and
X server on May 31.
I have been running error-free for over two weeks with the "linux-
generic" package version 4.4.0.79.85. It appears there may be something
in Linux kernel version 4.8.0-53.56 that caused the problems, but
Have you seen this issue since last comment?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694596
Title:
LiteOn NVMe issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/
I'm adding the actual errors I saw, just for the record.
What happens is that the root file system becomes read-only due to
errors on the drive. My root file system is a logical volume on an
encrypted partition (LVM with LUKS encryption), mounted and encrypted
with the following options:
$ mount
** Summary changed:
- LiteOn NVMe APST issue
+ LiteOn NVMe issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694596
Title:
LiteOn NVMe issue
To manage notifications about this bug go to:
https:
14 matches
Mail list logo
