Hi Jesper,
RAID 1 is mirroring. I suppose, a reason for the failure might be a timing
problem. I do not know for sure, if yous system has got a real RAID-controller
or if it is made by software.
The real controller should not produce write errors, however maybe at heavy
load it might happen.
On 2024-03-28 15:02, Hans wrote:
Am Donnerstag, 28. März 2024, 14:49:37 CET schrieb Jesper Dybdal:
Hello,
memtest86+ is for testing RAM, but do you not want to test ext4 filesystem?
Sorry - I should have left more of the previous mails quoted. I have
previously tested the RAID1 consistency
Am Donnerstag, 28. März 2024, 14:49:37 CET schrieb Jesper Dybdal:
Hello,
memtest86+ is for testing RAM, but do you not want to test ext4 filesystem?
If so, I suggest to boot a live system like Knoppix or similar, then run your
test by using
e2fsck -y /dev/sda1
or wherever your filesystem
[Sorry - I accidentally sent this too quickly in an incomplete state.
Second try here:]
On Wed, Mar 20, 2024, 11:28 AM Jesper Dybdal
wrote:
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
On 2024-03-20 22:58, Nicholas Geovanis wrote:
On Wed, Mar 20, 2024, 11:28 AM Jesper Dybdal
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
On Wed, Mar 20, 2024, 11:28 AM Jesper Dybdal
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+.
On 20/03/24 at 09:15, Jesper Dybdal wrote:
[Sorry for the accidental Danish-language subject line :-( ]
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
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.
[Sorry for the accidental Danish-language subject line :-( ]
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
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:
10 matches
Mail list logo
