SATA probe problem

Romain Kang romain at kzsu.stanford.edu
Mon Aug 27 14:59:20 UTC 2007


I've just built a new machine with Feisty (i386):
	AMD X2 4400 (Brisbane)
	Biostar TF7050-M2, 6/01/07 firmware
	2x1G Crucial Ballistix RAM
	SATA1: Seagate ST3300622AS, 300 GB
	SATA2: Samsung HD501LJ, 500 GB

The Samsung 500 GB will be the bulk store for MythTV, but it gets
correctly detected only about 50% of the system boots.  However,
the BIOS correctly finds both hard drives every time I've watched
it.  Below are two dmesg examples, first where the Samsung goes
missing and the second where it is correctly attached.

Is there some module option to libata or sata_nv that can make the
initialization more reliable, or perhaps a way to reprobe for attached
disks?

Thanks,
Romain Kang
romain at kzsu.stanford.edu

[    5.096000] ata2: SATA max UDMA/133 cmd 0x00010970 ctl 0x00010b72 bmdma 0x0001dc08 irq 19
[    5.696000] scsi1 : sata_nv
[    6.008000] ata2: SATA link down (SStatus 0 SControl 0)
----------------------------------------------------------------------
[    7.328000] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    7.328000] ata2.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
[    7.328000] ata2.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
[    7.328000] ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    7.328000] ata2.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
[    7.328000] ata2.00: configured for UDMA/133





More information about the ubuntu-users mailing list