Subject: Re: VIA SATA problem
To: NetBSD current <current-users@netbsd.org>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: current-users
Date: 06/22/2005 21:41:25
On Wed, Jun 22, 2005 at 09:27:57PM +0200, Michal 'hramrach' Suchanek wrote:
> On Wed, Jun 22, 2005 at 08:14:58PM +0200, Manuel Bouyer wrote:
> > On Wed, Jun 22, 2005 at 04:52:40PM +0200, Michal 'hramrach' Suchanek wrote:
> > > VIA Technologies VT6306 IEEE 1394 Host Controller (Firewire serial bus,
> > > interface 0x10, revision 0
> > > x46) at pci0 dev 14 function 0 not configured
> > > viaide0 at pci0 dev 15 function 0
> > > viaide0: VIA Technologies VT8237 SATA Controller (rev. 0x80)
> > > viaide0: bus-master DMA support present
> > > viaide0: primary channel wired to native-PCI mode
> > > viaide0: using ioapic0 pin 20 (irq 10) for native-PCI interrupt
> > > atabus0 at viaide0 channel 0
> > > viaide0: secondary channel wired to native-PCI mode
> > > atabus1 at viaide0 channel 1
> > > ...
> > > wd0 at atabus0 drive 0: <Maxtor 6Y200P0>
> > > wd0: drive supports 16-sector PIO transfers, LBA48 addressing
> > > wd0: 189 GB, 395136 cyl, 16 head, 63 sec, 512 bytes/sect x 398297088
> > > sectors
> > > wd0: 32-bit data port
> > > wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
> > > wd0(viaide0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using
> > > DMA)
> > > ...
> > > viaide0:0:0: lost interrupt
> > >         type: ata tc_bcount: 16384 tc_skip: 0
> > > viaide0:0:0: bus-master DMA error: missing interrupt,
> > > status=0x20
> > > viaide0:0:0: device timeout, c_bcount=16384, c_skip0
> > > wd0a: device timeout writing fsbn 18432256 of 18432256-18432287 (wd0 bn 18432319; cn 18286 tn 0 sn 31), retrying
> > > wd0: soft error (corrected)
> > 
> > Is this the only error ? Because this error has been recovered by the
> > driver, and the userland software should not have seen it at all.
> 
> It is the only error seen in dmesg output. But newfs always complains:
> wfts: write error for sector 16: Read-only filesystem

This is a different issue. I guess you're trying to newfs a partition starting
at sector 0. The first few sectors of the disk are reserved for the
MBR partition table, disklabel, boot blocks, etc ...
Make the partition start at sector 32 for example.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--