Public SourceMage Discussion List

[nealbirch <nealbirch AT attbi.com>]

Bearcat M. Sandor wrote:
> Folks,
>
> I'm on sorcery devl and test grimoire.
>
> I cast the init.d spell this morning. When i boot up now I get a big red
> FAILED. Everything loads fine though.  It's right after RieserFS
> finishes it's business. Actually it's on the last line that decares the
> RieserFs version and right b4 the localtime.sh is run.  It happens in
> all run levels.  I'm pretty sure it's a problem in the mount.sh script. 
> I notice a few differences in my old file vs this new one.

could I see your fstab, too?

> in the new one, right after the if statement that reports a bad fsck we
> see:
>
> mount    -n -o remount,rw /
>   echo     > /etc/mtab
>   mount    -f -o remount,rw /
>   echo "Mounting local filesystems..."
> # Fixed so as to not mount networked filesystems yet (no networking)
> # mountnfs.sh will take care of this.
>   mount    -a  -t  nosmbfs,nonfs,noncpfs
>   evaluate_retval
>   rm       -f /fastboot /forcefsck
>
>
> in my old one I had:
>
> echo     "done."
>   mount    -n -o remount,rw /
>   echo     > /etc/mtab
>   mount    -f -o remount,rw /
>   mount    -a -F
>   rm       -f /fastboot /forcefsck

-F     (Used in conjunction with -a.)  Fork off a  new  incarnation  of 
mount  for  each  device.   This will do the mounts on different devices 
or different NFS servers  in  parallel.   This  has  the advantage that 
it is faster; also NFS timeouts go in parallel. A disadvantage is that 
the mounts are  done  in  undefined  order. Thus,  you cannot use this 
option if you want to mount both /usr and /usr/spool.

-f     Causes everything to be done except for the actual system call; 
if  it's  not  obvious, this ``fakes'' mounting the file system.
...It can also be used to add entries for devices that were mounted 
earlier with the -n option.

For the life of me, I can't remember why we put the -f in there. We did 
take the -F out because if it goes on it's merry way, mounting things 
all higgledy-piggily, some folks ended up with /var/run mounted before 
/var, for instance, when /var was on a different drive.

> The new one also includes that source statement (I'm no bash programmer
> yet, but i assume that's just like an 'include'). The echo statement
> doesn't matter

yup, the "source /etc/init.d/functions" is where the big red FAILED 
messages come from, along with some internal niceties.

> Notice that I had 2 mount statements in my old script.  Could the mount
> statement in the new script be causing a problem? Note that I have no
> samba nfs or pfs (what's that?).  Why is the first mount in my old file
> a fake?

Its remounting /, though once again, I dont' remember why. my notes are 
in disarray.

> Anyone got any ideas?  I could fiddle by exchanging mount statements I
> suppose. I'm more interested in finding out what's causing the FAILED
> message, so that someone else doesn't run in to it and panic.
>
> I'll be out for the weekend and respond to any mesages by Tuesday.

I wanna look at your fstab. It may be an order issue.


--
"You can fool some of the people all of the time
--and those are the ones you have to concentrate on!"
GW Bush-- from the N.Y. Times