Well, now i still have the problem as i originally described it - a 'sometimes' problem that seems to be related to the time it takes the disk to 'wake up.'

AFTER booting doing '/etc/init.d/mountall.sh start' works fine, so that script is fine now.

If i reboot the system such that it is starting up with the disk already 'awake' it mounts fine.



Dr. Alex Sheppard wrote:
After digging around in the scripts in /etc/init.d i found this in mountall.sh:


       #
       # Mount local file systems in /etc/fstab.
       #
       mount_all_local() {
mount -a -t nonfs,nfs4,smbfs,cifs,ncp,ncpfs,coda,ocfs2,gfs,gfs2 -O no_netdev
        }


Now that function is supposed to mount all local filesystems?? But it will only mount the ones of the specified types, and the list omits common types like ext2 and ext3 (my problem partitions being ext3).

So i modified that section to look like this:

       #
       # Mount local file systems in /etc/fstab.
       #
       mount_all_local() {
           mount -a -O no_netdev
       }

... and my problem is solved.


Am i overlooking something here - is there a downside to my fix?? I don't understand why the filesystem types were explicitly listed in the first place??


Alex





Debian Bug Tracking System wrote:
Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
Debian sysvinit maintainers <[email protected]>

If you wish to submit further information on this problem, please
send it to [email protected], as before.

Please do not send mail to [email protected] unless you wish
to report a problem with the Bug-tracking system.




--
Dr. Alex Sheppard
Mob: 0775 1074054




--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to