LinuxQuestions.org - Installing a secondary sata drive

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Installing a secondary sata drive (https://www.linuxquestions.org/questions/slackware-14/installing-a-secondary-sata-drive-496728/)

Installing a secondary sata drive

Hello,

I recently bought a new Barracuda 7200.10 SATA - ST3300620AS drive. The sata drive controller is builtin my motherboard. However when I boot up slackware it seem to recognize the new drive from the dmesg:

Code:

root@black_magic:~# cat dmesg.out

ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE802 bmdma 0xDC00 irq 10

ata2: SATA max UDMA/133 cmd 0xE400 ctl 0xE002 bmdma 0xDC08 irq 10

scsi0 : ata_piix

ata1.00: ATA-6, max UDMA/133, 234441648 sectors: LBA48 NCQ (depth 0/32)

ata1.00: ata1: dev 0 multi count 16

ata1.00: configured for UDMA/133

scsi1 : ata_piix

ata2.00: ATA-7, max UDMA/133, 586072368 sectors: LBA48 NCQ (depth 0/32)

ata2.00: ata2: dev 0 multi count 16

ata2.00: configured for UDMA/133

  Vendor: ATA      Model: ST3120827AS      Rev: 3.42

  Type:  Direct-Access                      ANSI SCSI revision: 05

  Vendor: ATA      Model: ST3300620AS      Rev: 3.AA

  Type:  Direct-Access                      ANSI SCSI revision: 05

SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)

sda: Write Protect is off

sda: Mode Sense: 00 3a 00 00

SCSI device sda: drive cache: write back

SCSI device sda: 234441648 512-byte hdwr sectors (120034 MB)

sda: Write Protect is off

sda: Mode Sense: 00 3a 00 00

SCSI device sda: drive cache: write back

 sda: sda1 sda2 sda3

sd 0:0:0:0: Attached scsi disk sda

SCSI device sdb: 586072368 512-byte hdwr sectors (300069 MB)

sdb: Write Protect is off

sdb: Mode Sense: 00 3a 00 00

SCSI device sdb: drive cache: write back

SCSI device sdb: 586072368 512-byte hdwr sectors (300069 MB)

sdb: Write Protect is off

sdb: Mode Sense: 00 3a 00 00

SCSI device sdb: drive cache: write back

 sdb: unknown partition table

sd 1:0:0:0: Attached scsi disk sdb

My primary drive that I have slackware installed is on a sata drive that is connected to the same sata drive controller that is on my motherboard which is why you see two different devices. The sda drive is the one that is working, but the sdb (new Barracuda 7200.10 SATA - ST3300620AS drive) isn't working, because when I use fdisk i get the following error:

Code:

root@black_magic:~# fdisk /dev/sdb



Unable to open /dev/sdb

I'm not sure what my problem is, I'm using a new 2.6.18 kernel, so I was wondering if I left something out of the kernel and need to recompile it. Just want to know if anyone got this drive working in slackware???

Thanks,

djgerbavor3

Does the drive show up if you just issue "fdisk -l" ?

My preference is "cfdisk /dev/sdb" for partitioning.

I usually get that message for a bad drive ... have you checked it, even though it is new?

I used the 320GB version of that drive for a dual boot WinXP / Slackware-11.0 install for a customer's box earlier this month with no problems.

the output of fdisk -l is:

Code:

root@black_magic:/var/run/mysql# fdisk -l



Disk /dev/sda: 120.0 GB, 120034123776 bytes

255 heads, 63 sectors/track, 14593 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes



  Device Boot      Start        End      Blocks  Id  System

/dev/sda1              1        123      987966  82  Linux swap

/dev/sda2            124        7419    58605120  83  Linux

/dev/sda3            7420      14593    57625155  83  Linux

Another thing when I look in dev directory I don't see sdb here is list of all my sd* devs

Code:

root@black_magic:/var/run/mysql# cd /dev/sd

Display all 126 possibilities? (y or n)

sda    sda2  sdb10  sdb4  sdc10  sdc4  sdd10  sdd4  sde10  sde4  sdf10  sdf4  sdg10  sdg4  sdh10  sdh4

sda1  sda3  sdb11  sdb5  sdc11  sdc5  sdd11  sdd5  sde11  sde5  sdf11  sdf5  sdg11  sdg5  sdh11  sdh5

sda10  sda4  sdb12  sdb6  sdc12  sdc6  sdd12  sdd6  sde12  sde6  sdf12  sdf6  sdg12  sdg6  sdh12  sdh6

sda11  sda5  sdb13  sdb7  sdc13  sdc7  sdd13  sdd7  sde13  sde7  sdf13  sdf7  sdg13  sdg7  sdh13  sdh7

sda12  sda6  sdb14  sdb8  sdc14  sdc8  sdd14  sdd8  sde14  sde8  sdf14  sdf8  sdg14  sdg8  sdh14  sdh8

sda13  sda7  sdb15  sdb9  sdc15  sdc9  sdd15  sdd9  sde15  sde9  sdf15  sdf9  sdg15  sdg9  sdh15  sdh9

sda14  sda8  sdb2  sdc    sdc2  sdd    sdd2  sde    sde2  sdf    sdf2  sdg    sdg2  sdh    sdh2

sda15  sda9  sdb3  sdc1  sdc3  sdd1  sdd3  sde1  sde3  sdf1  sdf3  sdg1  sdg3  sdh1  sdh3

i tried doing dfisk /dev/sdc through /dev/sdh and nothing keep getting the same error. This is stumping me. I'm going to try and see if I can see it with another os. I'll update this thread when I know more information. Thanks for you help

djgerbavor3

Hey,

well I boot off the slackware 10.2 cd. When I do fdisk -l i see both sata drives. I was able to create partitions However, when I boot back into my 2.6.18 kernel, I can't see them nor fdisk to them. fdisk still say can't open /dev/sdb. When I look a the proc fs I see this:

Code:

root@black_magic:~# cat /proc/partitions

major minor  #blocks  name



  8    0  117220824 sda

  8    1    987966 sda1

  8    2  58605120 sda2

  8    3  57625155 sda3

  8    16  293036184 sdb

  8    17  293033601 sdb1

I'm not sure what this means, so I decide to recompile my kernel with more options, but when I run lilo, get the following error:

Code:

root@black_magic:~# lilo

Warning: '/proc/partitions' does not match '/dev' directory structure.

    Name change: '/dev/sdb' -> '/dev/sdb'

Fatal: open /dev/sdb: No such file or directory

My lilo.conf file is:

Code:

# LILO configuration file

# generated by 'liloconfig'

#

# Start LILO global section

boot = /dev/sda

message = /boot/boot_message.txt

prompt

timeout = 1200

#default = 2.8.18_IVTV

# Override dangerous defaults that rewrite the partition table:

change-rules

  reset

# VESA framebuffer console @ 1024x768x256

vga = 773

# End LILO global section

# Linux bootable partition config begins

image = /boot/vmlinuz

  root = /dev/sda2

  label = 2.4.31

  read-only

image = /boot/vmlinuz-2.6.18

  root = /dev/sda2

  label = 2.6.18

  read-only

image = /boot/vmlinuz-2.6.18_trim

  root = /dev/sda2

  label = 2.6.18_trim

  read-only

image = /boot/vmlinuz-2.6.18_IVTV

  root = /dev/sda2

  label = 2.6.18_IVTV

  read-only

image = /boot/vmlinuz-2.6.18_IVTV_2

  root = /dev/sda2

  label = 2.6.18_IVTV_2

  read-only

# Linux bootable partition config ends

so i don't know what to do next, I might disconnect the second drive for a little bit.

Any suggest??

djgerbavore

Not much of an idea. At first glance it seemed to me a
conflict between /proc/partitions and devfs; but since
devfs isn't in 2.6.18 ...

Perhaps this thread will shed some light on your issue?