NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Booting
2173 Topics
ReadyNas NV+ Default Username/Password
Hi, I found an older ReadyNas NV+ unit at my new job, Part number is RNV2-S2-0000. I found instructions online how to reset it to factory default, which I have (seemingly) successfully done. I can connect to it with RAIDar, and I was able to do initial setup through it for X-Raid, and the front shows 637GB available of 637GB. However, I am unable to sign in to the unit at http://xxx.xxx.xx.x/admin so I can update it, configure shares, etcetera. I have tried the combibation of admin/admin, admin/password, admin/netgear1, admin/[blank] with no success. Anyone know what the correct username/password for this model is when reset to factory? I would love to get some use out of this thing! Thanks!Solved42KViews0likes2Comments
Readynas Duo Factory reset and boot
I want to reset my Readynas to factory defaults. I held down reset button 30 seconds and Disk 1 & 2 leds flashed a few times. I did this with these instructions: Duo / NV / NV+ / X6/600 To perform an OS Re-install or Factory Default, this is managed via the Reset button on the back of the chassis. Locate the reset pinhole. ReadyNAS X6/600: the pinhole is on the back in the lower left corner. ReadyNAS Duo/NV/NV+: the pinhole is next to the USB port in the back. Get a straightened paper clip and depress the hidden switch in the pinhole while the power is off, and then power on the ReadyNAS. To perform other options such as Skip Volume Check, Tech Support Mode, and Memory Test, this is managed via the Power button. With the system off, hold down the Power button, and wait for the desired LED flashes. Release the Power button when the option you desire is active. Now my disk 2 led is lit and power led is blinking fast. Also raidar won't find it. I reseted this 10 minutes ago so is there a problem and what to do?Solved34KViews0likes8CommentsBlinking power light
Hello everyone. This is my first post on here. I've had this ReadyNAS since November 2014 with no problems, but yesterday after I saw the email for needing to migrate the readycloud service to mynetgear, I logged in to the web admin and updated the firmware on the 102 to the 6.4.1 firmware and when it rebooted, I couldn't access my volumes. I tried to do a USB recovery (I'm running OS X, so I can't run the recovery tool) and that seemed to work after I loaded onto a second USB drive (the first one wouldn't work). However, after I started the 102 back up, the power light just started blinking...and blinking...and blinking. Then, I tried to do the OS reload, but the buttons are completely non-responive. Double clicking the power button won't shutdown the NAS. Pulling the plug from the NAS and holding the reset button doesn't allow me to cycle through the setting either. Once the 102 starts up, all the lights light up, and the power button starts blinking again and releasing the reset and pushing the backup button, like the intructions for doing an OS reload say, don't let me cycle through the different boot menu options. Oddly enough, yesterday and early this morning, I was able to at least SEE the NAS in RAIDar and even the firmware version in the readycloud web dashboard, but this evening I can't even do that. At one point, it was even allowing me to mount the SMB shares on my desktop, but with no visible data, of course. Now, it won't allow me to do that either. Any suggestions would be greatly appreciated. Thanks!Solved25KViews0likes17Comments
"XZ-compressed data is corrupt - system halted" after upgrade to 6.5.2 #27451687
Hi all, Yesterday, I logged into the admin page to do a routine check and noticed that 6.5.2 was available. The system was running 6.5.1. I proceeded to upgrade and it took a loooong time to become available, which eventually it didn't. I went downstairs to check and it was saying its IP was 192.168.70.24 which was very weird since its fixed IP is 192.168.70.100. I decided to reboot it and it got stuck on "Booting...". Then I created a USB recovery drive and tried the reboot from the USB. Nothing, it just gets stuck on "Booting from external USB". The USB drive LED doesn't even flash. As this box has a HDMI plug, I connected it to my TV and the result is that it goes through the boot process, BIOS loading and all until it stops with: "XZ-compressed data is corrupt - system halted" And that's it. What can I do?18KViews0likes18Comments
ReadyNAS error: "mount_block_root+1f1"
After installing the 6.7.3 firmware (6.7.1 > 6.7.3 upgrade), I'm seeing the error message "mount_block_root+1f1" on the LCD. I was going to try the USB Recovery method, but I saw in this similar thread that it isn't working as a go-to solution. I see mdgm-ntgr has been able to solve this error for McRob1, so I'm hoping he can do the same here and spell out the steps involved.Solved18KViews0likes21CommentsReadyNAS 316 unable to boot after 6.7.3 upgrade
Hello, I upgraded my ReadyNAS 316 today through the admin page to 6.7.3. The device won't boot so I'm unable to access my files or the admin page. The error message says "ERR: Could not properly extract" and then "lcd_panic_handle r+7d". I've tried to do USB recovery as some have pointed out previously, but that doens't seem to work. It returns with the same error. I've also tried booting into Volume ReadOnly and performing an OS reinstall from the boot menu, but nothing works. Full disclosure: I haven't tried a Factory Default reset yet since I don't have a recent backup (I know, I know. I have a 8TB HDD for backing up the NAS that I was trying to format before the upgrade so I could do the backup. I had to do the upgrade because 6.7.3 is supposed to have a fix for formatting external HDD > 2TB). Does anyone know how to fix this issue? If not, does anyone know how to gain access to the files so I can do a Factory Default reset?Solved18KViews0likes24CommentsReadyNAS 102 – Blue light blinking, no boot
My ReadyNAS 102 has been working with an issue for a few years. I tried to connect recently and it wouldn't let me. I tried to reboot and it wouldn't so I pulled the power. Now it won't boot up (blue light blinking) so I removed the two drives and tried to reboot just the chassis and again just a blue blinking light. I'm on Mac 10.11.5 and honestly I'm not sure about the firmware version on the Netgear – I haven't manually updated in a while and I can't remeber if it's on auto update! Any ideas on what may be amiss or how to resolve? Thanks. Edit: I managed to connect to it without drives in via RAIDar – light still flashing but now I know the firmware is 6.5.1.Solved17KViews0likes23CommentsReadynas Duo and the slow blinking blue light
Hello all, I'm the lucky owner of a readynas duo with a single Seagate disk of 1TB with default configuration (X-Raid i think). The Readynas was working fine for months until yesterday : i got this slow blinking blue light at boot. After 24h hours waiting, the issue is the same : i can not access to my data. The Readynas is running Raidiator 4.1.7, it's still detected by RAIDar wich only show the firmware version in the info column. Ping is ok but i can not access anymore the web interface, neither my SMB shares, even my ssh connection is blocked. I spent several hours reading forums and FAQ without finding any clue about what's happening with my Readynas Duo... So i wonder : 1) What's happening with my nas, anyone knows the origin of the problem ? 2) Is there a way to get back my readynas working ? 3) Is there a way to read data from the Readynas HDD pluging it on my computer for example ? I will keep looking for any informations, if someone could help it would be great :) PS : Sorry for my mistakes, i'm doing my best to write understandable english ;)16KViews0likes12Comments
rn104 updated to 6.4.0 and possible solution to random lock-ups
Hello everyone, I have updated my RN104 last week, and have been poised by the unit hanging up randomly since then. I have searched andread a lot of posts here, and after 5 hard reboot and re-syncing, I may have found a solution. At least, it's been 1 day the unit has not locked up, so I'm crossing my fingers. The culprit, I think, might by the snapshot creation. I had 3 share protected by snapshots. Documents, Caldav/Carddav hosting and my ebooks collection. All those share had a daily snapshooting policy. After reading the "FAQs on upgrading ReadyNAS firmware to 6.4.0" post linked in here, the last chapter caught my eye: btrfs-cleaner is commonly invoked after Smart Snapshot Management prunes older snapshots. ReadyNAS commonly prunes older snapshots based on its snapshot schedule. Now, my nas is almost 80% full, and the snapshots where taking around 4Gb of space (out of a 4 disks Raid5 array of 6To usable). As the unit completely locks up, no SSH-ing in to check how much CPU the btrfs-cleaner process takes, of course, and nothing in the syslog appart a bunch "@" at the time the hangs-up hapenned. Oct 13 21:48:05 nas kernel: [ 6591.520831] md: delaying resync of md126 until md127 has finished (they share one or more physical units) Oct 13 21:48:06 nas readydropd[4685]: DEBUG:readydropd.c:897 Shares.conf has been changed Oct 13 21:48:07 nas readydropd[4685]: DEBUG:readydropd.c:652 Reload Share configs Oct 13 21:48:08 nas kernel: [ 6593.661751] md: delaying resync of md126 until md127 has finished (they share one or more physical units) Oct 13 21:48:08 nas kernel: [ 6594.415415] md: delaying resync of md126 until md127 has finished (they share one or more physical units) Oct 13 21:48:09 nas kernel: [ 6594.927980] md: delaying resync of md126 until md127 has finished (they share one or more physical units) @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@Oct 13 21:53:01 nas kernel : imklog 5.8.11, log source = /proc/kmsg started. Oct 13 21:53:01 nas rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2837" x-info="http://www.rsyslog.com"] start Oct 13 21:53:01 nas kernel: Booting Linux on physical CPU 0x0 Oct 13 21:53:01 nas kernel: Initializing cgroup subsys cpuset Oct 13 21:53:01 nas kernel: Initializing cgroup subsys cpu Oct 13 21:53:01 nas kernel: Initializing cgroup subsys cpuacct Reading the FAQ, I thought that I would try to remove the snapshots creation schedules of my shares, and remove all the existing snapshots. Since this moment, I had no more issues. By the way netgear, I'd really like to know another way than using the timeline to clean old snapshot. Removing 108 snapshots manually, one after the other was not fun... The "emergency" button in the shares/browse is nowhere to be found today in my web gui, so that only leaves the timeline afaik... It might not be relevant, but maybe the combination of low disk space, numerous snapshots and high CPU usage (because syncing back the array after the last hard reboot, my cpu load reported by "top" was around 12~15 at that time) might have been the issue. To be really torough, I even have deactivated DLNA, AFP and SMB services, leaving only the NFS, as I'm using linux boxes as client anyway. DLNA re-scanning the shares seems to be heavy, when resyncing the disks. Maybe it can help other people I've seen here having unresponsive units after bootup too. I'll come back comenting here if the unit locks-up again, but I am confident. Regards. Thierry.Solved13KViews0likes92Comments
