Here are my syslog

https://gist.github.com/publicENEMY/fc2022c368862ea6c7cc

 

Recently ive been getting weird message on my unraid screen. Happens when i move file to my unraid. When it happens, i see that file moving progress has halted.

 

Thanks.

Boot in SAFE mode

Boot in SAFE mode

 

Im sorry but, why do i have to boot in safe mode? Do i need the syslog from safe mode? Or if boot in safe mode the problem will be automagically fixed? In safe mode i can see the problem?

 

Why?

Booting is Safe mode stops all your plugins being loaded.    That helps identify if the problem is a core issue, or is a by-product of something one of the plugins is loading.

Booting is Safe mode stops all your plugins being loaded.    That helps identify if the problem is a core issue, or is a by-product of something one of the plugins is loading.

 

Thank you.

Updated syslog.

 

https://gist.github.com/publicENEMY/2432567ee2d73195b328

 

Error found in notepad++

 

Line 738: Jan 23 20:22:03 Tower kernel: sas: ata7: end_device-4:0: dev error handler

Line 748: Jan 23 20:22:03 Tower kernel: sas: ata7: end_device-4:0: dev error handler

Line 749: Jan 23 20:22:03 Tower kernel: sas: ata8: end_device-4:1: dev error handler

Line 763: Jan 23 20:22:03 Tower kernel: sas: ata7: end_device-4:0: dev error handler

Line 764: Jan 23 20:22:03 Tower kernel: sas: ata8: end_device-4:1: dev error handler

Line 765: Jan 23 20:22:03 Tower kernel: sas: ata9: end_device-4:2: dev error handler

Line 780: Jan 23 20:22:03 Tower kernel: sas: ata7: end_device-4:0: dev error handler

Line 781: Jan 23 20:22:03 Tower kernel: sas: ata8: end_device-4:1: dev error handler

Line 782: Jan 23 20:22:03 Tower kernel: sas: ata9: end_device-4:2: dev error handler

Line 783: Jan 23 20:22:03 Tower kernel: sas: ata10: end_device-4:3: dev error handler

Line 795: Jan 23 20:22:03 Tower kernel: usb 2-1.6: device descriptor read/64, error -110

Line 797: Jan 23 20:22:03 Tower kernel: sas: ata7: end_device-4:0: dev error handler

Line 798: Jan 23 20:22:03 Tower kernel: sas: ata8: end_device-4:1: dev error handler

Line 799: Jan 23 20:22:03 Tower kernel: sas: ata9: end_device-4:2: dev error handler

Line 800: Jan 23 20:22:03 Tower kernel: sas: ata10: end_device-4:3: dev error handler

Line 801: Jan 23 20:22:03 Tower kernel: sas: ata11: end_device-4:4: dev error handler

Line 836: Jan 23 20:22:03 Tower kernel: sas: ata12: end_device-11:0: dev error handler

Line 849: Jan 23 20:22:03 Tower kernel: sas: ata12: end_device-11:0: dev error handler

Line 850: Jan 23 20:22:03 Tower kernel: sas: ata13: end_device-11:1: dev error handler

Line 863: Jan 23 20:22:03 Tower kernel: sas: ata12: end_device-11:0: dev error handler

Line 864: Jan 23 20:22:03 Tower kernel: sas: ata13: end_device-11:1: dev error handler

Line 865: Jan 23 20:22:03 Tower kernel: sas: ata14: end_device-11:2: dev error handler

Line 1231: Jan 23 20:22:09 Tower kernel: usb 2-1.6: device descriptor read/64, error -110

Line 1235: Jan 23 20:22:24 Tower kernel: usb 2-1.6: device descriptor read/64, error -110

Line 1239: Jan 23 20:22:40 Tower kernel: usb 2-1.6: device descriptor read/64, error -110

Line 1241: Jan 23 20:22:45 Tower kernel: usb 2-1.6: device descriptor read/8, error -110

Line 1243: Jan 23 20:22:50 Tower kernel: usb 2-1.6: device descriptor read/8, error -110

Line 1246: Jan 23 20:22:55 Tower kernel: usb 2-1.6: device descriptor read/8, error -110

Line 1248: Jan 23 20:23:00 Tower kernel: usb 2-1.6: device descriptor read/8, error -110

 

Thanks.

 

Can you tell us anything about the hardware those error messages refer to?

 

Are you still getting?

weird message on my unraid screen

If so post a screenshot so we can see what you mean.

 

How exactly are you trying to move files? On unRAID or on the network?

Can you tell us anything about the hardware those error messages refer to?

 

Are you still getting?

weird message on my unraid screen

If so post a screenshot so we can see what you mean.

 

How exactly are you trying to move files? On unRAID or on the network?

 

the error i first mention is the error verbosed in unraid monitor screen. unfortunately, i cant fully captured whats displayed on monitor screen(is there a log for this?). i just tried moving 50gb of files in this safe mode and i cant see any error. i now trying moving files not in safe mode.

 

i move files using teracopy from my windows to unraid. through network.

 

thanks.

Its been few days and i havent encounter any errors. possibly the error is caused by bad parity. in my unraid menu i can see that i have 2 parity errors that has been fixed.