W
Wolfgang Draxinger
First I must apologize at the readers in the german NGs, that
this is a crosspost in english NGs with english text, but I want
to keep it in a single thread and spread it internationally; the
more people can read it, the higher the probability that someone
other who reads this has the same problems.
Last weekend I got the components for my new system, with the
motherboard being an Asus A8N-SLi Premium and 3 Maxtor 6V300F0
SATA (Diamondmax 10) HDDs for storage. The HDDs are connected to
the nForce4 SATA Controller and I got both Linux and Windows
installed without major problems. But I stumbled over some
strange bahaviour and I hope someone may have an idea on what's
going on.
The first and most annoying is, that after some resets (either
warm reboot, or reset by reset switch) some of the HDDs don't
get recognized. Thereafer only a complete poweroff/poweron will
make them get recognized again. I have not yet found a way to
reproduce this behaviour, it just happens sometime. Notable is,
that allthough it's not determined which HDDs will get not
recognized, after a reset the same HDDs doesn't get recognized
again. Also I never had experienced the case that all HDDs don't
get recognized. I first stumbled over this, after I've boot into
Linux and the "md" RAID-5 I created from _partitions_ on the
disks (the partitions are on exactly the same blocks on all
HDDs) was reported to be about to fail. This also indicates,
that it is not a pure BIOS problem, since Linux doesn't see the
HDDs either in the case this happens.
The second strangenes, not really a problem, but more a brain
twister are some discrepancies between the numbering of the HDDs
in the BIOS configuration, the boot sequence and the numbering
in by the operating systems. The mainboard has 4 SATA
connectors, numberes SATA 1 to SATA 4 (well, that's logical and
nothing else expected). Of course I connected my HDDs in the
order 1,2,3. The strange happend when I tried to boot the Linux
I had installed on /dev/sda, expecting that this would be the
device identified by the BIOS as SATA 1. However instead of SATA
1 my Linux seems to have found it's way to the HDD identified by
the BIOS as SATA 3. But now it comes: Windows get's booted from
BIOS SATA 1, but Linux sees it on /dev/sdb (the second HDD). And
to top it: Linux and Windows agree, that Linux lies on HDD 1,
Windows on HDD 2 and that the first 30GB on HDD 3 are still
unformated.
Okay, here comes a table to summarize:
#HDD: SATA connector used
#HDD | OS | BIOS |
-----+----+------+
1 | 2 | 3 |
-----+----+------+
2 | 3 | 2 |
-----+----+------+
3 | 1 | 1 |
And maybe it's getting even more weird if I connect a fourth HDD.
I'd like to do to see what happens, but unfortunately I got no
spare one.
And last but not least I got a question about the Sil 3114
controller SW-RAID BIOS. After I got the components I was
experimenting a bit with the components to see what fits my
needs the best. I also tried out to use the Sil 3114 RAID for
both Linux (using dmraid to map it to Linux md functionality)
and Windows, so that they would share the RAID. But in the end I
didn't like it. So I straightly rewired the HDDs to the nForce4
SATA controller without deleting the RAID from them. I expected,
that after putting fresh partition tables and filesystems on
them there would remain no rests from the RAID configuration.
But after the "HDD doesn't get recognized" problem I wanted to
try them on the Sil 3114, but magically the Sil saw them in a
RAID again; if I have the HDD not connected to the Sil it's RAID
BIOS shows no RAID config. So either the RAID configuration gets
stored somewhere in the CMOS or the RAID controller, or on a
part of the disk, where fdisk and mkfs/format don't get. The
question is, if I can delete the RAID in the Sil RAID BIOS while
having the HDDs connected without having the data on them fried
or not.
And before someone replies "use google": I did and got tons of
complaints about data corruption and other strange stuff with a
A8N Maxtor combination, but I've experienced none of those. Once
the system is running it's ultra stable and I got none of the
problems discribed on the pages google reports me.
Thanks in advance for every usefull idea, hint and awnser that I
get to my problems, oberservations and questions.
Wolfgang Draxinger
Output from lspci and relevant parts of hal-device and Linux
kernel log following (and please remove this in all replies,
it's really not neccesary to cite this), the kernel used is
Linux 2.6.15 Gentoo patchset R5:
### lspci ###
00:00.0 Memory controller: nVidia Corporation CK804 Memory
Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
00:02.0 USB Controller: nVidia Corporation CK804 USB Controller
(rev a2)
00:02.1 USB Controller: nVidia Corporation CK804 USB Controller
(rev a3)
00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA
Controller (rev f3)
00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA
Controller (rev f3)
00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev
a3)
00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
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
01:00.0 VGA compatible controller: nVidia Corporation GeForce
7800 GT (rev a1)
05:06.0 Multimedia audio controller: Creative Labs SB Audigy (rev
04)
05:06.1 Input device controller: Creative Labs SB Audigy
MIDI/Game port (rev 04)
05:06.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire
Port (rev 04)
05:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A
IEEE-1394a-2000 Controller (PHY/Link)
05:0c.0 Ethernet controller: Marvell Technology Group Ltd.
88E8001 Gigabit Ethernet Controller (rev 13)
### hal-device entries for HDD 1-3 ###
9: udi = '/org/freedesktop/Hal/devices/storage_serial_V6012QKG'
block.storage_device =
'/org/freedesktop/Hal/devices/storage_serial_V6012QKG' (string)
info.udi =
'/org/freedesktop/Hal/devices/storage_serial_V6012QKG' (string)
storage.serial = 'V6012QKG' (string)
info.category = 'storage' (string)
info.product = 'Maxtor 6V300F0' (string)
info.vendor = 'ATA' (string)
storage.physical_device =
'/org/freedesktop/Hal/devices/pci_10de_54_scsi_host_0_scsi_device_lun0' (string)
storage.lun = 0 (0x0) (int)
storage.drive_type = 'disk' (string)
storage.vendor = 'ATA' (string)
storage.model = 'Maxtor 6V300F0' (string)
storage.bus = 'scsi' (string)
block.minor = 0 (0x0) (int)
block.major = 8 (0x8) (int)
block.device = '/dev/sda' (string)
info.parent =
'/org/freedesktop/Hal/devices/pci_10de_54_scsi_host_0_scsi_device_lun0' (string)
linux.sysfs_path_device = '/sys/block/sda' (string)
linux.sysfs_path = '/sys/block/sda' (string)
12: udi = '/org/freedesktop/Hal/devices/storage_serial_V601J4XG'
storage.policy.should_mount = false (bool)
block.storage_device =
'/org/freedesktop/Hal/devices/storage_serial_V601J4XG' (string)
info.udi =
'/org/freedesktop/Hal/devices/storage_serial_V601J4XG' (string)
storage.serial = 'V601J4XG' (string)
info.product = 'Maxtor 6V300F0' (string)
info.vendor = 'ATA' (string)
storage.physical_device =
'/org/freedesktop/Hal/devices/pci_10de_55_scsi_host_0_scsi_device_lun0' (string)
storage.lun = 0 (0x0) (int)
storage.drive_type = 'disk' (string)
storage.vendor = 'ATA' (string)
storage.model = 'Maxtor 6V300F0' (string)
storage.bus = 'scsi' (string)
block.minor = 16 (0x10) (int)
block.major = 8 (0x8) (int)
block.device = '/dev/sdb' (string)
'/org/freedesktop/Hal/devices/pci_10de_55_scsi_host_0_scsi_device_lun0' (string)
linux.sysfs_path_device = '/sys/block/sdb' (string)
linux.sysfs_path = '/sys/block/sdb' (string)
15: udi = '/org/freedesktop/Hal/devices/storage_serial_V601N2WG'
block.storage_device =
'/org/freedesktop/Hal/devices/storage_serial_V601N2WG' (string)
info.udi =
'/org/freedesktop/Hal/devices/storage_serial_V601N2WG' (string)
storage.serial = 'V601N2WG' (string)
info.product = 'Maxtor 6V300F0' (string)
info.vendor = 'ATA' (string)
storage.physical_device =
'/org/freedesktop/Hal/devices/pci_10de_55_scsi_host_scsi_device_lun0' (string)
storage.lun = 0 (0x0) (int)
storage.drive_type = 'disk' (string)
storage.vendor = 'ATA' (string)
storage.model = 'Maxtor 6V300F0' (string)
storage.bus = 'scsi' (string)
block.minor = 32 (0x20) (int)
block.major = 8 (0x8) (int)
block.device = '/dev/sdc' (string)
'/org/freedesktop/Hal/devices/pci_10de_55_scsi_host_scsi_device_lun0' (string)
linux.sysfs_path_device = '/sys/block/sdc' (string)
linux.sysfs_path = '/sys/block/sdc' (string)
### Kernel log, SATA device enumeration ###
ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD800 irq 217
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD808 irq 217
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4773 85:7c69 86:3e01
87:4763 88:407f
ata1: dev 0 ATA-7, max UDMA/133, 586114704 sectors: LBA48
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
ata1: dev 0 configured for UDMA/133
scsi0 : sata_nv
ata2: no device found (phy stat 00000000)
scsi1 : sata_nv
Vendor: ATA Model: Maxtor 6V300F0 Rev: VA11
Type: Direct-Access ANSI SCSI revision:
05
ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 22
GSI 17 sharing vector 0xE1 and IRQ 17
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [APSJ] -> GSI 22
(level, low) -> IRQ 225
PCI: Setting latency timer of device 0000:00:08.0 to 64
ata3: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xC400 irq 225
ata4: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xC408 irq 225
ata3: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4773 85:7c69 86:3e01
87:4763 88:407f
ata3: dev 0 ATA-7, max UDMA/133, 586114704 sectors: LBA48
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
ata3: dev 0 configured for UDMA/133
scsi2 : sata_nv
ata4: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4773 85:7c69 86:3e01
87:4763 88:407f
ata4: dev 0 ATA-7, max UDMA/133, 586114704 sectors: LBA48
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
ata4: dev 0 configured for UDMA/133
scsi3 : sata_nv
Vendor: ATA Model: Maxtor 6V300F0 Rev: VA11
Type: Direct-Access ANSI SCSI revision:
05
Vendor: ATA Model: Maxtor 6V300F0 Rev: VA11
Type: Direct-Access ANSI SCSI revision:
05
SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4
sd 0:0:0:0: Attached scsi disk sda
SCSI device sdb: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sdb: drive cache: write back
sdb: sdb1 sdb2
sd 2:0:0:0: Attached scsi disk sdb
SCSI device sdc: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sdc: drive cache: write back
SCSI device sdc: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sdc: drive cache: write back
sdc: sdc1 sdc2
sd 3:0:0:0: Attached scsi disk sdc
--
this is a crosspost in english NGs with english text, but I want
to keep it in a single thread and spread it internationally; the
more people can read it, the higher the probability that someone
other who reads this has the same problems.
Last weekend I got the components for my new system, with the
motherboard being an Asus A8N-SLi Premium and 3 Maxtor 6V300F0
SATA (Diamondmax 10) HDDs for storage. The HDDs are connected to
the nForce4 SATA Controller and I got both Linux and Windows
installed without major problems. But I stumbled over some
strange bahaviour and I hope someone may have an idea on what's
going on.
The first and most annoying is, that after some resets (either
warm reboot, or reset by reset switch) some of the HDDs don't
get recognized. Thereafer only a complete poweroff/poweron will
make them get recognized again. I have not yet found a way to
reproduce this behaviour, it just happens sometime. Notable is,
that allthough it's not determined which HDDs will get not
recognized, after a reset the same HDDs doesn't get recognized
again. Also I never had experienced the case that all HDDs don't
get recognized. I first stumbled over this, after I've boot into
Linux and the "md" RAID-5 I created from _partitions_ on the
disks (the partitions are on exactly the same blocks on all
HDDs) was reported to be about to fail. This also indicates,
that it is not a pure BIOS problem, since Linux doesn't see the
HDDs either in the case this happens.
The second strangenes, not really a problem, but more a brain
twister are some discrepancies between the numbering of the HDDs
in the BIOS configuration, the boot sequence and the numbering
in by the operating systems. The mainboard has 4 SATA
connectors, numberes SATA 1 to SATA 4 (well, that's logical and
nothing else expected). Of course I connected my HDDs in the
order 1,2,3. The strange happend when I tried to boot the Linux
I had installed on /dev/sda, expecting that this would be the
device identified by the BIOS as SATA 1. However instead of SATA
1 my Linux seems to have found it's way to the HDD identified by
the BIOS as SATA 3. But now it comes: Windows get's booted from
BIOS SATA 1, but Linux sees it on /dev/sdb (the second HDD). And
to top it: Linux and Windows agree, that Linux lies on HDD 1,
Windows on HDD 2 and that the first 30GB on HDD 3 are still
unformated.
Okay, here comes a table to summarize:
#HDD: SATA connector used
#HDD | OS | BIOS |
-----+----+------+
1 | 2 | 3 |
-----+----+------+
2 | 3 | 2 |
-----+----+------+
3 | 1 | 1 |
And maybe it's getting even more weird if I connect a fourth HDD.
I'd like to do to see what happens, but unfortunately I got no
spare one.
And last but not least I got a question about the Sil 3114
controller SW-RAID BIOS. After I got the components I was
experimenting a bit with the components to see what fits my
needs the best. I also tried out to use the Sil 3114 RAID for
both Linux (using dmraid to map it to Linux md functionality)
and Windows, so that they would share the RAID. But in the end I
didn't like it. So I straightly rewired the HDDs to the nForce4
SATA controller without deleting the RAID from them. I expected,
that after putting fresh partition tables and filesystems on
them there would remain no rests from the RAID configuration.
But after the "HDD doesn't get recognized" problem I wanted to
try them on the Sil 3114, but magically the Sil saw them in a
RAID again; if I have the HDD not connected to the Sil it's RAID
BIOS shows no RAID config. So either the RAID configuration gets
stored somewhere in the CMOS or the RAID controller, or on a
part of the disk, where fdisk and mkfs/format don't get. The
question is, if I can delete the RAID in the Sil RAID BIOS while
having the HDDs connected without having the data on them fried
or not.
And before someone replies "use google": I did and got tons of
complaints about data corruption and other strange stuff with a
A8N Maxtor combination, but I've experienced none of those. Once
the system is running it's ultra stable and I got none of the
problems discribed on the pages google reports me.
Thanks in advance for every usefull idea, hint and awnser that I
get to my problems, oberservations and questions.
Wolfgang Draxinger
Output from lspci and relevant parts of hal-device and Linux
kernel log following (and please remove this in all replies,
it's really not neccesary to cite this), the kernel used is
Linux 2.6.15 Gentoo patchset R5:
### lspci ###
00:00.0 Memory controller: nVidia Corporation CK804 Memory
Controller (rev a3)
00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2)
00:02.0 USB Controller: nVidia Corporation CK804 USB Controller
(rev a2)
00:02.1 USB Controller: nVidia Corporation CK804 USB Controller
(rev a3)
00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2)
00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA
Controller (rev f3)
00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA
Controller (rev f3)
00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev a2)
00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev
a3)
00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3)
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
01:00.0 VGA compatible controller: nVidia Corporation GeForce
7800 GT (rev a1)
05:06.0 Multimedia audio controller: Creative Labs SB Audigy (rev
04)
05:06.1 Input device controller: Creative Labs SB Audigy
MIDI/Game port (rev 04)
05:06.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire
Port (rev 04)
05:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A
IEEE-1394a-2000 Controller (PHY/Link)
05:0c.0 Ethernet controller: Marvell Technology Group Ltd.
88E8001 Gigabit Ethernet Controller (rev 13)
### hal-device entries for HDD 1-3 ###
9: udi = '/org/freedesktop/Hal/devices/storage_serial_V6012QKG'
block.storage_device =
'/org/freedesktop/Hal/devices/storage_serial_V6012QKG' (string)
info.udi =
'/org/freedesktop/Hal/devices/storage_serial_V6012QKG' (string)
storage.serial = 'V6012QKG' (string)
info.category = 'storage' (string)
info.product = 'Maxtor 6V300F0' (string)
info.vendor = 'ATA' (string)
storage.physical_device =
'/org/freedesktop/Hal/devices/pci_10de_54_scsi_host_0_scsi_device_lun0' (string)
storage.lun = 0 (0x0) (int)
storage.drive_type = 'disk' (string)
storage.vendor = 'ATA' (string)
storage.model = 'Maxtor 6V300F0' (string)
storage.bus = 'scsi' (string)
block.minor = 0 (0x0) (int)
block.major = 8 (0x8) (int)
block.device = '/dev/sda' (string)
info.parent =
'/org/freedesktop/Hal/devices/pci_10de_54_scsi_host_0_scsi_device_lun0' (string)
linux.sysfs_path_device = '/sys/block/sda' (string)
linux.sysfs_path = '/sys/block/sda' (string)
12: udi = '/org/freedesktop/Hal/devices/storage_serial_V601J4XG'
storage.policy.should_mount = false (bool)
block.storage_device =
'/org/freedesktop/Hal/devices/storage_serial_V601J4XG' (string)
info.udi =
'/org/freedesktop/Hal/devices/storage_serial_V601J4XG' (string)
storage.serial = 'V601J4XG' (string)
info.product = 'Maxtor 6V300F0' (string)
info.vendor = 'ATA' (string)
storage.physical_device =
'/org/freedesktop/Hal/devices/pci_10de_55_scsi_host_0_scsi_device_lun0' (string)
storage.lun = 0 (0x0) (int)
storage.drive_type = 'disk' (string)
storage.vendor = 'ATA' (string)
storage.model = 'Maxtor 6V300F0' (string)
storage.bus = 'scsi' (string)
block.minor = 16 (0x10) (int)
block.major = 8 (0x8) (int)
block.device = '/dev/sdb' (string)
'/org/freedesktop/Hal/devices/pci_10de_55_scsi_host_0_scsi_device_lun0' (string)
linux.sysfs_path_device = '/sys/block/sdb' (string)
linux.sysfs_path = '/sys/block/sdb' (string)
15: udi = '/org/freedesktop/Hal/devices/storage_serial_V601N2WG'
block.storage_device =
'/org/freedesktop/Hal/devices/storage_serial_V601N2WG' (string)
info.udi =
'/org/freedesktop/Hal/devices/storage_serial_V601N2WG' (string)
storage.serial = 'V601N2WG' (string)
info.product = 'Maxtor 6V300F0' (string)
info.vendor = 'ATA' (string)
storage.physical_device =
'/org/freedesktop/Hal/devices/pci_10de_55_scsi_host_scsi_device_lun0' (string)
storage.lun = 0 (0x0) (int)
storage.drive_type = 'disk' (string)
storage.vendor = 'ATA' (string)
storage.model = 'Maxtor 6V300F0' (string)
storage.bus = 'scsi' (string)
block.minor = 32 (0x20) (int)
block.major = 8 (0x8) (int)
block.device = '/dev/sdc' (string)
'/org/freedesktop/Hal/devices/pci_10de_55_scsi_host_scsi_device_lun0' (string)
linux.sysfs_path_device = '/sys/block/sdc' (string)
linux.sysfs_path = '/sys/block/sdc' (string)
### Kernel log, SATA device enumeration ###
ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xD800 irq 217
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xD808 irq 217
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4773 85:7c69 86:3e01
87:4763 88:407f
ata1: dev 0 ATA-7, max UDMA/133, 586114704 sectors: LBA48
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
ata1: dev 0 configured for UDMA/133
scsi0 : sata_nv
ata2: no device found (phy stat 00000000)
scsi1 : sata_nv
Vendor: ATA Model: Maxtor 6V300F0 Rev: VA11
Type: Direct-Access ANSI SCSI revision:
05
ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 22
GSI 17 sharing vector 0xE1 and IRQ 17
ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [APSJ] -> GSI 22
(level, low) -> IRQ 225
PCI: Setting latency timer of device 0000:00:08.0 to 64
ata3: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xC400 irq 225
ata4: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xC408 irq 225
ata3: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4773 85:7c69 86:3e01
87:4763 88:407f
ata3: dev 0 ATA-7, max UDMA/133, 586114704 sectors: LBA48
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
ata3: dev 0 configured for UDMA/133
scsi2 : sata_nv
ata4: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4773 85:7c69 86:3e01
87:4763 88:407f
ata4: dev 0 ATA-7, max UDMA/133, 586114704 sectors: LBA48
nv_sata: Primary device added
nv_sata: Primary device removed
nv_sata: Secondary device added
nv_sata: Secondary device removed
ata4: dev 0 configured for UDMA/133
scsi3 : sata_nv
Vendor: ATA Model: Maxtor 6V300F0 Rev: VA11
Type: Direct-Access ANSI SCSI revision:
05
Vendor: ATA Model: Maxtor 6V300F0 Rev: VA11
Type: Direct-Access ANSI SCSI revision:
05
SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4
sd 0:0:0:0: Attached scsi disk sda
SCSI device sdb: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sdb: drive cache: write back
sdb: sdb1 sdb2
sd 2:0:0:0: Attached scsi disk sdb
SCSI device sdc: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sdc: drive cache: write back
SCSI device sdc: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sdc: drive cache: write back
sdc: sdc1 sdc2
sd 3:0:0:0: Attached scsi disk sdc
--