On 12/15/2009 10:08 AM, Alain Knaff wrote: > > This does indeed look like a different problem to me... No sector with a > "bad" track id, but lots of sectors "skipped". But these skips look more > like they are happening during read (rather than being really missed), as > on the second pass, they are present. > > Could you try the same with a "higher" repetition count: > > fdrawcmd readid 0 repeat=40 > > Just to make sure that eventually all sectors show up > > Also, on your case, the actual read error seems to be on track 0. Could you > give me also the headers of track 0? >
Just to further complicate things, or maybe not... I mentioned I had multiple machines with this problem. Some running different versions of SuSE. Mainly 11.0, which is where all the info I've provided came from thus far. This machine also has a SuSE-11.2 disk on it. When I do all this using SuSE-11.2 my results look more like ael's. So I think when the cause is found, it will be a single cause. Regards Mark -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
