mathgoy Posted January 16, 2018 Share Posted January 16, 2018 Hi Gents, Since the update, my array won't work at all. When I reboot the server, it will work for about 10min and then, I can't browse my shares on the hard drives neither from a machine on the same network nor from the server itself. However, cache drive still runs smoothly. I can browse it and all my dockers and VM are still working. I tried to uninstall most of the plugins but it won't fix the issue. Here is an extract from the log where we can see on the first line the main errors (kworker/u32:6 Not tainted and Call Trace) Jan 15 23:33:01 MAXIMUS kernel: CPU: 3 PID: 21564 Comm: kworker/u32:6 Not tainted 4.14.13-unRAID #1 Jan 15 23:33:01 MAXIMUS kernel: Hardware name: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F/X9SRE/X9SRE-3F/X9SRi/X9SRi-3F, BIOS 3.2 01/16/2015 Jan 15 23:33:01 MAXIMUS kernel: Workqueue: scsi_tmf_7 scmd_eh_abort_handler Jan 15 23:33:01 MAXIMUS kernel: task: ffff880807380000 task.stack: ffffc90007840000 Jan 15 23:33:01 MAXIMUS kernel: RIP: 0010:isci_task_abort_task+0x18/0x334 [isci] Jan 15 23:33:01 MAXIMUS kernel: RSP: 0018:ffffc90007843ce8 EFLAGS: 00010296 Jan 15 23:33:01 MAXIMUS kernel: RAX: ffffffffa01d6cbb RBX: ffff880818fef1a8 RCX: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: RDX: ffff88085ec18020 RSI: 0000000000000400 RDI: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: RBP: 0000000000000000 R08: 00000000000000d2 R09: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: R10: ffffc90007843e58 R11: ffff8808073800c0 R12: ffff8808562d6800 Jan 15 23:33:01 MAXIMUS kernel: R13: 0000000000000000 R14: 0000000000000008 R15: 0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: FS: 0000000000000000(0000) GS:ffff88085f2c0000(0000) knlGS:0000000000000000 Jan 15 23:33:01 MAXIMUS kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 15 23:33:01 MAXIMUS kernel: CR2: 0000000000000000 CR3: 0000000001c0a003 CR4: 00000000000626e0 Jan 15 23:33:01 MAXIMUS kernel: Call Trace: Jan 15 23:33:01 MAXIMUS kernel: ? __freed_request+0x34/0x86 Jan 15 23:33:01 MAXIMUS kernel: ? freed_request+0x31/0x4b Jan 15 23:33:01 MAXIMUS kernel: ? __blk_put_request+0xed/0x131 Jan 15 23:33:01 MAXIMUS kernel: ? blk_put_request+0x38/0x4b Jan 15 23:33:01 MAXIMUS kernel: ? scsi_execute+0x168/0x177 Jan 15 23:33:01 MAXIMUS kernel: ? scsi_test_unit_ready+0x45/0x99 Jan 15 23:33:01 MAXIMUS kernel: ? cpuacct_charge+0x2c/0x6b Jan 15 23:33:01 MAXIMUS kernel: sas_eh_abort_handler+0x2a/0x3c [libsas] Jan 15 23:33:01 MAXIMUS kernel: scmd_eh_abort_handler+0x35/0x8f Jan 15 23:33:01 MAXIMUS kernel: process_one_work+0x146/0x239 Jan 15 23:33:01 MAXIMUS kernel: ? rescuer_thread+0x258/0x258 Jan 15 23:33:01 MAXIMUS kernel: worker_thread+0x1c3/0x292 Jan 15 23:33:01 MAXIMUS kernel: kthread+0x10f/0x117 Jan 15 23:33:01 MAXIMUS kernel: ? kthread_create_on_node+0x3a/0x3a Thanks you all for your help! Quote Link to comment
bonienl Posted January 16, 2018 Share Posted January 16, 2018 (edited) Did you try starting in safemode? Plugins which are known to may cause issues are: - Preclear - S3 sleep Uninstall these plugins for the time being. Please post diagnostics. Edited January 16, 2018 by bonienl Quote Link to comment
mathgoy Posted January 16, 2018 Author Share Posted January 16, 2018 Hi bonienl and thanks for your feedback. Preclear and SE sleep are not installed. I started the machine in safemode and it looks like it works. Only Plex docker and a VM are currently running. Since it works in Safe mode do you still need diagnostics? Cheers Quote Link to comment
mathgoy Posted January 23, 2018 Author Share Posted January 23, 2018 Well, since nobody could help me so far, I went back to 6.3.5 which runs smoothly. Any ideas why 6.4.0 bugs like that on my system? Cheers Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.