[opensuse-autoinstall] SLES 11 SP1 x86_64 invalid root filesystem after autoyast install
Hello all, I'm having a strange problem while trying to use the same autoyast I used for SLES 11 on SLES 11 SP1. I didn't think there would be any compatibility issues, but maybe there is? The problem is that during the second stage of install, after the first reboot, the boot process stops (while still in initrd) and drops me to a shell. When I exit the shell (control-D), the boot process continues and everything is fine. The system functions completely normally after boot. I've engaged Novell support, but so far we have not found a resolution. However, I followed the suggestion of manually installing a machine and then using the cloned autoinst.xml as a starting point. Every time I build a box with that autoyast file, I do not see this issue. I've looked and looked, but cannot find the issue, or any significant difference between my autoyast and the cloned system's autoyast. I've attached both here. Can anybody see something I'm overlooking? There are two files below. The first (autoinst.xml) is a clone of the manually installed system which always works. The second (autoyast_slspgen06e.xml) is the slightly modified SLES 11 autoyast file that produces the invalid root filesystem problem. Also a few screenshots (edited to include an index dot): Thanks in advance, Justin
Am 23.08.2010 15:32, schrieb justin.kinney@academy.com:
Hello all,
I'm having a strange problem while trying to use the same autoyast I used for SLES 11 on SLES 11 SP1. I didn't think there would be any compatibility issues, but maybe there is?
The problem is that during the second stage of install, after the first reboot, the boot process stops (while still in initrd) and drops me to a shell. When I exit the shell (control-D), the boot process continues and everything is fine. The system functions completely normally after boot.
I've engaged Novell support, but so far we have not found a resolution. However, I followed the suggestion of manually installing a machine and then using the cloned autoinst.xml as a starting point. Every time I build a box with that autoyast file, I do not see this issue.
I've looked and looked, but cannot find the issue, or any significant difference between my autoyast and the cloned system's autoyast. I've attached both here. Can anybody see something I'm overlooking?
There are two files below. The first (autoinst.xml) is a clone of the manually installed system which always works. The second (autoyast_slspgen06e.xml) is the slightly modified SLES 11 autoyast file that produces the invalid root filesystem problem.
Also a few screenshots (edited to include an index dot):
Thanks in advance, Justin
Hi Justin,
taking a quick look and comparing with a tool like "kdiff" shows some
different enties (regarding the bootloader, grub .
The "autoinst.xml" from your manual installation for example has entries
in <bootloader> and
I'm having a strange problem while trying to use the same autoyast I used for SLES 11 on SLES 11 SP1. I didn't think there would be any compatibility issues, but maybe there is?
The problem is that during the second stage of install, after the first reboot, the boot process stops (while still in initrd) and drops me to a shell. When I exit the shell (control-D), the boot process continues and everything is fine. The system functions completely normally after boot.
I've engaged Novell support, but so far we have not found a resolution. However, I followed the suggestion of manually installing a machine and then using the cloned autoinst.xml as a starting point. Every time I build a box with that autoyast file, I do not see this issue.
I've looked and looked, but cannot find the issue, or any significant difference between my autoyast and the cloned system's autoyast. I've attached both here. Can anybody see something I'm overlooking?
There are two files below. The first (autoinst.xml) is a clone of the manually installed system which always works. The second (autoyast_slspgen06e.xml) is the slightly modified SLES 11 autoyast file that produces the invalid root filesystem problem.
Also a few screenshots (edited to include an index dot):
Thanks in advance, Justin
Hi Justin,
taking a quick look and comparing with a tool like "kdiff" shows some different enties (regarding the bootloader, grub .
The "autoinst.xml" from your manual installation for example has entries in <bootloader> and
like this:
<image>(hd0,0)/vmlinuz-2.6.32.12-0.7-default</image> <initrd>(hd0,0)/initrd-2.6.32.12-0.7-default</initrd>
<pertitioning> (boot) <fstopt>acl,user_xattr</fstopt>
These entries are missing in your original file. I don't know if it is a help for you. Try "kdiff" or any similar tool and it gives a good starting point to compare that files.
I'm still struggeling with my own <bootloader> entries so I'm not really an expert for your question ;-)
Thanks for the reply. I've added the entire <bootloader> from the working autoyast into my autoyast and I am testing now. My concern is that the kernel version referenced above may change. Will autoyast figure out that a newer kernel was installed and adjust appropriately? I assume that it will, but I'd like to leave it as generic as possible and let the system figure it out at build time. Thanks, Justin -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
I'm having a strange problem while trying to use the same autoyast I used for SLES 11 on SLES 11 SP1. I didn't think there would be any compatibility issues, but maybe there is?
The problem is that during the second stage of install, after the first reboot, the boot process stops (while still in initrd) and drops me to a shell. When I exit the shell (control-D), the boot process continues and everything is fine. The system functions completely normally after boot.
I've engaged Novell support, but so far we have not found a resolution. However, I followed the suggestion of manually installing a machine and then using the cloned autoinst.xml as a starting point. Every time I build a box with that autoyast file, I do not see this issue.
I've looked and looked, but cannot find the issue, or any significant difference between my autoyast and the cloned system's autoyast. I've attached both here. Can anybody see something I'm overlooking?
There are two files below. The first (autoinst.xml) is a clone of the manually installed system which always works. The second (autoyast_slspgen06e.xml) is the slightly modified SLES 11 autoyast file that produces the invalid root filesystem problem.
Also a few screenshots (edited to include an index dot):
Thanks in advance, Justin
Hi Justin,
taking a quick look and comparing with a tool like "kdiff" shows some different enties (regarding the bootloader, grub .
The "autoinst.xml" from your manual installation for example has entries in <bootloader> and
like this:
<image>(hd0,0)/vmlinuz-2.6.32.12-0.7-default</image> <initrd>(hd0,0)/initrd-2.6.32.12-0.7-default</initrd>
<pertitioning> (boot) <fstopt>acl,user_xattr</fstopt>
These entries are missing in your original file. I don't know if it is a help for you. Try "kdiff" or any similar tool and it gives a good starting point to compare that files.
I'm still struggeling with my own <bootloader> entries so I'm not really an expert for your question ;-)
Thanks for the reply. I've added the entire <bootloader> from the working autoyast into my autoyast and I am testing now. My concern is that the kernel version referenced above may change. Will autoyast figure out that a newer kernel was installed and adjust appropriately? I assume that it will, but I'd like to leave it as generic as possible and let the system figure it out at build time.
The test failed. An interesting thing that I didn't mention is that if I reboot (rather than just exit the shell) 3 times, the system will finally load normally. I've attached the revised autoyast. Note that I've added our local package and update repositories. If it makes it simpler for troubleshooting, I can leave these out. The problem occurs in either case. Thanks, Justin
taking a quick look and comparing with a tool like "kdiff" shows some different enties (regarding the bootloader, grub .
The "autoinst.xml" from your manual installation for example has entries in <bootloader> and
like this:
<image>(hd0,0)/vmlinuz-2.6.32.12-0.7-default</image> <initrd>(hd0,0)/initrd-2.6.32.12-0.7-default</initrd>
<pertitioning> (boot) <fstopt>acl,user_xattr</fstopt>
These entries are missing in your original file. I don't know if it is a help for you. Try "kdiff" or any similar tool and it gives a good starting point to compare that files.
I'm still struggeling with my own <bootloader> entries so I'm not really an expert for your question ;-)
Thanks for the reply. I've added the entire <bootloader> from the working autoyast into my autoyast and I am testing now. My concern is that the kernel version referenced above may change. Will autoyast figure out that a newer kernel was installed and adjust appropriately? I assume that it will, but I'd like to leave it as generic as possible and let the system figure it out at build time.
The test failed. An interesting thing that I didn't mention is that if I reboot (rather than just exit the shell) 3 times, the system will finally load normally.
I've attached the revised autoyast. Note that I've added our local package and update repositories. If it makes it simpler for troubleshooting, I can leave these out. The problem occurs in either case.
OK, making some progress...After removing the following <remove-package> lines, my autoyast file works. <package>eject</package> <package>elilo</package> <package>emacs</package> <package>emacs-info</package> <package>emacs-x11</package> <package>finger</package> <package>FirmwareUpdateKit</package> <package>ivman</package> <package>pm-profiler</package> <package>ppp</package> <package>rcs</package> <package>rsh</package> <package>suspend</package> <package>wireless-tools</package> Do any of these look like they could cause this issue? Thanks, Justin -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
OK, making some progress...After removing the following <remove-package> lines, my autoyast file works.
<package>eject</package> <package>elilo</package> <package>emacs</package> <package>emacs-info</package> <package>emacs-x11</package> <package>finger</package> <package>FirmwareUpdateKit</package> <package>ivman</package> <package>pm-profiler</package> <package>ppp</package> <package>rcs</package> <package>rsh</package> <package>suspend</package> <package>wireless-tools</package>
Do any of these look like they could cause this issue?
Looks like leaving the "suspend" package in place does the trick... It's the only package of the bunch that modifies anything regarding mkinitrd. Thanks, Justin -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (2)
-
Ivan De Masi -
justin.kinney＠academy.com