I have a SATA drive attached to a PowerPC 8349E board, using the SIL 3114 controller. I'm running the latest code from Paul Mackerras (PowerPC maintainer) (2.6.18-blabla).
I'm experiencing a number of I/O errors with the SATA drive. fdisk can see the partition table, but when I issue the "w" command, I get this output:
Calling ioctl() to re-read partition table.
SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
sda: unknown partition table
SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
sda: unknown partition table
Syncing disks.
I cannot mount any partitions. On boot, I see this:
sata_sil 0000:00:10.0: Applying R_ERR on DMA activate FIS errata fix
ata1: SATA max UDMA/100 cmd 0xD100E080 ctl 0xD100E08A bmdma 0xD100E000 irq 22
ata2: SATA max UDMA/100 cmd 0xD100E0C0 ctl 0xD100E0CA bmdma 0xD100E008 irq 22
ata3: SATA max UDMA/100 cmd 0xD100E280 ctl 0xD100E28A bmdma 0xD100E200 irq 22
ata4: SATA max UDMA/100 cmd 0xD100E2C0 ctl 0xD100E2CA bmdma 0xD100E208 irq 22
scsi0 : sata_sil
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: ATA-7, max UDMA/133, 321672960 sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 0
ata1.00: configured for UDMA/100
scsi1 : sata_sil
ata2: SATA link down (SStatus 0 SControl 310)
scsi2 : sata_sil
ata3: SATA link down (SStatus 0 SControl 310)
scsi3 : sata_sil
ata4: SATA link down (SStatus 0 SControl 310)
scsi 0:0:0:0: Direct-Access ATA HDT722516DLA380 V43O PQ: 0 ANSI: 5
SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
sda: unknown partition table
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
The odd thing is that this works in 2.6.13, so something is broken. I don't know if it's a bug in the sata_sil driver, or a configuration issue. Can anyone help?
--
Timur Tabi
Linux Kernel Developer @ Freescale
Timur,
fdisk manipulates DOS-style partition maps. Have you compiled these
into your latest kernel? You don't actually have any errors in the
below messages, other than the partition map being unreadable...
Chris
On 29 Sep 2006, at 21:11, Timur Tabi wrote:
> I have a SATA drive attached to a PowerPC 8349E board, using the
> SIL 3114 controller. I'm running the latest code from Paul
> Mackerras (PowerPC maintainer) (2.6.18-blabla).
>
> I'm experiencing a number of I/O errors with the SATA drive. fdisk
> can see the partition table, but when I issue the "w" command, I
> get this output:
>
> Calling ioctl() to re-read partition table.
> SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
> sda: Write Protect is off
> SCSI device sda: drive cache: write back
> sda: unknown partition table
> SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
> sda: Write Protect is off
> SCSI device sda: drive cache: write back
> sda: unknown partition table
> Syncing disks.
>
> I cannot mount any partitions. On boot, I see this:
>
> sata_sil 0000:00:10.0: Applying R_ERR on DMA activate FIS errata fix
> ata1: SATA max UDMA/100 cmd 0xD100E080 ctl 0xD100E08A bmdma
> 0xD100E000 irq 22
> ata2: SATA max UDMA/100 cmd 0xD100E0C0 ctl 0xD100E0CA bmdma
> 0xD100E008 irq 22
> ata3: SATA max UDMA/100 cmd 0xD100E280 ctl 0xD100E28A bmdma
> 0xD100E200 irq 22
> ata4: SATA max UDMA/100 cmd 0xD100E2C0 ctl 0xD100E2CA bmdma
> 0xD100E208 irq 22
> scsi0 : sata_sil
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata1.00: ATA-7, max UDMA/133, 321672960 sectors: LBA48 NCQ (depth
> 0/32)
> ata1.00: ata1: dev 0 multi count 0
> ata1.00: configured for UDMA/100
> scsi1 : sata_sil
> ata2: SATA link down (SStatus 0 SControl 310)
> scsi2 : sata_sil
> ata3: SATA link down (SStatus 0 SControl 310)
> scsi3 : sata_sil
> ata4: SATA link down (SStatus 0 SControl 310)
> scsi 0:0:0:0: Direct-Access ATA HDT722516DLA380 V43O PQ:
> 0 ANSI: 5
> SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
> sda: Write Protect is off
> SCSI device sda: drive cache: write back
> SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
> sda: Write Protect is off
> SCSI device sda: drive cache: write back
> sda: unknown partition table
> sd 0:0:0:0: Attached scsi disk sda
> sd 0:0:0:0: Attached scsi generic sg0 type 0
>
> The odd thing is that this works in 2.6.13, so something is
> broken. I don't know if it's a bug in the sata_sil driver, or a
> configuration issue. Can anyone help?
>
> --
> Timur Tabi
> Linux Kernel Developer @ Freescale
> -
> To unsubscribe from this list: send the line "unsubscribe linux-
> kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Chris Boot
[email protected]
http://www.bootc.net/
On Fri, 29 Sep 2006 15:11:20 -0500 Timur Tabi <[email protected]> wrote:
> I have a SATA drive attached to a PowerPC 8349E board, using the SIL 3114 controller. I'm running the latest code from Paul Mackerras (PowerPC maintainer) (2.6.18-blabla).
>
> I'm experiencing a number of I/O errors with the SATA drive. fdisk can see the partition table, but when I issue the "w" command, I get this output:
>
> The odd thing is that this works in 2.6.13, so something is broken. I don't know if it's a bug in the sata_sil driver, or a configuration issue. Can anyone help?
>
Do you use MSDOS or MAC partition (or other) type? Make sure you have
the one you use in the config.
It looks like the arch/powerpc/configs/mpc83* defconfigs enable neither.
-Olof
Chris Boot wrote:
> Timur,
>
> fdisk manipulates DOS-style partition maps. Have you compiled these into
> your latest kernel? You don't actually have any errors in the below
> messages, other than the partition map being unreadable...
Yes, that was it! Thank you very much. All I had to do was select "PC BIOS (MSDOS partition tables) support" configuration option, and that was it.
--
Timur Tabi
Linux Kernel Developer @ Freescale