Forum Discussion

Aspirant

Jul 24, 2020

Solved

Lost volume after migration from RN314 to RN3138

Hi I wanted to migrate my data and volume from a Readynas RN314 to a new rackmount RN3138. Shut down both units, transferred the drives and kept the same drive order. After boot I was able to l...

JohnCM_S
Jul 29, 2020
Hi Jellen,

This should be fixed now. Please check if you can now access your volume.

The OS was filled up so one of our L3 experts cleaned it. The problem could be the Docker because he saw that installed.

Regards,

Sandshark

Sensei - Experienced User

Jul 25, 2020

You didn't say you did, but I just want to verify that you did NOT export the volume (you shouldn't have).

Have you tried putting the drives back in the 314 and seeing what happens? Assuming the three drives you listed are all there is, you could try every combination of two and see if it'll boot with a degraded volume.

Jellen

Aspirant

Jul 25, 2020

Hi Sandshark

No I din't export the volume. John is looking into the logs but looks like my volume has 2 devices. I'll keep you guys up to date.

Strange thing on the device my 3X 8TB Seagete disks show the Hard disk light continuos on, the one WD 3TB drive flickers. It's all one volume.

Thanks for the replies, keeping fingers crossed to recover the volume.

StephenB
Guru - Experienced User
Jul 26, 2020
Jellen wrote:

John is looking into the logs but looks like my volume has 2 devices.

If you vertically expanded the RN314 (upgrading to larger disks), then you have two RAID groups - md126 and md127 if you use XRAID. Those show up as two inactive volumes in the admin web ui when the volume can't be mounted.
- Jellen
  Aspirant
  Jul 27, 2020
  Thanks StephenB for your feedback.
  
  Do you also know the solution to recover from this situation? Can you do something wrong with a firmware reinstall in this situation?
  
  Kind regards
  - StephenB
    Guru - Experienced User
    Jul 27, 2020
    Jellen wrote:
    
    Do you also know the solution to recover from this situation? Can you do something wrong with a firmware reinstall in this situation?
    
    There's several potential causes, and I think Netgear is in a better position to fix it. A firmware reinstall shouldn't have caused this.
    
    But you shouldn't have needed to do a firmware reinstall - all you needed to do was migrate the disks and power up the NAS. Did you do one anyway?