BRICKED

[MLBBERK]

Product is not eligible for support.  The device appears in comcast router page of connected devices but is not accessible in either Windows or Mac environments.  I would like to retrieve my data and thought I could use a Paragon Linux reader software to view the files and decide what to keep and what to trash.  Software won't mount the drive (s).  I can wipe the drives and use them, but I don't want to do it until I know what I am erasing.  Is there any hope of solving this.  No one at Netgear will talk to me, spend over an hour and a half on hold, then got transferred to a black hole. Twice.  Can't write to them because warranty is timed out. Really need some help here.

If you want to make a suggestion please cc: murraylberkowitz@gmail.com

thanks in advance

[Sandshark · Accepted solution]

If you are just starting fresh, with no intention of recovering any data on the current drives, remove the old ones and install the new ones and all will start in the factory fresh condition.  You won't have to do anything special.

If you intend to replace the drives one at a time to grow the volume and retain the data, then you first need to get access.  You do an OS re-install with both current drives installed.

[StephenB]

What ReadyNAS model are you talking about?  There are several lines (running different firmware), and the resolution depends on what model you have.

Can you log in if you browse to https://nas-ip-address/admin in your browser (using the real IP address)?

[MLBBERK]

thanks for the reply: no I did not try that but here is the model NAME RN 10200. MODEL #RND-2D

[MLBBERK]

Additonally, I used a comamand prompt to get the IP address, and when I tried to ping it the reply was "no direct path to device". I think there may be some Windows security barriers in the mix. I have win10 latest update, and Mac Big Sur also latest update.  Neither machine could connect but both showed the presence of the NAS.  

[Sandshark]

Perhaps you should start from the beginning.  How were things set up when the files were placed on the NAS?  What has changed since then?

[StephenB]

I agree that it would be good to start from the beginning.

---

@MLBBERK wrote:

 here is the model NAME RN 10200. MODEL #RND-2D

---

That would be an RN102, not a Duo.

---

@MLBBERK wrote:

Additonally, I used a command prompt to get the IP address

---

What IP address did you get?

[MLBBERK]

I read the model number off the label on the bottom I took it down after two days and can start it up again  if you need the specific address, but it was something like 198.68.0.0, or close.  Let me know if you need the precise IP address and I will provide it. thanks very much for replying.

[StephenB]

---

@MLBBERK wrote:

if you need the specific address, but it was something like 198.68.0.0, or close.  Let me know if you need the precise IP address and I will provide it. thanks very much for replying.

---

I think we do need it actual IP address.

It would also be good to know exactly how you found it.

[Sandshark]

That's the IP address of your router.  We need to know the IP address of the NAS -- the one you say you got via the command prompt and pinged.  This is all unusual because the normal ways to get the IP address for the NAS are via the GUI of your router or RAIDar.

[MLBBERK]

sorry, you are correct. it was 10.0.227

[MLBBERK]

10.0.0.227

[Sandshark]

That's an odd address, though not necessarilly wrong.  It's just atypical that it would be assigned so high unless you did something specific to cause that.  But if that is the address and 198.68.0.0 is the router IP, that's your problem and we need to figure out how you got there.

Again, please start from the beginning.  How was it set up when it was working?  What changed between then and now (the router, perhaps)?  How did you determine that is the correct IP address of the NAS?

It would also be helpful to know the local IP address of your computer.  You can get that by runing ipconfig in the command prompt.  In fact, this whole section would be helpful:

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::7de2:55b:aadb:94cc%14
   IPv4 Address. . . . . . . . . . . : 192.168.0.6
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1

Or the WiFi section if you are connected that way. 

[MLBBERK]

OK I will try it again tomorrow and see if I can get what you asked for.  Again, I really appreciate your patience and trying to help.

[MLBBERK]

attached is the ipconfig/all cmd results.  While the other day it did show the NAS, it does not now. I tried to do a factory reset on the NAS because the last time it was used was in a different residence with a different ISP and I thought the issue was to wipe that from the NAS and start a setup all over again. I held the reset down for a minute while holding it down and pwoering up.  All lights in the front (blue) are lit, indicating both dirves are powered up and the backup light is on as well. No luck at all.  Perhaps if the the NAS won't reset, them perhaps it is hopeless.  I just wish there was way to read the drives and then I would be happy to get a new one.  I did use the Comcast software to show connected devices on my Mac, where yesterday it clearly showed the NAS, but I am sorry I didn't take a screen shot of it because it is not showing today. I have attached a current screen shot as well, if it helps at all.  I think there are only 3 devices that are connected by ethernet, everything else is wireless. So the Sonos devices are identified and the unknown could be the NAS  Thanks again for all of your help, but I am close to surrendering. 

[StephenB]

---

@MLBBERK wrote:

attached is the ipconfig/all cmd results.  

---

Actually that's not what you attached - you attached the device list from your router's web ui screen.  Not CMD at all (and no ipconfig/all results).

The NAS is connected with ethernet, and most of the ones in your screenshot are connected by wifi.  However, the first offline device shown says it was connected with ethernet, and it has e8:fc:af:82:30 as its mac address.  That is assigned to Netgear, so I suspect it is your NAS. 

If so, the question then is why is it off-line???  If you look at the back of the NAS, you should see an LED on the ethernet port.  It should be green (or perhaps yellow if you have an old router).  Can you see if that is lit?

---

@MLBBERK wrote:

 I tried to do a factory reset on the NAS because the last time it was used was in a different residence with a different ISP and I thought the issue was to wipe that from the NAS and start a setup all over again.  I held the reset down for a minute while holding it down and pwoering up.

A factory reset reformats the drives, and sets everything up from scratch.  All data is lost in that process. The good news is that you used the wrong procedure, so you probably didn't do any damage.

[MLBBERK]

the ethernet port on the back of the NAS blinks (green) which I always thought was an indication of data being transfered form the router (which also blinks from its port that is connected to the NAS). Agreed that wwith only  3 ethernet connections, and two idenitfied as Sonos, I would assume that is the NAS. Did you see the Macintosh screen shots? I thought they might be helpful.  I absolutely issued ipconfig/all in the command prompt, but do it again just to make sure.  I believe there are products that will allow a Windows machine to read the contents of Linux drives.  That could solve my problem by allowing me to access the data on the NAS.  I can mount the NAS drive(s) in a USB case and the move the files to the PC's drive. Once I get that done, the NAS becomes a door stop and I'll start all over since getting support on the current NAS is unrealistic.  Netgear can't answer the phone now in less than 30 minutes, and then they transfer me to outerspace where no one answers.  Actually, and I'm sure this is pandemic related, most of the software/tech  companies are in the same boat. My first attempt at getting support resulted in an 800 number call that wound up in Maylasia.  The whole process is overwhelming. I just want my data back.  Seems like that shouldn't be a monumental request.  If it weren't for you, I would have received no repsonse at all! So I'm grateful to you. Will send another ipconfig file as soon as I get going this morning. 

[MLBBERK]

rear view, the shot is a still, but the green light is blinking regularly

[MLBBERK]

please see attached

[Sandshark]

---

@MLBBERK wrote:

 I tried to do a factory reset on the NAS because the last time it was used was in a different residence with a different ISP and I thought the issue was to wipe that from the NAS and start a setup all over again. 

---

It would be good to see the ipconfig screen and how you determined the IP address, but I think you are on the right track.  That's why I asked you to start from the beginning.  If you set up the NAS with a static IP on another ISP's router, there is a good chance that the information you gave is correct, and the problem.  The NAS static IP is in the subnet of the old router, so computers on the current router's subnet won't see it.  RAIDar does not have that limitation, so you realy ought to see what is shows, too.

If that is the problem, you want to do an OS re-install, not a factory default.  In addition to setting the NAS back to using DHCP for it's addressing, it will change the admin password to the default, password.  Then, use address reservation in the router to secure a permanent address for the NAS, not a static IP in the NAS.  Then, if you change routers again, it'll not have a reservation but will still be using DHCP.

[StephenB]

---

@MLBBERK wrote:

Did you see the Macintosh screen shots? I thought they might be helpful.  I absolutely issued ipconfig/all in the command prompt, but do it again just to make sure.  

---

You have only posted this one screenshot:

and of course the photo of the back the your unit.

As I said before, the first "offline device" appears to be the NAS.  I suggest navigating to this screen again, when the NAS is booting (and showing the green LED on the ethernet port.  Then see if it shows up as an on-line device.

[MLBBERK]

we may be out of synch on my postings. Today I sent a photo of the NAS with a green light. It is actually blinking but for a still you couldn't see it. I also sent a new ipconfig sheet from today with the ipcofig command on it at the top. Still not recognizable.  I alsoasked if you knew of software tranlator to read the Linux drives. I don't think the NAS is recoverable, but I am sure the data is still there.  Please let me know if you want a resend.

[StephenB]

---

@MLBBERK wrote:

we may be out of synch on my postings.

---

You might want to look at the entire thread and download the attachments that are actually there - I think you might be trying to attach multiple files to your posts, which doesn't work.

---

@MLBBERK wrote:

we may be out of synch on my postings. Today I sent a photo of the NAS with a green light. It is actually blinking but for a still you couldn't see it. 

---

The green light looks fine.  What I don't know is if the light was green when you took that first screenshot (or if the NAS was turned off).

---

@MLBBERK wrote:

I also asked if you knew of software tranlator to read the Linux drives. 

---

ReclaiMe would work if you can connect one of the drives to a Windows machine.  https://www.reclaime.com/

---

@MLBBERK wrote:

 I don't think the NAS is recoverable, but I am sure the data is still there.  

---

I'm not personally convinced of that (at least not yet).

[Sandshark]

The one screen shot you posted is of little use because it does not show actual IP addresses.  We need to get the IP address of your computer (best determined with ipconfig) and of the NAS (best determined with RAIDar).  RAIDar may also show additional status information.  I personally think your NAS is booting fine, but one drive has failed (thus the blinking LEDs) and you just don't have it configured such that it's visible on the same subnet your computers are on.  But you just aren't providing the information needed to confirm that.

[MLBBERK]

Attached please find the most recent ipconfig results. You may need to zoom in to be able to read it. Let me know if that helps.  BTW the blinking lights i referred to earlier were the node lights, both on the router and the back of the NAS. I thought that indicated data moving between the router and the NAS.  The front of the NAS has several blue lights, one for each drive and the "On" light. Those are steady as a rock.  Hope this helps. 

[Sandshark]

OK, so both your NAS and computer appear to have a 10.0.0.xxx address, though you have still not stated how you determined the NAS IP address.  Given the "no direct path to device" response to a ping but the NAS is being assigned an IP address, that tends to indicate that something in the middle (a firewall, for example) is blocking your access.  If the NAS was bricked such that it couldn't even reply to a ping, it most likely would also not be assigned an IP address.

You really need to run RAIDar and see what it says about the IP address and status of the NAS.