![]() That is, the login to actually works perfectly fine! ![]() In actuality, the sequence of events in Firefox was 49 happens before 48. The significance didn't occur to me until I pondered what you are saying. In the end, I was able to flash the latest firmware from what appears to be from (R7000-V1.0.11.100_10.2.100.chk) to what is now version R7000-V1.0.11.136_10.2.120.chk from what appears to be based on these two reference urls I found in the Netgear download support site.įormatting link Notice that screenshot was taken at 8:51am yesterday. But I don't know for sure why SRWARe Iron worked with but Firefox would never let me log in when I used a url. I suspect it was something similar that prevented me from logging in also. It could be my Firefox settings though, but what happened was a dialog box asking for an "OK" popped up in SRWare Iron, but not in Firefox. It's definitely a problem with Firefox though as there was ANOTHER problem which only showed up with Firefox, which was that I couldn't hit the "Apply" button whenever I changed some settings in Firfox, and yet I could hit that same "Apply" button when I switched to SRWare Iron to do it. The solution should have come to me sooner, which was to use SRWare Iron (I didn't try any other browser than Iron so others may have worked also). I had two main problems, one of which is the router stopped accepting the login/password for reasons unknown to me and the second was that as a result of that first problem (which had nothing to do with Firefox), I did a (whole bunch of) factory resets to try to log into the router, but that's when the Firefox wouldn't let me log in and wouldn't let me choose to not worry about the lack of a bona fide certificate either. Would it be possible for someone to enlighten me on the steps to follow on these last / first steps.I solved it but I can't really say what specific action solved it because almost everything made no sense because it all "should" have been working. In DHCP window you can see something like this:ĭHCPREQUEST for 00:90:12:34:56:78 () from interface 192.168.0.1 received Run _Start_ping.bat (And run again and again until its start ping WDMC).Run _Start_DHCP.bat and _Start_TFTP.bat.I think my mistake comes from the fact that I did not apply the following DSM installation instructions: ![]() ![]() The commands indicated in the operating instructions run correctly without any errors.Īfter reconnecting the hard disk to the M圜loud board, the system does not start (the LED remains red). When plugging the hard disk back into my *nix, parted and fdisk find no errors. The partitions were created in the right order, with larger sizes than those given (cropping on the sdb3 part). I tried to create the partitions with the windows tool. In any case, a huge thank you to Fox for all the work done and for the documentation produced. I’m asking for a little help to get me out of this mess. ![]() I can’t solve these problems, and if I ignore them, then problems arise when creating file systems. Parted gives me an error related to misaligned partitions. Now I’m stuck at this stage: Connect to WDMC via Telnet and run this commands: So I took the M圜loud apart, and plugged the hard drive directly into my *nix. I tried the first recommended method to install DSM, but the Mycloud got bricked. I write for the first time on this forum.Ĭan you imagine my joy when I learned that DSM was available for my old M圜loud taking dust? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |