ReadyNAS 2100 won't boot, disk lights on, power light off

Thanks very much for the replies mdgm and cloud.

To answer your questions

inode usage:

# df -i
df: invalid option -- i
BusyBox v1.18.4 (2011-03-28 19:05:01 PDT) multi-call binary.

Usage: df [-Pkmh] [FILESYSTEM]...

#

It appears that the busybox implementation of df is the "mini" version. Is there another way I can answer your question?

Backup jobs are all remote rsync servers to local share.
Logs:

# ls -l
-rw-r--r--    1    737513 Dec 10 16:07 backup_001.log
-rw-r--r--    1   5161841 Dec 10 16:14 backup_002.log
-rw-r--r--    1    588161 Dec 10 16:15 backup_003.log
-rw-r--r--    1 263446696 Dec 10 16:44 backup_004.log
-rw-r--r--    1 121744015 Dec 10 16:32 backup_005.log
-rw-r--r--    1    609174 Dec 10 16:05 backup_006.log
-rw-r--r--    1 127012558 Dec 10 16:39 backup_007.log
-rw-r--r--    1    400183 Jun 13  2013 backup_008.log
-rw-r--r--    1 258006931 Dec 10 20:47 backup_012.log
-rw-r--r--    1 188727175 Dec 10 17:06 backup_013.log
-rw-r--r--    1   5368536 Dec 10 16:14 backup_015.log
-rw-r--r--    1  11568244 Dec 10 16:12 backup_016.log
-rw-r--r--    1   2365328 Dec 10 16:05 backup_017.log
-rw-r--r--    1 160811116 Dec 10 16:39 backup_018.log
-rw-r--r--    1        32 Dec 10 16:07 status_backup_001
-rw-r--r--    1        32 Dec 10 16:14 status_backup_002
-rw-r--r--    1        32 Dec 10 16:15 status_backup_003
-rw-r--r--    1        32 Dec 10 16:44 status_backup_004
-rw-r--r--    1        32 Dec 10 16:32 status_backup_005
-rw-r--r--    1        32 Dec 10 16:05 status_backup_006
-rw-r--r--    1        32 Dec 10 16:38 status_backup_007
-rw-r--r--    1        32 Jun 13  2013 status_backup_008
-rw-r--r--    1        32 Dec 10 20:47 status_backup_012
-rw-r--r--    1        32 Dec 10 17:06 status_backup_013
-rw-r--r--    1        31 Dec 10 16:05 status_backup_014
-rw-r--r--    1        32 Dec 10 16:14 status_backup_015
-rw-r--r--    1        32 Dec 10 16:12 status_backup_016
-rw-r--r--    1        32 Dec 10 16:05 status_backup_017
-rw-r--r--    1        32 Dec 10 16:39 status_backup_018

Job 12 was the last to run and appears to have completed successfully. I became aware of the boot issue the following day. Just to make things interesting, I believe those times are shown in UTC -8 and I'm in UTC +8. The backups are scheduled to execute from midnight my time.

/.os_status contents:

# cat .os_status
BOOT
#

/varlog/frontview/enclosure.log contents:

# cat enclosure.log
disk!!1!!status=ok::descr=Channel 1: ST2000DM001-9YN164, 1863 GB
disk!!2!!status=ok::descr=Channel 2: ST2000DM001-9YN164, 1863 GB
disk!!3!!status=ok::descr=Channel 3: ST2000DM001-9YN164, 1863 GB
disk!!4!!status=ok::descr=Channel 4: ST2000DM001-9YN164, 1863 GB
model!!0!!mode=pro::descr=ReadyNAS 2100::arch=x86
Boot!!FS_CHECK!!100%
#

As far as I can tell, the data volume mounts without error. In fact I can't see anything in any of the logs that looks like an error, although I could easily be overlooking something.

The last things that appear in the logs after a boot seem to refer to the system restarting.
Messages:

# tail messages
Dec 12 13:08:04 nas-client1 kernel: iSCSI_TPG[1] - Added ACL with TCQ Depth: 16 for iSCSI Initiator Node: iqn.everyone
Dec 12 13:08:04 nas-client1 kernel: iSCSI_TPG[1]_LUN[0->0] - Added RW ACL for  InitiatorNode: iqn.everyone
Dec 12 13:08:04 nas-client1 kernel: Disabling iSCSI Authentication Methods for TPG: 1.
Dec 12 13:08:04 nas-client1 kernel: iSCSI_TPG[1] - Enabled iSCSI Target Portal Group
Dec 12 13:08:04 nas-client1 kernel: LIO_Target_ConfigFS: REGISTER -> iqn.2013-05.nas-client1:vmstore00 TPGT: 1 PORTAL: 192.168.1.178:3260
Dec 12 13:08:04 nas-client1 kernel: CORE[0] - Added Network Portal: 192.168.1.178:3260 on TCP on network device: None
Dec 12 13:08:04 nas-client1 kernel: CORE[iqn.2013-05.nas-client1:vmstore00] - Added Network Portal: 192.168.1.178:3260,1 on TCP on network device: None
Dec 12 13:08:04 nas-client1 kernel: CORE[iqn.2013-05.nas-client1:vmstore00]_TPG[1] - Incremented np_exports to 1
Dec 12 13:08:04 nas-client1 kernel: LIO_Target_ConfigFS: addnptotpg done!
Dec 12 13:08:09 nas-client1 syslogd 1.4.1#18: restart.
#

cron.log:

# tail cron.log
Dec 11 14:20:35 nas-client1 /usr/sbin/cron[2039]: (CRON) INFO (Running @reboot jobs)
Dec 11 15:59:04 nas-client1 /usr/sbin/cron[2089]: (CRON) INFO (pidfile fd = 3)
Dec 11 15:59:04 nas-client1 /usr/sbin/cron[2093]: (CRON) STARTUP (fork ok)
Dec 11 15:59:04 nas-client1 /usr/sbin/cron[2093]: (CRON) INFO (Running @reboot jobs)
Dec 12 13:00:07 nas-client1 /usr/sbin/cron[2067]: (CRON) INFO (pidfile fd = 3)
Dec 12 13:00:08 nas-client1 /usr/sbin/cron[2068]: (CRON) STARTUP (fork ok)
Dec 12 13:00:08 nas-client1 /usr/sbin/cron[2068]: (CRON) INFO (Running @reboot jobs)
Dec 12 13:08:03 nas-client1 /usr/sbin/cron[2064]: (CRON) INFO (pidfile fd = 3)
Dec 12 13:08:03 nas-client1 /usr/sbin/cron[2065]: (CRON) STARTUP (fork ok)
Dec 12 13:08:03 nas-client1 /usr/sbin/cron[2065]: (CRON) INFO (Running @reboot jobs)
#

Is the NAS being sent for a reboot and failing to shutdown??

I'm obviously missing something here.

Chris.