NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Pro 6 won't boot up after going from 6.7.1 to 6.7.3
Upgraded my pro 2 from 6.7.1 to 6.7.3 beta without any issues, but tried my Pro 6 a bit later and it appears to have not gone well. It showed upgrading FW on the screen for a long time and from the webpage it appeared to show it was still on 6.7.1 but it would finally time out and not let me in. After about 30 minutes I tried booting it again and it just goes to retrying startup at around 77 or 83 percent and sits for a long period. I tried an os reinstall from the boot menu and it also said updating FW, but it appears to be back in the same position. I have had issues in the last few months after some upgrades and some power issues when it didn't shut down cleanly. Not sure if it is due for a factory reset or maybe something is low on space. I can boot it up in Maint mode if there is someone that can maybe take a quick look if not I will probably see about trying a factory reset and restore the data/config.
Thanks,
Jeff
Yes you had the same problem. It should now be fixed.
Edit:
If you have updated to 6.7.3 and ran into this issue please try USB Boot Recovery (note for those using RAIDiator-x86 systems such as the Pro 6 you'll need to use the RAIDiator-x86 4.2.x USB Boot Recovery tool with the OS6 firmware renamed to RAIDiator-x86-something) with ReadyNAS OS 6.7.4 which is now available!
If you have not yet upgraded please upgrade to 6.7.4 rather than 6.7.3. If your system has already been fixed I would still suggest updating to 6.7.4 the normal way using the web admin GUI.
12 Replies
Replies have been turned off for this discussion
Just as an update to this. I did bring it up in Debug mode and it is displaying "no ip address" on the display, but in Raidar 6.3 it does show up and that it is in Tech Support mode. It also shows it is on 6.7.3-T283 and does show the IP 192.168.168.168 for both IPs. Not sure if that is normal or not.
Thanks
After a bit more digging via ssh I think I might be having the same problem as noted here:
Filesystem 1K-blocks Used Available Use% Mounted on
udev 10240 4 10236 1% /dev
/dev/md0 4190208 1144380 0 100% /
tmpfs 2018872 8 2018864 1% /dev/shm
tmpfs 2018872 16964 2001908 1% /run
tmpfs 1009436 8 1009428 1% /run/lock
tmpfs 2018872 0 2018872 0% /sys/fs/cgroup
/dev/md126 11696688832 5317807976 6377199192 46% /data
/dev/md126 11696688832 5317807976 6377199192 46% /apps
/dev/md126 11696688832 5317807976 6377199192 46% /home
root@CalvCoNAS:/mnt/var/cores# btrfs fi df /
Data, single: total=3.57GiB, used=580.03MiB
System, DUP: total=8.00MiB, used=16.00KiB
System, single: total=4.00MiB, used=0.00B
Metadata, DUP: total=204.56MiB, used=12.75MiB
Metadata, single: total=8.00MiB, used=0.00B
GlobalReserve, single: total=512.00MiB, used=320.25MiBroot@CalvCoNAS:/mnt/var/cores# btrfs fi usage /
Overall:
Device size: 4.00GiB
Device allocated: 4.00GiB
Device unallocated: 0.00B
Device missing: 0.00B
Used: 605.56MiB
Free (estimated): 3.00GiB (min: 3.00GiB)
Data ratio: 1.00
Metadata ratio: 1.96
Global reserve: 512.00MiB (used: 320.25MiB)Data,single: Size:3.57GiB, Used:580.03MiB
/dev/md0 3.57GiBMetadata,single: Size:8.00MiB, Used:0.00B
/dev/md0 8.00MiBMetadata,DUP: Size:204.56MiB, Used:12.75MiB
/dev/md0 409.12MiBSystem,single: Size:4.00MiB, Used:0.00B
/dev/md0 4.00MiBSystem,DUP: Size:8.00MiB, Used:16.00KiB
/dev/md0 16.00MiBUnallocated:
/dev/md0 0.00BI found there was a /var/cores/core-smdb file, but I'm unable to move or remove anything as I just get the message "No space left on device". The other post mentions that Skywalker was able to fix the root fs, but it doesn't mention what was done.
I did also try to download the logs, but it failes most likely because of the space issue as well.
Thanks,
Jeff
I see what Skywalker did. I've replied to your PM.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
