Description of problem: I performed a live upgrade from mdv 2010.2 according to the instructions on http://www.mageia.org/wiki/doku.php?id=qa_upgrade Upon upgrading the package 'suspend' the following error was logged (copied from urpmi.log): 1925/2014: suspend ################################################################# mktemp: kan geen map aanmaken via sjabloon â<U+0080><U+0098>/tmp/initrd.XXXXXXâ<U+0080><U+0099>: Bestand of map bestaat nietremoving upgraded package dia-0.97.1-1mdv2010.1.x86_6 4 mktemp: kan geen bestand aanmaken via sjabloon â<U+0080><U+0098>/tmp/initrd.img.XXXXXXâ<U+0080><U+0099>: Bestand of map bestaat niet Error creating temporaries. Try again mkinitrd failed: (mkinitrd -f /boot/initrd-2.6.38.7-desktop-1.mga.img 2.6.38.7-desktop-1.mga) at /usr/lib/libDrakX/bootloader.pm line 124. The reason proved to be that /tmp had disappeared. After finishing the upgrade process, the initrd symlink in /boot was broken. After manually creating /tmp and running mkinitrd again, a proper initrd was created.
Translation of Dutch error messages: kan geen map aanmaken via sjabloon => cannot create directory using template Bestand of map bestaat niet => File or directory not found
CC: (none) => pterjanComponent: Release (media, process) => RPM PackagesSource RPM: suspend => mkinitrd
Hmm if something removed /tmp the bug is in what removed it We can create it in mkinitrd but many other apps would be annoyed too...
The error message above was the only suspicious thing I noticed, but if you need more debug info I'll be happy to provide it. Some kind of sanity check would probably be nice after the upgrade process, if I hadn't noticed this my system would not have booted up again (at least not with the Mageia kernel).
Yes mkinitrd is important so it would be nice to make it more robust, but after reboot I would expect some services to not start without /tmp, probably including X so it's important to find why it has happened
Was this bug ever reproduced, and if so, was it reproduced with Mageia 1 official release, too?
Keywords: (none) => NEEDINFOCC: (none) => marja11
I haven't reproduced it on a different system.
(In reply to comment #6) > I haven't reproduced it on a different system. Well, if you reproduced it on the same system: that is interesting, too. Did you reïnstall MDV 2010.2 first? Did you upgrade to Mageia 1 official?
No, I didn't do a re-upgrade from 2010.2 to Mageia 1 on the same machine.
@ Reinout Thanks for replying :) Closing as old, because there are no reports about this being an issue in Mageia 1 or current cauldron
Status: NEW => RESOLVEDResolution: (none) => OLD