Re: Need help getting a firewire HD to automount during boot in Suse

["Hex Star" <hexstar@gmail.com>]

On 5/7/06, Herbie <technowombat@yahoo.com> wrote:

Well, I can't talk for Suse, but it's all pretty much the same. Init
scripts live in /etc/init.d and usually have helpful names.

The runlevel init dirs are /etc/rc0.d ---> /etc/rc5.d and have numbered
symlinks to the init scripts that get run in that level.

Here's a tutorial for you
http://yolinux.com/TUTORIALS/LinuxTutorialInitProcess.html

Basically look in /etc/init.d for something called firewire or similar. Or
even better

grep -il firewire /etc/init.d/

will show you which init scripts have the word firewire in them.

herbie

On Sat, 6 May 2006, Hex Star wrote:

> On 5/6/06, Herbie < technowombat@yahoo.com> wrote:
>>
>> Check the order of your init scripts. I'd imagine that the firewire card
>> and attached devices need to be scanned and initialised, and this is
>> likely happening after the system mounts all drives.
>>
>> I'd set the entry in fstab to noauto and simply add mount /websites to
>> either the end of the firewire init script, or in rc.local (which should
>> be at S99, yes?)
>>
>> herbie
>>
>> On Sat, 6 May 2006, Hex Star wrote:
>>
>> > Hello, I have a HP NetServer LH3R running Suse 10 and I've put in a
>> firewire
>> > PCI card and connected a firewire external HD to that card, linux sees
>> and
>> > can interact with the HD fine but since I'm planning to install cPanel
>> and
>> > would like to use the firewire drive as the clients home folder for
>> added
>> > disk space I need the drive to be automounted during boot, so far I've
>> tried
>> > adding "mount -rw /dev/hdb1 /websites"  (without the quotes of course)
>> to
>> > /etc/rc.d/boot.local but that didn't work so I removed that and then
>> tried
>> > adding "/dev/sdb1 /websites ext3 rw,auto,user,exec 0 0" (without the
>> quotes
>> > of course) to /etc/fstab and now Suse sees the drive and knows the
>> > mountpoint should be /websites but despite auto being in the fstab file
>> it's
>> > not auto mounting during the boot it's still not working :-(...can
>> anyone
>> > please tell me what I'm doing wrong and what I need to do to get this
>> drive
>> > to auto mount during boot? I'm pulling my hair out trying to get this to
>> > work and would greatly appreciate any help you guys can provide me,
>> thanks!
>> > :-)
>> >
>>
>> -
>> To unsubscribe, send email to majordomo@luci.org with
>> "unsubscribe luci-discuss" in the body.
>>
> Thanks for the reply :-), where in Suse 10 would I find the firewire init
> script?
>

-
To unsubscribe, send email to majordomo@luci.org with
"unsubscribe luci-discuss" in the body.

Hmm actually I found something interesting, the firewire HD is being
auto mounted upon boot (revealed by typing mount in terminal), but
oddly enough it isn't mounting to the mount point I specified in
/etc/fstab which is /websites (and yes it exists and I can write to
it), instead mount shows it being mounted at /media/websites which I
confirmed by copying a big file to that location and indeed I heard the
firewire HD working...even more perplexing is the fact that KDE
(running KDE on server until it goes public at which time it'll be
running cPanel and X will be removed) knows the drive should be mounted
at /websites (shown by looking in KDiskFree, it shows 0B for the drives
free space and such which is a sign it isn't mounted according to KDE
and it shows for the mountpoint /websites) and if I mount the drive
through Konquerer and then do mount, it shows the drive being mounted
once at /media/websites and then at /websites...very weird...o_O and
yes there's only one entry for the device in /etc/fstab...I even had a
friend vnc to the server and despite multiple tries he could not figure
out the cause of this weirdness...anyone experience this? Know how to
fix this? Would appreciate any tips you guys could provide, thanks! :-)