Something corrupts raid5 disks slightly during reboot
I know this sounds stupid, but anyway:
I have seen the very same symptome caused by RAM faults (too slow ram for given clocks, to be exact).
Yes gzipping/gunzipping a gigabyte of /dev/random data didn`t show up a crc error.
That was an i845 chipset, by the way...
regards, Samium Gromoff
Quoted 5 lines · you [Samium Gromoff]
I know this sounds stupid, but anyway:
I have seen the very same symptome caused by RAM faults (too slow ram for given clocks, to be exact).
The very same? You mean if booted, wrote few kB's of data to disk, synced, then pressed reset, the same three bytes were corrupted (set to zero) each time after reboot?
I can buy the faulty ram explanation for many symptoms, but it somehow in this case it seems very unlikely. The box can be doing its thing (backing up
Quoted 1 line
20 workstations onto 6 ide disks) for weeks without ever corrupting
anything, and the when I power it down and up (after manually raidstopping and umounting), three bytes get corrupted. (Well, sometimes few bytes in addition to the three, but usually just three.)
Quoted 2 lines
Yes gzipping/gunzipping a gigabyte of
/dev/randomdata didn`t show up a crc error.
The box does survive memtest, but you're right that doesn't prove anything.
Quoted 1 line
That was an i845 chipset, by the way...
This is i815.
-- v --
At Thu, 15 Jan 2004 00:30:40 +0200,
Quoted 11 lines · Ville Herva
Quoted 5 lines · you [Samium Gromoff]
I know this sounds stupid, but anyway:
I have seen the very same symptome caused by RAM faults (too slow ram for given clocks, to be exact).
The very same? You mean if booted, wrote few kB's of data to disk, synced, then pressed reset, the same three bytes were corrupted (set to zero) each time after reboot?
No, corruption after reboot and perfect work inbetween.
Quoted 1 line
regards, Samium Gromoff
Quoted 7 lines · you [Samium Gromoff]
At Thu, 15 Jan 2004 00:30:40 +0200,
Quoted 5 lines · Ville Herva
Quoted 3 lines · you [Samium Gromoff]
I know this sounds stupid, but anyway:
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
I have seen the very same symptome caused by RAM faults (too slow ram for given clocks, to be exact).
The very same? You mean if booted, wrote few kB's of data to disk, synced, then pressed reset, the same three bytes were corrupted (set to zero) each time after reboot?
No, corruption after reboot and perfect work inbetween.
Very strange. And you got rid of it by replacing the memory?
Any theories on how faulty memory could actually cause something like this? A bad spot in memory on an area where the bios code is cached, and hence is never used apart from running the bios startup (not even by memtest86)?
-- v --
At Thu, 15 Jan 2004 21:57:58 +0200,
Quoted 12 lines · Ville Herva
Quoted 10 lines · you [Samium Gromoff]
At Thu, 15 Jan 2004 00:30:40 +0200,
Quoted 8 lines · Ville Herva
Quoted 5 lines · you [Samium Gromoff]
I know this sounds stupid, but anyway:
I have seen the very same symptome caused by RAM faults (too slow ram for given clocks, to be exact).
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
The very same? You mean if booted, wrote few kB's of data to disk, synced, then pressed reset, the same three bytes were corrupted (set to zero) each time after reboot?
No, corruption after reboot and perfect work inbetween.
Very strange. And you got rid of it by replacing the memory?
Yeah.
Quoted 3 lines
Any theories on how faulty memory could actually cause something like this? A bad spot in memory on an area where the bios code is cached, and hence is never used apart from running the bios startup (not even by memtest86)?
No idea, really :-)
Quoted 3 lines
-- v --
regards, Samium Gromoff