Page 2 of 2 FirstFirst 12
Results 11 to 19 of 19

Thread: rsync failing on TUMBLEWEED on USB attached drive.

  1. #11
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,136

    Default Re: rsync failing on TUMBLEWEED on USB attached drive.

    Quote Originally Posted by FlameBait View Post
    /dev/sdb1 is the USB Drive

    Code:
    flamebait@flamebait:/run/media/flamebait/BACKUP> df -h
    Filesystem               Size  Used Avail Use% Mounted on
    devtmpfs                 5.9G     0  5.9G   0% /dev
    tmpfs                    5.9G   29M  5.9G   1% /dev/shm
    tmpfs                    5.9G  2.5M  5.9G   1% /run
    tmpfs                    5.9G     0  5.9G   0% /sys/fs/cgroup
    /dev/sda2                 20G  9.0G   10G  48% /
    /dev/sda3                436G  163G  251G  40% /home
    192.168.1.9:/nfs          50M  6.2M   44M  13% /nfs
    192.168.1.9:/nfs/Movies  3.6T  2.5T  1.2T  70% /nfs/Movies
    tmpfs                    1.2G   28K  1.2G   1% /run/user/1000
    /dev/sdb1                932G  356G  576G  39% /run/media/flamebait/BACKUP



    Perfect!. It is not that it must be with a CLI command. Your GUI screen copy is of course also right (when it would be vissible to non Google lovers ). Even you telling what you did to find that out makes what you say trustworthy. But copy/paste from the CLI is of course always the easiest thing to tell people here the message. Not much comment needed then.
    Henk van Velden

  2. #12
    Join Date
    Jan 2009
    Location
    Taft, Republic of California. UTC -8
    Posts
    1,474

    Default Re: rsync failing on TUMBLEWEED on USB attached drive.

    Quote Originally Posted by hcvv View Post
    Perfect!. It is not that it must be with a CLI command. Your GUI screen copy is of course also right (when it would be vissible to non Google lovers ). Even you telling what you did to find that out makes what you say trustworthy. But copy/paste from the CLI is of course always the easiest thing to tell people here the message. Not much comment needed then.
    As you can see I'm not out of space.
    The rsync command that always has worked for years across several USB drives I've used for backup is not working.

    Something in TUMBLEWEED recently changed to make it not work.
    You can see two of my NFS mount points /nsf/Picture and /nsf/Music unmounted by some process too. That's why they didn't show up with this command. /nfs/Movies would be unmounted by this process too but it's open in Dolphin. /nfs/ never gets unmounted by this process whatever it is that's creeped into TUMBLEWEED. That's a "new" thing as of several weeks.

    How can I back up my /home? Now rsync no longer works?
    Tumbleweed

  3. #13
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,617
    Blog Entries
    3

    Default Re: rsync failing on TUMBLEWEED on USB attached drive.

    Quote Originally Posted by FlameBait View Post
    His is a picture. of the information I took with spectacle. I cropped it so It's just that popup.
    https://drive.google.com/open?id=0B2...GQ0bGxMT05xTkU
    That link took me to a google login page. I declined to login.

    Okay, I copied the link, then used it in a different browser where I am logged in to google. I could see it there. As hcvv says, google drive is not a good place for sharing images.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  4. #14
    Join Date
    Jan 2009
    Location
    Taft, Republic of California. UTC -8
    Posts
    1,474

    Default Re: rsync failing on TUMBLEWEED on USB attached drive.

    Quote Originally Posted by nrickert View Post
    That link took me to a google login page. I declined to login.

    Okay, I copied the link, then used it in a different browser where I am logged in to google. I could see it there. As hcvv says, google drive is not a good place for sharing images.
    Yes.. I don't have anywhere else to host it though
    The CLI command was used and the output is in the thread.
    Tumbleweed

  5. #15
    Join Date
    Jul 2008
    Location
    Sweden
    Posts
    174

    Default Re: rsync failing on TUMBLEWEED on USB attached drive.

    Any interesting information if run dmesg in terminal?
    With my system, using uas on USB3 I got some errors there
    Code:
    [Sep16 23:07] sd 8:0:0:0: [sdb] uas_eh_abort_handler ffff88042e5fd500 tag 0, inflight: CMD[  +3.002595] scsi host8: uas_eh_task_mgmt: ABORT TASK timed out
    [  +0.000065] sd 8:0:0:0: uas_eh_device_reset_handler
    [  +0.000008] scsi host8: uas_eh_task_mgmt: LOGICAL UNIT RESET: error already running a task
    [  +0.000006] scsi host8: uas_eh_bus_reset_handler start
    [  +0.000055] usb 4-3.1.1: stat urb: killed, stream 2
    [  +0.000053] sd 8:0:0:0: [sdb] uas_zap_dead ffff88042e5fd500 tag 0, inflight: CMD abort
    [  +0.000004] sd 8:0:0:0: [sdb] abort completed
    [  +0.063188] usb 4-3.1.1: reset SuperSpeed USB device number 4 using xhci_hcd
    [  +0.011111] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880435de9c00
    [  +0.000012] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880435de9c48
    [  +0.000004] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880435de9c90
    [  +0.000004] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880435de9cd8
    ASUS G46VW running openSUSE LEAP 42.1, Windows 8
    Samsung NP300V3A running openSUSE LEAP 42.1 Windows 7
    Some EEEPC running openSUSE LEAP 42.1, "Server" running sshfs, (mini)DLNA, NFS
    Raspberry Pi, Weezy, openSUSE 13.1 (two different SD-cards)

  6. #16
    Join Date
    Jan 2009
    Location
    Taft, Republic of California. UTC -8
    Posts
    1,474

    Default Re: rsync failing on TUMBLEWEED on USB attached drive.

    Quote Originally Posted by quinness View Post
    Any interesting information if run dmesg in terminal?
    With my system, using uas on USB3 I got some errors there
    Code:
    [Sep16 23:07] sd 8:0:0:0: [sdb] uas_eh_abort_handler ffff88042e5fd500 tag 0, inflight: CMD[  +3.002595] scsi host8: uas_eh_task_mgmt: ABORT TASK timed out
    [  +0.000065] sd 8:0:0:0: uas_eh_device_reset_handler
    [  +0.000008] scsi host8: uas_eh_task_mgmt: LOGICAL UNIT RESET: error already running a task
    [  +0.000006] scsi host8: uas_eh_bus_reset_handler start
    [  +0.000055] usb 4-3.1.1: stat urb: killed, stream 2
    [  +0.000053] sd 8:0:0:0: [sdb] uas_zap_dead ffff88042e5fd500 tag 0, inflight: CMD abort
    [  +0.000004] sd 8:0:0:0: [sdb] abort completed
    [  +0.063188] usb 4-3.1.1: reset SuperSpeed USB device number 4 using xhci_hcd
    [  +0.011111] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880435de9c00
    [  +0.000012] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880435de9c48
    [  +0.000004] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880435de9c90
    [  +0.000004] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880435de9cd8
    I don't know what dmesg is.
    Here is the output from what I googled that seemed to apply.
    It's a wall of text.
    Code:
    [158402.027410] usb 9-2: new SuperSpeed USB device number 3 using xhci_hcd
    [158402.042878] usb 9-2: New USB device found, idVendor=0bc2, idProduct=a003
    [158402.042882] usb 9-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [158402.042885] usb 9-2: Product: Backup+ BK
    [158402.042887] usb 9-2: Manufacturer: Seagate  
    [158402.042889] usb 9-2: SerialNumber: NA5CR1K0
    [158402.044885] usb 9-2: USB controller 0000:30:00.0 does not support streams, which are required by the UAS driver.
    [158402.044888] usb 9-2: Please try an other USB controller if you wish to use UAS.
    [158402.044891] usb-storage 9-2:1.0: USB Mass Storage device detected
    [158402.045010] usb-storage 9-2:1.0: Quirks match for vid 0bc2 pid a003: 2000000
    [158402.045029] scsi host11: usb-storage 9-2:1.0
    [161972.920061] usb 3-1: USB disconnect, device number 46
    [161973.148045] usb 3-2: USB disconnect, device number 47
    [162186.416014] usb 3-1: new low-speed USB device number 48 using uhci_hcd
    [162186.593683] usb 3-1: New USB device found, idVendor=046d, idProduct=c326
    [162186.593688] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    


    Tjis is what I get when AI have to do a CTRL-C because rsync stalls out.
    [/code]

    flamebait/.cache/google-chrome/Default/Cache/f_0b629a
    ^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(636) [sender=3.1.2]
    rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.xsession-errors-:0.The3ev" failed: Invalid argument (22)
    rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.15:46.png.PT1erw" failed: Invalid argument (22)
    rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.3:.jpg.cxzUTM" failed: Invalid argument (22)
    rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.WTF?.jpg.zpXt8L" failed: Invalid argument (22)
    rsync: mkstemp "/run/media/flamebait/BACKUP/flamebait/flamebait/.flash.asp?id=84712.eectme" failed: Invalid argument (22)
    rsync: rename "/run/media/flamebait/BACKUP/flamebait/flamebait/.cache/google-chrome/Default/Cache/.f_0988e9.LpcGQQ" -> "flamebait/.cache/google-chrome/Default/Cache/f_0988e9": No space left on device (28)
    rsync: rename "/run/media/flamebait/BACKUP/flamebait/flamebait/.cache/google-chrome/Default/Cache/.f_0a1f24.f3ol5Y" -> "flamebait/.cache/google-chrome/Default/Cache/f_0a1f24": No space left on device (28)
    rsync: rename "/run/media/flamebait/BACKUP/flamebait/flamebait/.cache/google-chrome/Default/Cache/.f_0a1f27.vuker7" -> "flamebait/.cache/google-chrome/Default/Cache/f_0a1f27": No space left on device (28)
    rsync: rename "/run/media/flamebait/BACKUP/flamebait/flamebait/.cache/google-chrome/Default/Cache/.f_0a1f29.zAUrUf" -> "flamebait/.cache/google-chrome/Default/Cache/f_0a1f29": No space left on device (28)
    [/code]

    Code:
    [156728.143401] usb 9-2: new SuperSpeed USB device number 2 using xhci_hcd
    [156728.158871] usb 9-2: New USB device found, idVendor=0bc2, idProduct=a003
    [156728.158875] usb 9-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [156728.158877] usb 9-2: Product: Backup+ BK
    [156728.158880] usb 9-2: Manufacturer: Seagate  
    [156728.158882] usb 9-2: SerialNumber: NA5CR1K0
    [156728.160184] usb 9-2: USB controller 0000:30:00.0 does not support streams, which are required by the UAS driver.
    [156728.160187] usb 9-2: Please try an other USB controller if you wish to use UAS.
    [156728.160190] usb-storage 9-2:1.0: USB Mass Storage device detected
    [156728.161377] usb-storage 9-2:1.0: Quirks match for vid 0bc2 pid a003: 2000000
    [156728.161398] scsi host10: usb-storage 9-2:1.0
    [158284.744071] usb 9-2: USB disconnect, device number 2
    [158402.027410] usb 9-2: new SuperSpeed USB device number 3 using xhci_hcd
    [158402.042878] usb 9-2: New USB device found, idVendor=0bc2, idProduct=a003
    [158402.042882] usb 9-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [158402.042885] usb 9-2: Product: Backup+ BK
    [158402.042887] usb 9-2: Manufacturer: Seagate  
    [158402.042889] usb 9-2: SerialNumber: NA5CR1K0
    [158402.044885] usb 9-2: USB controller 0000:30:00.0 does not support streams, which are required by the UAS driver.
    [158402.044888] usb 9-2: Please try an other USB controller if you wish to use UAS.
    [158402.044891] usb-storage 9-2:1.0: USB Mass Storage device detected
    [158402.045010] usb-storage 9-2:1.0: Quirks match for vid 0bc2 pid a003: 2000000
    [158402.045029] scsi host11: usb-storage 9-2:1.0
    [161972.920061] usb 3-1: USB disconnect, device number 46
    [161973.148045] usb 3-2: USB disconnect, device number 47
    [162186.416014] usb 3-1: new low-speed USB device number 48 using uhci_hcd
    [162186.593683] usb 3-1: New USB device found, idVendor=046d, idProduct=c326
    [162186.593688] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    


    All I know is it worked before and doesn't now.
    I really need to back up my /home.
    Tumbleweed

  7. #17
    Join Date
    Jan 2009
    Location
    Taft, Republic of California. UTC -8
    Posts
    1,474

    Default Re: rsync failing on TUMBLEWEED on USB attached drive.

    I just think I found my problem.
    That Seagate drive is failing.

    I just took a HGST TOURO Mobile USB 3 hard drive out of its blister pack and set it up to use as a back up drive.
    It's having no problems and not stalling out.
    I should have known better than to trust a Seagate

    I think I found the source of my problem

    Code:
    rsync -av /home/flamebait /run/media/flamebait/'TOURO Mobile'/Flamebait/
    


    Seems to work just fine
    Tumbleweed

  8. #18
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,617
    Blog Entries
    3

    Default Re: rsync failing on TUMBLEWEED on USB attached drive.

    Quote Originally Posted by FlameBait View Post
    Here is the output from what I googled that seemed to apply.
    It's a wall of text.
    That what I was concerned about in my first comment in this thread.

    You have hardware issues. I've seen the same with one of my external drives. I filed bug 891168 about it.

    It turned out to be a cabling problem.

    All I know is it worked before and doesn't now.
    I really need to back up my /home.
    The newer kernels or newer "udev" seem to be more sensitive to intermittent errors.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  9. #19
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    25,136

    Default Re: rsync failing on TUMBLEWEED on USB attached drive.

    Congratulations you found it.
    Henk van Velden

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •