Comment 22 for bug 430333

I think this might be a Linux bug, i.e., not specific to Ubuntu.

As this is a UNIX-style application, no userland application should contain code that can produce the corruption you describe.

This said, the component most likely being responsible is the libscsi driver module doing the real disk operation.

Here are some things I´d propose:

- Test behaviour with default BIOS options
- Test behaviour with other distro
- Burn-in test, that is, writing defined patterns to the drive and check the results

Please remember that there is still a slight chance of a hardware failure. A module with a defect like this is very unlikely to enter the Linux stable branch.