Bug 5745

Summary:	Mount failed with status=32
Product:	Mageia	Reporter:	Dave Hodgins <davidwhodgins>
Component:	RPM Packages	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia, thierry.vignaud
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	util-linux-2.21.1-1.mga2.src.rpm	CVE:
Status comment:

Description Dave Hodgins 2012-05-04 08:49:20 CEST

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.

Manuel Hiebel 2012-05-04 17:38:56 CEST

Assignee: bugsquad => tmb

Thierry Vignaud 2012-05-07 18:58:29 CEST

CC: (none) => mageia, thierry.vignaud

Comment 1 Marja Van Waes 2012-05-26 13:02:29 CEST

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

Comment 2 Dave Hodgins 2012-05-26 21:49:49 CEST

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.

Comment 3 Colin Guthrie 2012-06-03 21:35:42 CEST

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 => RESOLVED
Resolution: (none) => OLD