Hi I did the update yesterday everything was working great.

 

I was going to play a movie on plex and i got no shares in my unraid.

 

What should i do .

 

 

nas-diagnostics-20180114-1759.zip

Edited January 14, 20188 yr by francrouge

1 minute ago, francrouge said:

Hi I did the update yesterday everything was working great.

 

I was going to play a movie on plex and i got no shares in my unraid.

 

What should i do .

 

 

nas-diagnostics-20180114-1759.zip

I did a reboot and now it seem ok but why did this happend any advice ?

Hi Mate,

 

I had the very same issue here. Had to reboot the machine to get things back.

Hope it won't happen again
 

Well, I spoke too fast.

This happened again.

 

Right after a system reboot, all the server's services (shares, dockers, VM) will work but after some few minutes, the array will stop working (Can't access to shares through the netwrok and also can'et access to folders even locally).

Cache drive still works, VMs and dockers too.

 

This is really a huge issue, someone can help plz

 

thanks

Try booting in safe mode, or if you're using the s3 plugin uninstall it as it apparently has issues with v6.4

 

 

Well didn't reboot yet in safe mode but here is the log:

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

 

Edited January 15, 20188 yr by mathgoy