RN212 - Removed one disk, now cant see data on remaining disk

Ok, that gives a lot more detail!

PM sent

Thanks

Hi Paul_Thomas 

Thanks for the logs. I appreciate it.

Something very odd is going on here, something I have never seen before! The NAS operating system (OS) is definitely messed up, but I am pretty sure the data is just fine. I suspect that this oddity came about after you did the OS re-install. Something must have gone wrong then (not something you did). Firstly, the logs don't go back further than the 14th. This is because the NAS logs indicate that the NAS was factory defaulted, which it was not.

[2019/05/14 21:36:50 UTC] Factory default initiated on ReadyNASOS 6.10.0 (ReadyNASOS).
[2019/05/14 21:37:13 UTC] Updated from ReadyNASOS 6.10.0 (ReadyNASOS) to 6.10.0 (ReadyNASOS).

The hostname is also suspicious as that is the default name upon manual reflash of the OS.

May 14 14:37:19 readynasos connmand[2885]: System hostname is readynasos

Looking at the raids, we can see that the OS raid was re-created as well. Even more strangely the OS raid is now build with /dev/zram0 rather than /dev/sda1. The data raid looks fine tough.

--- OS raid ---
/dev/md/0:
Creation Time : Tue May 14 14:36:30 2019
/dev/zram0 <<<=== zram0??? What...

--- Data raid ---
/dev/md/data-0:
Creation Time : Wed Mar 21 02:34:51 2018
/dev/sda3 <<<=== Normal

Looking in the partition log, have zram0 and no sda1. Very strange!

8 0 3907018584 sda
8 2 524288 sda2
8 3 3902299936 sda3
250 0 4194304 zram0
9 0 4190208 md0
9 1 523712 md1
9 127 3902168832 md127

Anyhow, the data is unharmed here for all I can see in the logs. Getting access to the data is troublesome right now, probably because of the state of the OS. I reckon, to recover the OS, one would need to reinstate the sda1 partition, re-create md0 (OS) raid and flash a fresh OS install onto that. This can certainly be done but would require NETGEAR assistance.

Options? Unless you have a support contract it will cost a fee to have NETGEAR support fix this. If you have an up-to-date backup then that might be the best route here. Up to you :)

Cheers

Hi,

Many thanks for your detailed diagnostics.

Unfortunatly, I think we needed the log from when it first booted with the removed disk.  This boot was strange, I first thought there was a problem as the fans were at full speed for longer than usual & the boot process was very slow.  When I connected, it ran through the setup wizard, I also noticed a strange NAS name, it had a fomat somthing tike "xx xx xx xx" I think each xx may have been a hex number but I couldn't be certain now.  Each pair was different and there may have been 4 to 6 pairs.

I guess the OS is using the nvram disk as the main raid disk cant be accesssed/used for some reason.

As I mentioned, its not the data I need, I really wanted the share permissions.  I suspect even with an OS reinstall & making the disk accecible this would be lost as I would expect the UID & GID's to be different.

When I get some time over the weekend, I'll put the disk in my windows server & see what the disk looks like.  I'll then be doing a diskpart clean, befor adding it to the EDA500 to build an x-raid miror.

Thanks again for all your help & advice.

Paul

---

Paul_Thomas wrote:

 

As I mentioned, its not the data I need, I really wanted the share permissions.  I suspect even with an OS reinstall & making the disk accecible this would be lost as I would expect the UID & GID's to be different.

 

---

If you recreated the user accounts, they likely would be different.   You could try looking in the log zip file in shares.log, though it might not include your old shares. You could also log in with ssh, and look at the user accounts (though they might also have been trashed).

I suggest documenting this info on your RN314, so you will have it when needed.  For example capturing screenshots of the web ui, and also download the configuration files from system->settings.

---

Paul_Thomas wrote:

I also noticed a strange NAS name, it had a fomat somthing tike "xx xx xx xx" I think each xx may have

That would be the default NAS name - based on the ethernet mac address.

Thanks for all the help on this.  Hopefully it was a one off blip!

I've now put the disk in the EDA500 and the rn314, and that went fine.  A new (unusable) volume appeard as expected, I performed a "DESTROY" on the volume, and the disk was immediatly detected and started to mirror with the existing disk.

Thanks

Paul