Slax Problem: Read-only hard drives
Dan
hard drives (because Windows OS stopped working). Unfortunately all the
drives mounted as read-only. When I tried applying write permissions
through the GUI, the operation timed out (right click on drive >
Properties). I have two drives connected through IDE and a USB drive as
well. For some reason, I can write to the parent directory of one of
the drive's but not to any subfolders.
Any ideas on why I can't apply write permissions?
TIA for any help,
Dan
Joe
You would need to remount the drives read/write:
sudo mount -o rw,remount /mount-path
If a drive is mounted r/o, you can't change permissions on individual
folders.
-Joe
Dan
> sudo mount -o rw,remount /mount-path
> If a drive is mounted r/o, you can't change permissions on individual
> folders.
>
> -Joe
Thanks Joe,
I'll try this tonight. Could the fact that the drives mounted as
read-only by default indicate a problem, or is this typical? I'm new to
Linux.
-Dan
Kees Theunissen
Hmm. ... ran Slax LiveCD ... transfer files ... because Windows OS
stopped working.
Does this mean you want to write to a windows disk?
If so I hope it's not a ntfs filesystem.
Below is a quote from the kernel documentation
(/usr/src/linux-2.4.31/Documentation/filesystems/ntfs.txt).
NTFS Overview
=============
Legato Systems, Inc. (http://www.legato.com) have sponsored Anton
Altaparmakov to develop NTFS on Linux since June 2001.
To mount an NTFS volume, use the filesystem type 'ntfs'. The driver
currently works only in read-only mode, with no fault-tolerance
supported.
If you enable the dangerous(!) write support, make sure you can
recover from a complete loss of data. Also, download the Linux-NTFS
project distribution from Sourceforge at
http://sourceforge.net/projects/linux-ntfs/
and always run the included ntfsfix utility after performing a write
to an NTFS partition from Linux to fix some of the damage done by
the Linux NTFS driver and to schedule an automatic chkdsk when
Windows reboots. You should run ntfsfix _after_ unmounting the
partition in Linux but _before_ rebooting into Windows. During the
next reboot into Windows, chkdsk will be run automatically fixing
the remaining damage. If no errors are found it is a good indication
that the driver + ntfsfix together worked to full satisfaction. (-;
Please note that the experimental write support is limited to
Windows NT4 and earlier versions at the moment.
[ ... ]
Regards,
Kees.
--
Kees Theunissen.
Dan
> Dan wrote:
> > I ran Slax LiveCD off of a CD so that I could transfer files between
> > hard drives (because Windows OS stopped working).
> > Any ideas on why I can't apply write permissions?
>
> Hmm. ... ran Slax LiveCD ... transfer files ... because Windows OS
> stopped working.
>
> Does this mean you want to write to a windows disk?
> If so I hope it's not a ntfs filesystem.
Wow, thanks for pointing this out Kees. Yes I do believe the internal
drives are formatted NTFS so I guess this is failsafe feature of Slax.
But I doubt the USB external drive is NTFS, so this still doesn't
explain why that one is mounting as read-only by default.
-Dan
Joe
What kernel? In the 2.4 kernels, writing to NTFS was *very* dangerous.
I looked at the code at some point, and found that it forced read-only,
no matter what.
The 2.6 kernels have different ntfs code, that actually is supposed to
be safe wrt to writing. Not all writes are supported, I think only
appends are possible (I still mount my ntfs partitions read-only on my
dual-boot laptop, though...)
-Joe
Eef Hartman
> But I doubt the USB external drive is NTFS, so this still doesn't
> explain why that one is mounting as read-only by default.
Vfat type partitions (which most USB memory sticks etc. will still use)
don't have the concept of "file owner", so the owner OF the files
(and - by default - the only user that can write TO the disk) is
normally the mounter, which means if you mount it as root, you MUST
change the default permissions (see the "?mask" options in the man page
for "mount" in the vfat section).
To access a vfat partition for "everyone" you either need "umask=0"
(everything is allowed) or better "fmask=0111" and "dmask=0" (only
directories normally need "execute" permissions).
The default is "umask=077" when mounted at bootup (in rc.S), as no
default umask has been set.
--
********************************************************************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M....@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
********************************************************************
notbob
>
> To access a vfat partition for "everyone" you either need "umask=0"
I use a this for a small secondary HDD that was originally formated as
vfat:
/dev/hdd1 /mnt/hd vfat defaults,umask=022 1 0
This allows no one except root to change it, but allows everyone to
copy files from it as their own 755 file. It also allows my creaky
ol' w98 box, via samba, to access and even map to it. Very handy.
nb