(était iSCSI)
Alors, sur notre contrôleur raid matériel, un lspci donne :
RAID bus controller: Intel Corporation 82801 SATA Controller [RAID mode]
(rev 05)
Et dmesg donne :
Apr 13 14:40:33 anna[4981]: DEBUG: retrieving partman-auto-crypto 22
Apr 13 14:40:33 anna[4981]: DEBUG: retrieving partman-crypto 81
Apr 13 14:40:34 kernel: [ 291.484465] raid6: sse2x1 9405 MB/s
Apr 13 14:40:34 kernel: [ 291.552431] raid6: sse2x2 12421 MB/s
Apr 13 14:40:34 kernel: [ 291.620408] raid6: sse2x4 14683 MB/s
Apr 13 14:40:34 kernel: [ 291.620409] raid6: using algorithm sse2x4
(14683 MB/s)
Apr 13 14:40:34 kernel: [ 291.620410] raid6: using ssse3x2 recovery
algorithm
Apr 13 14:40:34 kernel: [ 291.620599] xor: automatically using best
checksumming function:
Apr 13 14:40:34 kernel: [ 291.660396] avx : 27073.000 MB/sec
Apr 13 14:40:34 kernel: [ 291.663671] Btrfs loaded
Apr 13 14:40:34 kernel: [ 291.671371] JFS: nTxBlock = 8192, nTxLock =
65536
Apr 13 14:40:34 kernel: [ 291.679022] SGI XFS with ACLs, security
attributes, realtime, large block/inode numbers, no debug enabled
Apr 13 14:40:35 kernel: [ 292.062065] md: md127 stopped.
Apr 13 14:40:35 kernel: [ 292.063324] sda: sda1 sda2
Apr 13 14:40:35 md-devices: mdadm: Container /dev/md/imsm0 has been
assembled with 2 drives
Apr 13 14:40:35 kernel: [ 292.064864] sdb: sdb1 sdb2
Apr 13 14:40:35 kernel: [ 292.066981] md: bind<sdb>
Apr 13 14:40:35 kernel: [ 292.067132] md: bind<sda>
Apr 13 14:40:40 kernel: [ 297.394628] device-mapper: uevent: version
1.0.3
Apr 13 14:40:40 kernel: [ 297.394701] device-mapper: ioctl:
4.27.0-ioctl (2013-10-30) initialised: dm-devel@???
Apr 13 14:40:40 partman: No matching physical volumes found
Apr 13 14:40:40 partman: Reading all physical volumes. This may take
a while...
Apr 13 14:40:40 partman: No volume groups found
Apr 13 14:40:40 partman-lvm: No volume groups found
Apr 13 14:40:40 kernel: [ 297.417866] sda: sda1 sda2
Apr 13 14:40:40 kernel: [ 297.418739] sdb: sdb1 sdb2
Apr 13 14:40:45 kernel: [ 302.426845] Loading iSCSI transport class
v2.0-870.
Apr 13 14:40:45 kernel: [ 302.428393] iscsi: registered transport (tcp)
D'après lspci le contrôleur est supporté par le driver noyau ahci, qui
pour sa part a l'air satisfait :
Apr 13 14:35:45 kernel: [ 0.459760] ahci 0000:00:1f.2: version 3.0
Apr 13 14:35:45 kernel: [ 0.459864] ahci 0000:00:1f.2: irq 42 for
MSI/MSI-X
Apr 13 14:35:45 kernel: [ 0.473073] ahci 0000:00:1f.2: AHCI
0001.0300 32 slots 6 ports 6 Gbps 0x7 impl RAID mode
Apr 13 14:35:45 kernel: [ 0.473421] ahci 0000:00:1f.2: flags: 64bit
ncq pm led clo pio slum part ems apst
Apr 13 14:35:45 kernel: [ 0.489671] scsi0 : ahci
Apr 13 14:35:45 kernel: [ 0.490319] scsi1 : ahci
Apr 13 14:35:45 kernel: [ 0.490913] scsi2 : ahci
Apr 13 14:35:45 kernel: [ 0.491404] scsi3 : ahci
Apr 13 14:35:45 kernel: [ 0.491880] scsi4 : ahci
Apr 13 14:35:45 kernel: [ 0.492313] scsi5 : ahci
Apr 13 14:35:45 kernel: [ 0.492655] ata1: SATA max UDMA/133 abar
m2048@0xf7d26000 port 0xf7d26100 irq 42
Apr 13 14:35:45 kernel: [ 0.492983] ata2: SATA max UDMA/133 abar
m2048@0xf7d26000 port 0xf7d26180 irq 42
Apr 13 14:35:45 kernel: [ 0.493317] ata3: SATA max UDMA/133 abar
m2048@0xf7d26000 port 0xf7d26200 irq 42
Apr 13 14:35:45 kernel: [ 0.493630] ata4: DUMMY
Apr 13 14:35:45 kernel: [ 0.493940] ata5: DUMMY
Apr 13 14:35:45 kernel: [ 0.494245] ata6: DUMMY
Ça vous parle ? Du coup, pourquoi l'installeur debian butte ?
Merci de vos lumières.
PS : le copain a pu obtenir ces infos en bootant un truc qui fait serveur
et permet de voir les logs et le matos (je ne connais pas le nom de
l'outil)...
--
Frédéric
