Hi everyone, I have successfully installed SLES9 SP2 via autoyast and are now switching to SLES9 SP3 install-source. Install goes fine, but after reboot I get: Waiting for device /dev/sda5 to appear: .....not found -- device nodes: <list of devices, no sda> No root device found: exiting to bin/sh It a machine with SATA-controller, and it seems like SATA-support is missing from the installed kernel? I read in the docs that the system with drivers has changed, now a custom initrd is built during install. Seems like it cannot identify the correct driver for the SATA-card and does add that to the initrd. How do I add this driver myself during install? ( Or, is this really another problem? ) Regards Daniel
On Thursday 05 January 2006 14:39, suselist@nlsn.nu wrote:
I have successfully installed SLES9 SP2 via autoyast and are now switching to SLES9 SP3 install-source.
Install goes fine, but after reboot I get:
Waiting for device /dev/sda5 to appear: .....not found -- device nodes: <list of devices, no sda> No root device found: exiting to bin/sh
It a machine with SATA-controller, and it seems like SATA-support is missing from the installed kernel?
How do I add this driver myself during install? ( Or, is this really another problem? )
Sorry I can't help but I would guess you have the same problem with a manual installation? Then I think you should send a mail to suse-sles-e@suse.com You have to subscribe to the list via eMail to suse-sles-e-subscribe@suse.com -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Hello
I have successfully installed SLES9 SP2 via autoyast and are now switching to SLES9 SP3 install-source.
Install goes fine, but after reboot I get:
Waiting for device /dev/sda5 to appear: .....not found -- device nodes: <list of devices, no sda> No root device found: exiting to bin/sh
It a machine with SATA-controller, and it seems like SATA-support is missing from the installed kernel?
I read in the docs that the system with drivers has changed, now a custom initrd is built during install. Seems like it cannot identify the correct driver for the SATA-card and does add that to the initrd.
How do I add this driver myself during install? ( Or, is this really another problem? )
install it with the SLES9-SP3-CD1 -- mit freundlichen Grüßen / best Regard, Günther J. Niederwimmer
Günther J. Niederwimmer wrote:
Hello
I have successfully installed SLES9 SP2 via autoyast and are now switching to SLES9 SP3 install-source.
Install goes fine, but after reboot I get:
Waiting for device /dev/sda5 to appear: .....not found -- device nodes: <list of devices, no sda> No root device found: exiting to bin/sh
It a machine with SATA-controller, and it seems like SATA-support is missing from the installed kernel?
I read in the docs that the system with drivers has changed, now a custom initrd is built during install. Seems like it cannot identify the correct driver for the SATA-card and does add that to the initrd.
How do I add this driver myself during install? ( Or, is this really another problem? )
install it with the SLES9-SP3-CD1
Greetings. I work with Daniel. I tried the SLES9 SP3 RC4 CD1 and the same problem occurs. During the installation, the SATA drive is recognized and the software is properly installed. But on the first reboot, /dev/sda cannot be found. Best regards, Hans Deragon -- Consultant en informatique/Software Consultant Deragon Informatique inc. http://www.deragon.biz Open source (contribution): mailto://hans@deragon.biz http://autopoweroff.deragon.biz
On Fri, Jan 06, 2006 at 03:44:51PM -0500, Hans Deragon wrote:
I work with Daniel. I tried the SLES9 SP3 RC4 CD1 and the same problem occurs. During the installation, the SATA drive is recognized and the software is properly installed. But on the first reboot, /dev/sda cannot be found.
Sounds like the autoyast system is missing adding the right modules into the initrd. Might write a post-install that adds the required modules into the INITRD_MODULES variable in /etc/sysconfig/kernel and re-run mkinitrd (or do the edit in the chroot post) and see if that fixes it. Kind of a hack but might help. I had to do something similar for the right scsi driver on a test sun galaxy2 box when we first got it. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [The guys got drunk, Eric is hungover] Eric: "My head hurts!" Red: "That's your brain trying to comprehend its own stupidity!" => That 70's Show
participants (5)
-
Günther J. Niederwimmer -
Hans Deragon -
Mike Marion -
suselist＠nlsn.nu -
Uwe Gansert