Ttyjfyk

Can a bounded number sequence be strictly ascending?

PTIJ: Why can't I eat anything?

Why is Beresheet doing a only a one-way trip?

Force user to remove USB token

Can Mathematica be used to create an Artistic 3D extrusion from a 2D image and wrap a line pattern around it?

Why does the negative sign arise in this thermodynamic relation?

Good allowance savings plan?

They call me Inspector Morse

GPLv2 - licensing for commercial use

What's the "normal" opposite of flautando?

Who is eating data? Xargs?

Are babies of evil humanoid species inherently evil?

Do I really need to have a scientific explanation for my premise?

What wound would be of little consequence to a biped but terrible for a quadruped?

How to create a hard link to an inode (ext4)?

Is there an equal sign with wider gap?

How do I deal with a powergamer in a game full of beginners in a school club?

Should I tell my boss the work he did was worthless

Given the sum of two powers of two, extract the exponents

Try Catch Block Affecting a Variable in an Enclosing Scope

Tricky AM-GM inequality

Grey hair or white hair

Best approach to update all entries in a list that is paginated?

Good for you! in Russian

badblocks fails to spot corrupting disk controller

0

I have file corruption problem on a HDD (the SDD in the same computer works fine):

for i in 1..10; do
 dd if=/dev/zero of=zeroes_$i.dat bs=512 count=4M
done
md5sum zeroes_*

yields the correct checksum a981130cf2b7e09f4686dc273cf7187e for some files, but often another one. grep confirms that it finds non-zero characters in some files.
So there is definitely something fishy here (based on swapping hardware with another computer, I suspect more the controller than the disk, but this is not the topic of this question).
This is «reproducible» in the sense that there are always several zeroes_$i.dat files with a failing checksum.

Now the strange part: badblocks -wvs -b 32768 -c 2048 report no error even after testing 4 patterns.
What could cause badblocks to fail to find corrupting IO?

hard-disk corruption badblocks

share|improve this question

asked 3 hours ago

jrouquiejrouquie

1042

New contributor

jrouquie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What does dmesg tell you?
  
  – roaima
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  it may be hardware related. What kind of controller are you using ? does it have settings like write-back write-through ?
  
  – dominix
  27 mins ago
  

  
  
  
  

add a comment | 

0

I have file corruption problem on a HDD (the SDD in the same computer works fine):

for i in 1..10; do
 dd if=/dev/zero of=zeroes_$i.dat bs=512 count=4M
done
md5sum zeroes_*

yields the correct checksum a981130cf2b7e09f4686dc273cf7187e for some files, but often another one. grep confirms that it finds non-zero characters in some files.
So there is definitely something fishy here (based on swapping hardware with another computer, I suspect more the controller than the disk, but this is not the topic of this question).
This is «reproducible» in the sense that there are always several zeroes_$i.dat files with a failing checksum.

Now the strange part: badblocks -wvs -b 32768 -c 2048 report no error even after testing 4 patterns.
What could cause badblocks to fail to find corrupting IO?

hard-disk corruption badblocks

share|improve this question

asked 3 hours ago

jrouquiejrouquie

1042

New contributor

jrouquie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  What does dmesg tell you?
  
  – roaima
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  it may be hardware related. What kind of controller are you using ? does it have settings like write-back write-through ?
  
  – dominix
  27 mins ago
  

  
  
  
  

add a comment | 

I have file corruption problem on a HDD (the SDD in the same computer works fine):

for i in 1..10; do
 dd if=/dev/zero of=zeroes_$i.dat bs=512 count=4M
done
md5sum zeroes_*

yields the correct checksum a981130cf2b7e09f4686dc273cf7187e for some files, but often another one. grep confirms that it finds non-zero characters in some files.
So there is definitely something fishy here (based on swapping hardware with another computer, I suspect more the controller than the disk, but this is not the topic of this question).
This is «reproducible» in the sense that there are always several zeroes_$i.dat files with a failing checksum.

Now the strange part: badblocks -wvs -b 32768 -c 2048 report no error even after testing 4 patterns.
What could cause badblocks to fail to find corrupting IO?

hard-disk corruption badblocks

share|improve this question

asked 3 hours ago

jrouquiejrouquie

1042

New contributor

jrouquie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

for i in 1..10; do
 dd if=/dev/zero of=zeroes_$i.dat bs=512 count=4M
done
md5sum zeroes_*

share|improve this question

asked 3 hours ago

jrouquiejrouquie

1042

New contributor

jrouquie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

asked 3 hours ago

jrouquiejrouquie

1042

New contributor

jrouquie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 3 hours ago

jrouquiejrouquie

1042

New contributor

jrouquie is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 3 hours ago

jrouquiejrouquie

1042