NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
ReadyNAS OS 6 on Legacy models
983 TopicsReadyNAS104 assistance needed
Hi, I have an old ReadyNAS 104 that apparently just crashed. I can get it to reboot and I can access it from a browser but it shows the volume as new? I have 4 - Toshipba 3 TB drives in a RAID 4 configuration. I have attempted to access the BOOT menu by rebooting the NAS with my finger on the power button but that does not appear to work. When I look at the drives they are all showing green but "new" and the volume I had for many years is now gone. Please help6Views0likes2CommentsReadyNAS Pro 6 - Stuck on booting while checking fs
I have searched for similar errrors on here, but none seem to either work or be related as to my situation. My Pro 6 just started to freeze a couple days ago while it was running. I had updated it to OS6 a long while ago. Thinking it might just be a random error, I restarted the device and now it gets to the checking root fs and stops around half way (sometimes more or less). I have tried the following: OS Reinstall - Completes and boots to same percentage. Disk Tests ran fine and rebooted itself (though now this is no longer an option in the boot menu) USB Recovery ran and shutdown. Boots back to same percentage. Tech Support mode works Tried start_raids and it seemed to see every drive. Ran some mdadm commands to examine the drives and array as found in other posts on here with no glaring errors found. Running a 'smartctl -t long /dev/sda' now. Not sure what else to do to get it to boot so I can get my files (prefer it to continue being useful but can get soem other NAS and move my data as long as I can get to it). Thoughts/ideas/help? Thank you.157Views1like27CommentsNo Volumes Exist Suddenly - ReadyNas 10400 - HELP!
I was in the middle of running a full backup of my readynas 10400 system yesterday and something has gone wrong. Now I cannot access the shares, and the system is showing the message that 'No Volumes Exist' and telling me to remove inactive volumes in order to use the disks. It was set up as a Raid 5 array using 4 discs, and one of them failed the other day, hence my decision to run a backup. I do not have a full backup of all the data so I need to get access back into those shares. I am at a loss as to what to do. I've replaced the failed drive with a new one but still no joy. From what I have read this probably means that the array is out of sync but I don't know how to get it to resyncronise. I have downloaded the logs so can supply them if required. I was in the process of setting up a robust backup system when this happened, so I hadn't managed to back it all up yet. Help, basically.31Views0likes1CommentCredentials for terminal login on ReadyNAS 212 after Management Service is offline
Been trying to restore access to the admin page of my ReadyNAS 212. Not sure what caused the web interface to quit working. I can see the internal drives but not the external drives in Windows file explorer. I tried an OS reinstall. Now I'm trying to login using terminal after setting the device into tech support mode. Password has been reset after OS install to admin\password but the credentials don't work for terminal. Credentials work for Raidar. I've also tried root for the ID and different old netgear passwords seen on this forum. I don't want to reset the firmware unless I absolutely have to as the config files I have backed up are several years old. Any suggestions out there? Jim433Views0likes7CommentsRemove Inactive Volumes to sue the disk - RN316
Reading this forum, it sounds like this is not an uncommon situation... I recently had a hard drive fail on my RN316 - replaced it, knowing another was expected to fail soon, and about 2 hours after the resync of the first drive completed, the second drive failed. When I replaced that drive, it did not automatically resync. When I finally managed to get the resync to happen, I was presented with the attached image in the Volumes page - warnings about removing inactive volumes to use disks, and the red drives... I have managed to assemble the arrays /dev/md127 and /dev/md126 - however btrfs is giving me the following when I attempt to mount /dev/md127 mount: wrong fs type, bad option, bad superblock on /dev/md127, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. Does this sound like it's salvageable by a rebuild of the NAS, or should I be handing the whole thing over to a data recovery expert? (unfortunately, I have no backup - I was naive and trusted RAID5 with the bulk of the data on this NAS - I won't be doing that again)1.2KViews0likes19CommentsUSB drive no longer recognised
I have been connecting the same external USB drive to my ReadyNAS to perform backups and now after the latest firmware update to 6.10.10 it is now no longer recognised. This now makes it impossible for me to backup my files using the backup feature. I have followed the instructs to connect a new drive and are getting the same result. Even though this product is now legacy and no longer supported, Netgear shouldn't be disabling any of the functions that have been used since purchase. I would appreciate that support look into this instead of suggesting that I purchase a new NAS.Solved2.4KViews0likes22CommentsReadyNAS 104 – Volume gone after attempted disk upgrade
Hi all, appreciate this community resource, longtime 104 (6.10.10) user without issue until now. I had upgraded drives before 10 years ago and sought to upgrade again after running low on space. I am running 3GB x 4 Raid 5 and purchased 4x 12GB IronWolf Pros for the update. I, unwisely, did not backup prior to attempting the upgrade. I started by removing the 3GB drive from Bay 1 and inserting the new 12GB drive. Data started to synchronize. Took a few days. Finished syncing, then when I checked on the device, the LED said "DEAD." Looked at my logs and saw a note that looked like Drive 2 had failed. I removed the 12GB drive from Bay 1 and re-inserted the original 3GB. I hoped the volume might reappear, but it did not. Now the system shows no volume, and I am looking for next steps to try to rebuild or recover this array. Any guidance or assistance would be deeply appreciated. Posting relevant time portion from status.log: [24/12/30 00:22:27 PST] warning:disk:LOGMSG_DELETE_DISK Disk Model:WDC WD30EFRX-68EUZN0 Serial:WD-WCC4N5KCFYHA was removed from Channel 1 of the head unit. [24/12/30 00:22:35 PST] warning:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Redundant to Degraded. [24/12/30 00:27:38 PST] notice:volume:LOGMSG_RESILVERSTARTED_VOLUME Resyncing started for Volume data. [24/12/30 00:28:43 PST] notice:disk:LOGMSG_ADD_DISK Disk Model:ST12000NE0008-2JL101 Serial:ZHZ5RXWY was added to Channel 1 of the head unit. [24/12/30 01:00:25 PST] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume data is Degraded. [24/12/31 01:09:06 PST] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume data is Degraded. [25/01/01 01:06:51 PST] warning:volume:LOGMSG_HEALTH_VOLUME_WARN Volume data is Degraded. [25/01/01 02:47:41 PST] notice:volume:LOGMSG_HEALTH_VOLUME Volume data health changed from Degraded to Dead. [25/01/01 02:51:46 PST] notice:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 1 (Internal) changed state from RESYNC to ONLINE. [25/01/01 02:56:37 PST] err:disk:LOGMSG_ZFS_DISK_STATUS_CHANGED Disk in channel 2 (Internal) changed state from ONLINE to FAILED. [25/01/01 02:57:47 PST] notice:volume:LOGMSG_RESILVERCOMPLETE_VOLUME Volume data is resynced. [25/01/01 19:59:09 PST] notice:system:LOGMSG_SYSTEM_REBOOT The system is rebooting. [25/01/01 20:00:44 PST] notice:system:LOGMSG_SYSTEM_REBOOT The system is rebooting. [25/01/01 20:03:01 PST] warning:disk:LOGMSG_DELETE_DISK Disk Model:WDC WD30EFRX-68EUZN0 Serial:WD-WCC4N6SL6CEA was removed from Channel 2 of the head unit. [25/01/01 20:07:37 PST] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. [25/01/01 20:10:16 PST] notice:disk:LOGMSG_ADD_DISK Disk Model:WDC WD30EFRX-68EUZN0 Serial:WD-WCC4N6SL6CEA was added to Channel 2 of the head unit. [25/01/01 20:10:16 PST] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send. [25/01/01 20:26:41 PST] notice:system:LOGMSG_SYSTEM_REBOOT The system is rebooting. [25/01/01 20:34:36 PST] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started. [25/01/01 20:37:05 PST] warning:disk:LOGMSG_DELETE_DISK Disk Model:ST12000NE0008-2JL101 Serial:ZHZ5RXWY was removed from Channel 1 of the head unit. [25/01/01 20:40:35 PST] notice:system:LOGMSG_SYSTEM_REBOOT The system is rebooting. [25/01/01 20:37:05 PST] warning:system:LOGMSG_SENT_ALERT_MESG_FAILED Alert message failed to send. [25/01/01 20:41:16 PST] notice:disk:LOGMSG_ADD_DISK Disk Model:WDC WD30EFRX-68EUZN0 Serial:WD-WCC4N5KCFYHA was added to Channel 1 of the head unit. [25/01/01 20:48:24 PST] info:system:LOGMSG_START_READYNASD ReadyNASOS background service started.348Views0likes2CommentsRN314 don't boot anymore after trying to fix "no space left on device" error.
Hi, Here's the full story that led me to a ReadyNAS RN314 that no longer starts with a "flush_space+5a" message on the LCD. Actually, after seeing that I lost (I mean visible on the network) the SMB, NFS shares from my RN314 I tried to login via the Web UI. But each time it was looping on the login screen until it asked me to follow th recovery password procedure that I did not follow. Instead I logged in via SSH and I discovered that the OS was complaining about "no space left on device" on the / (root) making /tmp unsuable for all the pplications! I ran the command df to see where the space was really missing and there was still almost 1TB on the data file system (/dev/md127) and 1,3 GB on the / (/dev/md0) and ieven the I-nodes were not used at 100%. Weird as I was not able to still create a file in /tmp (no space left on device), it should be something related to btrfs. I deleted some log files from /var/log to free some MB and I tried to check the /dev/md0 with the command btrfs filsystem check / (if I rember well the syntax). It ran the night and when I wake up the ssh connection was closed. I reconnected and it says that the filesystem was in read only. Then I asked a reboot and unfortunatly the NAS stop booting with the LCD displaying "flush_space+5a" msg and since it does boot anymore. After googled a bit, I found that maybe reinstalling the OS via the boot menu can soved the issue without loosing all my 8TB of data. I tried and unfortunatly no change I got still the "flush_space+5a" like in the normal boot mode. I don't want to try the USB recovery method as I understood well the /dev/md0 will be reflashed and all my data on /dev/md127 will be reset loosing all my data. I there a way to boot like in Tech support mode (via the boot menu) or an other way to gain access to my data that I could backup on an external disk before resting everything. I hope I will not loose almost 10 years of data. Br, Cataldo. PS: The firmware installed was the latest available.Solved2.3KViews0likes26CommentsSuccessful RN104 disk replacement
Hello community, I just want to share something positive! I just completed the replacement of all 4 1TB disks in my ReadyNAS RN104. Firmware Level 6.10.10. Volume is a X-RAID RAID-5. I'm positively impressed that I could replace disk by disk by new 4TB disk drives and the ReadyNAS handled this perfectly fine. Sure, the rebuild and data redistribute took some time (days) but this was the result of me buying the model with the slow Marvel processor. Thanks Netgear!305Views0likes1Comment