I'm still having problems with Unraid crashing when copying files.  Advice from last weekend was that it was a hardware issue.  Following is from the start up script.  Is this "Warning" message a problem?  Thanks!

 

 

Tower kernel: scst: ***WARNING***: Patch io_context was not applied on your kernel. SCST will be working with not the best performance.

Jun 25 15:08:02 Tower kernel: [746]: scst: scst_cmd_thread:3729:Processing thread started, PID 746

Jun 25 15:08:02 Tower kernel: [747]: scst: scst_init_thread:3482:Init thread started, PID 747

Jun 25 15:08:02 Tower kernel: [748]: scst: scst_tm_thread:5092:Task management thread started, PID 748

Jun 25 15:08:02 Tower kernel: [745]: scst: init_scst:2089:SCST version 2.0.0-pre1-procfs loaded successfully (max mem for commands 217MB, per device 86MB)

Jun 25 15:08:02 Tower kernel: [745]: scst: scst_print_config:1859:Enabled features: EXTRACHECKS, DEBUG

Jun 25 15:08:02 Tower kernel: [749]: scst: scst_global_mgmt_thread:5663:Management thread started, PID 749

Jun 25 15:08:02 Tower kernel: mvsas 0000:01:00.0: mvsas: driver version 0.8.4

Jun 25 15:08:02 Tower kernel: mvsas 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16

Jun 25 15:08:02 Tower kernel: mvsas 0000:01:00.0: setting latency timer to 64

Jun 25 15:08:02 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 491:Init flash rom ok,flash type is 0x101.

Jun 25 15:08:02 Tower kernel: usb 1-5: configuration #1 chosen from 1 choice

Jun 25 15:08:02 Tower kernel: scsi1 : SCSI emulation for USB Mass Storage devices

Jun 25 15:08:02 Tower kernel: usb-storage: device found at 2

Jun 25 15:08:02 Tower kernel: usb-storage: waiting for device to settle before scanning

Jun 25 15:08:02 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 529:Phy 0 SAS ADDRESS 500304800082c950

Jun 25 15:08:02 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 529:Phy 1 SAS ADDRESS 500304800082c950

Jun 25 15:08:02 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 529:Phy 2 SAS ADDRESS 500304800082c950

Jun 25 15:08:02 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 529:Phy 3 SAS ADDRESS 500304800082c950

Jun 25 15:08:02 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 529:Phy 4 SAS ADDRESS 500304800082c950

Jun 25 15:08:02 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 529:Phy 5 SAS ADDRESS 500304800082c950

Jun 25 15:08:02 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 529:Phy 6 SAS ADDRESS 500304800082c950

Jun 25 15:08:02 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_spi.c 529:Phy 7 SAS ADDRESS 500304800082c950

Jun 25 15:08:02 Tower kernel: mvsas 0000:01:00.0: mvsas: PCI-E x4, Bandwidth Usage: 2.5 Gbps

Jun 25 15:08:02 Tower kernel: scsi 1:0:0:0: Direct-Access    SanDisk  U3 Cruzer Micro  4.04 PQ: 0 ANSI: 2

Jun 25 15:08:02 Tower kernel: [753]: scst_suspend_activity:599:suspend_count 0

Jun 25 15:08:02 Tower kernel: [753]: scst_susp_wait:578:wait_event() returned 0

Jun 25 15:08:02 Tower kernel: [753]: scst_suspend_activity:644:Waiting for 0 active commands finally to complete

Jun 25 15:08:02 Tower kernel: [753]: scst_susp_wait:578:wait_event() returned 0

Jun 25 15:08:02 Tower kernel: [753]: __scst_resume_activity:675:suspend_count 0 left

Jun 25 15:08:02 Tower kernel: [753]: scst: scst_register_device:792:Attached to scsi1, channel 0, id 0, lun 0, type 0

Jun 25 15:08:02

No. It's not a problem.