I've kinda given up for the moment. I finally figured out the 137GB limit and created a partition much smaller than that. The driver *seems* to work, but when I do md5sums on the files I copy to the disk, I get random results, i.e. never the same thing twice on the same file once RAM cache is cleared. The disk drive itself works just fine on a different machine using sata_nv. Maybe it's something specific to the 1622TA2 card I have. I dunno. I have another SATA drive coming that's only 80GB. I'll put that one on this controller when it comes in and see if things change. Bob --- Richard Purdie <rpurdie@xxxxxxxxx> wrote: > On Wed, 2006-12-20 at 20:16 -0800, Bob Stewart wrote: > > Sorry, that should have been "logblocks". As shown below, it works unless > the > > partition is such that logblocks will be larger than 16383. In fdisk, that > > number of cylinders anything greater than 16709. "Works" is relative, > though. > > When doing a copy of several gigabytes, the syslog shows periodic device > > errors, which I have posted previously. Each time, it lowers the access > rate > > until it eventually reaches PI04. > [...] > > Here is the fdisk screen for the above disk. If I use a figure larger than > > 16709 cylinders mkfs.xfs will not be successful. > > > > Disk /dev/sda: 200.0 GB, 200049647616 bytes > > 255 heads, 63 sectors/track, 24321 cylinders > > Units = cylinders of 16065 * 512 = 8225280 bytes > > > > Device Boot Start End Blocks Id System > > /dev/sda1 1 16709 134215011 83 Linux > > Its probably significant that the problem appears at >137GB. I've got a > similar issue with a 320GB drive I've just tried to use. I've not pinned > down the limit but I partitioned the drive in two and the first half > works, the second half gives corrupt superblock errors when trying to > mount it (ext3). > > I tried both the 2.6.19 version and one based on 2.6.20-rc4, same > problem. Is there anything specific the driver needs to do work with > disks > 137GB? > > I've just tried to grab the datasheet but the Initio webserver has > chosen this moment to act up... > > Richard > > - > To unsubscribe from this list: send the line "unsubscribe linux-ide" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
