× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: ReadyNAS 2100 won't boot, disk lights on, power light of

chrisdavies
Aspirant

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

Hi,

I have a ReadyNAS 2100 which locked up after I tried to view a backup log through frontview.
Although frontview was unresponsive, the device still responded to pings. after waiting a day or son I decided to reboot it.
It wouldn't shut down with the usual power button sequence, so I held the button till it stopped. On reboot, it sent an email indicating a firmware update is available (currently 4.2.19, suggested to go to 4.2.24), responded to pings and appeared briefly in Raidar, then disappeared and stopped pinging. When I checked the unit which is in my climate controlled server room, the 4 disk lights were on, network light was flickering and power light was *off*.

Subsequently I tried pulling the power lead and leaving it for 10 mins before rebooting - no change.
I also tried a OS reinstall from the boot menu - no change.

In techsupport mode I can verify that the 4GB partition is not filled by backup logs (40% used).

None of the logs I have looked at give me any clues, but I can't see a log of a failed boot to help me determine what is actually failing.

Can anyone help me with the location of that log, or make a suggestion as to how to proceed from here.

Cheers,

Chris.
Message 1 of 7
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNAS 2100 won't boot, disk lights on, power light of

What's the inode usage like?

# df -i


What's the size of the backup job log?

Was the backup in progress when the NAS hung?

On the OS partition what are the contents of /.os_status and /var/log/frontview/enclosure.log ?
Message 2 of 7
cloud1
Aspirant

Re: ReadyNAS 2100 won't boot, disk lights on, power light of

what else did you see in tech support? Did you try to start RAID of the data volume? Systme logs is in OS partition: /var/log
Message 3 of 7
chrisdavies
Aspirant

Re: ReadyNAS 2100 won't boot, disk lights on, power light of

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.
Message 4 of 7
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNAS 2100 won't boot, disk lights on, power light of

I thought looking at the above output some of the backup logs were pretty big. There was 1.1 GB of logs in /var/log

That's huge. And there was an attempt to download the logs. So while the OS partition was full the system would have choked trying to deal with such huge log files.

Via a Teamviewer session I removed the relevant spool file and some large backup logs, checked quickly for other possible problems, synced writes, unmounted the OS partition, stopped the RAID and rebooted.
Message 5 of 7
chrisdavies
Aspirant

Re: ReadyNAS 2100 won't boot, disk lights on, power light of

And now it all works perfectly again, with no data loss.

Thanks very much for the time you put into this mdgm.

Chris.
Message 6 of 7
iros
Aspirant

Re: ReadyNAS 2100 won't boot, disk lights on, power light of

Hello.

I have same problem with RN2100

Can anybody help me ?

 

Message 7 of 7
Top Contributors
Discussion stats
  • 6 replies
  • 2262 views
  • 0 kudos
  • 4 in conversation
Announcements