Bug 118

Summary:	After GNOME installation when package writing stops an error occurs
Product:	Mageia	Reporter:	Dick Gevers <dvgevers>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	Keywords:	NEEDINFO
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakx-installer-stage2	CVE:
Status comment:
Attachments:	report.bug.gz from /root/drakx

Description Dick Gevers 2011-02-19 19:14:07 CET

Description of problem:

Install from DVD choose only type GNOME.

At the end of the package writing an error screen appears saying
"31 installation transactions failed".

Installation may be continued anyway and after User management is compoleted appears the screenof package installation again saying 256 packages are being installed. But only a very few packages are installed during 3 seconds or so, then the screen closes again.

During the summary in Timezone -->  Configure another error appears saying 
"An error occurred
cannot list the available zoneinfo"
(probably due to missing package).

Also in Summary is shown: Graphical interface and in red: "not configured".

Moreover in summary -->Security level, setting the level to secure gives the error 
"An error occurred
output in file /mnt.etc/security/msec/security.conf: No such file or directory".

Indeed the console shows there is no directory 'msec'.

I'm not sure if all of above is related, but I suspect they are.



Reproducible: 

Steps to Reproduce:

Comment 1 Dick Gevers 2011-02-19 19:14:42 CET

Created attachment 13 [details]
report.bug.gz from /root/drakx

Comment 2 Dick Gevers 2011-02-19 19:20:38 CET

Moreover, afetr completing the install, the system was not bootable, because the grub menu list displays only Mandriva Cooker (which is in separate partitions on the same box): there is no grub entry for Mageia.

The /boot/grub/menu.lst that was written during install is reading:

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,3)/gfxmenu

title Mandriva Linux (Cooker)
root (hd0,0)
configfile /grub/menu.lst

(BTW, I did not change anything in section bootloader during the installation summary).

Comment 3 Dick Gevers 2011-02-20 11:48:25 CET

When I tried the same installation method a 2nd time it worked okay.

But IMHO it should have worked the 1st time....

Comment 4 Ahmad Samir 2011-03-04 22:27:32 CET

From the log:
* kernel-desktop-2.6.37-3.mga not installed, unpacking of archive failed on file /boot/System.map-2.6.37-desktop-3.mga;4d5ff89b: cpio: write failed - Resource temporarily unavailable

so this looks like a problem with either your optical drive or HD. Also from the log:
<6>EXT4-fs (sda1): INFO: recovery required on readonly filesystem
<6>EXT4-fs (sda1): write access will be enabled during recovery
<6>EXT4-fs (sda1): recovery complete
<6>EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
<6>EXT4-fs (sda4): INFO: recovery required on readonly filesystem
<6>EXT4-fs (sda4): write access will be enabled during recovery
<6>EXT4-fs (sda4): recovery complete
<6>EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
<6>EXT4-fs (sda5): INFO: recovery required on readonly filesystem
<6>EXT4-fs (sda5): write access will be enabled during recovery
<6>EXT4-fs (sda5): recovery complete
<6>EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
<6>EXT3-fs (sda6): recovery required on readonly filesystem
<6>EXT3-fs (sda6): write access will be enabled during recovery
<6>EXT3-fs: barriers not enabled
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3-fs (sda6): recovery complete
<6>EXT3-fs (sda6): mounted filesystem with ordered data mode
<6>EXT4-fs (sda7): INFO: recovery required on readonly filesystem
<6>EXT4-fs (sda7): write access will be enabled during recovery
<6>EXT4-fs (sda7): recovery complete
<6>EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (null)
<6>Adding 8387580k swap on /dev/sda3.  Priority:-1 extents:1 across:8387580k 
<6>EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: acl
<6>EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: acl
<6>EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: acl
<6>EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: acl
<6>EXT3-fs: barriers not enabled
<6>kjournald starting.  Commit interval 5 seconds
<6>EXT3-fs (sda6): using internal journal
<6>EXT3-fs (sda6): mounted filesystem with ordered data mode


I think we should close as worksforme, unless you can reproduce the issue (so far it looks like a one-time glitch...).

Keywords: (none) => NEEDINFO

Comment 5 Dick Gevers 2011-03-04 23:17:06 CET

Sure it may be a one time glitch, but I doubt this conclusion can be reached from the quoted parts of the log in comment #4: this just means the previous shutdown was irregular and disks needed recovery: so what?

Comment 6 Ahmad Samir 2011-03-05 00:25:25 CET

And the first part:
* kernel-desktop-2.6.37-3.mga not installed, unpacking of archive failed on
file /boot/System.map-2.6.37-desktop-3.mga;4d5ff89b: cpio: write failed -
Resource temporarily unavailable

?

Comment 7 Dick Gevers 2011-03-05 08:39:18 CET

Because recovery is incomplete, partitions are still read only ? 

It looks to me the unpacking of the archive is too impatient, because recovery hasn't finished.

Ahmad Samir 2011-03-08 21:04:20 CET

Source RPM: mageia-dvd-1-x86_64.iso => drakx-installer-stage2

Comment 8 Dick Gevers 2011-04-27 21:43:15 CEST

OLD

Status: NEW => RESOLVED
Resolution: (none) => OLD