SATA on 2.6.8.1 recognized but not mounted

Clojster · 10-18-2004, 11:31 AM

I know it was here before, but I didn't find any solution.
Here is my problem: libata seems to detect and load my SATA disc correctly, but I don't know where do I have it now. It's not on the usual place /dev/hde1 or whatewer. It's not on the /dev/scsi1 too...

Here is my dmesg:

Code:

libata version 1.02 loaded.
sata_sil version 0.54
ACPI: PCI interrupt 0000:01:0b.0[A] -> GSI 18 (level, high) -> IRQ 18
ata1: SATA max UDMA/100 cmd 0xF8996080 ctl 0xF899608A bmdma 0xF8996000 irq 18
ata2: SATA max UDMA/100 cmd 0xF89960C0 ctl 0xF89960CA bmdma 0xF8996008 irq 18
ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003 88:207f
ata1: dev 0 ATA, max UDMA/133, 390721968 sectors: lba48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: no device found (phy stat 00000000)
scsi1 : sata_sil
  Vendor: ATA       Model: ST3200822AS       Rev: 3.01
  Type:   Direct-Access                      ANSI SCSI revision: 05

Do you know where could be the problem?

Thanks.
-jakub

Linux24 · 10-18-2004, 12:50 PM

Fedora Core 2 put my SATA here:

/dev/sda

Clojster · 10-18-2004, 06:25 PM

thanks for reply, but no /dev/sda in there

Linux24 · 10-18-2004, 11:21 PM

Did you try looking in /etc/fstab to see what it says?

You might also try going to su and then typing

fdisk -l

Mine looks like this:

Code:

Disk /dev/sda: 80.0 GB, 80026361856 bytes
16 heads, 63 sectors/track, 155061 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1       40641    20482843+   7  HPFS/NTFS
/dev/sda2           40641      155056    57665317+   f  W95 Ext'd (LBA)
/dev/sda5           40641       60961    10241406   83  Linux
/dev/sda6           60962       61997      522081   82  Linux swap
/dev/sda7           61997      114432    26426893+  83  Linux
/dev/sda8          114432      155056    20474811    b  W95 FAT32

Are you booting off of this disk?

Clojster · 10-19-2004, 01:15 PM

Thanks for your input!

fdisk -l says this:

Code:

Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1        3187    25599546    7  HPFS/NTFS
/dev/hda2            3188       19457   130688775    f  W95 Ext'd (LBA)
/dev/hda5            3188       17648   116157951    7  HPFS/NTFS
/dev/hda6           17649       19317    13406211   83  Linux
/dev/hda7           19318       19457     1124518+  82  Linux swap

Disk /dev/hdb: 60.0 GB, 60022480896 bytes
16 heads, 63 sectors/track, 116301 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hdb1   *          16      116296    58605151+   f  W95 Ext'd (LBA)
/dev/hdb5              17      116296    58605120    b  W95 FAT32

I don't know why, but my SATA disk ain't listed here...
I have configured my kernel with libata driver for SATA. This way it finds my SATA disk very quickly (according to my dmesg pasted here on my first post). The other way (without libata) it just searches for very long time and my booting is very very slow.
But as you can see - it isnt listed under /dev

Oh, and no - I'm not booting off of this disk...

What do you suggest?
-jakub

Linux24 · 10-19-2004, 01:23 PM

Well, let's see, one thing at a time...

When it boots very slow, does it see the SATA disk drive? Do you only have one SATA disk drive or do you have two plugged in?

Have you checked the cable to make sure it is plugged in good?

Clojster · 10-19-2004, 02:50 PM

Maybe you missunderstood me.
Let me explain:

With precompiled kernel (2.4.26) it boots okay and find SATA disk well. (It's attached to /dev/hde). But this precompiled kernel uses the other way than with "libata" to find SATA disks. And that way is pretty slow... it is checking each SATA slot i have there and as i have got only one SATA disk, it hangs for about one minute when probing that channel where no disk is connected. And I don't want that... it's slow.

But with "libata" driver compiled into kernel my system says that thing I have posted in my first post. It finds it okay but I don't have any /dev/blabla which could be my SATA disk.

In /proc/scsi I have indentifier of my SATA disk and it says the same thing as I posted in first post.

Linux24 · 10-20-2004, 11:23 AM

I only have one SATA disk as well, and my boot times are slow as it tries to probe for the second drive (it assumes it is a RAID instead of just a different IDE port).

Add this to your boot manager append line:

hdg=none

and it will stop probing for the second drive.

On yours it might not consider it hdg, so check /var/logs for the failure message to find the second drive during one of your slow boots and you'll see what the dev is called.

Clojster · 10-20-2004, 03:00 PM

ok, thanks a lot... I will do this.

Clojster · 10-21-2004, 04:38 PM

Quote:

Originally posted by Linux24
....
Add this to your boot manager append line:

hdg=none

and it will stop probing for the second drive.

Can you please post here how your lilo.conf looks like? I don't know where to put that hdg=none nor the correct syntax for it...
When I put it just like that under line where is defined the boot partition, I get error message that "token hdg unknown" or something simillar.

Thanks for your help.

Linux24 · 10-22-2004, 02:16 PM

image=/boot/vmlinuz-2.6.5-1.358
label=linux
initrd=/boot/initrd-2.6.5-1.358.img
read-only
append="rhgb quiet root=LABEL=/"

Change it to this:

image=/boot/vmlinuz-2.6.5-1.358
label=linux
initrd=/boot/initrd-2.6.5-1.358.img
read-only
append="rhgb quiet root=LABEL=/ hdg=none"

But hdg will only work if that is the dev that lilo and your bios think your 2nd SATA live on. Check the boot time error message in your logs in /var and you'll see what it is called if you grep for "failed"