NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS Ultra4 - Possible Corrupted Firmware - No Access to Shares
Workstation OS: MACOS Sierra Model: RNDU4000 Firmware: 4.2.30 OS: x86 Drives: RAID Level X-RAID2, 4 disks Network: Connected via LAN Interface 1 I have lo...
itsonlycomputer wrote:
Any way to install it in this condition?
No, that's the problem. On OS4, you need to install an add-on, and if the root is full, you can't. So if the NAS doesn't allow to connect via SSH, Tech Support Mode is the next step.
If you want to contact NETGEAR for Support, they have option for paid Support.
Otherwise, you can try to fix it yourself. But please careful, these instructions are only meant to be taken as is. I'm not responsible for anything bad that can happen, perform the actions only if you understand them and feel safe doing it.
These are only valid for RAIDiator4.2 and are meant to cover this specific situation only!
Most of the commands I gave are nonintrusive (or close to nonintrusive).
Spoiler1. Boot into Tech Support Mode via Boot Menu: https://kb.netgear.com/20898/ReadyNAS-ReadyDATA-Boot-Menu 2. Use RAIDar to identify the IP address. 3. Telnet the IP shown by RAIDar. 4. You can find the credentials here: http://netgear.nas-central.org/wiki/TechSupportMode 5. Start the RAID arrays: start_raid.sh 6. Mount the OS volume: mount /dev/md0 /sysroot 7. Check space usage: df -h 8. If md0 is indeed 100% full, continue, if not paste the output here and stop. 9. Move into the OS volume: cd /sysroot 10. Calculate the space usage for each subfolder: du -h -d1 . 11. In the output, there should be a big folder, with multiple GB of data (typical OS space usage is <1GB out of the 4GB capacity).
If you know what is wrong, continue, if not paste the output here and stop. 12. Move to the big folder: cd <folder> 13. Repeat (calculate the space, move to the big folder, etc.), until you clearly identify either which log file is big and shouldn't be or which folder is big and shouldn't be. This type of condition is often due to a log file that wasn't truncated/rotated and that's filling up the OS volume or some data that was written to the OS instead of the data volume. If the space used is mainly in the current folder, check the size of the files in the current folder: ls -alh 14. Take necessary actions to free up the space if you know what to do, otherwise paste the output here and stop. 15. Move back to the root: cd / 16. Sync: sync 17. Unmount the OS volume: umount /sysroot 18. Stop the RAID arrays: mdadm -S /dev/md* 19. Reboot the machine: reboot -fIf at any point, you're not sure, paste here the ouput and stop.
(I'm going to bed for now, but I'll review tomorrow.)
If it's indeed a full root, it's very easy to fix via Tech Support mode. But I can't really help you to do that since I'm no longer working for NETGEAR Support...
Is SSH enabled on the NAS?
Is SSH enabled on the NAS?
Note taken, what ever instructions you provide, I'll do at my own risk. I'm not sure if ever installed that add-on or not. Any way to install it in this condition? Either way, if you could provide complete instructions, I'll do at my own risk. This device is long past its warranty.
Thanks
David
You should be able to get paid support for this (which I believe costs about $75).
Do you need to get data off of the NAS? If not, you can simply do a factory reset, reconfigure it, and then restore the data from backup.
itsonlycomputer wrote:
Any way to install it in this condition?
No, that's the problem. On OS4, you need to install an add-on, and if the root is full, you can't. So if the NAS doesn't allow to connect via SSH, Tech Support Mode is the next step.
If you want to contact NETGEAR for Support, they have option for paid Support.
Otherwise, you can try to fix it yourself. But please careful, these instructions are only meant to be taken as is. I'm not responsible for anything bad that can happen, perform the actions only if you understand them and feel safe doing it.
These are only valid for RAIDiator4.2 and are meant to cover this specific situation only!
Most of the commands I gave are nonintrusive (or close to nonintrusive).
Spoiler1. Boot into Tech Support Mode via Boot Menu: https://kb.netgear.com/20898/ReadyNAS-ReadyDATA-Boot-Menu 2. Use RAIDar to identify the IP address. 3. Telnet the IP shown by RAIDar. 4. You can find the credentials here: http://netgear.nas-central.org/wiki/TechSupportMode 5. Start the RAID arrays: start_raid.sh 6. Mount the OS volume: mount /dev/md0 /sysroot 7. Check space usage: df -h 8. If md0 is indeed 100% full, continue, if not paste the output here and stop. 9. Move into the OS volume: cd /sysroot 10. Calculate the space usage for each subfolder: du -h -d1 . 11. In the output, there should be a big folder, with multiple GB of data (typical OS space usage is <1GB out of the 4GB capacity).
If you know what is wrong, continue, if not paste the output here and stop. 12. Move to the big folder: cd <folder> 13. Repeat (calculate the space, move to the big folder, etc.), until you clearly identify either which log file is big and shouldn't be or which folder is big and shouldn't be. This type of condition is often due to a log file that wasn't truncated/rotated and that's filling up the OS volume or some data that was written to the OS instead of the data volume. If the space used is mainly in the current folder, check the size of the files in the current folder: ls -alh 14. Take necessary actions to free up the space if you know what to do, otherwise paste the output here and stop. 15. Move back to the root: cd / 16. Sync: sync 17. Unmount the OS volume: umount /sysroot 18. Stop the RAID arrays: mdadm -S /dev/md* 19. Reboot the machine: reboot -fIf at any point, you're not sure, paste here the ouput and stop.
(I'm going to bed for now, but I'll review tomorrow.)
Note also that sometimes when the root volume gets filled some config files can be corrupted as there's not enough space to write the new versions. If that's the case then some more work is required to fix the problem.
mdgm wrote:Note also that sometimes when the root volume gets filled some config files can be corrupted as there's not enough space to write the new versions. If that's the case then some more work is required to fix the problem.
I've never found myself in this situation, but these are some really good to have instructions just in case. For my own benefit and that of the OP, would an OS re-install (once there is sufficent space for it to work) likely fix some/most of the corrupted config files? Also, is there a way to install the SSH add-on on OS 4.x or to enable SSH in OS 5.x or 6.x via tech support mode FTP?
**CORRECTION** correct syntax is: start_raid.sh There was an extra 's' in your example
I received an error attempting to start the raid array.
# start_raids.sh
-sh: start_raids.sh: not found
#start_raid.sh
mount /dev/md0 /sysroot
df -h
--------- Result of df -h command -------------------
Filesystem Size Used Available Use% Mounted on
tmpfs 10.0M 0 10.0M 0% /dev
/dev/md0 4.0G 3.8G 0 100% /sysroot
#cd /sysroot
Attempting: du -h --max-depth=1 (Returns invalid option -> Usage: du [-aHLdclsxhmk] [FILE]...
[STOPPING UNTIL I HEAR FROM YOU]
itsonlycomputer wrote:
I received an error attempting to start the raid array.
jak0lantash mistyped the command. Try
# start_raid.sh
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
