This is a multi-part message in MIME format.
On 2024-03-20 22:58, Nicholas Geovanis wrote:
On Wed, Mar 20, 2024, 11:28 AM Jesper Dybdal
<jd-debian-user@dybdal.dk> wrote:
I have now done the following:
* Checked the RAID array - no problems found.
* Run fsck. It found three cases of the block count being
incorrect. I
don't know which the other two affected files are.
* Run one pass of memtest86+. Nothing found.
So it seems not to be a problem with the disks.
A bug in ext4? Well, ext4 has always done its job for me wihtout
problems.
A RAM error that memtest86+ did not find? Possible. Once upon a
time,
when you bought an ordinary pc, its RAM had ECC as a matter of
course;
unfortunately, that is not the case nowadays.
I think I'll let memtest86+ run overnight one of the coming nights.
Unless it is simply a RAM error, then it is a bit scary...
I've now let memtest86+ run for 8 hours, during which i did 14 passes of
all its tests. It found nothing wrong.
I have seen that a couple times, unlikely but possible. Maybe review
your RAM configuration too, ensure that the sticks are on the same
supported refresh rate and distributed across the slots in an approved
way.
Regards,
Jesper
On 2024-03-19 21:47, Franco Martelli wrote:
> On 19/03/24 at 15:43, Jesper Dybdal wrote:
>
>>
>> My plan is to boot a rescue disk and mount that partition
read-only.
>> Then:
>> * If the file looks ok after reboot, then I'll strongly suspect
the
>> RAM - and run memtest.
>> * Otherwise, I'll have to run fsck and see what happens.
>>
>> kernel version:
>> root@nuser:~# uname -a
>> Linux nuser 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31)
>> x86_64 GNU/Linux
>>
>> The partition in question is a RAID 1 controlled by md.
>
> Another check you can perform it is on the RAID array, by
default it
> runs on the first Sunday of each month at 00:57. You should have
this
> file /etc/cron.d/mdadm that takes care to run this check monthly.
>
> Before you reboot, does it look OK /proc/mdstat ?
>
--
Jesper Dybdal
https://www.dybdal.dk
--
Jesper Dybdal
https://www.dybdal.dk
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
On 2024-03-20 22:58, Nicholas Geovanis wrote:<br>
<blockquote type="cite" cite="mid:
CAJmb-YnCNDazdrjmKuZCHECdZEsCPCJuWp5Zs52xVjoe-ZLGbg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Mar 20, 2024,
11:28 AM Jesper Dybdal <<a
href="mailto:
jd-debian-user@dybdal.dk"
moz-do-not-send="true" class="moz-txt-link-freetext">
jd-debian-user@dybdal.dk</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I
have now done the following:<br>
* Checked the RAID array - no problems found.<br>
* Run fsck. It found three cases of the block count being
incorrect. I <br>
don't know which the other two affected files are.<br>
* Run one pass of memtest86+. Nothing found.<br>
<br>
So it seems not to be a problem with the disks.<br>
A bug in ext4? Well, ext4 has always done its job for me
wihtout problems.<br>
A RAM error that memtest86+ did not find? Possible. Once
upon a time, <br>
when you bought an ordinary pc, its RAM had ECC as a
matter of course; <br>
unfortunately, that is not the case nowadays.<br>
<br>
I think I'll let memtest86+ run overnight one of the
coming nights.<br>
<br>
Unless it is simply a RAM error, then it is a bit scary...<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
</div>
</blockquote>
I've now let memtest86+ run for 8 hours, during which i did 14
passes of all its tests. It found nothing wrong.<br>
<blockquote type="cite" cite="mid:
CAJmb-YnCNDazdrjmKuZCHECdZEsCPCJuWp5Zs52xVjoe-ZLGbg@mail.gmail.com">
<div dir="auto">
<div dir="auto">I have seen that a couple times, unlikely but
possible. Maybe review your RAM configuration too, ensure that
the sticks are on the same supported refresh rate and
distributed across the slots in an approved way.</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Regards,<br>
Jesper<br>
<br>
On 2024-03-19 21:47, Franco Martelli wrote:<br>
> On 19/03/24 at 15:43, Jesper Dybdal wrote:<br>
><br>
>><br>
>> My plan is to boot a rescue disk and mount that
partition read-only. <br>
>> Then:<br>
>> * If the file looks ok after reboot, then I'll
strongly suspect the <br>
>> RAM - and run memtest.<br>
>> * Otherwise, I'll have to run fsck and see what
happens.<br>
>><br>
>> kernel version:<br>
>> root@nuser:~# uname -a<br>
>> Linux nuser 5.10.0-28-amd64 #1 SMP Debian
5.10.209-2 (2024-01-31) <br>
>> x86_64 GNU/Linux<br>
>><br>
>> The partition in question is a RAID 1 controlled
by md.<br>
><br>
> Another check you can perform it is on the RAID
array, by default it <br>
> runs on the first Sunday of each month at 00:57. You
should have this <br>
> file /etc/cron.d/mdadm that takes care to run this
check monthly.<br>
><br>
> Before you reboot, does it look OK /proc/mdstat ?<br>
><br>
<br>
-- <br>
Jesper Dybdal<br>
<a href="
https://www.dybdal.dk"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">
https://www.dybdal.dk</a><br>
<br>
<br>
<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Jesper Dybdal
<a class="moz-txt-link-freetext" href="
https://www.dybdal.dk">https://www.dybdal.dk</a></pre>
</body>
</html>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)