ReadyNAS RN316 - mount_block_root+1f1 - Issues creating USB Recovery

[matthewhaymes]

Hi all

THis morning my ReadyNAS 316 became unreachable via my network.  Upon reset I received the following error - "mount_block_root+1f1".  I cannot see the NAS via RAIDar.

This thread - https://community.netgear.com/t5/Using-your-ReadyNAS/RN516-quot-mount-block-root-1f1-quot-after-os-6... - recommends using the USB Recovery Tool.

I use a Mac, so I set up Parallels with Windows 10 and downloaded the tool and latest ReadyNAS OS 6 version, 6.7.4 (the same version that was/is on my NAS).  I can select the select the flash drive and format, select the product, select the model, but when it comes to "Select Firmware Image" nothing shows up. If I ignore this and press "Create" a message comes up, "Start to prepare USB recovery flash", but nothing happens.

The drives are WD40EFRX and have all passed the WD Lifeguard Quick Test.

Can anyone offer any suggestions?

[matthewhaymes · Accepted solution]

Success!

I purchased a Lexar JumpDrive 8GB from Woolworths at lunch.  Prepare it fresh using USB Recovery Tool and 6.7.4 on my work laptop.

First boot holding the OK button down, it looked like a few errors, but the LCD then showed "Booting...". After a minute, the NAS suddenly powered down.  I powered it up again without pressing the OK button.  LCD showed an error, complaing no drives were present.  Powered down, inserted the drives.  LCD showed "Booting..." then showed an increasing percentage.  At 31% I went to grab a coffee - screen was blank when I got back.  Booted up RAIDar on my Mac, and there it was.

Looks like all data and settings in place.

Is there anything I can send you to help root cause analysis or future troubleshooting?

[mdgm-ntgr]

You need to download the 6.7.4 firmware. If you download a zip file you need to extract the contents. Then place the .img file in the x86 folder of the USB Boot Recovery tool. Then the app should be able to use it.

[matthewhaymes]

Thank you for the response.  I'm fairly confident I have done this correctly.  I downloaded the ReadyNASOS-6.7.4-x86_64 ZIP file, then extracted the IMG file contained to the x86 folder.  I've tried resetting the app and rebooting the OS, but the app still doesn't seem to recognise that the IMG file is in place.

[matthewhaymes]

Screenshots - https://goo.gl/photos/L4AZJXmEYmzatFm58

[mdgm-ntgr]

Did you remember to right click on the tool and select to run it as an administrator?

[matthewhaymes]

Oh, no.  I didn't know that was required - must've missed it in the instructions.  

I just tested out this approach - unfortunately, with the same result.  

Could the fact that I am running this on a VM through Parallels have an impact?

[mdgm-ntgr]

It might. So you're running this from a Mac?

You could try using a 3rd party tool such as Rufus in the VM instead. A syslinux bootable key with a MBR bootloader should work. You'd need to put the files on the USB key (in addition to the syslinux bootloader hidden files that Rufus would put on when creating a syslinux bootable USB key):

initrd.gz

kernel

syslinux.cfg

ReadyNASOS-6.7.4-x86_64.img

NTGR_USBBOOT_INFO.txt

[matthewhaymes]

Yes, I am running Windows 10 in Parallels on macOS.

Your suggestion went straight over my head!  But always willing to learn.  

So Rufus is a Windows app that I should run on the the Windows VM.  I should use it to created a "syslinux bootable key with MBR bootloader" out of my USB.  In doing so, Rufus will add some hidden files to my USB.  I should then add the list of files you mentioned - thes come from the x86 folder of the Recovery Tool installation.  Sound about right?

[matthewhaymes]

OK - Rufus in progress.

These are the settings I've used, look OK? https://goo.gl/photos/9FzGQu7ctMem2Snh7

[matthewhaymes]

Now Rufus is done.  Plugged in the USB, booted up the NAS.  Held down OK until I saw the "Boot from external USB".  The message remains on the LCD screen.  So now I just let it do it's magic, or is that message incorrect?

[matthewhaymes]

I've now tried this with the 3 USB sticks I own:

• 8GB Toshiba TransMemory
• 16GB Kingston Datatravel
• 32GB Sandisk Cruzer

Same result - I get to the "Boot from external USB" message but it doesn't move past that point.

[mdgm-ntgr]

If you hook up the HDMI port to a display what do you see when trying to boot off USB?

You could try with these files instead of the default ones

https://www.readynas.com/contributed/mdgm/r6usbboot/latest/initrd.gz

https://www.readynas.com/contributed/mdgm/r6usbboot/latest/kernel

With these the NAS should boot into a tech support mode like state.

[matthewhaymes]

OK, wow.  For years using this thing and never even realise it had HDMI out.  Shame.

Here is a link to what I see on the screen (https://goo.gl/photos/uTAU3hcM95NZYDay6).  It looks like it is waiting on keyboard input...?  That photo album also includes the error on the screen if I do nothing.

I tried replacing those two files - so results.

I've taken my USBs to work, and am creating recovery drives with a Windows native laptop - working fine.  Will test them tonight.  Will also test them with the new files, if no love.

Do we have a list of USB drives known to have worked, to date?

[mdgm-ntgr]

O.K. You created a FreeDOS boot key. On that USB key perhaps now run our USB Boot Recovery tool (if you haven't already) to overwrite the key with a syslinux bootable USB key and see if you get any different results. Rufus creating a FreeDOS bootable USB key would put a good MBR on.

The image showing the mount_block_root error is showing a normal boot not one off USB.

[matthewhaymes]

The first screenshot was the result of using Rufus, then copying files you recommended earlier manually (USB Boot Recovery tool doesn't work on my Win 10 VM).

Correct, the second screenshot was the result if I didn't have anything plugged in - so 'normal' boot.

Now I'm at work, I've used the USB Recovery Tool to format all the USB drives, then Create.  

Is this ideal?  Or should I instead use Rufus to format the drives, then use the USB Recovery Tool to Create?

[mdgm-ntgr]

It depends on how the key is formatted. Our tool expects a good MBR and to have a single partition on the USB key.

You can try what you've created using your work PC and if that doesn't work proceed to try further things.

When you used Rufus clearly you selected to use the FreeDOS boot loader. Our USB Boot Recovery process uses the syslinux bootloader.

[matthewhaymes]

Ach, work computer blocks Rufus!

When I was using Rufus there were only options for FreeDOS, ISO Image, and DD Image - no syslinux.  Could that mean one of the other options I had select was incorrect?

[mdgm-ntgr]

Perhaps you weren't running it as an administrator. Anyway Rufus should have put a good MBR on and created a partition on the disk. So subsequently running our tool on the same key should be fine. Some have reported success creating a FreeDOS key using Rufus then running our usbrecovery.exe tool.

[matthewhaymes]

Finger-crossed.  I should be able to test by 7PM tonight.

Thanks for you help so far.

[matthewhaymes · Accepted solution]

Success!

I purchased a Lexar JumpDrive 8GB from Woolworths at lunch.  Prepare it fresh using USB Recovery Tool and 6.7.4 on my work laptop.

First boot holding the OK button down, it looked like a few errors, but the LCD then showed "Booting...". After a minute, the NAS suddenly powered down.  I powered it up again without pressing the OK button.  LCD showed an error, complaing no drives were present.  Powered down, inserted the drives.  LCD showed "Booting..." then showed an increasing percentage.  At 31% I went to grab a coffee - screen was blank when I got back.  Booted up RAIDar on my Mac, and there it was.

Looks like all data and settings in place.

Is there anything I can send you to help root cause analysis or future troubleshooting?

[mdgm-ntgr]

Thanks for the update. Glad it's now resolved.

I've already sent a dump of the internal flash (before fixing it) from another system to engineering. Not sure what more I could give them than that that might help.

Which firmware did you update from and to when running into the problem (would show in initrd.log)?

[Rottenweiler]

mount_block_root+1f1

Unable to EVER get to a boot menu no matter what I try?

I have tried the hidden reset button, have tried holding the OK button for 30 secs, no matter what I do, disks inserted, no disks, scratch disk, it NEVER shows any Boot Menu items like I would expect?

I have tried three different USB recovery sticks, one type that I KNOW worked on a previous recovery with no luck.

I DID create them as an administrator.

They do seem to create and flash properly.

Is there somwething I am missing?

I have three ReadyNAS 316 and am afraid now to power up the other two?

Do we have ANY idea or indication WHAT caused this problem to suddenly appear?

For me it occured after I had it running 6.7.4 just fine... powered down properly for a vacation and upon power up today the unit is now locked up at mount_block_root+1f1 

Can't access via RAIDar.

I do see some messages when booting/connected by HDMI cable.

Not sure what to do with them since I cant get to boot menu at all.

This has been a seriously frustrating month in my ReadyNAS world I have to say...

[Rottenweiler]

Follow up...

I was FINALLY able to get this USB recovery to work... in my case I would call it PAINful... 6 hours spent working reading the forums, trying a dozen USB drives, trying to recover... over and over

I did get it to work, I'm just NOT sure why...

Anyway, what DID work for me (and I have no idea WHY) was this...

Open a brand new (out of package) USB stick, in my case PNY 32GB USB 3.0 unit (Turbo Attache 3), insert into Windows 10 machine.

Did NOT format via Windows when asked.

Ran the Netgear ReadyNAS USB Recovery Utility AS ADMINISTRATOR

I did NOT format using the utility.

I simply went directly to selections for my ReadyNAS unit and hit CREATE.

Finished the program, closed it, safe eject, insert into ReadyNAS 316 and powered on.

THIS time while holding the center OK button, the OK button light STAYed lit (hadn't happened on multiple prior attempts)...

The LCD flashed to say "Boot from external USB"... it then proceeded to boot (Thank the gods...)

Once booted, went to the RAIDar, then Admin page and then attempted to manually install the firmware as had been suggested....

NOW I am getting a failure when trying to upload the 6.7.4 image via the Web GUI page? Unrecognized Server Error.

[matthewhaymes]

I update from 6.7.1 to 6.7.4 on June 1st.  Since then I had been having intermittent connectivity issues, where my network could see the NAS and the shares, but the folders and files were inaccesible.  June 12th I couldn't get any access, so performed a reboot - that's when the mount_block_root+1f1 appeared.

[Rottenweiler]

Same scenario for me, my unit had been doing fine, ReadyNAS 316, running v6.7.4, it was AFTER a graceful power down and then when the unit was re-powered on a few days later, this drama...