Oh HO! I figured it out. I removed the drive w/o umount first. I just did
it again and figured it out. How do I fix that?
:-)~MIKE~(-:
On Thu, Jul 11, 2013 at 4:54 PM, Michael Havens <
bmike1@gmail.com> wrote:
> Well.... I restarted the machine and then tried again. I was sble to
> create /bmike1 in /mnt/backup. then chown. and rsync is in process now.
> What follows is what I did prior to the restart. Why do you think it
> needed the microsoft fix?
>
> I think I figured it out; the thumb drive is mounted twice.
>
> nope... that wasn't the problem:
>
> bmike1@PresarioLapTop1:/mnt/backup$ mkdir bmike1
> mkdir: cannot create directory `bmike1': Read-only file system
>
> then Iried it with sudo... same result.
>
> bmike1@PresarioLapTop1:/mnt/backup$ mount | grep backup
> /dev/sdb on /mnt/backup type ext3 (rw,noexec,nosuid,nodev,noatime)
>
> bmike1@PresarioLapTop1:/mnt/backup$ mount|grep back
> /dev/sdb on /mnt/backup type ext3 (rw,noexec,nosuid,nodev,noatime)
> bmike1@PresarioLapTop1:/mnt/backup$ ls -l
> ls: reading directory .: Input/output error
> total 0
>
>
> :-)~MIKE~(-:
>
>
> On Thu, Jul 11, 2013 at 3:11 PM, Matt Graham <danceswithcrows@usa.net>wrote:
>
>> From: Michael Havens
>> > Is my USB drive dead?
>> > bmike1@PresarioLapTop1:~/Desktop$ ./Backup\ bmike1
>> > rsync: mkdir "/mnt/backup/bmike1" failed: Read-only file system (30)
>> > bmike1@PresarioLapTop1:~/Desktop$ dmesg | tail -n 30
>> > [74384.693378] type=1701 audit(1373570392.790:842): auid=4294967295
>> > uid=1000 gid=1000 ses=4294967295 pid=7116 comm="chromium-browse"
>> > reason="seccomp" sig=0 syscall=33 compat=0 ip=0xb63eb424 code=0x50000
>> [snip a lot of very similar lines]
>>
>> Whatever this is, it's completely useless. It *might* be better to do ""mount
>> | grep backup" and look at that for something that's vaguely
>>
>> disk-related. In the long term, it'd probably be a good idea to find out
>> what's dumping this to the kernel log buffer and tell it to stop doing
>> that.
>>
>> However, the timestamps on the first and last messages differ by 3084
>> seconds.
>> Provided you tried to do something to /mnt/backup , then ran dmesg fairly
>> soon after that (< 3084 seconds), then there are no messages in the
>> kernel log
>> buffer about disk problems. This is a good sign (maybe).
>>
>> What's the output from "mount | grep backup"? It should say something
>> like:
>>
>> /dev/sdd on /mnt/backup type ext3 (rw)
>>
>> ...if it says (ro), then for some reason, your distro is doing something
>> dumb.
>> In that case, edit your fstab and change "noauto,users" to
>> "noauto,users,rw".
>> Then umount and remount the disk, and it should work better. You still
>> may
>> have to mkdir /mnt/backup/bmike1 and chown that dir to bmike1, but at
>> least
>> you'd be able to do this if the filesystem's mounted rw.
>>
>> --
>> Matt G / Dances With Crows
>> The Crow202 Blog: http://crow202.org/wordpress/
>> There is no Darkness in Eternity/But only Light too dim for us to see
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>
>
>
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
(text/plain)