2nd sata drive not recognized (kernel 2.6.16.11-Slackware 10.2)

adscvr · 04-27-2006, 10:39 PM

I had installed Slackware 10.2 on a single sata drive with kernel 2.6.16.11. Today i connect another drive and although the kernel recognizes it, i can't found it.
Here is the kernel output:

Code:

[...]
sata_sil 0000:01:0b.0: Applying R_ERR on DMA activate FIS errata fix
ata1: SATA max UDMA/100 cmd 0xF0802080 ctl 0xF080208A bmdma 0xF0802000 irq 185
ata2: SATA max UDMA/100 cmd 0xF08020C0 ctl 0xF08020CA bmdma 0xF0802008 irq 185
ata3: SATA max UDMA/100 cmd 0xF0802280 ctl 0xF080228A bmdma 0xF0802200 irq 185
ata4: SATA max UDMA/100 cmd 0xF08022C0 ctl 0xF08022CA bmdma 0xF0802208 irq 185
ata1: SATA link down (SStatus 0)
scsi0 : sata_sil
ata2: SATA link down (SStatus 0)
scsi1 : sata_sil
ata3: SATA link up 1.5 Gbps (SStatus 113)
ata3: dev 0 cfg 49:2f00 82:74eb 83:7fea 84:4023 85:74e9 86:3c02 87:4023 88:203f
ata3: dev 0 ATA-6, max UDMA/100, 321672960 sectors: LBA48
ata3: dev 0 configured for UDMA/100
scsi2 : sata_sil
ata4: SATA link up 1.5 Gbps (SStatus 113)
ata4: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 88:40ff
ata4: dev 0 ATA-7, max UDMA7, 312581808 sectors: LBA48
ata4: dev 0 configured for UDMA/100
scsi3 : sata_sil
  Vendor: ATA       Model: HDS722516VLSA80   Rev: V34O
  Type:   Direct-Access                      ANSI SCSI revision: 05
  Vendor: ATA       Model: SAMSUNG HD160JJ   Rev: ZM10
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 321672960 512-byte hdwr sectors (164697 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
sd 2:0:0:0: Attached scsi disk sda
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
sdb: Mode Sense: 00 3a 00 00
SCSI device sdb: drive cache: write back
 sdb: sdb1 sdb2 sdb3
sd 3:0:0:0: Attached scsi disk sdb
sd 2:0:0:0: Attached scsi generic sg0 type 0
sd 3:0:0:0: Attached scsi generic sg1 type 0
[...]

As you can see, the 2nd drive is sdb. But when i try to run fdisk:

Code:

adscvr@gilead:~# fdisk /dev/sdb

Unable to open /dev/sdb

And i can't locate the sdb, sdb[1..3] files in the /dev directory:

Code:

adscvr@gilead:~# ls /dev/sdb*
/dev/sdb10  /dev/sdb12  /dev/sdb14  /dev/sdb3  /dev/sdb5  /dev/sdb7  /dev/sdb9
/dev/sdb11  /dev/sdb13  /dev/sdb15  /dev/sdb4  /dev/sdb6  /dev/sdb8

I'm clueless. I have no RAID set. I have a sil3114 PCI-to-SATA controller.

Does anyone have a problem like this? Can anyone help me?
Thanks!!

Brian1 · 04-28-2006, 06:41 PM

You need to use the fdisk command as root not as a user.
To list drives you can use the command ' /sbin/fdisk -l ' as root of course.

Brian1

adscvr · 05-02-2006, 08:25 AM

I ran it as root with the same result. When i plug a usb device it is recognized and assigned the sdc.So it seems that the sdb is reserved beforehand (in the boot procedure as the kernel output shows). What i don't undestand is why the nodes sdb, sd[1..3] not exist.

The SATA controller is a Silicon Image SiI3114. The drive that is not recognized is a Samsung HD160JJ SATA-II NCQ and the other (working) is a Hitachi SATA device. I've read that several people use this device with no problem at all (on windows at least).

Is there any option in the kernel that i must set?