Bug 105265

Summary:	mkinitrd failed
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Andreas Klein <asklein>
Component:	Installation	Assignee:	E-mail List <yast2-maintainers>
Status:	RESOLVED WORKSFORME	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Blocker
Priority:	P5 - None	CC:	aj, vetter
Version:	Beta 2
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Andreas Klein 2005-08-17 16:53:41 UTC

New installation on USB-harddisk.
Software-Selection: Detailed, all selections checked.
After installing the packages from the 1st CD, I get the following message:
An error occured during initrd creation.
/sbin/mkinitrd: line 2770: /etc/fstab: No such file or directory
No '/' mountpoint specified in /etc/fstab

I had a look /etc/fstab and it really seems to be complete.
The real problem is, that there is no /bin/bash, /bin/sh or initrd command
installed.
Don't know, if it happens only when installin on USB disk as I did.

Comment 1 Andreas Klein 2005-08-17 17:28:35 UTC

I installed again onto USB-disk, this time without changeing the
software-selection. This time no problem.
So the problem seems to be related to checking all selections during initial
install. Maybe the dependencies don't get resolved, so that no mkinitrd gets
installed?

Comment 2 Arvin Schnell 2005-08-17 20:48:44 UTC

Please provide logs of the failed installation.  Did you deselect bash
or what?

Comment 3 Lukas Ocilka 2005-08-17 20:53:47 UTC

Please, if you reproduce the bug somehow, attach YaST logs. It might be quite
complex problem and we need logs when we want to foreclose other possibilities.

Generally: every complex YaST / Installation bug needs y2logs to be fixed fast.

Thanks

(Arvin, you were faster ;))

Comment 4 Andreas Klein 2005-08-18 09:08:59 UTC

I mounted the drive, but logs were not saved to the harddisk. I will install the
machine again, to see if I can reproduce the problem.

Comment 5 Andreas Klein 2005-08-18 11:00:11 UTC

I tried to reproduce, but I wasn't able to see the problem again.
We will install some other machines tonight, maybe I will manage to reproduce it.