Re: [Hampshire] Mass storage mounting as read only?

Top Page

Reply to this message
Author: AdamC
Date:  
To: Hampshire LUG Discussion List
Subject: Re: [Hampshire] Mass storage mounting as read only?
2008/9/18 Hugo Mills <hugo@???>:
> On Thu, Sep 18, 2008 at 05:56:30PM +0100, AdamC wrote:
>> I have a Iriver h320 which basically works as a mass storage device
>> under Linux (vfat filesystem). Everything worked fine, until I tried
>> to sync files from my laptop to the H320 using rsync. That said, I'm
>> not sure that rsync is the definite culprit here.
>>
>> When I plug the device in to my Ubuntu 8.04 laptop, it automounts
>> under /media/H300 but as read only.
>>
>> mount gives:
>> /dev/sdb1 on /media/H300 type vfat
>> (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)
>>
>> Is there anything here which means that the device is mount as
>> read-only?
>
> No, nothing in there. You may possibly get better information from
> "cat /proc/mounts", which is the raw data from the kernel. The command
> "mount" uses slightly cooked data, and is occasionally wrong under
> some circumstances (unlikely here, but...).
>
> It is possible that the device has a media error on it, and has
> been remounted read-only -- check your system log file
> (/var/log/syslog) to see if that's the case.
>
> Are you sure that the uid/umask are correct? Check the permissions
> on the filesystem, using ls -l.
>
> Finally, are you trying to copy a device node to it, perhaps? That
> would complain in much the same way, IIRC, as it's mounted with
> "nodev" option.
>
> Just a few thoughts,
> Hugo.


Many thanks Hugo - your suggestion fixed it - it turns out /media/H300
itself had insufficient permissions - a quick sudo chmod -R o+rw fixed
it.

Thanks once again.
Adam
--
You back your data up on the same planet?
http://www.monkeez.org
PGP key: 0x7111B833