tfgrid/info_tfgrid
33
3
Fork 0
Code Issues Pull Requests 2 Packages Projects Releases Activity

manual, update new pr

Browse Source
This commit is contained in:
Mik-TF
2024-05-14 17:06:21 -04:00
parent cf82a6f7b9
commit 4228ae6e1a
23 changed files with 326 additions and 83 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
collections/faq/faq.md
View File

@@ -219,6 +219,7 @@
- [Troubleshooting and Error Messages](#troubleshooting-and-error-messages)
- [Is it possible to access the Error Screen or Log Screen?](#is-it-possible-to-access-the-error-screen-or-log-screen)
- [What does it mean when I see, during the 3Node boot, the message: error = context deadline exceeded?](#what-does-it-mean-when-i-see-during-the-3node-boot-the-message-error--context-deadline-exceeded)
- [How can I fix the error messages: "context deadline exceeded" accompanied with "node is behind acceptable delay with timestamp"?](#how-can-i-fix-the-error-messages-context-deadline-exceeded-accompanied-with-node-is-behind-acceptable-delay-with-timestamp)
- [I try to boot a 3Node, but I get the error: "No Route to Host on Linux". What does it mean?](#i-try-to-boot-a-3node-but-i-get-the-error-no-route-to-host-on-linux-what-does-it-mean)
- [How can I fix the error: "Network configuration succeed but Zero-OS kernel could not be downloaded" when booting a 3Node?](#how-can-i-fix-the-error-network-configuration-succeed-but-zero-os-kernel-could-not-be-downloaded-when-booting-a-3node)
- [Using SAS disks, I get the error; "No ssd found, failed to register". What can I do to fix this?](#using-sas-disks-i-get-the-error-no-ssd-found-failed-to-register-what-can-i-do-to-fix-this)
@@ -2042,6 +2043,15 @@ Yes! On the Zero-OS console, hit alt-F2 to open up the Error/Log Screen, and hit
In general, this message means that the ThreeFold Grid asked something to your 3Node, and your 3Node could not respond fast enough. It is usually necessary to read the following error message to understand the situation more specifically.
### How can I fix the error messages: "context deadline exceeded" accompanied with "node is behind acceptable delay with timestamp"?
This often indicates that the real-time clock of the system is not synced with current time. There have been different fixes reported to this issue.
You can boot the node using a Ubuntu live image to sync the hardware time. After that, you can reboot the node and it should boot normally.
You can fix this manually in the BIOS. Go to the BIOS settings and adjust the **Time** and **Date** settings.
You can also try to adjust the clock by NTP over the network, if it applies to your case.
### I try to boot a 3Node, but I get the error: "No Route to Host on Linux". What does it mean?