Hi, Using the pdc202xx version 0.30 driver for a Promise 20265 chip under the 2.4.0 kernel I'm getting file system corruptions. Whats odd though is that e2fsck can't correct the corrupted file systems. Here is the setup :- Hardware: AMD Athlon Asus A7V motherboard Via Apollo Chipset Promise 20265 IDE controler IBM 75GXP hard disk Under the 2.2.16 kernel I have no problems (this is running without UDMA). Upgrading to the 2.4.0 kernel, with the pdc202xx driver, I occasionally get bad blocks showing up on my root partition. e2fsck (both from E2fsprogs version 1.18 and version 1.10) run with "-c" pick up the bad blocks, but are unable to fix the problem - and so just adds the blocks in question to the list of bad blocks. Now for the bizare part, running badblocks -w /dev/hda1 1052226 and the bad blocks disappear! I can recreate the ext2 fs afterwards without any problems. This has happened on two different machines (both with an identical hardware set up). Is this a known problem? Are there any work arounds? Thanks in advance for your help, David Summers. P.S. I attach various output files, lspci -v, and dumpe2fs on the fs when the bad blocks were noted. the kernel module on boot up says :- Feb 22 18:51:00 cpt4 kernel: PDC20265: IDE controller on PCI bus 00 dev 88 Feb 22 18:51:00 cpt4 kernel: PCI: Found IRQ 10 for device 00:11.0 Feb 22 18:51:00 cpt4 kernel: PDC20265: chipset revision 2 Feb 22 18:51:00 cpt4 kernel: PDC20265: not 100%% native mode: will probe irqs later Feb 22 18:51:00 cpt4 kernel: PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode. Feb 22 18:51:00 cpt4 kernel: ide0: BM-DMA at 0x7800-0x7807, BIOS settings: hda:DMA, hdb:DMA Feb 22 18:51:00 cpt4 kernel: ide1: BM-DMA at 0x7808-0x780f, BIOS settings: hdc:DMA, hdd:DMA