Ok, thank you. This really seems to get complicated.
I changed the scripts, rebooted and the second raid partition (named godzilla2, I called the mount points by their device labels) got mounted but not the first one.
I then executed the mount script of the first partition manually and received the following error:
/dev/sdc1 /mnt/sdc1 ntfs noauto,users,exec,ro,umask=000 0 0 # Added by TC
mkdir: can't create directory '/mnt/godzilla1': File exists
Volume is scheduled for check.
Please boot into Windows TWICE, or use the 'force' option.
NOTE: If you had not scheduled check and last time accessed this volume
using ntfsmount and shutdown system properly, then init scripts in your
distribution are broken. Please report to your distribution developers
(NOT to us!) that init scripts kill ntfsmount or mount.ntfs-fuse during
shutdown instead of proper umount.
This worries me, because I did manually mount and work with the drives before, whithout getting any errors.
Thanks a lot for your help
EDIT: I have found a working solution: using mount with the -t option
I am now using the following mount command in the script: sudo mount -t ntfs $RAIDDev1 /mnt/godzilla1
Rich, I would love to learn what your thoughts were on recommending ntfsprogs.tcz and
fuse.tcz and what the differences are between that and mount and mount -t