lanolano Posted August 19, 2015 Share Posted August 19, 2015 Hi, Newbie here. Decided to try out UNRAID 6, but can't get it to boot. I've pinpointed the problem to my ARC-1320ix-16 controller. Boot freezes after loading the mvsas, even with no drives attached. The system boots without errors if I remove the controller card. I know the card works fine on Windows, so it must be a driver/settings issue. Anyone got any experience with this card? Link to comment
RobJ Posted August 19, 2015 Share Posted August 19, 2015 Card apparently has a Marvell 88SE6440 chipset. Just as a test, try turning off all virtualization options in your BIOS, and see if that makes a difference. Some Marvell chipsets are known to be incompatible with certain virtualization options. There's a Defect report about it. Your chipset model isn't listed, but ... Link to comment
lanolano Posted August 19, 2015 Author Share Posted August 19, 2015 Thank you I managed to boot the system now without any disks in the controller. Not sure what the culprit was, but I disabled lots of stuff in the bios (My mb is: jetway NAF92 Q67 ) UNRAID finds the controller, but hangs for a minute when loading mvsas. Log output below (note that this is unraid 5.0.6 with a patch from areca - http://www.areca.com.tw/support/s_unRAID/unRAID.htm) It seems to be producing some errors: Aug 19 13:25:16 Tower kernel: scsi1 : mvsas Aug 19 13:25:16 Tower kernel: sas: phy-1:0 added to port-1:0, phy_mask:0x1 (5001b4d50bd2d03f) Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1217:set wide port phy map 1 Aug 19 13:25:16 Tower kernel: sas: phy1 matched wide port0 Aug 19 13:25:16 Tower kernel: sas: phy-1:1 added to port-1:0, phy_mask:0x3 (5001b4d50bd2d03f) Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1217:set wide port phy map 3 Aug 19 13:25:16 Tower kernel: sas: phy2 matched wide port0 Aug 19 13:25:16 Tower kernel: sas: phy-1:2 added to port-1:0, phy_mask:0x7 (5001b4d50bd2d03f) Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1217:set wide port phy map 7 Aug 19 13:25:16 Tower kernel: sas: phy3 matched wide port0 Aug 19 13:25:16 Tower kernel: sas: phy-1:3 added to port-1:0, phy_mask:0xf (5001b4d50bd2d03f) Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1217:set wide port phy map f Aug 19 13:25:16 Tower kernel: sas: phy0 matched wide port0 Aug 19 13:25:16 Tower kernel: sas: phy-1:4 added to port-1:0, phy_mask:0xf (5001b4d50bd2d03f) Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1217:set wide port phy map f Aug 19 13:25:16 Tower kernel: sas: phy1 matched wide port0 Aug 19 13:25:16 Tower kernel: sas: phy-1:5 added to port-1:0, phy_mask:0xf (5001b4d50bd2d03f) Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1217:set wide port phy map f Aug 19 13:25:16 Tower kernel: sas: phy2 matched wide port0 Aug 19 13:25:16 Tower kernel: sas: phy-1:6 added to port-1:0, phy_mask:0xf (5001b4d50bd2d03f) Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1217:set wide port phy map f Aug 19 13:25:16 Tower kernel: sas: phy3 matched wide port0 Aug 19 13:25:16 Tower kernel: sas: phy-1:7 added to port-1:0, phy_mask:0xf (5001b4d50bd2d03f) Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1217:set wide port phy map f Aug 19 13:25:16 Tower kernel: sas: DOING DISCOVERY on port 0, pid:6 Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy00:U:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy01:U:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy02:U:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy03:U:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy04:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy05:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy06:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy07:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy08:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy09:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy10:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy11:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy12:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy13:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy14:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy15:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy16:U:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy17:U:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy18:U:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy19:U:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy20:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy21:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy22:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy23:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy24:S:A attached: 5005043011ab0000 (host) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy25:S:A attached: 5005043011ab0000 (host) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy26:S:A attached: 5005043011ab0000 (host) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy27:S:A attached: 5005043011ab0000 (host) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy28:U:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy29:U:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy30:U:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy31:U:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy32:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy33:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy34:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy35:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy36:D:A attached: 5001b4d50bd2d03d (host+target) Aug 19 13:25:16 Tower kernel: sas: ex 5001b4d50bd2d03f phy37:D:0 attached: 0000000000000000 (no device) Aug 19 13:25:16 Tower kernel: sas: DONE DISCOVERY on port 0, pid:6, result:0 Aug 19 13:25:16 Tower kernel: scsi 1:0:0:0: command f746fe40 timed out Aug 19 13:25:16 Tower kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Aug 19 13:25:16 Tower kernel: sas: trying to find task 0xec472800 Aug 19 13:25:16 Tower kernel: sas: sas_scsi_find_task: aborting task 0xec472800 Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1422:TMF task[1] timeout. Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1647:mvs_abort_task:rc= 5 Aug 19 13:25:16 Tower kernel: sas: sas_scsi_find_task: querying task 0xec472800 Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1422:TMF task[80] timeout. Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1569:mvs_query_task:rc= 5 Aug 19 13:25:16 Tower kernel: sas: sas_scsi_find_task: task 0xec472800 failed to abort Aug 19 13:25:16 Tower kernel: sas: task 0xec472800 is not at LU: I_T recover Aug 19 13:25:16 Tower kernel: sas: I_T nexus reset for dev 5001b4d50bd2d03d Aug 19 13:25:16 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[1]:rc= 0 Aug 19 13:25:16 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at 00000001 Aug 19 13:25:16 Tower kernel: IP: [<c13f6356>] _raw_spin_unlock_irqrestore+0x3/0xa Aug 19 13:25:16 Tower kernel: *pdpt = 0000000000000000 *pde = f000eef300000000 Aug 19 13:25:16 Tower kernel: Oops: 0002 [#1] SMP Aug 19 13:25:16 Tower kernel: Modules linked in: coretemp hwmon sg i2c_i801 i2c_core mvsas(+) libsas scsi_transport_sas ahci libahci e1000e ptp pps_core mperf Aug 19 13:25:16 Tower kernel: Pid: 917, comm: scsi_eh_1 Not tainted 3.9.11p-unRAID #1 / Aug 19 13:25:16 Tower kernel: EIP: 0060:[<c13f6356>] EFLAGS: 00010082 CPU: 0 Aug 19 13:25:16 Tower kernel: EIP is at _raw_spin_unlock_irqrestore+0x3/0xa Aug 19 13:25:16 Tower kernel: EAX: 00000001 EBX: 00000000 ECX: ec44c600 EDX: 00000002 Aug 19 13:25:16 Tower kernel: ESI: 00000001 EDI: 00000002 EBP: f7611e58 ESP: f7611e58 Aug 19 13:25:16 Tower kernel: DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 Aug 19 13:25:16 Tower kernel: CR0: 80050033 CR2: 00000001 CR3: 015c7000 CR4: 000407f0 Aug 19 13:25:16 Tower kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 Aug 19 13:25:16 Tower kernel: DR6: ffff0ff0 DR7: 00000400 Aug 19 13:25:16 Tower kernel: Process scsi_eh_1 (pid: 917, ti=f7610000 task=ec587960 task.ti=f7610000) Aug 19 13:25:16 Tower kernel: Stack: Aug 19 13:25:16 Tower kernel: 00000003 f8521c4d f85267a2 f8526640 000005f7 f85262d8 00000001 00000000 Aug 19 13:25:16 Tower kernel: f76a0000 00000000 ec472800 f746fe40 ec44c600 f7611f18 f8504abe f8508348 Aug 19 13:25:16 Tower kernel: 0bd2d03d 5001b4d5 00000001 c15b7000 f7611efc f7611f04 eceb6000 00000000 Aug 19 13:25:16 Tower kernel: Call Trace: Aug 19 13:25:16 Tower kernel: [<f8521c4d>] mvs_I_T_nexus_reset+0xb8/0xc3 [mvsas] Aug 19 13:25:16 Tower kernel: [<f8504abe>] ? sas_scsi_recover_host+0x5b5/0x9d2 [libsas] Aug 19 13:25:16 Tower kernel: [<c12daa0b>] ? __pm_runtime_resume+0x3b/0x43 Aug 19 13:25:16 Tower kernel: [<c12f0449>] ? scsi_error_handler+0x8f/0x399 Aug 19 13:25:16 Tower kernel: [<c10474ae>] ? default_wake_function+0xb/0xd Aug 19 13:25:16 Tower kernel: [<c1044488>] ? complete+0x42/0x49 Aug 19 13:25:16 Tower kernel: [<c103e301>] ? kthread+0x90/0x95 Aug 19 13:25:16 Tower kernel: [<c12f03ba>] ? scsi_eh_get_sense+0xc4/0xc4 Aug 19 13:25:16 Tower kernel: [<c13f6d37>] ? ret_from_kernel_thread+0x1b/0x28 Aug 19 13:25:16 Tower kernel: [<c103e271>] ? kthread_freezable_should_stop+0x4a/0x4a Aug 19 13:25:16 Tower kernel: Code: 08 eb f6 89 d8 5b 5d c3 55 89 e5 fa ba 00 01 00 00 f0 66 0f c1 10 88 d1 66 c1 ea 08 38 d1 74 06 f3 90 8a 08 eb f6 5d c3 55 89 e5 <80> 00 01 52 9d 5d c3 55 89 e5 83 ca ff f0 0f c1 10 4a b9 01 00 Aug 19 13:25:16 Tower kernel: EIP: [<c13f6356>] _raw_spin_unlock_irqrestore+0x3/0xa SS:ESP 0068:f7611e58 Aug 19 13:25:16 Tower kernel: CR2: 0000000000000001 Aug 19 13:25:16 Tower kernel: ---[ end trace f64ed39f0ad9b19f ]--- Here's the whole syslog: https://www.dropbox.com/s/k0xpbq6pmmmjgv9/syslog.txt I'm now trying Unraid 6 again with one disk added. This doesn't seem to work as it's been hanging for 15 minutes now on "mounting non-root local file systems"... Link to comment
RobJ Posted August 19, 2015 Share Posted August 19, 2015 I'm afraid you're out of luck with that card, under Linux. That card appears incompatible with that driver, even if it's patched. I know we have other Areca's that do work, but not this one. I'm sorry. The only other thing I can think of is make sure you have the latest firmware for the card. That has made a difference with a few Areca's, I believe. Link to comment
lanolano Posted August 19, 2015 Author Share Posted August 19, 2015 Damn... Guess I'll try something else then. Perhaps Esxi and unraid as vm would work Thanks for answering Link to comment
lanolano Posted August 20, 2015 Author Share Posted August 20, 2015 Update! Ching at Areca cooked me a driver for the ARC-1320ix for UNRAID 6.0.1! Now it works perfectly Driver attached if anyone needs it. arcsas-unRAID-6.0.1-20150820.zip Link to comment
RobJ Posted August 21, 2015 Share Posted August 21, 2015 Because that's amazing, I'm moving this to the Disk Controllers board! I think other Areca users will be very interested! Link to comment
BRiT Posted August 21, 2015 Share Posted August 21, 2015 Now if only they could work with @limetech to get the driver included in all future builds. We dont know if this is just the standard driver or if it had to be modified. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.