ReadyNas 3220 Hang every few days!

[Bilal-Hasan]

Hello,

Could you please assist us to find out why our new device ReadyNas 3220 keep hanging every few days! we have to restart it to bring it to life again!

We are using this device for saving backup files throw Acronis backup system

Device Firmware updated to latest version 6.6.0 but same issue still exist!

Checking log files for warning or errors but find nothing to figure the cause of this hanging!

Thanks,

Bilal

[mdgm-ntgr]

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

How many machines are you backing up? Do you stagger the backups?

Which firmware are you running?

Is the NAS used for other tasks or just for your storing your Acronis backups?

[Bilal-Hasan]

I send you the logs as "Sending Logs" instructions

We are backing up about 40 computers and 2 servers

ReadyNas 3220 firware version : 6.6.0

We are using the NAS for only storing Acronis backup

[mdgm-ntgr]

The logs don't go back very far unfortunately and the most recent power cycle was a graceful restart not a crash. It's best if you download the logs ASAP after a crash.

You are using NAS disks designed for desktop NAS units not a 12-bay rackmount.

You should be using an enterprise NAS HDD or some other enterprise disk. We do have a compatibility list.

Also it appears you have disk spin-down enabled which is quite an odd configuration for a rackmount unit with NAS class HDDs.

[Bilal-Hasan]

I send you an updated logs after the devices stopped again today!

Thanks,

Bilal

[mdgm-ntgr]

Those logs show it was restarted normally i.e. it did not hang.

[Bilal-Hasan]

These are the latest logs after the device hang!

I could not find an answer why it keep hanging or how to fix it!

[mdgm-ntgr]

The logs very clearly show a graceful restart

Dec 19 09:58:16 SDS_BACKUP_NAS systemd[1]: Reached target Shutdown.
Dec 19 09:58:16 SDS_BACKUP_NAS systemd[1]: Reached target Final Step.
Dec 19 09:58:16 SDS_BACKUP_NAS systemd[1]: Starting Reboot...
Dec 19 09:58:16 SDS_BACKUP_NAS systemd[1]: Shutting down.
Dec 19 09:58:16 SDS_BACKUP_NAS systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Dec 19 09:58:16 SDS_BACKUP_NAS systemd-journald[1753]: Journal stopped
-- Reboot --
Dec 19 09:59:08 SDS_BACKUP_NAS systemd-journald[1759]: Runtime journal (/run/log/journal/) is 8.0M, max 191.8M, 183.8M free.
Dec 19 09:59:08 SDS_BACKUP_NAS systemd-journald[1759]: System journal (/var/log/journal/) is 56.0M, max 50.0M, 0B free.
Dec 19 09:59:08 SDS_BACKUP_NAS systemd-journald[1759]: Time spent on flushing to /var is 14.385ms for 2 entries.
Dec 19 09:59:08 SDS_BACKUP_NAS kernel: Initializing cgroup subsys cpuset
Dec 19 09:59:08 SDS_BACKUP_NAS kernel: Initializing cgroup subsys cpu
Dec 19 09:59:08 SDS_BACKUP_NAS kernel: Initializing cgroup subsys cpuacct

Though looking at the date the logs you sent are a few weeks old. Perhaps you meant to send a different set of logs?