Public bug reported: I've connected SATA HDD (old SeaGate ST9100824AS) throught USB<->SATA dongle to my Linux machine. It appears that HDD in question got it's spindle stuck. And the dmesg started filling with following:
[1811376.769217] INFO: task umount:30901 blocked for more than 120 seconds. [1811376.769229] Tainted: G W OE 4.10.0-37-generic #41~16.04.1-Ubuntu [1811376.769232] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [1811376.769236] umount D 0 30901 14256 0x00000000 [1811376.769241] Call Trace: [1811376.769255] __schedule+0x232/0x700 [1811376.769263] ? blk_delay_queue+0x3d/0x50 [1811376.769267] schedule+0x36/0x80 [1811376.769272] schedule_timeout+0x235/0x3f0 [1811376.769276] ? __blk_run_queue+0x33/0x40 [1811376.769283] ? blk_queue_bio+0x3fa/0x410 [1811376.769290] ? ktime_get+0x3c/0xb0 [1811376.769294] io_schedule_timeout+0xa4/0x110 [1811376.769298] wait_for_completion_io+0xb4/0x140 [1811376.769302] ? wake_up_q+0x70/0x70 [1811376.769305] submit_bio_wait+0x68/0x90 [1811376.769310] blkdev_issue_flush+0x5f/0x90 [1811376.769316] ext4_sync_fs+0x152/0x1e0 [1811376.769322] __sync_filesystem+0x30/0x50 [1811376.769325] sync_filesystem+0x3c/0x60 [1811376.769331] generic_shutdown_super+0x27/0x100 [1811376.769335] kill_block_super+0x2c/0xa0 [1811376.769340] deactivate_locked_super+0x43/0x70 [1811376.769344] deactivate_super+0x5c/0x60 [1811376.769351] cleanup_mnt+0x3f/0x90 [1811376.769356] __cleanup_mnt+0x12/0x20 [1811376.769363] task_work_run+0x7e/0xa0 [1811376.769369] exit_to_usermode_loop+0xaa/0xb0 [1811376.769374] syscall_return_slowpath+0x59/0x60 [1811376.769379] entry_SYSCALL_64_fastpath+0xab/0xad [1811376.769383] RIP: 0033:0x7fcb97c4a447 [1811376.769385] RSP: 002b:00007ffccd08bd68 EFLAGS: 00000202 ORIG_RAX: 00000000000000a6 [1811376.769389] RAX: 0000000000000000 RBX: 000000000068df70 RCX: 00007fcb97c4a447 [1811376.769391] RDX: 0000000000000000 RSI: 0000000000000002 RDI: 000000000068e150 [1811376.769393] RBP: 000000000068e150 R08: 0061663464613830 R09: 3563333866376431 [1811376.769395] R10: 0000000000000751 R11: 0000000000000202 R12: 00007fcb9815383c [1811376.769397] R13: 0000000000000002 R14: 0000000000696b50 R15: 00007ffccd08bff8 Funny part is, that I was unable to hook another healthy HDD to any spare USB slots, it just kept spewing Call Trace I've already mentioned. Well, restarting the machine "solved" the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Nov 14 12:10:43 2017 InstallationDate: Installed on 2017-08-16 (90 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732145 Title: Unable to connect another external HDD after the one with stuck spindle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1732145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs