1 |
Stefan G. Weichinger: |
2 |
> Am 05.10.20 um 21:32 schrieb karl@××××××××.se: |
3 |
... |
4 |
> What do you think, is 2 TB maybe too big for the controller? |
5 |
|
6 |
>>> 0a:0e.0 RAID bus controller: Adaptec AAC-RAID |
7 |
|
8 |
This doesn't really tells us which controller it is, try with |
9 |
|
10 |
lspci -s 0a:0e.0 -nn |
11 |
|
12 |
In the kernel source one can then find drivers/scsi/aacraid/linit.h, |
13 |
and since lsscsi says ICP, my guess it is one of theese below. |
14 |
When we know which one, one can try to check for issues. |
15 |
|
16 |
/* |
17 |
* Because of the way Linux names scsi devices, the order in this table has |
18 |
* become important. Check for on-board Raid first, add-in cards second. |
19 |
* |
20 |
* Note: The last field is used to index into aac_drivers below. |
21 |
*/ |
22 |
static const struct pci_device_id aac_pci_tbl[] = { |
23 |
... |
24 |
{ 0x9005, 0x0286, 0x9005, 0x029e, 0, 0, 25 }, /* ICP9024RO (Lancer) */ |
25 |
{ 0x9005, 0x0286, 0x9005, 0x029f, 0, 0, 26 }, /* ICP9014RO (Lancer) */ |
26 |
{ 0x9005, 0x0286, 0x9005, 0x02a0, 0, 0, 27 }, /* ICP9047MA (Lancer) */ |
27 |
{ 0x9005, 0x0286, 0x9005, 0x02a1, 0, 0, 28 }, /* ICP9087MA (Lancer) */ |
28 |
{ 0x9005, 0x0286, 0x9005, 0x02a3, 0, 0, 29 }, /* ICP5445AU (Hurricane44) */ |
29 |
{ 0x9005, 0x0285, 0x9005, 0x02a4, 0, 0, 30 }, /* ICP9085LI (Marauder-X) */ |
30 |
{ 0x9005, 0x0285, 0x9005, 0x02a5, 0, 0, 31 }, /* ICP5085BR (Marauder-E) */ |
31 |
{ 0x9005, 0x0286, 0x9005, 0x02a6, 0, 0, 32 }, /* ICP9067MA (Intruder-6) */ |
32 |
... |
33 |
}; |
34 |
MODULE_DEVICE_TABLE(pci, aac_pci_tbl); |
35 |
|
36 |
/* |
37 |
* dmb - For now we add the number of channels to this structure. |
38 |
* In the future we should add a fib that reports the number of channels |
39 |
* for the card. At that time we can remove the channels from here |
40 |
*/ |
41 |
static struct aac_driver_ident aac_drivers[] = { |
42 |
... |
43 |
{ aac_rkt_init, "aacraid", "ICP ", "ICP9024RO ", 2 }, /* ICP9024RO (Lancer) */ |
44 |
{ aac_rkt_init, "aacraid", "ICP ", "ICP9014RO ", 1 }, /* ICP9014RO (Lancer) */ |
45 |
{ aac_rkt_init, "aacraid", "ICP ", "ICP9047MA ", 1 }, /* ICP9047MA (Lancer) */ |
46 |
{ aac_rkt_init, "aacraid", "ICP ", "ICP9087MA ", 1 }, /* ICP9087MA (Lancer) */ |
47 |
{ aac_rkt_init, "aacraid", "ICP ", "ICP5445AU ", 1 }, /* ICP5445AU (Hurricane44) */ |
48 |
{ aac_rx_init, "aacraid", "ICP ", "ICP9085LI ", 1 }, /* ICP9085LI (Marauder-X) */ |
49 |
{ aac_rx_init, "aacraid", "ICP ", "ICP5085BR ", 1 }, /* ICP5085BR (Marauder-E) */ |
50 |
{ aac_rkt_init, "aacraid", "ICP ", "ICP9067MA ", 1 }, /* ICP9067MA (Intruder-6) */ |
51 |
... |
52 |
}; |
53 |
|
54 |
> > What do sg_verify /dev/sg11 return ? |
55 |
> nothing |
56 |
|
57 |
Well, you have to check the return status: echo $? |
58 |
|
59 |
> > Can you do sg_dd if=foo of=/dev/sg11 count=10 and get it back with |
60 |
> > sg_dd if=/dev/sg11 of=bar count=10, with cmp foo bar; echo $? |
61 |
> > returning 0 ? |
62 |
> Yes, that works. |
63 |
|
64 |
Then it seems the drive itself is ok. |
65 |
|
66 |
Regards, |
67 |
/Karl Hammar |