Tracking an error during installation
I am trying to kickstart a machine using a kickstart xml file that I have use multiple times before. However, for some unknown reason this time around, I get an error message: "An error occured during the installation" Putting aside my admiration for how wonderfully helpful that error message actually is, I can't seem to find a way to figure out what is actually wrong so I can fix it. Could someone, please tell me where to look to find what actually went wrong? Thanx -- Mitko Haralanov mitko@pathscale.com http://www.pathscale.com ========================================== Any sufficiently advanced bug is indistinguishable from a feature. -- Rich Kulawiec
On Thu, 4 Aug 2005 12:10:37 -0700 Mitko Haralanov <mitko@pathscale.com> wrote:
I am trying to kickstart a machine using a kickstart xml file that I have use multiple times before. However, for some unknown reason this time around, I get an error message:
"An error occured during the installation"
Putting aside my admiration for how wonderfully helpful that error message actually is, I can't seem to find a way to figure out what is actually wrong so I can fix it.
OK, I managed to find this in the dmesg output hidden well in the menues: lockd: failed to open /var/lib/nfs/state: err=-2 Anyone have an idea why this would be showing up and whether it is the problem? -- Mitko Haralanov mitko@pathscale.com http://www.pathscale.com ========================================== The value of a program is proportional to the weight of its output.
On Thu, 4 Aug 2005, Mitko Haralanov wrote:
I am trying to kickstart a machine using a kickstart xml file that I have use multiple times before. However, for some unknown reason this time around, I get an error message:
"An error occured during the installation"
Putting aside my admiration for how wonderfully helpful that error message actually is, I can't seem to find a way to figure out what is actually wrong so I can fix it.
Could someone, please tell me where to look to find what actually went wrong?
boot with 'start_shell=1'. This will start a bash right before yast is started (and after it is run). You can then run 'yast' manually and do all sorts of debugging. Steffen
participants (2)
-
Mitko Haralanov -
Steffen Winterfeldt