• 6.6.6 - USB UD Drives disappear and can't be remounted


    DZMM
    • Closed

    I'm posting here even though this might be something for @dlandon and the Unassigned devices plugin.  I'm pretty sure though it's 6.6.6 related as the problem only started when I upgraded.

     

    I have had 2 HDDs connected via USB as UDs for about 3 months with no problems at all, but yesterday after upgrading from 6.6.3 to 6.6.6 the devices disappeared from the GUI view on the Main tab, and only after power cycling a few times was I able to get them to reappear - however I couldn't get them to remount.

     

    I then rebooted and the drives auto-mounted again ok, but after a few hours the same thing happened again, and I again can't get them to remount after power cycling to get them to reappear.  I captured diagnostics this time.

     

    This is a big issue for me as I have apps and VMs that need constant access.  I have a nvme drive also mounted and this is fine, so whatever the problem is it only seems to affect my USB drives (2x500GB SSD drives in a BTRFS pool)

    highlander-diagnostics-20181209-0908.zip




    User Feedback

    Recommended Comments

    It looks like your disk(s) have a lot of btrfs errors:

    Dec  9 01:50:08 Highlander kernel: BTRFS info (device sda1): forced readonly
    Dec  9 01:50:08 Highlander kernel: BTRFS: error (device sda1) in btrfs_finish_ordered_io:3074: errno=-5 IO failure
    Dec  9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14581760
    Dec  9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14585856
    Dec  9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14577664
    Dec  9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14594048
    Dec  9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14577664
    Dec  9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14598144
    Dec  9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14581760
    Dec  9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14602240
    Dec  9 01:50:08 Highlander kernel: BTRFS info (device sda1): no csum found for inode 4647604 start 14581760
    Dec  9 01:50:08 Highlander kernel: BTRFS: error (device sda1) in btrfs_finish_ordered_io:3074: errno=-5 IO failure
    Dec  9 01:50:08 Highlander unassigned.devices: benchmark: shell_exec(/usr/sbin/hdparm -C /dev/sda 2>/dev/null | /bin/grep -c standby) took 106.512354s.
    Dec  9 01:50:08 Highlander kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
    Dec  9 01:50:08 Highlander kernel: sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
    Dec  9 01:50:08 Highlander kernel: BTRFS: error (device sda1) in btrfs_run_delayed_refs:3058: errno=-5 IO failure
    Dec  9 01:50:08 Highlander kernel: BTRFS error (device sda1): pending csums is 21020672
    Dec  9 01:50:08 Highlander kernel: usb 3-1: new high-speed USB device number 3 using xhci_hcd
    Dec  9 01:50:13 Highlander kernel: btrfs_dev_stat_print_on_error: 12786 callbacks suppressed
    Dec  9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sdb1 errs: wr 10555024, rd 11332069, flush 304, corrupt 81, gen 1
    Dec  9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 1, rd 7704, flush 0, corrupt 0, gen 0
    Dec  9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sdb1 errs: wr 10555025, rd 11332069, flush 304, corrupt 81, gen 1
    Dec  9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 2, rd 7704, flush 0, corrupt 0, gen 0
    Dec  9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sdb1 errs: wr 10555025, rd 11332070, flush 304, corrupt 81, gen 1
    Dec  9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 2, rd 7705, flush 0, corrupt 0, gen 0
    Dec  9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sdb1 errs: wr 10555025, rd 11332071, flush 304, corrupt 81, gen 1
    Dec  9 01:50:13 Highlander kernel: BTRFS error (device sda1): bdev /dev/sda1 errs: wr 2, rd 7706, flush 0, corrupt 0, gen 0

    I can't make any sense of your log with regards to UD, but it appears you have disks with a lot of errors.  If the SSD (sda) is on a USB port, you may have port or cable problem.

    Link to comment

    Please change the status to closed.  It is not an urgent issue, even though you feel that you need an immediate answer.  LT places a lot of importance on urgent issues and an urgent status for this issue is not warranted.

    Link to comment
    8 hours ago, DZMM said:

    Done

    I'm not seing the repost on the UD thread, so will comment here.

     

    Dec  8 09:08:12 Highlander kernel: BTRFS info (device sda1): bdev /dev/sdb1 errs: wr 10554074, rd 11326465, flush 304, corrupt 81, gen 1

    Device sdb on this pool dropped out at some point in the past, run a scrub but IMO bad idea to use a pool of USB devices, USB is very prone to disconnects and generally bad at reporting and handling errors.

    Link to comment
    32 minutes ago, johnnie.black said:

    I'm not seing the repost on the UD thread, so will comment here.

     

    
    Dec  8 09:08:12 Highlander kernel: BTRFS info (device sda1): bdev /dev/sdb1 errs: wr 10554074, rd 11326465, flush 304, corrupt 81, gen 1

    Device sdb on this pool dropped out at some point in the past, run a scrub but IMO bad idea to use a pool of USB devices, USB is very prone to disconnects and generally bad at reporting and handling errors.

    yeah, when it works it great but even 3 problems in 4 months is too much.  I've decided to just get a bigger nvme drive so I can ditch the small 2x500GBs.  Luckily I can return one of the SSDs and the other I'll probably just put on eBay together with my old SM961

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.