- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: ReadyNas 314 boot stopped to 93%
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
The readynas won't finish the boot process. It blocked on 93% and it show upnphttpd.service on the Screen display.
I preview to reinstall the firmware but i want to know if someone have already this problem.
Smb Share is working, but ftp share don't show any folder after log in.
When i attemp to the web admistration page, it show the login box but after entering user and password i have the message ReadyNas admin page if offline.
Raidar shows : Management service is offline
Model : 314
Firmware : 6.10.2
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OS reinstall via Boot Menu solved the problem. Thank you
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNas 314 boot stopped to 93%
Hi Rajema,
Can you still download the NAS system logs through RAIDar? If you can, please download it and then provide it to us so we can check what is the cause of the issue.
You may upload the logs to a file-sharing site then send the download link via PM (private message).
Regards,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNas 314 boot stopped to 93%
I can download the log file. It have been send to you via PM
But there is the result from Diagnostic on Raidar
------------------------------
Successfully completed diagnostics
System
No errors found.
Logs
No errors found.
System Management
2019-12-12 08:05:21: DB (main) schema version: 24 ==> 24
2019-12-12 08:05:21: DB (queue) schema version: new ==> 0
2019-12-12 08:05:21: Failed to INSERT INTO service_cifs
2019-12-12 08:05:21: rndb_import() ==> 1 (257ms)
2019-12-12 08:05:21: Error rndb_import() ==> rc=1
2019-12-12 08:05:21: dba import failed
2019-12-12 08:05:21: Failed to start ReadyNAS System Daemon.
2019-12-12 08:05:21: Failed to start ReadyNAS System Daemon.
2019-12-12 08:05:20: DB (main) schema version: 24 ==> 24
2019-12-12 08:05:20: DB (queue) schema version: new ==> 0
2019-12-12 08:05:20: Failed to INSERT INTO service_cifs
2019-12-12 08:05:20: rndb_import() ==> 1 (208ms)
2019-12-12 08:05:20: Error rndb_import() ==> rc=1
2019-12-12 08:05:20: dba import failed
2019-12-12 08:05:20: Failed to start ReadyNAS System Daemon.
2019-12-12 08:05:19: DB (main) schema version: 24 ==> 24
2019-12-12 08:05:19: DB (queue) schema version: new ==> 0
2019-12-12 08:05:19: Failed to INSERT INTO service_cifs
2019-12-12 08:05:19: rndb_import() ==> 1 (199ms)
2019-12-12 08:05:19: Error rndb_import() ==> rc=1
2019-12-12 08:05:19: dba import failed
2019-12-12 08:05:19: Failed to start ReadyNAS System Daemon.
2019-12-12 08:05:18: DB (main) schema version: 24 ==> 24
2019-12-12 08:05:18: DB (queue) schema version: new ==> 0
2019-12-12 08:05:18: Failed to INSERT INTO service_cifs
2019-12-12 08:05:18: rndb_import() ==> 1 (235ms)
2019-12-12 08:05:18: Error rndb_import() ==> rc=1
2019-12-12 08:05:18: dba import failed
2019-12-12 08:05:18: Failed to start ReadyNAS System Daemon
--------------------------------------
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: ReadyNas 314 boot stopped to 93%
@Rajema wrote:2019-12-12 08:05:21: Failed to INSERT INTO service_cifs
That error I think from memory would suggest corruption of the main service configuration file. As it's corrupt the management service can't import expected values into the database.
If the 4GB root volume isn't overly full (can easily check that looking at e.g. btrfs.log) then simply replacing that configuration file with the default one or a working one from a backup should be enough to resolve the problem.
Re-installing the firmware wouldn't help with this problem.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OS reinstall via Boot Menu solved the problem. Thank you