Hi! At work we got a SGI Prism 4M Power server running Suse Linux 10.0, and connected to the server there is 2 ea diskless clients. This is a flight simulator and we start the sim from the diskless clients. For 3 month ago we got error starting clients, Kernel panic - not syncing: Attemted to kill init. By using Yast (Yet Another System Tool) we where able to get it running again, put got full topp 3-4 weeks ago. It is not longer helping using Yast. Probably is Yast generating some backup files somewhere on our harddisk that has to be removed, because they probably is blocking the system. Do anyone knows witch directory this backup files might be?

Welcome to LinuxQuestions

You will have to explain how you were able to get the system running again by using YAST and what you mean by "got full topp 3-4 weeks ago"

Have you check the logs for problems at /var/log/

Here is a good explanation of a kernel panic.
https://www.linuxquestions.org/quest...it-4175614101/

1 members found this post helpful.

Hi again!
I ment "got full stop for 3-4 weeks ago".

Yast is used like this:

Selecting "Network services" and "NFS servers" we remove and attaching directories listed under, and restart NFS server again:

Directories Host wildcard Options
/diskless_nfs * rw,no_root_squash,sync
/diskless_nfs/rptinst/ * rw,no_root_squash,sync
/home * rw,sync,no_root_squash
/sim * rw,sync,no_root_squash
/etc * sync,ro,no_root_squash
/local_home * rw,sync,no_root_squash

This prosedyre has worked fine, untill 3-4 weeks ago.

We suspect that Yast is creating a backup log/file on our harddisk that is blocking our diskless clients to boot/mount on our server. So the question is, where do we find this directory?
Error messages on our diskless clients is attached.


I will also check the links you sendt me.

Thanks, so far.

Attached Thumbnails

   

Have you looked at the log files?

This issue is related to setting of time and date on our server. Our BIOS battery in the Timekeeping RAM is worn out and it is not possible to keep correct time and date on the server. In our case we saw that year was set to over year 2100 on bootup, and it was not possible to mount our two diskless clients. When setting correct time and date our diskless clients mounted to the server. So, when we shut down server we must set time and date on startup, prior to mounting. We are now working with the issue how to program 4ea new Timekeeping RAM's.