| View previous topic :: View next topic |
| Author |
Message |
Nori
n00b
Joined: 18 Nov 2004
Posts: 32
|
 Posted: Sat Dec 31, 2005 12:09 pm Post subject: sata-device recognised but not usable? |
 |
|
Hello everyone,
I'm trying to get my sata-hdd to work under an Asrock 939Dual-SATA2 board. It seems that the device is properly recognised by the kernel, but I can't find a device like /dev/sd0 to use my hdd. Perhaps I overlooked something simple, but I'm not very experienced with sata devices under linux. (hda and hdb are by two ide-disks)
dmesg:
| Code: |
...
Probing IDE interface ide0...
input: AT Translated Set 2 keyboard on isa0060/serio0
hda: SAMSUNG SP1614N, ATA DISK drive
hdb: Maxtor 34098H4, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: LITE-ON DVDRW SOHW-1653S, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 1024KiB
hda: 312581808 sectors (160041 MB) w/8192KiB Cache, CHS=19457/255/63, UDMA(100)
hda: cache flushes supported
hda: hda1 hda2
hdb: max request size: 128KiB
hdb: 80043264 sectors (40982 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hdb: cache flushes not supported
hdb: hdb1 hdb2 hdb3 < hdb5 >
hdc: ATAPI 63X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
libata version 1.12 loaded.
ACPI: PCI Interrupt 0000:00:12.1[A] -> GSI 19 (level, low) -> IRQ 217
ata1: SATA max UDMA/133 cmd 0xEC00 ctl 0xE082 bmdma 0xD880 irq 217
ata2: SATA max UDMA/133 cmd 0xE000 ctl 0xDC02 bmdma 0xD888 irq 217
ata1: no device found (phy stat 00000000)
scsi0 : sata_uli
ata2: dev 0 cfg 49:2f00 82:74eb 83:7fea 84:4023 85:74e8 86:3c02 87:4023 88:003f
ata2: dev 0 ATA, max UDMA/100, 160836480 sectors: lba48
ata2: dev 0 configured for UDMA/100
scsi1 : sata_uli
Vendor: ATA Model: HDS722580VLSA80 Rev: V32O
Type: Direct-Access ANSI SCSI revision: 05
usbmon: debugfs is not available
... |
lspci:
| Code: |
00:00.0 Host bridge: ALi Corporation M1695 K8 Northbridge [PCI Express and HyperTransport]
00:01.0 PCI bridge: ALi Corporation PCI Express Root Port
00:02.0 PCI bridge: ALi Corporation PCI Express Root Port
00:04.0 Host bridge: ALi Corporation M1689 K8 Northbridge [Super K8 Single Chip]
00:05.0 PCI bridge: ALi Corporation AGP8X Controller
00:06.0 PCI bridge: ALi Corporation M5249 HTT to PCI Bridge
00:07.0 ISA bridge: ALi Corporation M1563 HyperTransport South Bridge (rev 70)
00:07.1 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
00:08.0 Multimedia audio controller: ALi Corporation M5455 PCI AC-Link Controller Audio Device (rev 20)
00:11.0 Ethernet controller: ALi Corporation M5263 Ethernet Controller (rev 40)
00:12.0 IDE interface: ALi Corporation M5229 IDE (rev c7)
00:12.1 IDE interface: ALi Corporation ULi 5289 SATA (rev 10)
00:13.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:13.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:13.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:13.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
03:00.0 VGA compatible controller: nVidia Corporation NV40 [GeForce 6800 GT] (rev a1)
04:07.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
04:07.1 Input device controller: Creative Labs SB Audigy MIDI/Game port (rev 04)
04:07.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)
|
ls /dev/disk/* -la:
| Code: |
/dev/disk/by-id:
total 0
drwxr-xr-x 2 root root 180 Dec 31 11:20 .
drwxr-xr-x 6 root root 120 Dec 31 11:03 ..
lrwxrwxrwx 1 root root 9 Dec 31 11:03 ata-Maxtor_34098H4_L41R949C -> ../../hdb
lrwxrwxrwx 1 root root 10 Dec 31 11:03 ata-Maxtor_34098H4_L41R949C-part1 -> ../../hdb1
lrwxrwxrwx 1 root root 10 Dec 31 11:03 ata-Maxtor_34098H4_L41R949C-part2 -> ../../hdb2
lrwxrwxrwx 1 root root 10 Dec 31 11:03 ata-Maxtor_34098H4_L41R949C-part5 -> ../../hdb5
lrwxrwxrwx 1 root root 9 Dec 31 11:03 ata-SAMSUNG_SP1614N_S016J10X636696 -> ../../hda
lrwxrwxrwx 1 root root 10 Dec 31 11:03 ata-SAMSUNG_SP1614N_S016J10X636696-part1 -> ../../hda1
lrwxrwxrwx 1 root root 10 Dec 31 11:03 ata-SAMSUNG_SP1614N_S016J10X636696-part2 -> ../../hda2
/dev/disk/by-label:
total 0
drwxr-xr-x 2 root root 80 Dec 31 11:03 .
drwxr-xr-x 6 root root 120 Dec 31 11:03 ..
lrwxrwxrwx 1 root root 10 Dec 31 11:03 MEDIA -> ../../hda2
lrwxrwxrwx 1 root root 10 Dec 31 11:03 system -> ../../hda1
/dev/disk/by-path:
total 0
drwxr-xr-x 2 root root 180 Dec 31 11:20 .
drwxr-xr-x 6 root root 120 Dec 31 11:03 ..
lrwxrwxrwx 1 root root 9 Dec 31 11:03 pci-0000:00:12.0-ide-0:0 -> ../../hda
lrwxrwxrwx 1 root root 10 Dec 31 11:03 pci-0000:00:12.0-ide-0:0-part1 -> ../../hda1
lrwxrwxrwx 1 root root 10 Dec 31 11:03 pci-0000:00:12.0-ide-0:0-part2 -> ../../hda2
lrwxrwxrwx 1 root root 9 Dec 31 11:03 pci-0000:00:12.0-ide-0:1 -> ../../hdb
lrwxrwxrwx 1 root root 10 Dec 31 11:03 pci-0000:00:12.0-ide-0:1-part1 -> ../../hdb1
lrwxrwxrwx 1 root root 10 Dec 31 11:03 pci-0000:00:12.0-ide-0:1-part2 -> ../../hdb2
lrwxrwxrwx 1 root root 10 Dec 31 11:03 pci-0000:00:12.0-ide-0:1-part5 -> ../../hdb5
/dev/disk/by-uuid:
total 0
drwxr-xr-x 2 root root 120 Dec 31 11:03 .
drwxr-xr-x 6 root root 120 Dec 31 11:03 ..
lrwxrwxrwx 1 root root 10 Dec 31 11:03 042d5386-3c43-4fd6-b433-915f1ec709bb -> ../../hdb2
lrwxrwxrwx 1 root root 10 Dec 31 11:03 1254E01854DFFC7B -> ../../hda2
lrwxrwxrwx 1 root root 10 Dec 31 11:03 40E89570E89564C6 -> ../../hda1
lrwxrwxrwx 1 root root 10 Dec 31 11:03 b35f6a8a-251a-4cfa-a56f-33ba85d63afe -> ../../hdb1
|
|
|
| Back to top |
|
 |
agent_jdh
Veteran
Joined: 08 Aug 2002
Posts: 1783
Location: Scotland
|
| Posted: Sat Dec 31, 2005 12:20 pm Post subject: |
|
|
If you're using the libata driver (which you should be), the SATA device should be e.g. /dev/sdaX (where X is the partition no.), e.g. /dev/sda0, not /dev/sd0.
EDIT: Could you post the relevant sections of your kernel config?
_________________
Jingle Jangle Jewellery |
|
| Back to top |
|
|
widan
Veteran
Joined: 07 Jun 2005
Posts: 1512
Location: Paris, France
|
| Posted: Sat Dec 31, 2005 2:56 pm Post subject: |
|
|
| If you built SATA support as modules, check that sd_mod is loaded (it's the SCSI disk device driver). If you have SATA built in, check that you have "SCSI disk support" selected in menuconfig. |
|
| Back to top |
|
|
Nori
n00b
Joined: 18 Nov 2004
Posts: 32
|
| Posted: Sat Dec 31, 2005 4:08 pm Post subject: |
|
|
Thanks for the quick help.
I didn't realize that this is actually a SCSI-disk for the kernel. Support for disk-drives was not enabled.
Happy new year,
Nori |
|
| Back to top |
|
|
mmbrothers
Apprentice
Joined: 24 Dec 2005
Posts: 224
Location: Boston
|
| Posted: Sat Dec 31, 2005 4:25 pm Post subject: |
|
|
| agent_jdh wrote: | If you're using the libata driver (which you should be), the SATA device should be e.g. /dev/sdaX (where X is the partition no.), e.g. /dev/sda0, not /dev/sd0.
EDIT: Could you post the relevant sections of your kernel config? |
Also there is no such device as /dev/sda0. Numbering of partitions starts at 1. |
|
| Back to top |
|
|
agent_jdh
Veteran
Joined: 08 Aug 2002
Posts: 1783
Location: Scotland
|
| Posted: Sat Dec 31, 2005 5:10 pm Post subject: |
|
|
| mmbrothers wrote: | | agent_jdh wrote: | If you're using the libata driver (which you should be), the SATA device should be e.g. /dev/sdaX (where X is the partition no.), e.g. /dev/sda0, not /dev/sd0.
EDIT: Could you post the relevant sections of your kernel config? |
Also there is no such device as /dev/sda0. Numbering of partitions starts at 1. |
Correct. Just a typo.
_________________
Jingle Jangle Jewellery |
|
| Back to top |
|
|
|
Kernel & Hardware
