1 |
On Sun, Sep 3, 2017 at 2:39 AM, Peter Humphrey <peter@××××××××××××.uk> wrote: |
2 |
> On Sunday, 3 September 2017 03:34:06 BST R0b0t1 wrote: |
3 |
>> On Sat, Sep 2, 2017 at 8:49 AM, Peter Humphrey <peter@××××××××××××.uk> |
4 |
> wrote: |
5 |
>> > A week or two ago I was investigating some other weirdnesses and at one |
6 |
>> > point I zeroed out the first partition: the unformatted one containing |
7 |
>> > the UEFI data. It took longer than I expected, having only 2MB to fill. |
8 |
>> > I wonder if it strayed outside the partition... |
9 |
>> |
10 |
>> Are you trimming your drive? |
11 |
> |
12 |
> Yes; this is root's crontab: |
13 |
> |
14 |
> 9 3,15 * * * /sbin/fstrim -a |
15 |
> |
16 |
|
17 |
I think a reduction in drive performance (when you are maintaining it |
18 |
properly) is the best argument for being ready to replace the drive, |
19 |
as this seems unlikely to happen to me unless the drive is actually |
20 |
wearing out. |
21 |
|
22 |
At the same time I have seen this exact situation fixed by a firmware |
23 |
upgrade. Still, this seems more alarming than the other issues you've |
24 |
described. |