This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
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 lost access to all of my shares on my NAS, I do have access to the Admin interface, however any changes made are not saved. From what I can tell, my drives are intact and healthy, but believe my firmware must somehow be corrupted.
I attempted to upload the 4.2.30 firmware again and I'm getting a message that the firmware version for x86 is invalid.
Any help would be greatly appreciated as I do not have a full backup of the device, was in the process of uploading data to a cloud backup when all of this happened. Ugggggghhhhhh
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).
1. 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 -f
If 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.)
Re: ReadyNAS Ultra4 - Possible Corrupted Firmware - No Access to Shares
Without doing a thing, I no longer have access to the Front panel, so I am unable to download any logs. Also, the IP address changed to a 192.168.168.168 address, going to try resetting my ip address on my mac to see if I can access it.
Re: ReadyNAS Ultra4 - Possible Corrupted Firmware - No Access to Shares
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?
Re: ReadyNAS Ultra4 - Possible Corrupted Firmware - No Access to Shares
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.
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).
1. 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 -f
If 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.)
Re: ReadyNAS Ultra4 - Possible Corrupted Firmware - No Access to Shares
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.
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?
Re: ReadyNAS Ultra4 - Possible Corrupted Firmware - No Access to Shares
The OS partition is certainly full.
Look in /var/log and /var/cache first.
Anything in /var/cache can be deleted. If you run ReadyDLNA you should also run an add-on which shifts the DLNA cache to the data volume. Obviously you can't do that now, post back when your system boots properly again.
With logs, it is best to truncate them. The easiest way to do this is echo > logfile-name
