ReadyNAS Pro 6 Firmware reinstalled but won't restore config

[markbarlow]

dmesg results...

[StephenB]

The partitions list shows that the partitions needed for the data volume are on the disks.  It also shows that the RAID is already assembled.

 9 0 4190208 md0
 9 1 1566720 md1
 9 127 19510844160 md127

So you should be able to mount the data volume using

mount -o ro /dev/md127 /data

That should mount the volume as read-only.  After you do that, ls -als /data should show your shares.

dmesg shows there is file corruption in your OS partition.  That is not surprising (as rnutil chroot failed earlier).

[ 595.213837] BTRFS critical (device md0): corrupt leaf, invalid file extent type:
block=54001664, root=1, slot=67
[ 595.223846] BTRFS critical (device md0): corrupt leaf, invalid file extent type:
block=54001664, root=1, slot=67
[ 595.223876] BTRFS error (device md0): Error removing orphan entry, stopping
orphan cleanup
[ 595.223882] BTRFS error (device md0): could not do orphan cleanup -22
[ 595.337133] BTRFS error (device md0): open_ctree failed
[ 682.190323] EXT4-fs (md0): VFS: Can't find ext4 filesystem
[ 682.190922] BTRFS info (device md0): has skinny extents
[ 682.244639] BTRFS critical (device md0): corrupt leaf, invalid file extent type:
block=54001664, root=1, slot=67
[ 682.255034] BTRFS critical (device md0): corrupt leaf, invalid file extent type:
block=54001664, root=1, slot=67
[ 682.255053] BTRFS error (device md0): Error removing orphan entry, stopping
orphan cleanup
[ 682.255055] BTRFS error (device md0): could not do orphan cleanup -22
[ 682.361132] BTRFS error (device md0): open_ctree failed
[ 2240.568391] BTRFS: device label 33eaaddd:data devid 1 transid 352962 /dev/md127
[ 3348.180959] BTRFS info (device md0): has skinny extents
[ 3348.299370] BTRFS critical (device md0): corrupt leaf, invalid file extent type:
block=54001664, root=1, slot=67
[ 3348.299615] BTRFS critical (device md0): corrupt leaf, invalid file extent type:
block=54001664, root=1, slot=67
[ 3348.299646] BTRFS error (device md0): Error removing orphan entry, stopping
orphan cleanup
[ 3348.299652] BTRFS error (device md0): could not do orphan cleanup -22
[ 3348.711124] BTRFS error (device md0): open_ctree failed

The OS reinstall you did before didn't resolve this.

My suggestion now: If the mount command above works, then rebooting the NAS, and see if your data volume mounts properly (it should).

Once you've confirmed that,

1. Backup all the files
2. Do a factory default to fix the file corruption.
3. Reconfigure the NAS and restore the files from your backup.

[markbarlow]

Unfortunately it won't mount...

# mount -o ro /dev/md127 /data
mount: mounting /dev/md127 on /data failed: No such file or directory
# ls -als /data
ls: /data No such file or directory

[markbarlow]

Would reinstalling the OS via the USB Recovery Tool as described here...

https://kb.netgear.com/29952/How-do-I-use-the-USB-Recovery-Tool-on-my-ReadyNAS-OS-6-storage-system

Also, because this is unsupported with OS6 is this the correct choice or should I use the OS4.2 USB Recovery Tool?

https://kb.netgear.com/30267/RAIDiator-4-2-USB-Recovery-Tool

Thanks,

M:-)

[StephenB]

---

@markbarlow wrote:

Unfortunately it won't mount...

# mount -o ro /dev/md127 /data
mount: mounting /dev/md127 on /data failed: No such file or directory

---

Was your data volume called data?

Or was it called something else?

If you aren't sure, try 

mount -o ro /dev/md127 /mnt

I don't recommend a USB recovery right now.

[markbarlow]

Well that mounted and I can use the Telnet login to view the shares and directories but when I do a standard boot and navigate to the web admin UI it still doesn't show the volume.

When I reboot again and go back into support mode it doesn't re mount the volume and I have to do that manually again.

Mark 🙂

[StephenB]

---

@markbarlow wrote:

Well that mounted and I can use the Telnet login to view the shares and directories but when I do a standard boot and navigate to the web admin UI it still doesn't show the volume.

When I reboot again and go back into support mode it doesn't re mount the volume and I have to do that manually again.

---

There does appear to be some damage to the OS partition (we first saw that when rnutil chroot failed)

If you have some USB drives, we could attempt to connect them to the NAS and mount them.  Then you could copy files off using linux commands. Then the data would be safe.

You could also try another OS reinstall, and see if that helps.  As a reminder, it would reset the admin password to password and it will also reset the NAS network configuration to use DHCP with no bonding.

[Sandshark]

USB recovery on a legacy ReadyNAS must be done using the OS4.2 recovery system but with a re-named OS6 bios file.  Since USB recovery doesn't check the BIOS version, it's not necessary to use one that's been altered as when upgrading from OS4.2.x to OS6.

[StephenB]

---

@Sandshark wrote:

USB recovery on a legacy ReadyNAS must be done using the OS4.2 recovery system but with a re-named OS6 bios file.  Since USB recovery doesn't check the BIOS version, it's not necessary to use one that's been altered as when upgrading from OS4.2.x to OS6.

---

@markbarlow:  It is quite possible that you will need to do the USB recovery.  But I suggest off-loading data first if you can, and then trying the OS reinstall first.

Though if we can offload all the data, I think a factory default is a better path.  Though painful, that gives you a completely clean system.

[markbarlow]

Thanks Stephen, I really appreciate your help. Mark 🙂

[markbarlow]

How do I rename the OS6 bios file to use with the OS4.2 recovery system?

Is there a support article on the process?

Thanks,

Mark 🙂

[markbarlow]

Also, if I connect an external USB drive, will it mount automatically or do I need to mount that manually?

If manual, how do I do this?

Thanks,

M:-)

[StephenB]

---

@markbarlow wrote:

Also, if I connect an external USB drive, will it mount automatically or do I need to mount that manually?

---

I'm not sure, given your damaged OS.

You might need to format the drive as FAT32 (or even EXT).  FAT32 wouldn't allow files bigger than 2 GB; EXT doesn't have that limitation, but can't be mounted on Windows (and I think Mac).

[markbarlow]

Hi @StephenB,

I have mounted the USB drive and recovered the small number of files that weren't backed up.

I would like to use the USB Firmware recovery process and see if I can get it running without having to restore all the other data.

How do I rename the OS6 bios file to use with the OS4.2 recovery system?

Is there a support article on the process?

Thanks,

Mark 🙂

[StephenB · Accepted solution]

---

@markbarlow wrote:

I have mounted the USB drive and recovered the small number of files that weren't backed up.

---

Great news.

---

@markbarlow wrote:

Is there a support article on the process?

---

https://kb.netgear.com/30267/RAIDiator-4-2-USB-Recovery-Tool

Note the prep requires use of a Windows PC.  Also note the warning in the article. One thing the warning doesn't say - the NAS can be quite fussy about the USB drive. Generally it works best to use older/smaller flash drives.  Using one that has an activity light is often useful, as it gives you some evidence that the drive is being accessed during the process.

Though doing the recovery could save some time, I'd personally just do the factory default.

---

@markbarlow wrote:

How do I rename the OS6 bios file to use with the OS4.2 recovery system?

---

You can just rename it to match the 4.2.31 firmware before you select it via the recovery tool. (RAIDiator-x86-4.2.31)

Make sure you extract the image from the zip file.

[markbarlow]

Thanks for all your help @StephenB, I have Factory Reset the NAS and are pulling down the backed up files from MEGA.NZ

I really appreciate all your help!

Feel free to link with me on LinkedIN, and if you need anything in the future, don't hesitate to ask.

Cheers,

Mark 🙂

https://www.linkedin.com/in/markalistairbarlow/