Yes Johannes, I guess I just identified the problem. After the system is up everything works. However, during start up a message is printed that reports a failure: it says ntfs-3g is not a know file type. I don't remember the exact message but it clearly says the driver is not available.
After boot up everything works when the driver should be available. I changed the configuration so that the default ntfs module is used (which provides read-only access) and it worked. I don't have access to my PC now, but adding the ntfs-3g driver to the initial ramdisk should solve the problem, right? Thanks, Nima On Thu, Jun 25, 2009 at 8:26 AM, Johannes Wiedersich < johan...@physik.blm.tu-muenchen.de> wrote: > Nima Azarbayjany wrote: > > I have been trying to use the disk-manager utility to mount my NTFS > > partition on /dev/sda1. The utility successfully identifies the > partition > > and has added the following line to my fstab: > > > > /dev/sda1 /media/sda1 ntfs-3g defaults,locale=en_US.UTF-8 0 > 0 > > > > The partition is not automatically mounted during boot up. I am really > > confused. Can anyone tell what should I do? I have installed the > ntfs-3g > > package. The partition successfully mounts using the utility itself or > the > > mount command in terminal. Should it not mount automatically at startup > > when it has been added to fstab? > > Maybe the kernel tries to mount the partition at a stage when the > required modules are not yet available. > > Does 'mount -a' (as root) work after bootup? > > Johannes > >
