In my RN528X I had installed the firmware 6.9.5 patch 1 release and I downloaded and installed version 6.10.0. But at the time of the reboot after the upgrade the boot reaches 99% and then it doesn't go on and it doesn't finish. The display shows "Booting ....
What can it have happened and how can I solve it?
Thanks in advance.
/Sören
Model: RN528X|ReadyNAS 528X - Premium Performance Business Data Storage - 8-Bay
Try downloading the logs with RAIDar. You can then PM ("private message") one of the mods ( @JohnCM_S for example) or perhaps @Hopchen (former Netgear employee) and ask them to analyze them. Don't post a link to your logs here, as there is some privacy leakage if you do that.
Not sure if this will help but I had this identical problem today with a 204 unit. I had rebooted prior to the update and still it sat stuck for an hour at 99%. Multiple reboots failed to solve it and I was only semi-sure I had a valid backup.
Sorry to inform but I fowlloing the instruction but nerver get "boot menu message". Even if I hold the reset buttom in for two minutes the display just show "Booting..."
Now I tried to remov all 8 disks and boot the system and press the reaset butom when power the NAS on. Still after two minutes the Displa shows "Booting..." and the blue LED on the front turns off. Now I think after reading that som other person have the same type of experiance as I have that NETGEAR has a real problem with the new 6.10 when trying to upgrade from 5.9.1 😞
Model: RN528X|ReadyNAS 528X - Premium Performance Business Data Storage - 8-Bay
Now I think after reading that som other person have the same type of experiance as I have that NETGEAR has a real problem with the new 6.10 when trying to upgrade from 5.9.1
6.9.1?
I upgraded three systems from 6.9.5 to 6.10.0 with no issue. While it's possible that there is something broken on the 6.9.1->6.10.0 upgrade path, I think it is more likely that something in your specific system misbehaved during the upgrade.
Your best option is to use paid support (my.netgear.com).
With my unit, the disks were left in place; not removed. Unit was powered off by removing power lead from rear (power button not doing anything useful like turning it off).
Held in reset button with small paperclip, then whilst holding reset (tricky), reinserted power lead and then pushed and held both power and reset button till boot menu appeared. Then released both power and reset button.
Pushed backup button on front and selected "OS-Install" and click pressed reset again to select.
Left to boot and my unit was sorted.
I agree it does sound like some issue with the update as my box was perfectly fine before.
FYI - my box was running 6.9.5 prior to the update. Only errors I could find in the logs I pulled after recovery pointed to issues with mysql-server and Plex media server. So maybe interaction with the update and certain apps??
Got two more NAS boxes to update next week, think I might wait a little while now and make sure those backups are 100%
Just out of interest did you deploy the update by manually downloading or allow the box to update itself?
Plex error might just be a red herring.
Maybe I am wrong (probably), but it looks like it updated to 6.10.0 first, rebooted, then tried to automatically get 6.10.+Hotfix2 and then came unstuck; which I note there is now an option in Settings for installing "Automatic Hotfix Updates" enabled by default, don't recall seeing that before.
Between the first update/auto reboot and getting stuck was about 40 minutes (it seemed like an hour, but logs don't lie) before I thought something was amiss.
Here is some info:-
ReadyNAS 204 Timeline - (UK BST) 24/04/2019.
13:27 - Unit rebooted to flush caches etc. prior to update (should have double checked backup as well!!) 13:29 - Unit operational after reboot 13:31 - Allowed update to 6.10.0 to install (from 6.9.5)
- Period of downtime, unit reboots and sits at 99%, with "Booting", power button toggles text to "msql.service", all disk activity noise stops. RAIDar shows device as "Starting up" but cannot access. - Unit inaccessible from Management page or thru volume shares. Can ping device only. No SSH access.
14:10ish- Attempted manual intervention - unable to shutdown, removed power. 15:26 - Unit back in operation after OS-Reinstall (from Boot menu) ;due to failed boot attempts (and pulling power), disk drives needed resync for Raid 15:39 - Removed unneeded Plex Media App (for RN2xx) 21:36 - Raid Resynced - Unit fully operational, no visible issues.
Then seeing these events occured each time before "stuck" at 99% with Booting/msql.service on screen.
SYSTEM.LOG
Apr 24 14:15:15 NETGEARNAS /etc/mysql/debian-start[3003]: Upgrading MySQL tables if necessary. Apr 24 14:15:15 NETGEARNAS /etc/mysql/debian-start[3006]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Apr 24 14:15:15 NETGEARNAS /etc/mysql/debian-start[3006]: Looking for 'mysql' as: /usr/bin/mysql Apr 24 14:15:15 NETGEARNAS /etc/mysql/debian-start[3006]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Apr 24 14:15:15 NETGEARNAS /etc/mysql/debian-start[3006]: This installation of MySQL is already upgraded to 5.5.53, use --force if you still need to run mysql_upgrade Apr 24 14:15:15 NETGEARNAS /etc/mysql/debian-start[3017]: Checking for insecure root accounts. Apr 24 14:15:15 NETGEARNAS /etc/mysql/debian-start[3022]: WARNING: mysql.user contains 4 root accounts without password! Apr 24 14:15:16 NETGEARNAS nmbd[2153]: [2019/04/24 14:15:16.031191, 0] ../lib/util/become_daemon.c:138(daemon_ready) Apr 24 14:15:16 NETGEARNAS nmbd[2153]: daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections Apr 24 14:15:16 NETGEARNAS /etc/mysql/debian-start[3023]: Triggering myisam-recover for all MyISAM tables Apr 24 14:15:17 NETGEARNAS afpd[2524]: Netatalk AFP/TCP listening on 192.168.2.8:548 Apr 24 14:15:39 NETGEARNAS nmbd[2153]: [2019/04/24 14:15:39.300414, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2) Apr 24 14:15:39 NETGEARNAS nmbd[2153]: ***** Samba name server NETGEARNAS is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.8 ***** Apr 24 14:17:02 NETGEARNAS CRON[3141]: pam_unix(cron:session): session opened for user root by (uid=0) Apr 24 14:17:02 NETGEARNAS CRON[3142]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 24 14:17:02 NETGEARNAS CRON[3141]: pam_unix(cron:session): session closed for user root Apr 24 14:18:37 NETGEARNAS libapache2-mod-php5[3279]: php5_invoke opcache: already enabled for apache2 SAPI Apr 24 14:18:37 NETGEARNAS libapache2-mod-php5[3305]: php5_invoke xcache: already enabled for apache2 SAPI Apr 24 14:18:37 NETGEARNAS libapache2-mod-php5[3331]: php5_invoke gd: already enabled for apache2 SAPI Apr 24 14:18:38 NETGEARNAS libapache2-mod-php5[3357]: php5_invoke pdo_mysql: already enabled for apache2 SAPI Apr 24 14:18:38 NETGEARNAS libapache2-mod-php5[3383]: php5_invoke pdo: already enabled for apache2 SAPI Apr 24 14:18:38 NETGEARNAS libapache2-mod-php5[3409]: php5_invoke mysqli: already enabled for apache2 SAPI Apr 24 14:18:38 NETGEARNAS libapache2-mod-php5[3435]: php5_invoke json: already enabled for apache2 SAPI Apr 24 14:18:38 NETGEARNAS libapache2-mod-php5[3461]: php5_invoke mysql: already enabled for apache2 SAPI Apr 24 14:18:39 NETGEARNAS libapache2-mod-php5[3484]: apache2_invoke php5: already enabled -- Reboot --
SYSTEMMD.LOG
Apr 24 14:16:49 NETGEARNAS systemd[1]: Starting ReadyNAS Update... Apr 24 14:17:00 NETGEARNAS readynas-upgrade[2513]: W: Failed to fetch https://apt.readynas.com/packages/readynasos/dists/6.10.0/InRelease Could not resolve host: apt.readynas.com Apr 24 14:17:00 NETGEARNAS readynas-upgrade[2513]: W: Failed to fetch http://mirrors.kernel.org/debian/dists/jessie/InRelease Could not resolve 'mirrors.kernel.org' Apr 24 14:17:00 NETGEARNAS readynas-upgrade[2513]: W: Failed to fetch http://security.debian.org/dists/jessie/updates/InRelease Could not resolve 'security.debian.org' Apr 24 14:17:00 NETGEARNAS readynas-upgrade[2513]: W: Some index files failed to download. They have been ignored, or old ones used instead. Apr 24 14:17:02 NETGEARNAS CRON[3141]: pam_unix(cron:session): session opened for user root by (uid=0) Apr 24 14:17:02 NETGEARNAS CRON[3142]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 24 14:17:02 NETGEARNAS CRON[3141]: pam_unix(cron:session): session closed for user root Apr 24 14:18:35 NETGEARNAS readynas-upgrade[2513]: Setting up libapache2-mod-php5 (5.6.40+dfsg-0+deb8u2) ... Apr 24 14:18:37 NETGEARNAS libapache2-mod-php5[3279]: php5_invoke opcache: already enabled for apache2 SAPI Apr 24 14:18:37 NETGEARNAS libapache2-mod-php5[3305]: php5_invoke xcache: already enabled for apache2 SAPI Apr 24 14:18:37 NETGEARNAS libapache2-mod-php5[3331]: php5_invoke gd: already enabled for apache2 SAPI Apr 24 14:18:38 NETGEARNAS libapache2-mod-php5[3357]: php5_invoke pdo_mysql: already enabled for apache2 SAPI Apr 24 14:18:38 NETGEARNAS libapache2-mod-php5[3383]: php5_invoke pdo: already enabled for apache2 SAPI Apr 24 14:18:38 NETGEARNAS libapache2-mod-php5[3409]: php5_invoke mysqli: already enabled for apache2 SAPI Apr 24 14:18:38 NETGEARNAS libapache2-mod-php5[3435]: php5_invoke json: already enabled for apache2 SAPI Apr 24 14:18:38 NETGEARNAS libapache2-mod-php5[3461]: php5_invoke mysql: already enabled for apache2 SAPI Apr 24 14:18:39 NETGEARNAS readynas-upgrade[2513]: apache2_invoke php5: already enabled Apr 24 14:18:39 NETGEARNAS libapache2-mod-php5[3484]: apache2_invoke php5: already enabled Apr 24 14:18:40 NETGEARNAS systemd[1]: Reloading. Apr 24 14:18:40 NETGEARNAS systemd[1]: [/lib/systemd/system/fvapp-plexmediaserver-annapurna.service:11] Invalid escape sequences in line, correcting: "/bin/sh -c '/apps/plexmediaserver-annapurna/Binaries/Plex\ Media\ Server'" Apr 24 14:18:40 NETGEARNAS systemd[1]: systemd-journald-audit.socket: Cannot add dependency job, ignoring: Unit systemd-journald-audit.socket is masked. Apr 24 14:18:42 NETGEARNAS rn-update.sh[3124]: W: Failed to fetch https://apt.readynas.com/packages/readynasos/dists/6.10.0/InRelease Could not resolve host: apt.readynas.com Apr 24 14:18:42 NETGEARNAS rn-update.sh[3124]: W: Failed to fetch http://mirrors.kernel.org/debian/dists/jessie/InRelease Could not resolve 'mirrors.kernel.org' Apr 24 14:18:42 NETGEARNAS rn-update.sh[3124]: W: Failed to fetch http://security.debian.org/dists/jessie/updates/InRelease Could not resolve 'security.debian.org' Apr 24 14:18:42 NETGEARNAS rn-update.sh[3124]: W: Some index files failed to download. They have been ignored, or old ones used instead. Apr 24 14:28:50 NETGEARNAS systemd[1]: Starting Cleanup of Temporary Directories... Apr 24 14:28:50 NETGEARNAS systemd[1]: Started Cleanup of Temporary Directories. Apr 24 14:32:24 NETGEARNAS systemd-logind[2016]: Power key pressed. -- Reboot --
And then this
[2019/04/24 12:34:10 UTC] Updated from ReadyNASOS 6.9.5 (ReadyNASOS) to 6.10.0 (ReadyNASOS). [2019/04/24 14:25:02 UTC] Updated from ReadyNASOS 6.10.0 (ReadyNASOS) to 6.10.0 (ReadyNASOS).
These should have resolved, and might be part of the problem. Perhaps ask @JohnCM_S or @OOM-9 if they are willing to review the full log zip file. Don't post a link here, as there is information in the logs that shouldn't be posted publicly.
@Markwig My RN528X has been working well unitll i tried to do the upgrade from 6.9.5 to 6.10. No I have a NAS that is more or less dead. So fare it always end with "Booting..."
Do Yoy know if its possible to reinstall via the USB port?
@StephenB sorry. Misstyping. I whent from 6.9.5 to 6.10.0. I did it from the NAS. After first try and a reboot it still said that the unit had 6.9.5. So I tried one more time to upgrade to 6.10.0. Then I always end up att "Booting...". I have tried to follow instructions to get to the Boot Meny but I never get there.
Model: RN528X|ReadyNAS 528X - Premium Performance Business Data Storage - 8-Bay
Bit puzzling why you cannot seem to get the boot menu, as the option to "factory reset" is also there if needed. Did you leave the disks in when you tried? As StephenB said "the system boots from the disks" and they are needed so the unit can copy across the OS from its internal memory onto the disks and replace any corrupt OS files; leaving the data intact.
Please do not assume I am an expert on these units; there are far more qualified people than me on this forum.
But if your data is vital and you are unsure then I would urge you to seek guidance from Netgear on this before implementing; I did an OS reinstall as I was prepared to accept the loss and revert to backups, and buy a new unit if really needed.
If you are still stuck on 'Booting...' even when trying you access the boot menu, you can hook up a console cable to the NAS so we can check what it says and advise how to fix. You may provide to me the console logs via PM (private message).
