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.
ReadyNASinUK
Jan 13, 2022Aspirant
StephenB wrote:Are you seeing any file names starting with backup and including 143462034 in the log zip file? For instance, something like
backup_008_copy.1434962034.log
No, a few files like that but all with a number starting 1641...
If not, open each backup status log in turn
backup_001_status backup_002_status ...and until you find the one where the content includes a match for that number
BACKUP_STATUS__IN_PROGRESS!!1434962034!! ...
Once again no luck. For interest, they start with 1641... and 1642... so nothing even similar.
Thanks for the suggestion though, anything else I could try?
StephenB
Jan 13, 2022Guru - Experienced User
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.
- ReadyNASinUKJan 14, 2022Aspirant
StephenB your SUPERGURU status is well deserved!
StephenB wrote:
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.I tried exactly this and the power off sequence works now, as expected. I rarely used the backup button, if that was the source of the 000 file - so I'll let that sleeping dog lie and do without it.
I did consider diving into the NAS filesystem and looking for a file like this to delete, but would not have dared to do it without your advice, in case of unexpected damage.
Thanks again, Angus.
PS there was a typo in the path you suggested which I have fixed in the quote above, for info to anyone finding this solution in the future.
Related Content
NETGEAR Academy

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