* [gentoo-user] 4.4.2-hardened and Areca ARC-1110 problems
@ 2016-04-16 17:17 Calum
2016-04-16 19:00 ` J. Roeleveld
0 siblings, 1 reply; 2+ messages in thread
From: Calum @ 2016-04-16 17:17 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 10571 bytes --]
Hello all,
I have a server (in another country) running Gentoo with 3.17.7-hardened-r1.
It has a "RAID bus controller: Areca Technology Corp. ARC-1110 4-Port PCI-X
to SATA RAID Controller" (17d3:1110).
I have no physical access to it, and only a serial console and Debian
rescue image to recover with).
I don't have any access or info about the settings on the RAID controller
(unless I can get them from the OS).
This works well enough most of the time. (I do get some random hangs which
I have to hard reset to recover from).
I tried updating to linux-4.4.2-hardened (with the same kernel .config) but
get the following error upon booting
[ 35.805083] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.817201] arcmsr0: scsi id = 0 lun = 0 ccb = '0xffff8800d5120800' poll
command abort successfully
[ 35.835617] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.847700] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.859783] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.871870] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.883953] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.896035] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.908117] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.920199] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.932283] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.944364] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.956446] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.968529] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.980611] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 35.992693] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 36.004775] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 36.016858] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 36.028939] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 36.041021] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 36.053102] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 36.065187] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 36.077269] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 36.089351] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 36.101439] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 36.113543] arcmsr: executing bus reset eh.....num_resets = 0,
num_aborts = 24
[ 36.128326] arcmsr0: executing hw bus reset .....
[ 49.149028] arcmsr0: waiting for hw bus reset return, retry=0
[ 59.160983] arcmsr0: waiting for hw bus reset return, retry=1
[ 69.172962] arcmsr0: waiting for hw bus reset return, retry=2
[ 79.184902] arcmsr0: waiting for hw bus reset return, retry=3
[ 89.212917] Areca RAID Controller0: Model ARC-1110, F/W V1.49 2010-12-02
[ 89.240861] arcmsr: scsi bus reset eh returns with success
[ 96.108524] random: nonblocking pool is initialized
[ 109.252788] arcmsr0: abort device command of scsi id = 0 lun = 0
[ 109.264881] arcmsr0: scsi id = 0 lun = 0 ccb = '0xffff8800d5120e80' poll
command abort successfully
[ 109.283294] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.296764] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.310231] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.323700] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.337176] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.350645] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.364111] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.377580] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.391048] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.404517] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.417986] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.431455] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.444924] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.458393] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.471862] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.485330] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.498799] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.512267] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.525736] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.539206] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.552675] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.566144] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.579612] sd 0:0:0:0: Device offlined - not ready after error recovery
[ 109.593087] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_TIMEOUT
[ 109.610116] sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 00 00 08 af 00
00 08 00
[ 109.624888] blk_update_request: I/O error, dev sda, sector 2223
[ 109.636802] sd 0:0:0:0: rejecting I/O to offline device
[ 109.647324] sd 0:0:0:0: [sda] killing request
[ 109.656122] sd 0:0:0:0: [sda] FAILED Result: hostbyte=DID_NO_CONNECT
driverbyte=DRIVER_OK
[ 109.672630] sd 0:0:0:0: [sda] CDB: Read(10) 28 00 00 00 08 5f 00 00 08 00
[ 109.686270] blk_update_request: I/O error, dev sda, sector 2143
[ 109.698195] sd 0:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_TIMEOUT
[ 109.698201] EXT4-fs error (device sda1): __ext4_get_inode_loc:3981:
inode #8: block 260: comm swapper/0: unable to read itable block
[ 109.698213] sd 0:0:0:0: rejecting I/O to offline device
[ 109.698222] EXT4-fs (sda1): no journal found
[ 109.758504] sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 00 00 08 b7 00
00 08 00
[ 109.773453] blk_update_request: I/O error, dev sda, sector 2231
[ 109.785376] sd 0:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_TIMEOUT
[ 109.802578] sd 0:0:0:0: [sda] tag#11 CDB: Read(10) 28 00 00 00 08 bf 00
00 08 00
[ 109.817526] blk_update_request: I/O error, dev sda, sector 2239
[ 109.829449] sd 0:0:0:0: [sda] tag#12 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_TIMEOUT
[ 109.846652] sd 0:0:0:0: [sda] tag#12 CDB: Read(10) 28 00 00 00 08 c7 00
00 08 00
[ 109.861601] blk_update_request: I/O error, dev sda, sector 2247
[ 109.873522] sd 0:0:0:0: [sda] tag#13 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_TIMEOUT
[ 109.890726] sd 0:0:0:0: [sda] tag#13 CDB: Read(10) 28 00 00 00 08 cf 00
00 08 00
[ 109.905676] blk_update_request: I/O error, dev sda, sector 2255
[ 109.917599] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_TIMEOUT
[ 109.934801] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 00 00 08 d7 00
00 08 00
[ 109.949751] blk_update_request: I/O error, dev sda, sector 2263
[ 109.961673] sd 0:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_TIMEOUT
[ 109.978873] sd 0:0:0:0: [sda] tag#15 CDB: Read(10) 28 00 00 00 08 df 00
00 08 00
[ 109.993822] blk_update_request: I/O error, dev sda, sector 2271
[ 110.005742] sd 0:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_TIMEOUT
[ 110.022944] sd 0:0:0:0: [sda] tag#16 CDB: Read(10) 28 00 00 00 08 e7 00
00 08 00
[ 110.037887] blk_update_request: I/O error, dev sda, sector 2279
[ 110.049809] sd 0:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_TIMEOUT
[ 110.067011] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 00 00 08 ef 00
00 08 00
[ 110.081960] blk_update_request: I/O error, dev sda, sector 2287
[ 110.093919] VFS: Dirty inode writeback failed for block device sda1
(err=-5).
[ 110.108295] VFS: Cannot open root device "sda1" or unknown-block(8,1):
error -6
[ 110.123068] Please append a correct "root=" boot option; here are the
available partitions:
[ 110.143789] 0100 4096 ram0 (driver?)
[ 110.153140] 0101 4096 ram1 (driver?)
[ 110.162488] 0102 4096 ram2 (driver?)
[ 110.171836] 0103 4096 ram3 (driver?)
[ 110.181185] 0104 4096 ram4 (driver?)
[ 110.190535] 0105 4096 ram5 (driver?)
[ 110.199883] 0106 4096 ram6 (driver?)
[ 110.209232] 0107 4096 ram7 (driver?)
[ 110.218581] 0108 4096 ram8 (driver?)
[ 110.227930] 0109 4096 ram9 (driver?)
[ 110.237278] 010a 4096 ram10 (driver?)
[ 110.246801] 010b 4096 ram11 (driver?)
[ 110.256323] 010c 4096 ram12 (driver?)
[ 110.265843] 010d 4096 ram13 (driver?)
[ 110.275361] 010e 4096 ram14 (driver?)
[ 110.284885] 010f 4096 ram15 (driver?)
[ 110.294409] 0800 976762112 sda driver: sd
[ 110.303756] 0801 4200966 sda1 326de2ce-01
[ 110.313621] 0802 2104515 sda2 326de2ce-02
[ 110.323486] 0803 970454520 sda3 326de2ce-03
[ 110.333355] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(8,1)
[ 110.350033] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.2-hardened #1
[ 110.363326] Hardware name: FUJITSU
D2901-H1 /D2901-H1, BIOS 6.00
R1.09.2901.H1 05/19/2010
[ 110.390222] ffffc90000c5be28 ffffc90000c5bd90 ffffffff813063ec
0000000000000001
[ 110.405311] ffffffff82071fc0 ffffc90000c5be18 ffffffff8113853b
ffffffff00000010
[ 110.420393] ffffc90000c5be28 ffffc90000c5bdb8 0000000400000004
ffffc90000c5be48
[ 110.435474] Call Trace:
[ 110.440456] [<ffffffff813063ec>] dump_stack+0x45/0x69
[ 110.450806] [<ffffffff8113853b>] panic+0xbd/0x201
[ 110.460463] [<ffffffff81e14224>] mount_block_root+0x339/0x3cf
[ 110.472198] [<ffffffff81e144c3>] mount_root+0x92/0x9d
[ 110.482547] [<ffffffff81e1472b>] prepare_namespace+0x25d/0x2bf
[ 110.494455] [<ffffffff81e13c70>] kernel_init_freeable+0x27c/0x2be
[ 110.506882] [<ffffffff81691aa0>] ? rest_init+0x80/0x80
[ 110.517405] [<ffffffff81691aa9>] kernel_init+0x9/0xf0
[ 110.527753] [<ffffffff8169773e>] ret_from_fork+0x3e/0x70
[ 110.538621] [<ffffffff81691aa0>] ? rest_init+0x80/0x80
[ 110.549165] Kernel Offset: disabled
[ 110.556224] ---[ end Kernel panic - not syncing: VFS: Unable to mount
root fs on unknown-block(8,1)
Booting back into 3.17.7 makes it work again.
Does anyone have any idea about this? Does anyone know if the Areca driver
changed between 3.17.7 and 4.2.2?
Is there a more appropriate place to post regarding this?
Calum
[-- Attachment #2: Type: text/html, Size: 11738 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [gentoo-user] 4.4.2-hardened and Areca ARC-1110 problems
2016-04-16 17:17 [gentoo-user] 4.4.2-hardened and Areca ARC-1110 problems Calum
@ 2016-04-16 19:00 ` J. Roeleveld
0 siblings, 0 replies; 2+ messages in thread
From: J. Roeleveld @ 2016-04-16 19:00 UTC (permalink / raw
To: gentoo-user
On Saturday, April 16, 2016 06:17:28 PM Calum wrote:
> Hello all,
>
> I have a server (in another country) running Gentoo with 3.17.7-hardened-r1.
> It has a "RAID bus controller: Areca Technology Corp. ARC-1110 4-Port PCI-X
> to SATA RAID Controller" (17d3:1110).
>
> I have no physical access to it, and only a serial console and Debian
> rescue image to recover with).
> I don't have any access or info about the settings on the RAID controller
> (unless I can get them from the OS).
>
> This works well enough most of the time. (I do get some random hangs which
> I have to hard reset to recover from).
>
> I tried updating to linux-4.4.2-hardened (with the same kernel .config) but
> get the following error upon booting
>
> [ 35.805083] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.817201] arcmsr0: scsi id = 0 lun = 0 ccb = '0xffff8800d5120800' poll
> command abort successfully
> [ 35.835617] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.847700] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.859783] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.871870] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.883953] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.896035] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.908117] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.920199] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.932283] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.944364] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.956446] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.968529] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.980611] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 35.992693] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 36.004775] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 36.016858] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 36.028939] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 36.041021] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 36.053102] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 36.065187] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 36.077269] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 36.089351] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 36.101439] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 36.113543] arcmsr: executing bus reset eh.....num_resets = 0,
> num_aborts = 24
> [ 36.128326] arcmsr0: executing hw bus reset .....
> [ 49.149028] arcmsr0: waiting for hw bus reset return, retry=0
> [ 59.160983] arcmsr0: waiting for hw bus reset return, retry=1
> [ 69.172962] arcmsr0: waiting for hw bus reset return, retry=2
> [ 79.184902] arcmsr0: waiting for hw bus reset return, retry=3
> [ 89.212917] Areca RAID Controller0: Model ARC-1110, F/W V1.49 2010-12-02
> [ 89.240861] arcmsr: scsi bus reset eh returns with success
> [ 96.108524] random: nonblocking pool is initialized
> [ 109.252788] arcmsr0: abort device command of scsi id = 0 lun = 0
> [ 109.264881] arcmsr0: scsi id = 0 lun = 0 ccb = '0xffff8800d5120e80' poll
> command abort successfully
> [ 109.283294] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.296764] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.310231] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.323700] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.337176] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.350645] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.364111] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.377580] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.391048] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.404517] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.417986] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.431455] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.444924] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.458393] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.471862] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.485330] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.498799] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.512267] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.525736] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.539206] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.552675] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.566144] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.579612] sd 0:0:0:0: Device offlined - not ready after error recovery
> [ 109.593087] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_TIMEOUT
> [ 109.610116] sd 0:0:0:0: [sda] tag#9 CDB: Read(10) 28 00 00 00 08 af 00
> 00 08 00
> [ 109.624888] blk_update_request: I/O error, dev sda, sector 2223
> [ 109.636802] sd 0:0:0:0: rejecting I/O to offline device
> [ 109.647324] sd 0:0:0:0: [sda] killing request
> [ 109.656122] sd 0:0:0:0: [sda] FAILED Result: hostbyte=DID_NO_CONNECT
> driverbyte=DRIVER_OK
> [ 109.672630] sd 0:0:0:0: [sda] CDB: Read(10) 28 00 00 00 08 5f 00 00 08 00
> [ 109.686270] blk_update_request: I/O error, dev sda, sector 2143 [
> 109.698195] sd 0:0:0:0: [sda] tag#10 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_TIMEOUT
> [ 109.698201] EXT4-fs error (device sda1): __ext4_get_inode_loc:3981:
> inode #8: block 260: comm swapper/0: unable to read itable block
> [ 109.698213] sd 0:0:0:0: rejecting I/O to offline device
> [ 109.698222] EXT4-fs (sda1): no journal found
> [ 109.758504] sd 0:0:0:0: [sda] tag#10 CDB: Read(10) 28 00 00 00 08 b7 00
> 00 08 00
> [ 109.773453] blk_update_request: I/O error, dev sda, sector 2231
> [ 109.785376] sd 0:0:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_TIMEOUT
> [ 109.802578] sd 0:0:0:0: [sda] tag#11 CDB: Read(10) 28 00 00 00 08 bf 00
> 00 08 00
> [ 109.817526] blk_update_request: I/O error, dev sda, sector 2239
> [ 109.829449] sd 0:0:0:0: [sda] tag#12 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_TIMEOUT
> [ 109.846652] sd 0:0:0:0: [sda] tag#12 CDB: Read(10) 28 00 00 00 08 c7 00
> 00 08 00
> [ 109.861601] blk_update_request: I/O error, dev sda, sector 2247
> [ 109.873522] sd 0:0:0:0: [sda] tag#13 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_TIMEOUT
> [ 109.890726] sd 0:0:0:0: [sda] tag#13 CDB: Read(10) 28 00 00 00 08 cf 00
> 00 08 00
> [ 109.905676] blk_update_request: I/O error, dev sda, sector 2255
> [ 109.917599] sd 0:0:0:0: [sda] tag#14 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_TIMEOUT
> [ 109.934801] sd 0:0:0:0: [sda] tag#14 CDB: Read(10) 28 00 00 00 08 d7 00
> 00 08 00
> [ 109.949751] blk_update_request: I/O error, dev sda, sector 2263
> [ 109.961673] sd 0:0:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_TIMEOUT
> [ 109.978873] sd 0:0:0:0: [sda] tag#15 CDB: Read(10) 28 00 00 00 08 df 00
> 00 08 00
> [ 109.993822] blk_update_request: I/O error, dev sda, sector 2271
> [ 110.005742] sd 0:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_TIMEOUT
> [ 110.022944] sd 0:0:0:0: [sda] tag#16 CDB: Read(10) 28 00 00 00 08 e7 00
> 00 08 00
> [ 110.037887] blk_update_request: I/O error, dev sda, sector 2279
> [ 110.049809] sd 0:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_OK
> driverbyte=DRIVER_TIMEOUT
> [ 110.067011] sd 0:0:0:0: [sda] tag#17 CDB: Read(10) 28 00 00 00 08 ef 00
> 00 08 00
> [ 110.081960] blk_update_request: I/O error, dev sda, sector 2287
> [ 110.093919] VFS: Dirty inode writeback failed for block device sda1
> (err=-5).
> [ 110.108295] VFS: Cannot open root device "sda1" or unknown-block(8,1):
> error -6
> [ 110.123068] Please append a correct "root=" boot option; here are the
> available partitions:
> [ 110.143789] 0100 4096 ram0 (driver?)
> [ 110.153140] 0101 4096 ram1 (driver?)
> [ 110.162488] 0102 4096 ram2 (driver?)
> [ 110.171836] 0103 4096 ram3 (driver?)
> [ 110.181185] 0104 4096 ram4 (driver?)
> [ 110.190535] 0105 4096 ram5 (driver?)
> [ 110.199883] 0106 4096 ram6 (driver?)
> [ 110.209232] 0107 4096 ram7 (driver?)
> [ 110.218581] 0108 4096 ram8 (driver?)
> [ 110.227930] 0109 4096 ram9 (driver?)
> [ 110.237278] 010a 4096 ram10 (driver?)
> [ 110.246801] 010b 4096 ram11 (driver?)
> [ 110.256323] 010c 4096 ram12 (driver?)
> [ 110.265843] 010d 4096 ram13 (driver?)
> [ 110.275361] 010e 4096 ram14 (driver?)
> [ 110.284885] 010f 4096 ram15 (driver?)
> [ 110.294409] 0800 976762112 sda driver: sd
> [ 110.303756] 0801 4200966 sda1 326de2ce-01
> [ 110.313621] 0802 2104515 sda2 326de2ce-02
> [ 110.323486] 0803 970454520 sda3 326de2ce-03
> [ 110.333355] Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(8,1)
> [ 110.350033] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.2-hardened #1
> [ 110.363326] Hardware name: FUJITSU
> D2901-H1 /D2901-H1, BIOS 6.00
> R1.09.2901.H1 05/19/2010
> [ 110.390222] ffffc90000c5be28 ffffc90000c5bd90 ffffffff813063ec
> 0000000000000001
> [ 110.405311] ffffffff82071fc0 ffffc90000c5be18 ffffffff8113853b
> ffffffff00000010
> [ 110.420393] ffffc90000c5be28 ffffc90000c5bdb8 0000000400000004
> ffffc90000c5be48
> [ 110.435474] Call Trace:
> [ 110.440456] [<ffffffff813063ec>] dump_stack+0x45/0x69
> [ 110.450806] [<ffffffff8113853b>] panic+0xbd/0x201
> [ 110.460463] [<ffffffff81e14224>] mount_block_root+0x339/0x3cf
> [ 110.472198] [<ffffffff81e144c3>] mount_root+0x92/0x9d
> [ 110.482547] [<ffffffff81e1472b>] prepare_namespace+0x25d/0x2bf
> [ 110.494455] [<ffffffff81e13c70>] kernel_init_freeable+0x27c/0x2be
> [ 110.506882] [<ffffffff81691aa0>] ? rest_init+0x80/0x80
> [ 110.517405] [<ffffffff81691aa9>] kernel_init+0x9/0xf0
> [ 110.527753] [<ffffffff8169773e>] ret_from_fork+0x3e/0x70
> [ 110.538621] [<ffffffff81691aa0>] ? rest_init+0x80/0x80
> [ 110.549165] Kernel Offset: disabled
> [ 110.556224] ---[ end Kernel panic - not syncing: VFS: Unable to mount
> root fs on unknown-block(8,1)
>
> Booting back into 3.17.7 makes it work again.
>
> Does anyone have any idea about this? Does anyone know if the Areca driver
> changed between 3.17.7 and 4.2.2?
> Is there a more appropriate place to post regarding this?
>
> Calum
Not sure about that model, but I have the following in one of my servers:
02:00.0 RAID bus controller: Areca Technology Corp. ARC-1280/1280ML 24-Port
PCI-Express to SATA II RAID Controller
Subsystem: Areca Technology Corp. ARC-1280/1280ML 24-Port PCI-Express
to SATA II RAID Controller
Flags: bus master, fast devsel, latency 0, IRQ 37
Memory at fbd10000 (32-bit, non-prefetchable) [size=8K]
Expansion ROM at fbd00000 [disabled] [size=64K]
Capabilities: [98] Power Management version 2
Capabilities: [a0] MSI: Enable+ Count=1/2 Maskable- 64bit+
Capabilities: [d0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Kernel driver in use: arcmsr
(lspci -v output)
With the following kernel:
# uname -a
Linux artemis 4.1.7-hardened-r1-host #3 SMP Fri Jan 15 09:57:12 CET 2016
x86_64 Intel(R) Xeon(R) CPU E31220 @ 3.10GHz GenuineIntel GNU/Linux
And:
# eix -I xen
[U] app-emulation/xen
Available versions: 4.5.2-r2^t{tbz2} 4.5.2-r3^t 4.5.2-r4^t 4.6.0-
r5^t{tbz2} ~4.6.0-r6^st ~4.6.0-r7^st{tbz2} 4.6.0-r8^st{tbz2} {custom-cflags
debug efi flask xsm}
Installed versions: 4.5.2-r2^t{tbz2}(09:10:41 AM 12/28/2015)(efi -custom-
cflags -debug -flask -xsm)
Homepage: http://xen.org/
Description: The Xen virtual machine monitor
I haven't had any issues with this.
You can try the " Linux - CLI " tool to access the settings:
http://www.areca.com.tw/support/s_linux/linux.htm
(Near bottom of page)
About the stability, how are the disks connected to the controller? Is there
any way to find out more details?
--
Joost
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-04-16 19:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-04-16 17:17 [gentoo-user] 4.4.2-hardened and Areca ARC-1110 problems Calum
2016-04-16 19:00 ` J. Roeleveld
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox