Sbs Bofh wrote:
Also check /var/lib/YaST2/you/youlog for the applied changes.
It looks like a new kernel has been installed at least twice in the last six months and the machine was definitely not rebooted afterwards.
That would indeed explain your trouble.
I think it was a kernel update. Though I would have the rescue cd at hand just in case. (^-^)
I'm in slightly tricky situation - I'm working on the server from 400 miles away via ssh. If it reboot it and it doesn't come back up then in a heap of trouble. relative to a dead server, not being able to mount is a relatively minor problem :-)
Included in the kernel are the modules (or drivers for windows users;), that is the root of the problem. Please check if you are using lilo or grub as a bootloader. If you use lilo you might need to execute /sbin/lilo to write the updated config into the boot loader. That is indeed a message you receive when you update. Normally you should not have a problem rebooting the machine though I would never promise that. (^-^) Nevertheless I would take a good look at the hardware of the machine and google to research if there were any reports for trouble.
it looks like the automatic updates were NOT configured, so the previous admin must have applied the kernel updates through interactive update. does Yast always tell you to reboot if an update requires it?
I think so, any kernel update will only take effect after a reboot, so you either do not apply a kernel update or you reboot afterwards.
I'm a bit ignorant on patching linux, more used to the windows world where even a update for notepad.exe requires a reboot :-) in general is it only kernel updates on SuSE that need a reboot?
Generally a kernel update should be the only update that really requires a reboot. Sandy -- List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com