adding a second SATA drive
Kevin J. Cummings
cummings at kjchome.homeip.net
Thu Mar 23 19:00:41 UTC 2006
Marcel Janssen wrote:
> Hi,
>
> I've added a second sata drive to my system and I see from dmesg that it is
> being added :
> nv_sata: Secondary device added
Not a lot of messages here to tell by. I only have 1 SATA disk
installed on my system, but I see:
> libata version 1.20 loaded.
> sata_nv 0000:00:0b.0: version 0.8
> PCI: Setting latency timer of device 0000:00:0b.0 to 64
> ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xCC00 irq 10
> ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xCC08 irq 10
> ata1: dev 0 cfg 49:2f00 82:346b 83:5b01 84:4003 85:3469 86:1801 87:4003 88:203f
> ata1: dev 0 ATA-6, max UDMA/100, 78125000 sectors: LBA
> nv_sata: Primary device added
> nv_sata: Primary device removed
> nv_sata: Secondary device removed
> ata1: dev 0 configured for UDMA/100
> scsi1 : sata_nv
> ata2: no device found (phy stat 00000000)
> scsi2 : sata_nv
> Vendor: ATA Model: WDC WD400BD-75JM Rev: 05.0
> Type: Direct-Access ANSI SCSI revision: 05
> SCSI device sdb: 78125000 512-byte hdwr sectors (40000 MB)
> SCSI device sdb: drive cache: write back
> SCSI device sdb: 78125000 512-byte hdwr sectors (40000 MB)
> SCSI device sdb: drive cache: write back
> sdb: sdb1 sdb2
> sd 1:0:0:0: Attached scsi disk sdb
(yes, I have a small real SCSI drive on my system, so my SATA drive is sdb.)
> But, where can I find it ?
You need to look further into your /var/log/dmesg file to find all of
the messages associated with your drive. If you don't see it there,
perhaps you have a cabling issue?
> I check in /dev and expected something like /dev/sdb but it doesn't exist.
Stuff in /dev is created either during boot, or by hotplug events. If
the system doesn't see the drive, there won't be a device node for it in
/dev .
--
Kevin J. Cummings
kjchome at rcn.com
cummings at kjchome.homeip.net
cummings at kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)
More information about the fedora-list
mailing list