This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
ReadyNas Pro4 does not boot - at 85% fvbackup-q.service - Management service is offline
Hi,
My ReadyNAS Pro 4 will not boot anymore. It keeps hanging at 85% fvbackup-q.service, Raidar shows Management service is offline, and I can't login the admin-page anymore.
I have already read a lot and tried some things, but without success. I am curious if somebody can help me out with this issue.
I have upgraded the Readynas to OS6 last summer 2023 to 6.10.8, with all the good instructions from this community. I use it as COLD storage for backup purpose, so it's turned on like once per week. It ran like stable for 10months, but as of last week, it won't boot again.
I have read some related articles from this community, in which I recognize my issue, but can't find the steps to fix it for myself.
Re: ReadyNas Pro4 does not boot - at 85% fvbackup-q.service - Management service is offline
Of course the issue is here:
3.1G /mnt/media
/media only should contain mount points for USB drives (e.g., USB_HDD_1,etc). These mount points should be empty. So look in each subfolder and delete the files you see there (leaving the mount points).
Files can end up in these folders when a USB drive disconnects when a backup job is running.
FWIW, remounting the root as /mnt is useful when the NAS is running normally, as it keeps the mounts out of the way. It isn't needed in tech support mode, as nothing (including your data volume) should be mounted on a root folder.
Re: ReadyNas Pro4 does not boot - at 85% fvbackup-q.service - Management service is offline
In the third post you referenced, the poster's issue did seem to be a full OS partition, though he never showed what the partition use was before he deleted a lot of superfluous files and never explicitly says the file deletion he did was the fix. Do you have SSH enabled so you can check the OS partition use? The other poster still had SSH access when it failed to fully boot.
Also, do you have data you have to off-load? If not, have you tried doing a factory default?
I do have a backup, but it's like at least 2 months old, and I have organized some file recently. So it's no lifechanging event if I loose the recent changes, but I would really dislike that. That would be my final solution if nothing else prevails. Hence, I have not done a factory default yet.
In the third post you referenced, the poster's issue did seem to be a full OS partition, though he never showed what the partition use was before he deleted a lot of superfluous files and never explicitly says the file deletion he did was the fix. Do you have SSH enabled so you can check the OS partition use? The other poster still had SSH access when it failed to fully boot.
I can't remember that I have enabled it on OS6, since it's default is OFF, I would say the SSH is disabled.
Also, I have tried to SSH it with Putty (port 22), the response is "Fatal Error, Network error: Connection refused". I would again say the SSH is disabled.
However, I am able to reach it with Putty>Telnet from Tech-support mode.
Re: ReadyNas Pro4 does not boot - at 85% fvbackup-q.service - Management service is offline
Of course the issue is here:
3.1G /mnt/media
/media only should contain mount points for USB drives (e.g., USB_HDD_1,etc). These mount points should be empty. So look in each subfolder and delete the files you see there (leaving the mount points).
Files can end up in these folders when a USB drive disconnects when a backup job is running.
FWIW, remounting the root as /mnt is useful when the NAS is running normally, as it keeps the mounts out of the way. It isn't needed in tech support mode, as nothing (including your data volume) should be mounted on a root folder.
/media only should contain mount points for USB drives (e.g., USB_HDD_1,etc). These mount points should be empty. So look in each subfolder and delete the files you see there (leaving the mount points).
There was exact one .iso file of some old disk, the origin is from another system from which I push backup to the USB drive of this NAS over the network. I have deleted it with the command.
rm "abc.iso"
I googled all kinds of Linus commands to decipher your original code and then to list all subdirectories and files, and then i used cd to navigate to the folder. Actually, I found it really fun to do 🙂
I kinda was understanding with your help what I was doing and solving. Thank you for that being inspirational, not only for the solution and help, but also making me find out I liked this.
To be honest, yesterday I also was looking for some files to delete, since I guessed it would be the next step. But I was like focusing on /mnt (it says also 3.1G), but is is of course the parent directory. And I was really blind as it appears, because I really didnt see the /media folder.... like really blind, because I have scanned the list with 16 directories for like 10 times.
Files can end up in these folders when a USB drive disconnects when a backup job is running.
This is certainly possible, since I have timed it with some schedule (incl. shutting down HDD power), so I'm going to look into this schedule and improve it.
FWIW, remounting the root as /mnt is useful when the NAS is running normally, as it keeps the mounts out of the way. It isn't needed in tech support mode, as nothing (including your data volume) should be mounted on a root folder.
I do not really understand what you mean with this phrases. What do you mean?
Soms additional actions I took:
I have enabled SSH on root and on admin. I have downloaded the public_key.txt.
I upgraded the firmware to 6.10.10
I checked if I have some apps installed, but I haven't any
Some questions from this:
What is the difference between using PuTTY in SSH or Telnet? SSH failed since it was disabled, but Telnet was still possible, luckily.
I have upgraded this from OS4 to OS6. The boot menu shows "OS Reinstall". I'm not going to do that, but what will be reinstalled exactly? Is it going to OS4 or OS6 then?
It now has better results:
root@2HU422030133D:/# df /mnt Filesystem 1K-blocks Used Available Use% Mounted on /dev/md0 4190208 626496 3170944 17% /mnt root@2HU422030133D:/# btrfs fi df /mnt Data, single: total=3.58GiB, used=569.25MiB System, DUP: total=8.00MiB, used=16.00KiB Metadata, DUP: total=204.56MiB, used=13.27MiB GlobalReserve, single: total=16.00MiB, used=0.00B
FWIW, remounting the root as /mnt is useful when the NAS is running normally, as it keeps the mounts out of the way. It isn't needed in tech support mode, as nothing (including your data volume) should be mounted on a root folder.
I do not really understand what you mean with this phrases. What do you mean?
Your earlier post indicated you were using tech support mode. But you were exploring /mnt in your later post. I was assuming you were still using tech support mode. If you were, then there is no need to do the mount --bind / /mnt as you can just explore //.
As far as mount points go - they are placeholder folders. The NAS mounts file systems using these mount points (for example, the data volume is usually mounted as /data). Before the file system is mounted, /data is supposed to be just an empty folder. Afterwards it is used to access the data volume. If there are files in the /data folder before you mount the file system, then they are hidden by the mount. The mount command above works around that problem.
What is the difference between using PuTTY in SSH or Telnet? SSH failed since it was disabled, but Telnet was still possible, luckily.
As I mentioned above, Telnet is only supposed to work in tech support mode (using root as the username, and a backdoor password). SSH is what you'd normally use if the NAS is running.
I have upgraded this from OS4 to OS6. The boot menu shows "OS Reinstall". I'm not going to do that, but what will be reinstalled exactly? Is it going to OS4 or OS6 then?
When you install firmware, the NAS puts a copy of the installation package into its flash, as well as installing it to the disks.
The reinstall does a partial reinstallation of the OS from that package. So with the NAS is running 6.10.10, then the OS reinstall will partially reinstall 6.10.10.
While it is data-safe, it does make a couple of other changes:
the admin password is reset to password
the network configuration is set to use DHCP with no bonding
volume quota is disabled (it can be re-enabled from the volume settings wheel).
Your earlier post indicated you were using tech support mode. But you were exploring /mnt in your later post. I was assuming you were still using tech support mode. If you were, then there is no need to do the mount --bind / /mnt as you can just explore //.
Ok, I understand now. At first I was just typing what u did. Now I understand the bind.
The reinstall does a partial reinstallation of the OS from that package. So with the NAS is running 6.10.10, then the OS reinstall will partially reinstall 6.10.10.
What means a Partial reinstall? What is partly about it?
What means a Partial reinstall? What is partly about it?
Netgear hasn't said exactly what it reinstalls, and I haven't tried to figure it out.
But we know it doesn't overinstall everything, because there are situations where people have made mistakes with updating packages with SSH, and the OS reinstall didn't repair the damage.
