Downgrade from ReadyNAS OS 6.7 T180 Beta3 to T172 on Pro Pioneer (RNDP600E) stuck at boot no admin

[goodrip12]

Hi.

I upgraded to 6.7 Beta3 (T180) version from T172 over the weekend, and all was running fine until the networking appeared to go screwy, and I could no longer SSH to the unit, or use the admin page.

I tried the 3 presses of power button to shut down - said it was doing it, but after ages, still hadn't shut down, so held the button down to force it to shutdown.

After restart, volume needed to resync, so waited for that to finish, then decided that as other people had been having problems with the Beta3 release, I would roll back to T172 release.

This appeared to work OK initially, but NAS got stuck at 99%, and said 'upnphttpd.service' on the LCD, never completing.

I am able to SSH into the box, and all apps that were running before downgrade are running, networking OK, and can see all my data shares on my PC, but I am unable to access the admin webui... just says it's trying to connect....

So, it seems like a service has failed to start...

I tried 'systemctl status upnphttpd', and get :

Mar 06 07:23:39 MegaNAS upnphttpd[4036]: upnphttpd is started
Mar 06 07:23:39 MegaNAS upnphttpd[4036]: registering uuid:c6c8fe02-6c16-4a60-a87e-c7a489feff94, desc=http://192.168.128.128:10000/nasServi
ce.xml, uuid=c6c8fe02-6c16-4a60-a87e-c7a489feff94
Mar 06 07:23:39 MegaNAS upnphttpd[4036]: registering upnp:rootdevice, desc=http://192.168.128.128:10000/nasService.xml, uuid=c6c8fe02-6c16
-4a60-a87e-c7a489feff94
Mar 06 07:23:39 MegaNAS upnphttpd[4036]: registering urn:schemas-upnp-org:device:networkstoragedevice:, desc=http://192.168.128.128:10000/
nasService.xml, uuid=c6c8fe02-6c16-4a60-a87e-c7a489feff94
Mar 06 07:23:39 MegaNAS upnphttpd[4036]: registering uuid:c6c8fe02-6c16-4a60-a87e-c7a489feff94, desc=http://192.168.128.128:10000/nasServi
ce.xml, uuid=c6c8fe02-6c16-4a60-a87e-c7a489feff94
Mar 06 07:23:39 MegaNAS upnphttpd[4036]: registering upnp:rootdevice, desc=http://192.168.128.128:10000/nasService.xml, uuid=c6c8fe02-6c16
-4a60-a87e-c7a489feff94
Mar 06 07:23:39 MegaNAS upnphttpd[4036]: registering urn:schemas-upnp-org:device:networkstoragedevice:, desc=http://192.168.128.128:10000/
nasService.xml, uuid=c6c8fe02-6c16-4a60-a87e-c7a489feff94

Can anybody suggest something I can try to resolve this, please?

Thank-you

[YeZ · Accepted solution]

There is a database change between T172 and T180, so that contributed to this behavior. 

Can you do an OS re-install of T180? 

[goodrip12]

I've done a little more digging...

systemctl status -a readynasd

● readynasd.service - ReadyNAS System Daemon
Loaded: loaded (/lib/systemd/system/readynasd.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Mon 2017-03-06 11:51:13 WET; 2h 12min ago
Process: 28496 ExecStart=/usr/sbin/readynasd -v 3 -t (code=exited, status=255)
Main PID: 28496 (code=exited, status=255)
Status: "Importing DB"

Mar 06 11:51:13 MegaNAS systemd[1]: Failed to start ReadyNAS System Daemon.
Mar 06 11:51:13 MegaNAS systemd[1]: readynasd.service: Unit entered failed state.
Mar 06 11:51:13 MegaNAS systemd[1]: readynasd.service: Failed with result 'exit-code'.
Mar 06 11:51:13 MegaNAS systemd[1]: readynasd.service: Service hold-off time over, scheduling restart.
Mar 06 11:51:13 MegaNAS systemd[1]: Stopped ReadyNAS System Daemon.
Mar 06 11:51:13 MegaNAS systemd[1]: readynasd.service: Start request repeated too quickly.
Mar 06 11:51:13 MegaNAS systemd[1]: Failed to start ReadyNAS System Daemon.
Mar 06 11:51:13 MegaNAS systemd[1]: readynasd.service: Unit entered failed state.
Mar 06 11:51:13 MegaNAS systemd[1]: readynasd.service: Failed with result 'start-limit-hit'.

Then tried :

journalctl -xe

and got :

-- Unit readynasd.service has begun starting up.
Mar 06 14:27:55 MegaNAS apache2[3320]: [error] [client 192.168.128.8] Connect rddclient failed, referer: http://192.168.128.128/ad
min/
Mar 06 14:27:55 MegaNAS readynasd[9144]: readynasd log started
Mar 06 14:27:55 MegaNAS readynasd[9144]: readynasd started. (restarted=0)
Mar 06 14:27:55 MegaNAS readynasd[9144]: DB (main) schema version: 23 ==> 23
Mar 06 14:27:55 MegaNAS readynasd[9144]: DB (queue) schema version: new ==> 0
Mar 06 14:27:55 MegaNAS readynasd[9144]: Mismatched config version.
Mar 06 14:27:55 MegaNAS readynasd[9144]: rndb_amazon_s3_import() ==> 5 (0ms)
Mar 06 14:27:55 MegaNAS readynasd[9144]: rndb_import() ==> 5 (491ms)
Mar 06 14:27:55 MegaNAS readynasd[9144]: Error rndb_import() ==> rc=5
Mar 06 14:27:55 MegaNAS readynasd[9144]: dba import failed
Mar 06 14:27:55 MegaNAS systemd[1]: readynasd.service: Main process exited, code=exited, status=255/n/a
Mar 06 14:27:55 MegaNAS systemd[1]: Failed to start ReadyNAS System Daemon.
-- Subject: Unit readynasd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit readynasd.service has failed.
--
-- The result is failed.
Mar 06 14:27:55 MegaNAS systemd[1]: readynasd.service: Unit entered failed state.
Mar 06 14:27:55 MegaNAS systemd[1]: readynasd.service: Failed with result 'exit-code'.
Mar 06 14:27:55 MegaNAS systemd[1]: readynasd.service: Service hold-off time over, scheduling restart.
Mar 06 14:27:55 MegaNAS systemd[1]: Stopped ReadyNAS System Daemon.
-- Subject: Unit readynasd.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit readynasd.service has finished shutting down.

...so something to do with the database?

[YeZ · Accepted solution]

There is a database change between T172 and T180, so that contributed to this behavior. 

Can you do an OS re-install of T180? 

[goodrip12]

Thanks, @YeZ !

I did a USB reinstall of T180, and all looking good again..

So, I guess there's no way back from T180 to T172? I'm happy to wait for the final now, I think.Just hoping that the crash I had on the weekend was a one-off.

Regards,

goodrip12