So a few thoughts:
- any idea if this is related to my recent upgrade? ie. new feature in [K]Ubunto 22.04?
- is this likely to be a real issue, or an over-zealous warning?
I am thinking of doing two things: buying a new/larger(1TB) M.2 drive, and dd'ing everything over; and upgrading the firmware on this Crucial M.2
drive
- Is it a particularly risky operation up update the M.2 firmware without backing up the drive first?
I think I will press on with buying a new 1TB M.2 drive (I was thinking of doing that anyway, as it happens), and updating the firmware on this one
only after I have dd'd everything over and swapped to the new one.
Any recommendations for a decent M.2 1TB drive? I see a lot of slagging off on Amazon on the Crucial P2 I have here...
jkn <jkn...@nicorp.f9.co.uk> wrote:
So a few thoughts:
- any idea if this is related to my recent upgrade? ie. new feature in [K]Ubunto 22.04?I checked my NVMe and I don't have an 'error log' section. I don't know
- is this likely to be a real issue, or an over-zealous warning?
what yours means. You could try nvme-cli (that's the package in Ubuntu) eg:
$ sudo nvme error-log /dev/nvme0n1
$ sudo nvme smart-log /dev/nvme0n1
(other *-log commands available)
and see if it reports anything interesting. eg for me smart-log says:
$ sudo nvme smart-log /dev/nvme1n1
Smart Log for NVME device:nvme1n1 namespace-id:ffffffff
critical_warning : 0
temperature : 25 C
available_spare : 100%
available_spare_threshold : 5%
percentage_used : 10%
endurance group critical warning summary: 0
so I seem to have used 10% of my write endurance (I think).
It is possible doing an upgrade has eaten some of your available writes and pushed it over some threshold.
I am thinking of doing two things: buying a new/larger(1TB) M.2 drive, and dd'ing everything over; and upgrading the firmware on this Crucial M.2 drive
- Is it a particularly risky operation up update the M.2 firmware without backing up the drive first?In theory it shouldn't be a risk to update the firmware (it happens in production all the time), but if the drive is exhibiting failure signs I'd want to make a backup first just in case.
Theo
(who hadn't come across nvme-cli before and thinks it could be a useful way of using cheaper NVMe in servers and replacing drives when they start
running out of writes)
It is possible doing an upgrade has eaten some of your available writes and pushed it over some threshold.
Previously I would have aimed for an SSD with DRAM rather than a DRAM-less one but they seem to be harder to find these days. DRAMless is probably
fine unless you're serving databases or similar.
Theo <theom...@chiark.greenend.org.uk> wrote:Thanks Theo, that's all very useful. I do do some semi-intensive compiling so the point is well taken.
Previously I would have aimed for an SSD with DRAM rather than a DRAM-less one but they seem to be harder to find these days. DRAMless is probably fine unless you're serving databases or similar.One other thing... if it's going to be under any kind of intense workload
(eg compiling) what I tend to do is look for 'performance consistency' graphs, eg this is a cheap and old drive:
https://www.anandtech.com/show/9258/crucial-mx200-250gb-500gb-1tb-ssd-review/2
You can see the IOPS fall off a cliff once the buffer cache is exhausted.
One way to improve this is to leave some portion of the drive unwritten - eg partition it to 900GB not 1TB and leave the last 100GB as unwritten blocks. This gives the drive a bit more breathing space as it can have more spare blocks to play with. Anandtech's benchmarks sometimes incorporate such overprovisioning, eg: https://www.anandtech.com/show/9451/the-2tb-samsung-850-pro-evo-ssd-review/2
You probably don't care about performance to that level but it's something I look at when selecting drives.
Theo
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 415 |
Nodes: | 16 (2 / 14) |
Uptime: | 21:32:27 |
Calls: | 8,717 |
Calls today: | 6 |
Files: | 13,273 |
Messages: | 5,954,680 |