NAS hung while copying data on 6.2

Can you send me your logs (see Sending Logs link in my sig)?

Were you using SMB for the copy?

What are the settings for the share you were copying to? Do you have bitrot protection enabled/disabled? What about snapshots/protection ?

Wow, thanks for the quick reply mdgm. As well, thanks for all the advice you have provided to my other posts these last few weeks. Logs incoming as per your Sending Logs instructions.

I was indeed using SMB to do the copy. From an internal drive in my Windows PC to the NAS. I have bitrot protection disabled and do not have snapshots enabled.

SMB is the only protocol I have enabled on this share. What other share settings can I provide you with that might help?

Can you check the SMART output for the Load Cycle Count?

# smartctl --all /dev/sda | grep Load
# smartctl --all /dev/sdb | grep Load
# smartctl --all /dev/sdc | grep Load
# smartctl --all /dev/sdd | grep Load
# smartctl --all /dev/sde | grep Load
# smartctl --all /dev/sdf | grep Load

sda to sdf respectively. I hope your not thinking there is an issue with my disks. They've been solid prior to upgrading. All 6 are WD Reds btw.

193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       1846
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       1831
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       1188
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       1161
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       331
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       310

There is no issue with the Load Cycle Count.

What apps do you have installed.

I think the issue is possibly with an app.

Would be handy to see the output of

# journalctl -a

from just before the crash.

Whew.

I have htop, BitTorrentSync, linux-dash, Shell in a box, and PHPSysInfo installed. As well as CrashPlan, but that is installed manually.

That is a lot of output from journalctl. I could pipe it into a text file and send to you if you want. I can narrow both crashes down to sometime after 17:00hours (my log time).

Thanks.

If you look at

# top

Are any of your apps including those manually installed putting a high load on your system?

I've been using top/htop to keep an eye on the system the last few days to see what kind of load apps had on it. I didn't see anything out of the ordinary. CrashPlan can sometimes put quite the load on the system, but only when it is actively working. Which it wasn't while I was copying data.

I have shutdown some apps including CrashPlan while the volume rebuilds. Of course right now the most intensive process is md127_raid5. Once it's done resyncing I'll re-enable my typical apps and monitor. I don't usually run anything too intense on my NAS (Plex etc.), just CrashPlan and the odd monitor utility.

Do you want me to send the output of journalctl to the same email as the logs?

oshae wrote:
Do you want me to send the output of journalctl to the same email as the logs?

Yes, please.

I'm still not seeing what caused the crash. Sounds like monitoring the system to try to see what causes it to crash would be the next step.