NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNASinUK
Jan 11, 2022Aspirant
ReadyNAS RN104 Power Timer not switching off
After working for years, our ReadyNAS has stopped switching off out-of-hours. I have tried switching the power timer off and back on. Also using State and Event switching, though when it was worki...
- Jan 13, 2022
ReadyNASinUK wrote:
Thanks for the suggestion though, anything else I could try?
This suggestion will require ssh.
The poweroff script checks for running backup jobs using this check:
# Check for running backups. if grep -q 'IN_PROGRESS' /var/log/frontview/backup/status*; then OK_TO_HALT=0 CAUSE="backup job `grep -l 'IN_PROGRESS' /var/log/frontview/backup/status* | sed 's/.*status_backup_//' | xargs echo`" fi
This is intending to search files like
- status_backup_001
- status_backup_002
- ...
for "IN_PROGRESS". If it sees that string in any of those files, it holds off the shutdown. Though the search is broader than needed (all files that start with status are being scanned).
status_backup_XXX seems to be renamed to backup_XXX_status in the log zip.
Backup jobs on all my OS 6 ReadyNAS start with 001. So one puzzle is why status_backup_000 exists at all. I don't program the backup button, so one possibility is that 000 is used for that??? Just a total guess.
One thing you could do remove all backup jobs from from the backup button sequence (just in case the guess is correct). Then enable ssh and rename /var/log/frontview/backup/status_backup_000 to xstatus_backup_000. Reboot the NAS, and the power schedule should then work correctly. After you've confirmed that, you can re-add the backup jobs to the backup button sequence.
StephenB
Jan 11, 2022Guru - Experienced User
ReadyNASinUK wrote:
Other notes: in case it makes any difference, it has 6GB compared to the 2GB when orginally purchased)
The RN104 memory is soldered on (and it came with 512 mb, not 2 GB). Can you double check the NAS model?
ReadyNASinUK wrote:
After working for years, our ReadyNAS has stopped switching off out-of-hours.
There are a couple of things that will hold off a scheduled shutdown
- Backup job in progress (including ReadyDR)
- volume being resynced/reshaped/recovered
- RAID group in process of being deleted
Have you checked that those don't apply?
- ReadyNASinUKJan 12, 2022Aspirant
StephenB wrote:
ReadyNASinUK wrote:Other notes: in case it makes any difference, it has 6GB compared to the 2GB when orginally purchased)
The RN104 memory is soldered on (and it came with 512 mb, not 2 GB). Can you double check the NAS model?
The model is as stated in the header, orgininally with 2x 1GB disks but now with 3GB disks. Can't see how that would make a difference but...
ReadyNASinUK wrote:After working for years, our ReadyNAS has stopped switching off out-of-hours.
There are a couple of things that will hold off a scheduled shutdown
- Backup job in progress (including ReadyDR)
- volume being resynced/reshaped/recovered
- RAID group in process of being deleted
Have you checked that those don't apply?
1. ReadyDR does not run on RN104 afaik. All jobs are completed or failed (failed, if that PC is away for example) long before shut down time.
2. Nothing I can see in the main log. Bear in mind this fails every day. Is there somewhere to check if the system thinks one of these is in progress? - maybe not completed for some obscure reason? NB this error survives reboots and firmware upgrades.
3. Ditto as 2
- StephenBJan 12, 2022Guru - Experienced User
ReadyNASinUK wrote:
Nothing I can see in the main log. Bear in mind this fails every day. Is there somewhere to check if the system thinks one of these is in progress? - maybe not completed for some obscure reason?Have you downloaded the log zip file?
Look in system.log (searching for "Shutdown delayed").
- ReadyNASinUKJan 12, 2022Aspirant
StephenB wrote:
ReadyNASinUK wrote:
Nothing I can see in the main log. Bear in mind this fails every day. Is there somewhere to check if the system thinks one of these is in progress? - maybe not completed for some obscure reason?Have you downloaded the log zip file?
Look in system.log (searching for "Shutdown delayed").
Ah yes... I have looked in these logs before but clearly not well enough.
1. Strange, but the logs only seem to have activity for today. I don't recall clearing them.
2. Looking at a log from a few months back, there is a daily: Shutdown delayed due to backup job 000 in progress.
3. In both sets of logs, there is no file backup_000.log
4. In both sets there is a file backup_000_status with one line: BACKUP_STATUS__IN_PROGRESS,0!!1434962034!!OK
So my question is, how do I find out what backup job 000 is so I can delete it? I have many jobs, so I would rather not delete them all and start again. I don't see a reference number in the job settings.
I guess, if there is not a simple answer, I could write down all the jobs that have a log file, and check against the list of jobs. Or is job 000 some system backup?
Thanks for a very helpful answer.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!