> Hi. Hi!
> > I have a Promise Ultra100 TX2 card with 2 brand new Maxtor drives. The > setup should work in UDMA100 mode, but is downgraded to PIO mode 4 under > FreeBSD 5.1 and 4.8. > Hardware is definitely OK, I have 2 controllers, 6 different 80 wire IDE > cables, shielded and unshielded and no irq conflicts. Always the same > problem. Disks work perfectly on an onboard VIA controller. > The Promise BIOS is the latest. NetBSD also downgrades to PIO mode 4, in > an i386 and an alpha. Maybe some registers not setup correctly by the > driver(s)? > > dmesg excerpt: > > [...] > atapci0: <Promise TX2 ATA100 controller> port > 0xe080-0xe08f,0xe0a0-0xe0a3,0xe090-0xe097,0xe0a4-0xe0a7,0xe098-0xe09f > mem 0x84000000-0x84003fff irq 10 at device 14.0 on pci 0 > [...] > ad4: 39205MB <Maxtor 6E040L0> [79656/16/63] at ata2-master UDMA100 > [...] > ad4: UDMA ICRC error reading fsbn 0 (ad4 bn 0; cn 0 tn 0 sn 0) retrying > ad4: UDMA ICRC error reading fsbn 0 (ad4 bn 0; cn 0 tn 0 sn 0) retrying > ad4: UDMA ICRC error reading fsbn 0 (ad4 bn 0; cn 0 tn 0 sn 0) retrying > ad4: UDMA ICRC error reading fsbn 0 (ad4 bn 0; cn 0 tn 0 sn 0) falling > back to PIO mode Sorry, friend, your HDD is to be thrown out. Purche a new one (highly desirable not from China... :() and if you saw, or if you see something like this: ad2s1f: hard error reding fsbn 28247911 (ad2s1 bn 28247911; cn 1758 tn 89 sn 34) status=59 error=40 ad2s1f: hard error reding fsbn 28247911 (ad2s1 bn 28247911; cn 1758 tn 89 sn 34) status=59 error=40 THE FOLLOWING DISK SECTORS COULD NOT BE READ: 28247900, 28247903, 28247904, 28247905, 28247906, 28247907, 28247908, 28247909, 28247910, 28247911 ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Pahse 5 - Checl Cyl groups 219480 files, 28790271 used, 2584481 free (63457 frags, 315128 blocks, %0.2 fragmantation) ***** FILE SYSTEM STILL DIRTY ***** ***** PLEASE RERUN FSCK ***** then sure no doubt that the disk is broken After "clever" HDD's which "burn" the information about their bad blocks by themselves came to the scene FreeBSD, AFAIK, stopped supporting such a feature as searching and marking bad blocks. So, if you see these errors it means only one thing - the disk is dead, or will be dead tomorrow or so... :( Good luck! -- Error Code=-1 Continue? Yes | No -- > > > Help would be greatly appreciated! > > Regards > > Felix > _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"