While testing upgrading from Mageia 1 using the rc dvd, on the first reboot, I was dropped to an emergency shell due to the mount of a vfat partition returning a status of 32. In the emergency shell, I was able to mount the mountpoint without any problems. According to the man page, a return code of 32 is "mount failure", but doesn't provide any useful info to figure out why. On reboot, the same filesystem mounted fine. I have no idea why it failed on the first boot, and the output needs to provide much more info, to indicate why it failed.
Assignee: bugsquad => tmb
CC: (none) => mageia, thierry.vignaud
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
I can't replicate the problem, but I do know that nothing has been changed such that a mount failure doesn't give any useful info about why the mount has failed. Should be bug be kept open or closed as old? I'll leave that decision up to the util-linux maintainer.
I guess we should just chalk this one up to experience. If a systemic failure crops up again at some point, I'm sure we'll get a new bug report. Let's call it "old" for want of a better resolution.
Status: NEW => RESOLVEDResolution: (none) => OLD