it is going very slowly though for some of the files. On Sat, Apr 29, 2017 at 8:37 AM, Michael <bmi...@gmail.com> wrote:
> well.... I format the drive and things are transferring now. > > On Fri, Apr 28, 2017 at 8:15 PM, Michael <bmi...@gmail.com> wrote: > >> I think I fried it in my glove compartment. >> >> On Fri, Apr 28, 2017 at 8:14 PM, Michael <bmi...@gmail.com> wrote: >> >>> $ sudo fsck /dev/sdd >>> [sudo] password for bmike1: >>> fsck from util-linux 2.20.1 >>> e2fsck 1.42.9 (4-Feb-2014) >>> fsck.ext2: No medium found while trying to open /dev/sdd >>> >>> The superblock could not be read or does not describe a valid >>> ext2/ext3/ext4 >>> filesystem. If the device is valid and it really contains an >>> ext2/ext3/ext4 >>> filesystem (and not swap or ufs or something else), then the superblock >>> is corrupt, and you might try running e2fsck with an alternate >>> superblock: >>> e2fsck -b 8193 <device> >>> or >>> e2fsck -b 32768 <device> >>> <mount device> >>> bmike1@MikesBeast ~ $ sudo fsck /dev/sdd >>> fsck from util-linux 2.20.1 >>> e2fsck 1.42.9 (4-Feb-2014) >>> /dev/sdd is in use. >>> e2fsck: Cannot continue, aborting. >>> >>> >>> On Fri, Apr 28, 2017 at 7:50 PM, Michael <bmi...@gmail.com> wrote: >>> >>>> $ sudo fsck /media/bmike1/GORILLA64 >>>> [sudo] password for bmike1: >>>> fsck from util-linux 2.20.1 >>>> e2fsck 1.42.9 (4-Feb-2014) >>>> fsck.ext2: Is a directory while trying to open /media/bmike1/GORILLA64 >>>> >>>> The superblock could not be read or does not describe a valid >>>> ext2/ext3/ext4 >>>> filesystem. If the device is valid and it really contains an >>>> ext2/ext3/ext4 >>>> filesystem (and not swap or ufs or something else), then the superblock >>>> is corrupt, and you might try running e2fsck with an alternate >>>> superblock: >>>> e2fsck -b 8193 <device> >>>> or >>>> e2fsck -b 32768 <device> >>>> $ sudo fsck /dev/sdd1 >>>> fsck from util-linux 2.20.1 >>>> fsck.fat 3.0.26 (2014-03-07) >>>> 0x41: Dirty bit is set. Fs was not properly unmounted and some data may >>>> be corrupt. >>>> 1) Remove dirty bit >>>> 2) No action >>>> ? ^C >>>> <unmount device> >>>> bmike1@MikesBeast ~ $ sudo fsck /dev/sdd1 >>>> fsck from util-linux 2.20.1 >>>> e2fsck 1.42.9 (4-Feb-2014) >>>> fsck.ext2: No such file or directory while trying to open /dev/sdd1 >>>> Possibly non-existent device? >>>> >>>> >>>> On Fri, Apr 28, 2017 at 7:43 PM, Carruth, Rusty < >>>> rusty.carr...@smartm.com> wrote: >>>> >>>>> What does fsck say? >>>>> >>>>> >>>>> >>>>> *From:* PLUG-discuss [mailto:plug-discuss-boun...@lists.phxlinux.org] *On >>>>> Behalf Of *Michael >>>>> *Sent:* Friday, April 28, 2017 4:41 PM >>>>> *To:* PLUG >>>>> *Subject:* Rsync ran like 30-40 minutes >>>>> >>>>> >>>>> >>>>> this is what happened in that time: >>>>> >>>>> >>>>> >>>>> $ rsync -aWuq --delete-before --progress /home/bmike1/Documents >>>>> /media/bmike1/GORILLA64 >>>>> >>>>> ^C >>>>> >>>>> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at >>>>> rsync.c(632) [sender=3.1.0] >>>>> >>>>> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at >>>>> io.c(521) [generator=3.1.0] >>>>> >>>>> $ >>>>> >>>>> I then removed the quiet flag and: >>>>> >>>>> $ rsync -aWu --delete-before --progress /home/bmike1/Documents >>>>> /media/bmike1/GORILLA64 >>>>> >>>>> building file list ... >>>>> >>>>> 63787 files to consider >>>>> >>>>> deleting >>>>> Documents/Business/Photography/PropertyPhotographing/PrivateClients/Alliya >>>>> Maqsood/2016/2016101020/8230 Dames point crossing Blvd #802 Jacksonville >>>>> 32277 >>>>> >>>>> deleting Documents/Programs/darktable-2.0.6/src/common/.profiling.h.Y >>>>> hVpro >>>>> >>>>> Documents/ >>>>> >>>>> <truncate) >>>>> >>>>> hangs at: >>>>> >>>>> Documents/Programs/darktable-2.0.6/src/control/jobs.c >>>>> >>>>> ^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at >>>>> rsync.c(632) [sender=3.1.0] >>>>> >>>>> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at >>>>> io.c(521) [generator=3.1.0] >>>>> >>>>> >>>>> >>>>> So I run again and: >>>>> >>>>> rsync -aWu --delete-before --progress /home/bmike1/Documents >>>>> /media/bmike1/GORILLA64 >>>>> >>>>> building file list ... >>>>> >>>>> 63787 files to consider >>>>> >>>>> rsync: [generator] write error: Broken pipe (32) >>>>> >>>>> ^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at >>>>> rsync.c(632) [sender=3.1.0] >>>>> >>>>> rsync: [sender] write error: Broken pipe (32) >>>>> >>>>> >>>>> >>>>> and again: >>>>> >>>>> $ rsync -aWu --delete-before --progress /home/bmike1/Documents >>>>> /media/bmike1/GORILLA64 >>>>> >>>>> building file list ... >>>>> >>>>> 63787 files to consider >>>>> >>>>> Documents/ >>>>> >>>>> <truncate> >>>>> >>>>> this time it hung at : >>>>> >>>>> Documents/Programs/hugin-2016.2.0/mac/Applications.xcodeproj >>>>> /project.pbxproj >>>>> >>>>> 32,768 15% 0.00kB/s 0:00:00 ^X^C >>>>> >>>>> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at >>>>> rsync.c(632) [sender=3.1.0] >>>>> >>>>> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at >>>>> io.c(521) [generator=3.1.0] >>>>> >>>>> >>>>> >>>>> I'm thinking this flash drive got fried in the glove compartment of my >>>>> car. What do you think? >>>>> >>>>> -- >>>>> >>>>> :-)~MIKE~(-: >>>>> >>>>> --------------------------------------------------- >>>>> 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 >>>>> >>>> >>>> >>>> >>>> -- >>>> :-)~MIKE~(-: >>>> >>> >>> >>> >>> -- >>> :-)~MIKE~(-: >>> >> >> >> >> -- >> :-)~MIKE~(-: >> > > > > -- > :-)~MIKE~(-: > -- :-)~MIKE~(-:
--------------------------------------------------- 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
