1 |
Hello all, |
2 |
|
3 |
I have a server (in another country) running Gentoo with 3.17.7-hardened-r1. |
4 |
It has a "RAID bus controller: Areca Technology Corp. ARC-1110 4-Port PCI-X |
5 |
to SATA RAID Controller" (17d3:1110). |
6 |
|
7 |
I have no physical access to it, and only a serial console and Debian |
8 |
rescue image to recover with). |
9 |
I don't have any access or info about the settings on the RAID controller |
10 |
(unless I can get them from the OS). |
11 |
|
12 |
This works well enough most of the time. (I do get some random hangs which |
13 |
I have to hard reset to recover from). |
14 |
|
15 |
I tried updating to linux-4.4.2-hardened (with the same kernel .config) but |
16 |
get the following error upon booting |
17 |
|
18 |
[ 35.805083] arcmsr0: abort device command of scsi id = 0 lun = 0 |
19 |
[ 35.817201] arcmsr0: scsi id = 0 lun = 0 ccb = '0xffff8800d5120800' poll |
20 |
command abort successfully |
21 |
[ 35.835617] arcmsr0: abort device command of scsi id = 0 lun = 0 |
22 |
[ 35.847700] arcmsr0: abort device command of scsi id = 0 lun = 0 |
23 |
[ 35.859783] arcmsr0: abort device command of scsi id = 0 lun = 0 |
24 |
[ 35.871870] arcmsr0: abort device command of scsi id = 0 lun = 0 |
25 |
[ 35.883953] arcmsr0: abort device command of scsi id = 0 lun = 0 |
26 |
[ 35.896035] arcmsr0: abort device command of scsi id = 0 lun = 0 |
27 |
[ 35.908117] arcmsr0: abort device command of scsi id = 0 lun = 0 |
28 |
[ 35.920199] arcmsr0: abort device command of scsi id = 0 lun = 0 |
29 |
[ 35.932283] arcmsr0: abort device command of scsi id = 0 lun = 0 |
30 |
[ 35.944364] arcmsr0: abort device command of scsi id = 0 lun = 0 |
31 |
[ 35.956446] arcmsr0: abort device command of scsi id = 0 lun = 0 |
32 |
[ 35.968529] arcmsr0: abort device command of scsi id = 0 lun = 0 |
33 |
[ 35.980611] arcmsr0: abort device command of scsi id = 0 lun = 0 |
34 |
[ 35.992693] arcmsr0: abort device command of scsi id = 0 lun = 0 |
35 |
[ 36.004775] arcmsr0: abort device command of scsi id = 0 lun = 0 |
36 |
[ 36.016858] arcmsr0: abort device command of scsi id = 0 lun = 0 |
37 |
[ 36.028939] arcmsr0: abort device command of scsi id = 0 lun = 0 |
38 |
[ 36.041021] arcmsr0: abort device command of scsi id = 0 lun = 0 |
39 |
[ 36.053102] arcmsr0: abort device command of scsi id = 0 lun = 0 |
40 |
[ 36.065187] arcmsr0: abort device command of scsi id = 0 lun = 0 |
41 |
[ 36.077269] arcmsr0: abort device command of scsi id = 0 lun = 0 |
42 |
[ 36.089351] arcmsr0: abort device command of scsi id = 0 lun = 0 |
43 |
[ 36.101439] arcmsr0: abort device command of scsi id = 0 lun = 0 |
44 |
[ 36.113543] arcmsr: executing bus reset eh.....num_resets = 0, |
45 |
num_aborts = 24 |
46 |
[ 36.128326] arcmsr0: executing hw bus reset ..... |
47 |
[ 49.149028] arcmsr0: waiting for hw bus reset return, retry=0 |
48 |
[ 59.160983] arcmsr0: waiting for hw bus reset return, retry=1 |
49 |
[ 69.172962] arcmsr0: waiting for hw bus reset return, retry=2 |
50 |
[ 79.184902] arcmsr0: waiting for hw bus reset return, retry=3 |
51 |
[ 89.212917] Areca RAID Controller0: Model ARC-1110, F/W V1.49 2010-12-02 |
52 |
[ 89.240861] arcmsr: scsi bus reset eh returns with success |
53 |
[ 96.108524] random: nonblocking pool is initialized |
54 |
[ 109.252788] arcmsr0: abort device command of scsi id = 0 lun = 0 |
55 |
[ 109.264881] arcmsr0: scsi id = 0 lun = 0 ccb = '0xffff8800d5120e80' poll |
56 |
command abort successfully |
57 |
[ 109.283294] sd 0:0:0:0: Device offlined - not ready after error recovery |
58 |
[ 109.296764] sd 0:0:0:0: Device offlined - not ready after error recovery |
59 |
[ 109.310231] sd 0:0:0:0: Device offlined - not ready after error recovery |
60 |
[ 109.323700] sd 0:0:0:0: Device offlined - not ready after error recovery |
61 |
[ 109.337176] sd 0:0:0:0: Device offlined - not ready after error recovery |
62 |
[ 109.350645] sd 0:0:0:0: Device offlined - not ready after error recovery |
63 |
[ 109.364111] sd 0:0:0:0: Device offlined - not ready after error recovery |
64 |
[ 109.377580] sd 0:0:0:0: Device offlined - not ready after error recovery |
65 |
[ 109.391048] sd 0:0:0:0: Device offlined - not ready after error recovery |
66 |
[ 109.404517] sd 0:0:0:0: Device offlined - not ready after error recovery |
67 |
[ 109.417986] sd 0:0:0:0: Device offlined - not ready after error recovery |
68 |
[ 109.431455] sd 0:0:0:0: Device offlined - not ready after error recovery |
69 |
[ 109.444924] sd 0:0:0:0: Device offlined - not ready after error recovery |
70 |
[ 109.458393] sd 0:0:0:0: Device offlined - not ready after error recovery |
71 |
[ 109.471862] sd 0:0:0:0: Device offlined - not ready after error recovery |
72 |
[ 109.485330] sd 0:0:0:0: Device offlined - not ready after error recovery |
73 |
[ 109.498799] sd 0:0:0:0: Device offlined - not ready after error recovery |
74 |
[ 109.512267] sd 0:0:0:0: Device offlined - not ready after error recovery |
75 |
[ 109.525736] sd 0:0:0:0: Device offlined - not ready after error recovery |
76 |
[ 109.539206] sd 0:0:0:0: Device offlined - not ready after error recovery |
77 |
[ 109.552675] sd 0:0:0:0: Device offlined - not ready after error recovery |
78 |
[ 109.566144] sd 0:0:0:0: Device offlined - not ready after error recovery |
79 |
[ 109.579612] sd 0:0:0:0: Device offlined - not ready after error recovery |
80 |
[ 109.593087] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK |
81 |
driverbyte=DRIVER_TIMEOUT |
82 |
[ 109.610116] sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 00 00 08 af 00 |
83 |
00 08 00 |
84 |
[ 109.624888] blk_update_request: I/O error, dev sda, sector 2223 |
85 |
[ 109.636802] sd 0:0:0:0: rejecting I/O to offline device |
86 |
[ 109.647324] sd 0:0:0:0: [sda] killing request |
87 |
[ 109.656122] sd 0:0:0:0: [sda] FAILED Result: hostbyte=DID_NO_CONNECT |
88 |
driverbyte=DRIVER_OK |
89 |
[ 109.672630] sd 0:0:0:0: [sda] CDB: Read(10) 28 00 00 00 08 5f 00 00 08 00 |
90 |
[ 109.686270] blk_update_request: I/O error, dev sda, sector 2143 |
91 |
[ 109.698195] sd 0:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_OK |
92 |
driverbyte=DRIVER_TIMEOUT |
93 |
[ 109.698201] EXT4-fs error (device sda1): __ext4_get_inode_loc:3981: |
94 |
inode #8: block 260: comm swapper/0: unable to read itable block |
95 |
[ 109.698213] sd 0:0:0:0: rejecting I/O to offline device |
96 |
[ 109.698222] EXT4-fs (sda1): no journal found |
97 |
[ 109.758504] sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 00 00 08 b7 00 |
98 |
00 08 00 |
99 |
[ 109.773453] blk_update_request: I/O error, dev sda, sector 2231 |
100 |
[ 109.785376] sd 0:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK |
101 |
driverbyte=DRIVER_TIMEOUT |
102 |
[ 109.802578] sd 0:0:0:0: [sda] tag#11 CDB: Read(10) 28 00 00 00 08 bf 00 |
103 |
00 08 00 |
104 |
[ 109.817526] blk_update_request: I/O error, dev sda, sector 2239 |
105 |
[ 109.829449] sd 0:0:0:0: [sda] tag#12 FAILED Result: hostbyte=DID_OK |
106 |
driverbyte=DRIVER_TIMEOUT |
107 |
[ 109.846652] sd 0:0:0:0: [sda] tag#12 CDB: Read(10) 28 00 00 00 08 c7 00 |
108 |
00 08 00 |
109 |
[ 109.861601] blk_update_request: I/O error, dev sda, sector 2247 |
110 |
[ 109.873522] sd 0:0:0:0: [sda] tag#13 FAILED Result: hostbyte=DID_OK |
111 |
driverbyte=DRIVER_TIMEOUT |
112 |
[ 109.890726] sd 0:0:0:0: [sda] tag#13 CDB: Read(10) 28 00 00 00 08 cf 00 |
113 |
00 08 00 |
114 |
[ 109.905676] blk_update_request: I/O error, dev sda, sector 2255 |
115 |
[ 109.917599] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK |
116 |
driverbyte=DRIVER_TIMEOUT |
117 |
[ 109.934801] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 00 00 08 d7 00 |
118 |
00 08 00 |
119 |
[ 109.949751] blk_update_request: I/O error, dev sda, sector 2263 |
120 |
[ 109.961673] sd 0:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_OK |
121 |
driverbyte=DRIVER_TIMEOUT |
122 |
[ 109.978873] sd 0:0:0:0: [sda] tag#15 CDB: Read(10) 28 00 00 00 08 df 00 |
123 |
00 08 00 |
124 |
[ 109.993822] blk_update_request: I/O error, dev sda, sector 2271 |
125 |
[ 110.005742] sd 0:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_OK |
126 |
driverbyte=DRIVER_TIMEOUT |
127 |
[ 110.022944] sd 0:0:0:0: [sda] tag#16 CDB: Read(10) 28 00 00 00 08 e7 00 |
128 |
00 08 00 |
129 |
[ 110.037887] blk_update_request: I/O error, dev sda, sector 2279 |
130 |
[ 110.049809] sd 0:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_OK |
131 |
driverbyte=DRIVER_TIMEOUT |
132 |
[ 110.067011] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 00 00 08 ef 00 |
133 |
00 08 00 |
134 |
[ 110.081960] blk_update_request: I/O error, dev sda, sector 2287 |
135 |
[ 110.093919] VFS: Dirty inode writeback failed for block device sda1 |
136 |
(err=-5). |
137 |
[ 110.108295] VFS: Cannot open root device "sda1" or unknown-block(8,1): |
138 |
error -6 |
139 |
[ 110.123068] Please append a correct "root=" boot option; here are the |
140 |
available partitions: |
141 |
[ 110.143789] 0100 4096 ram0 (driver?) |
142 |
[ 110.153140] 0101 4096 ram1 (driver?) |
143 |
[ 110.162488] 0102 4096 ram2 (driver?) |
144 |
[ 110.171836] 0103 4096 ram3 (driver?) |
145 |
[ 110.181185] 0104 4096 ram4 (driver?) |
146 |
[ 110.190535] 0105 4096 ram5 (driver?) |
147 |
[ 110.199883] 0106 4096 ram6 (driver?) |
148 |
[ 110.209232] 0107 4096 ram7 (driver?) |
149 |
[ 110.218581] 0108 4096 ram8 (driver?) |
150 |
[ 110.227930] 0109 4096 ram9 (driver?) |
151 |
[ 110.237278] 010a 4096 ram10 (driver?) |
152 |
[ 110.246801] 010b 4096 ram11 (driver?) |
153 |
[ 110.256323] 010c 4096 ram12 (driver?) |
154 |
[ 110.265843] 010d 4096 ram13 (driver?) |
155 |
[ 110.275361] 010e 4096 ram14 (driver?) |
156 |
[ 110.284885] 010f 4096 ram15 (driver?) |
157 |
[ 110.294409] 0800 976762112 sda driver: sd |
158 |
[ 110.303756] 0801 4200966 sda1 326de2ce-01 |
159 |
[ 110.313621] 0802 2104515 sda2 326de2ce-02 |
160 |
[ 110.323486] 0803 970454520 sda3 326de2ce-03 |
161 |
[ 110.333355] Kernel panic - not syncing: VFS: Unable to mount root fs on |
162 |
unknown-block(8,1) |
163 |
[ 110.350033] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.2-hardened #1 |
164 |
[ 110.363326] Hardware name: FUJITSU |
165 |
D2901-H1 /D2901-H1, BIOS 6.00 |
166 |
R1.09.2901.H1 05/19/2010 |
167 |
[ 110.390222] ffffc90000c5be28 ffffc90000c5bd90 ffffffff813063ec |
168 |
0000000000000001 |
169 |
[ 110.405311] ffffffff82071fc0 ffffc90000c5be18 ffffffff8113853b |
170 |
ffffffff00000010 |
171 |
[ 110.420393] ffffc90000c5be28 ffffc90000c5bdb8 0000000400000004 |
172 |
ffffc90000c5be48 |
173 |
[ 110.435474] Call Trace: |
174 |
[ 110.440456] [<ffffffff813063ec>] dump_stack+0x45/0x69 |
175 |
[ 110.450806] [<ffffffff8113853b>] panic+0xbd/0x201 |
176 |
[ 110.460463] [<ffffffff81e14224>] mount_block_root+0x339/0x3cf |
177 |
[ 110.472198] [<ffffffff81e144c3>] mount_root+0x92/0x9d |
178 |
[ 110.482547] [<ffffffff81e1472b>] prepare_namespace+0x25d/0x2bf |
179 |
[ 110.494455] [<ffffffff81e13c70>] kernel_init_freeable+0x27c/0x2be |
180 |
[ 110.506882] [<ffffffff81691aa0>] ? rest_init+0x80/0x80 |
181 |
[ 110.517405] [<ffffffff81691aa9>] kernel_init+0x9/0xf0 |
182 |
[ 110.527753] [<ffffffff8169773e>] ret_from_fork+0x3e/0x70 |
183 |
[ 110.538621] [<ffffffff81691aa0>] ? rest_init+0x80/0x80 |
184 |
[ 110.549165] Kernel Offset: disabled |
185 |
[ 110.556224] ---[ end Kernel panic - not syncing: VFS: Unable to mount |
186 |
root fs on unknown-block(8,1) |
187 |
|
188 |
Booting back into 3.17.7 makes it work again. |
189 |
|
190 |
Does anyone have any idea about this? Does anyone know if the Areca driver |
191 |
changed between 3.17.7 and 4.2.2? |
192 |
Is there a more appropriate place to post regarding this? |
193 |
|
194 |
Calum |