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.
NAS not starting up - RN31400 - mount_block_roots_+1f1
Hi,
Our RN31400 NAS will not boot. On Friday it was switched off. When we try to switch it on it shows thie messege: mount_block_roots_+1f1.
Some posts online suggest USB recovery. However this page states we are not suppose to use it unless Netgear Technical support recommends it themself. Our pririty is to get files of the drives right now. Fixing it / returnign it for warranty is secondary (still important fo course). Does anyone know what's best thing to do now?
You may want to contact Support for assistance on USB Recovery but you are correct mount_block_root error means the NAS cannot mount the internal flash that is why it needs the USB Recovery procedure to resolve this.
You may want to try and access the boot menu and boot the NAS on volume read only mode to check if you will be able to access the data but it might not properly boot due to the error.
The best thing is to do the USB Recovery though it should not affect your data it would still be best that you have a full backup saved for safety. You may have to try several USB drives.
You may want to contact Support for assistance on USB Recovery but you are correct mount_block_root error means the NAS cannot mount the internal flash that is why it needs the USB Recovery procedure to resolve this.
You may want to try and access the boot menu and boot the NAS on volume read only mode to check if you will be able to access the data but it might not properly boot due to the error.
The best thing is to do the USB Recovery though it should not affect your data it would still be best that you have a full backup saved for safety. You may have to try several USB drives.
Re: NAS not starting up - RN31400 - mount_block_roots_+1f1
Hi Marc, Yeah, just after I worte this post I contacted suport as well. They suggest to use USB recovery and it's up and running again. Thanks for a quick reply and alternative suggestion as well 🙂
