NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS error: "mount_block_root+1f1"
After installing the 6.7.3 firmware (6.7.1 > 6.7.3 upgrade), I'm seeing the error message "mount_block_root+1f1" on the LCD. I was going to try the USB Recovery method, but I saw in this similar thread that it isn't working as a go-to solution. I see mdgm-ntgr has been able to solve this error for McRob1, so I'm hoping he can do the same here and spell out the steps involved.
USB Recovery with a variety of thumb drives, syslinux.exe versions and 6.7.3/4 didn't work on the unit that was having trouble.
Netgear sent a replacement 314, and the USB Recovery process worked great (on the first try!) for updating the firmware.
So the problem was that 6.7.3 effectively bricked my unit.
21 Replies
Replies have been turned off for this discussion
USB Boot Recovery is the solution. Be sure to right click on usbrecovery.exe and select Run as Administrator.
If USB Boot Recovery doesn't work for you you can try multiple USB keys. Some USB keys are incompatible.Some users who've had trouble with creating a USB Boot Recovery key with usbrecovery.exe have had success with Rufus
With Rufus you'd select the MBR partition scheme for BIOS or UEFI and select FAT32 as the filesystem (default) and the default cluster size.
Once the mount_block_root error is dealt with if there are any remaining issues we can see whether we can look into those.
It's not working. I tried using a 4GB SanDisk Cruzer, but the 314 kept booting as normal even though I was holding the Backup button. That resulted in the "mount_block_root+1f1" error.
Tried formatting the same USB drive using Rufus, but the instructions were unclear. Is "FreeDOS" the right choice? Do I run Rufus and then run usbrecovery.exe? Do I transfer the contents of a USB created with usbrecovery.exe to a Rufus-formatted USB?
Then I tried a Patriot 8GB USB drive. Now the 314 is in this weird state where it says "Netgear Storage / Welcome [ ]" and the power button is flashing. There doesn't appear to be any USB disk activity.
The disk needs to be syslinux bootable.
The same contents of the x86 folder that usbrecovery.exe puts on the USB key need to be put on the USB key.
Rufus should put the syslinux boot loader on the USB key itself if you chose the correct option.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
