Your message dated Sat, 13 Oct 2018 15:58:34 +0100
with message-id <[email protected]>
and subject line Re: Bug#425199: Mounting local filesystems... Failed!
has caused the Debian Bug report #425199,
regarding Mounting local filesystems... Failed!
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
425199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=425199
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: initscripts
Version: 1.13.25
I get this message when I boot. It comes from
/etc/init.d/mountall.sh. when it tries to mount per /etc/fstab. By
commenting out lines in /etc/fstab I found that it's the line which
mounts the proc filesystem on /proc that is causing the problem.
In ubantu I found that the mountall script had: mount ... -t noproc ..
In other words, it doesn't try to mount proc and thus no error message.
When I add noproc to Debian's mountall.sh (after -t of course), the
"Failed!" message disappears.
I checked on the internet and found old instructions (not labelled
"old") that fstab should have a line to mount proc. I'm using a
Debian from several years ago but upgrade it about once a year using
apt-get. So it should be current. But upgrading doesn't seem to modify
fstab (assuming that it shouldn't have a line to mount proc).
So a fix is needed: either use noproc or have upgrades modify
/etc/fstab.
David Lawyer
--- End Message ---
--- Begin Message ---
On Tue, 10 Jan 2012 15:04:55 +0000 Roger Leigh <[email protected]> wrote:
> On Tue, Jun 23, 2009 at 04:54:16PM +0200, Mike Hommey wrote:
> > On Tue, Jun 23, 2009 at 04:04:58PM +0200, Petter Reinholdtsen
> > <[email protected]> wrote:
> > >
> > > I suspect this approach will break systems with chroots where they
> > > want procfs to be mounted by mountall.sh. I believe the proper fix
> > > for your error about the /proc mounting, is to modify your /etc/fstab
> > > to match the one used by mountkernfs.sh. I believe it should look
> > > like this:
> > >
> > > proc /proc proc defaults 0 0
> >
> > Except it *does* look like that.
>
> Is it an issue with initscripts in current testing/unstable? I've
> updated the mountall shell functions to merge initscripts defaults
> with matching fstab entries, so both should be supported equally well
> now, and this should have solved this bug.
Closing this due to lack of response.
Ben.
--
Ben Hutchings
All the simple programs have been written, and all the good names taken
signature.asc
Description: This is a digitally signed message part
--- End Message ---
