Bug 137582

Summary:	swap formatting / mount with already mounted swap ...
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Michael Meeks <mmeeks>
Component:	YaST2	Assignee:	Thomas Fehr <fehr>
Status:	RESOLVED INVALID	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	Alpha 2
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michael Meeks 2005-12-08 14:23:32 UTC

So - I have a small memory machine - 128Mb - and so I had to mount a swap drive to even start the install process (from a mini-ISO of my own construction by copying the vmlinux/initrd).

Unfortunately - yast2 then asked to re-format the (already mounted) swap drive, and when I disabled that - claimed it had failed to mount it & bombed out of the install

continuing with 2 swap partitions on the disk instead - with some success but - it'd be nice to detect & fix that.

Comment 1 Michael Gross 2005-12-08 14:54:25 UTC

Hello. I am not sure if we can support this in that fashion because, as you already mentioned, you created this CD of your own.

Normally, you can tell YaST not to touch or format any partitions, you don't want to format (of course). So I cannot follow you here... please be more verbose: What did you do exactly and what was the exact error? Also provide the YaST2 logfiles, please.

Comment 2 Michael Gross 2005-12-08 14:54:51 UTC

Also provide the output of `fdisk -l', please.

Comment 3 Michael Meeks 2005-12-08 15:13:59 UTC

ok - the functioning install (with 2 swap partitions) is ongoing, and there will be no log file from a failed install [AFAICS]. Of course, I don't know the yast terminology but this is what I did:

<boot from stock initrc/yast2>
<select 'Install over network'(?)>
<setup HTTP path to install from>
 ... yast2 downloads 'root' ...
<yast2 moans about no memory - select a swap partion - enter /dev/hda1>
 ... yast2 continues running install ...

When I got to the disk partitioning, it wanted to format the live (mounted) swap partition - I turned formatting off, however - it then tried to mount it, and when it failed the whole install aborted.

fdisk -l would show you a disk completely empty - except for /dev/hda1 512Mb type 82 (swap).

Comment 4 Michael Gross 2005-12-08 16:09:28 UTC

YaST will write its logfiles already during the installation, so they should be available (please try to recover them). I'm not sure, though, if the logs are written to the RAM disk before a harddisk is available.

This sounds like YaST does not realize it has already mounted this partition before. Thomas: please look into that.

Comment 5 Thomas Fehr 2005-12-12 10:32:25 UTC

Without logfiles there is nothing I can do.
Need the logfiles from /var/log/YaST2-

Comment 6 Michael Meeks 2005-12-12 11:00:26 UTC

Thomas - have you even tried to repeat this on a small-memory (128Mb[!]) machine ? or is this just a "go away" NEEDINFO ? - it does not seem easy to get a log-file of an (easily repeatable) failure that causes yast2 to abort installation before any media is formatted. OTOH - it is surely easy to reproduce - you have QA engineers right ?

Comment 7 Thomas Fehr 2005-12-12 11:35:18 UTC

The logfile is available in ihe ramdisk image even before any media is
formatted so it is no problem to copy it after YaST2 display the popup about
aborted installation. I certainly do not have the time to repeat every bug 
report I get. Often they are not as easily reproducable as reporters assume,
since there are other side effects (partition layout, exact hardware, 
installation method). There are lots of factors that influence
memory requirements during installation besides the size of the physical memory.

I am not sure if the memory size of 128MB is supported at all, not sure but
AFAIK minimal memory requirement is 256M.

Comment 8 Thomas Fehr 2006-02-02 11:58:43 UTC

Closing this beacause lack of logfiles.