Unable to see USB 3.0 harddrive unless connected through USB 2.0

I recently found that I am unable to see my external usb harddrive on my Ubuntu guest VM. However, I am able to view contents on my host windows 10.

Even more peculiar is that this only happens on usb 3.0. With usb 2.0, I am able to view the external harddrive on Ubuntu guest VM.

I can confirm with a different external harddrive on usb 3.0 that I can see the disk and mount it.

I have tried running chkdsk while mounted on Windows, there were no errors reported or any issues to fix.

I have tried using different cables, Ubuntu VM still can’t see the harddrive.

While using usb 3.0:

from /var/log/kern.log:

Sep 17 21:11:58 presto kernel: [54287.057835] usb 4-1: new SuperSpeed Gen 1 USB device number 18 using xhci_hcd Sep 17 21:11:58 presto kernel: [54287.082809] usb 4-1: New USB device found, idVendor=0bc2, idProduct=ab26, bcdDevice= 1.07 Sep 17 21:11:58 presto kernel: [54287.082813] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 17 21:11:58 presto kernel: [54287.082815] usb 4-1: Product: BUP Slim BK Sep 17 21:11:58 presto kernel: [54287.082816] usb 4-1: Manufacturer: Seagate Sep 17 21:11:58 presto kernel: [54287.082817] usb 4-1: SerialNumber: NA7Y6BTV Sep 17 21:11:58 presto kernel: [54287.089866] scsi host33: uas Sep 17 21:11:58 presto kernel: [54287.092329] usb 4-1: stat urb: status -32 Sep 17 21:11:58 presto kernel: [54287.092414] scsi 33:0:0:0: tag#16 data cmplt err -32 uas-tag 1 inflight: CMD  Sep 17 21:11:58 presto kernel: [54287.092418] scsi 33:0:0:0: tag#16 CDB: Inquiry 12 00 00 00 24 00 Sep 17 21:12:18 presto kernel: [54307.810812] scsi 33:0:0:0: tag#16 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD  Sep 17 21:12:18 presto kernel: [54307.810820] scsi 33:0:0:0: tag#16 CDB: Inquiry 12 00 00 00 24 00 Sep 17 21:12:18 presto kernel: [54307.826485] scsi host33: uas_eh_device_reset_handler start Sep 17 21:12:19 presto kernel: [54307.959706] usb 4-1: reset SuperSpeed Gen 1 USB device number 18 using xhci_hcd Sep 17 21:12:19 presto kernel: [54307.990112] scsi host33: uas_eh_device_reset_handler success Sep 17 21:12:19 presto kernel: [54307.992180] usb 4-1: stat urb: status -32 Sep 17 21:12:19 presto kernel: [54307.995345] scsi 33:0:0:0: tag#16 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD  Sep 17 21:12:19 presto kernel: [54307.995349] scsi 33:0:0:0: tag#16 CDB: Test Unit Ready 00 00 00 00 00 00 Sep 17 21:12:19 presto kernel: [54307.995352] scsi host33: uas_eh_device_reset_handler start Sep 17 21:12:19 presto kernel: [54308.232431] usb 4-1: reset SuperSpeed Gen 1 USB device number 18 using xhci_hcd Sep 17 21:12:19 presto kernel: [54308.267987] scsi host33: uas_eh_device_reset_handler success Sep 17 21:12:19 presto kernel: [54308.267991] scsi 33:0:0:0: Device offlined - not ready after error recovery 

lsusb:

$   lsusb Bus 004 Device 017: ID 0bc2:ab26 Seagate RSS LLC  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 003 Device 004: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 003 Device 006: ID 0e0f:0008 VMware, Inc.  Bus 003 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub  

No luck with lsblk or fdisk -l:

$   lsblk | grep -v loop NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT sda      8:0    0    50G  0 disk  └─sda1   8:1    0    50G  0 part / sr0     11:0    1  1024M  0 rom   

While using usb 2.0 from /var/log/kern.log:

Sep 17 21:14:34 presto kernel: [54442.691706] usb 3-4.1: new high-speed USB device number 10 using xhci_hcd Sep 17 21:14:34 presto kernel: [54443.068445] usb 3-4.1: New USB device found, idVendor=0bc2, idProduct=ab26, bcdDevice= 1.07 Sep 17 21:14:34 presto kernel: [54443.068448] usb 3-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Sep 17 21:14:34 presto kernel: [54443.068450] usb 3-4.1: Product: BUP Slim BK Sep 17 21:14:34 presto kernel: [54443.068452] usb 3-4.1: Manufacturer: Seagate Sep 17 21:14:34 presto kernel: [54443.068453] usb 3-4.1: SerialNumber: NA7Y6BTV Sep 17 21:14:34 presto kernel: [54443.073959] scsi host33: uas Sep 17 21:14:34 presto kernel: [54443.076452] scsi 33:0:0:0: Direct-Access     Seagate  BUP Slim BK      0107 PQ: 0 ANSI: 6 Sep 17 21:14:34 presto kernel: [54443.080735] sd 33:0:0:0: Attached scsi generic sg2 type 0 Sep 17 21:14:34 presto kernel: [54443.189103] sd 33:0:0:0: [sdb] 1953525167 512-byte logical blocks: (1.00 TB/932 GiB) Sep 17 21:14:34 presto kernel: [54443.189105] sd 33:0:0:0: [sdb] 4096-byte physical blocks Sep 17 21:14:34 presto kernel: [54443.189899] sd 33:0:0:0: [sdb] Write Protect is off Sep 17 21:14:34 presto kernel: [54443.189901] sd 33:0:0:0: [sdb] Mode Sense: 53 00 00 08 Sep 17 21:14:34 presto kernel: [54443.191431] sd 33:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Sep 17 21:14:34 presto kernel: [54443.192963] sd 33:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes) Sep 17 21:14:34 presto kernel: [54443.209267]  sdb: sdb1 Sep 17 21:14:34 presto kernel: [54443.221130] sd 33:0:0:0: [sdb] Attached SCSI disk 

lsusb:

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 010: ID 0bc2:ab26 Seagate RSS LLC  Bus 003 Device 005: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 003 Device 004: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 003 Device 006: ID 0e0f:0008 VMware, Inc.  Bus 003 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 

lsblk:

$   lsblk | grep -v loop NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT sda      8:0    0    50G  0 disk  └─sda1   8:1    0    50G  0 part / sdb      8:16   0 931.5G  0 disk  └─sdb1   8:17   0 931.5G  0 part /media/kennzors/kennzors01 sr0     11:0    1  1024M  0 rom   

fdisk:

Disk /dev/sdb: 931.5 GiB, 1000204885504 bytes, 1953525167 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x08129a8d  Device     Boot Start        End    Sectors   Size Id Type /dev/sdb1        2048 1953521663 1953519616 931.5G  7 HPFS/NTFS/exFAT 

Any recommendations and pointers to get this working on usb 3.0 would be greatly appreciated!

Mac Harddrive not mounting

I have already read and followed the directions at How to read and write HFS+ journaled external HDD in Ubuntu without access to OS X?

I’m at the point of thinking that something has happened to destroy this harddrive in the three weeks since it was pulled out of the Mac it belonged to, but I feel like I need to check to see if there’s anything else that I might be doing wrong before giving up entirely.

Here’s the output of dmesg:

[ 2848.201938] usb 2-1: Manufacturer: GenesysLogic [ 2848.207932] hub 2-1:1.0: USB hub found [ 2848.213972] hub 2-1:1.0: 4 ports detected [ 2848.245887] usb 4-1.1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd [ 2848.266817] usb 4-1.1: New USB device found, idVendor=4971, idProduct=8017, bcdDevice=81.05 [ 2848.266820] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2848.266823] usb 4-1.1: Product: USB to ATA/ATAPI Bridge [ 2848.266824] usb 4-1.1: Manufacturer: JMicron [ 2848.266826] usb 4-1.1: SerialNumber: 111122223333 [ 2848.271864] scsi host6: uas [ 2848.272400] scsi 6:0:0:0: Direct-Access     Crucial_ CT500MX200SSD1   8105 PQ: 0 ANSI: 6 [ 2848.273410] sd 6:0:0:0: Attached scsi generic sg1 type 0 [ 2848.273471] sd 6:0:0:0: [sdb] Spinning up disk... [ 2849.277808] ...........not responding... [ 2859.518657] sd 6:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 2859.518664] sd 6:0:0:0: [sdb] Sense Key : Hardware Error [current]  [ 2859.518672] sd 6:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81  [ 2859.519160] sd 6:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 2859.519164] sd 6:0:0:0: [sdb] Sense Key : Hardware Error [current]  [ 2859.519170] sd 6:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81  [ 2859.519628] sd 6:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B) [ 2859.519632] sd 6:0:0:0: [sdb] 0-byte physical blocks [ 2859.520097] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled [ 2859.520265] sd 6:0:0:0: [sdb] Asking for cache data failed [ 2859.520274] sd 6:0:0:0: [sdb] Assuming drive cache: write through [ 2859.521294] sd 6:0:0:0: [sdb] Unit Not Ready [ 2859.521299] sd 6:0:0:0: [sdb] Sense Key : Hardware Error [current]  [ 2859.521306] sd 6:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81  [ 2859.521817] sd 6:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 2859.521821] sd 6:0:0:0: [sdb] Sense Key : Hardware Error [current]  [ 2859.521824] sd 6:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81  [ 2859.522207] sd 6:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 2859.522208] sd 6:0:0:0: [sdb] Sense Key : Hardware Error [current]  [ 2859.522211] sd 6:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81  [ 2859.523217] sd 6:0:0:0: [sdb] Attached SCSI disk 

And here is what happens with fsck.hfsplus:

sudo fsck.hfsplus -f /dev/sdb ** /dev/sdb 

What I really need is an image of this disk that I can look at in a virtual machine, so I tried to just go ahead and image the drive even though I can’t see into it. The result was:

sudo dd if=/dev/sdb of=macdrive.iso 0+0 records in 0+0 records out 0 bytes copied, 0.000129238 s, 0.0 kB/s 

Here’s a picture of the hard drive sitting in the USB adapter All I can hope now is that you look at this and say, “Well, of course, dummy! That will NEVER work…” and then tell me how these mac harddrives are special snowflakes that need a different adapter. Is that what’s wrong? Or is there something else that might make this drive readable?

My head is getting sore from banging it against this problem. Thanks for your help!

Internal Harddrive data not appearing

I have an internal 8TB harddrive to save data on and it happened now like 5 times in the last couple of months that suddenly I find the harddrive looks empty although the size is almost full. Not sure what is the problem?

Below is the entry in the /etc/fstab

/dev/sda    /media/8tb/    ext4    defaults    0    1 

Below is the output of sudo fdisk -l

Disk /dev/nvme0n1: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: AF64508D-2EF8-47BA-AF07-DFEBC571653A  Device              Start        End    Sectors   Size Type /dev/nvme0n1p1       2048    1050623    1048576   512M EFI System /dev/nvme0n1p2    1050624 1416884223 1415833600 675,1G Linux filesystem /dev/nvme0n1p3 1416884224 1953523711  536639488 255,9G Linux swap   Disk /dev/sda: 7,3 TiB, 8001563222016 bytes, 15628053168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes 

Below is the output of sudo blkid

/dev/nvme0n1p3: UUID="1d14ca05-c2f6-4e52-b16f-1709c3a28774" TYPE="swap" PARTUUID="644cf9ce-0e5a-4827-9611-df678b14a443" /dev/nvme0n1p1: UUID="6591-97DE" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="b4d38793-7edd-4384-8ddf-17f17f5cca75" /dev/nvme0n1p2: UUID="a388b104-a430-49fc-bbb7-ad0545f0cb4b" TYPE="ext4" PARTUUID="9e8edd3b-7307-403d-b7ca-29fd152d0af6" /dev/nvme0n1: PTUUID="af64508d-2ef8-47ba-af07-dfebc571653a" PTTYPE="gpt" 

And this is screenshot of the disks info:

enter image description here

Debian 9.9 Live usb: ata4.00 error without any harddrive

i have a problem installing (running) Debian9.9 on my system.

First my setup:

ADATA M2 256G - The destination drive WDC Blue 2T - Data disk Samsung EVO 120G - Windows 10 drive  USB SanDisk 16G FAT32 Debian 9.9 Live (created with LiLi USB creator) 

What i tried first

When i boot up the USB stick i got many ata4.00 error spam messages but could install debian 9.9 on the M2 disk. But when i tried to boot after install it ends up with the ata4.00 error spam

ata4.00: exception Emask 0x40 SAct 0x0 SErr 0x80800 act... ata4.00: irq_stat 0x40000001 ata4: SError: { HostInt 10B8B } ata4: exception Emask 0x40 SAct 0x0 SErr 0x80800 act... ata4: irq_stat 0x40000001 ata4: SError: { HostInt 10B8B } ata4: exception Emask 0x40 SAct 0x0 SErr 0x80800 act... ata4: irq_stat 0x40000001 ata4: SError: { HostInt 10B8B } ata4: exception Emask 0x40 SAct 0x0 SErr 0x80800 act... ata4: irq_stat 0x40000001 ata4: SError: { HostInt 10B8B } ata4: EH pending after 5 tries, giving up ata4.00: exception Emask 0x40 SAct 0x0 SErr 0x80800 act... ata4.00: irq_stat 0x40000001 ata4: SError: { HostInt 10B8B } ata4.00 cmd a0/01:00:00:00:01/00:00:00:00:00/a0...         Inquiry 12 01 00 00 ff 00res 51/54:03:00... ata4.00: status: { DRDY ERR  }  

or gets over it and hung up at

[ OK ] Started Update UTMP about System Runlevel Changes 

or it spams

[ OK ] Created slice User Slice of Debian-gdm        Starting User Manager for UID 117... [ OK ] Started Session c166 of user Debian-gdm. #(c is counting up) [ OK ] Started User Manager for UID 117...        Stopping User Manager for UID 117. [ OK ] Stopped User Manager for UID 117... [ OK ] Removed slice User Slice of Debian-gdm. ...  

Short story: It hung up at different stages on each boot but did not get once into the desktop environment (gnome). I thought it might be a hard-drive problem.

What i did to get the problem source

1. Remove other drives

I have removed all drives (and USB) except the M2 but resulted in the same error.

2. Remove all start from USB

My thoughts were that the M2 is broken (wondering why he could install without problems) so i removed it too and tried to start from USB only. But yeha guess what, same error on startup. So only thing it could be is BIOS settings, but i dont have any idea what exactly could solve this.

Windows 10 by the way starts up without problems selected from grub2…

If you need any more information please let me know. And yes i searched for this problem but found only articles related to broken drives, my issue exists even without any drive….

Error Photo

How do I remove all of the data on a harddrive partition without removing/altering the filesystem?

I have a drive that has corrupted data on it. I need to wipe all of the data on that hard drive partition without altering the filesystem because I cannot rebuild the filesystem (It’d a very old version of XFS and cannot be upgraded, it is in an arcade machine).

Trying to install Ubuntu on external hard drive and Grub on internal harddrive – BIOS

im trying to install ubuntu on my external hard drive and Grub on my internal hard drive, i once installed ubuntu on my internal but i dont have much space on my main SSD, i use a laptop and i decided to replace my old 500gb HDD with a 250gb SSD and i use my old one as an external disk.I already made a question asking how to install this but it was pretty bad an i didnt gave much info. After i tried to install it and rebooted my computer i got this error:

error: no such device: e5ba289-b231-4ad9-abda-b6a8a04c1c1e error: unknown file system entering rescue mode…

After i saw this i rebooted my laptop and booted my USB with ubuntu, and installed boot-repair, after another reboot i got the normal windows 10 starting screen.

I have the log from boot-repair if you need more information please leave a comment and i will give you the required information.

The boot-repair log: https://paste.ubuntu.com/p/DbS993K8mJ/

Harddrive Compatibility Issues

i recently bought a HP DL580 G7 from ebay. It didnt come with harddrives so i bought 2 x ST1200MM0118 harddrives.

I am seeing hell to try to get it working. I contacted HP support who told me to purchase HP harddrives ( not very helpful ), however they did assist me in updating the firmware of the p410i controller to 6.64 and all over drives using the SPP to the newest for that server.

I still get no response from both drives. Ive tried what i believe to be EVERYTHING. Ive tried booting with only 1 drive in, ive tried a random sata drive i have laying around ( which works perfectly in my external sata to usb dock ).

Im wondering if the backplane or the sas cable could be the problem, however im wondering if that might even be the problem.

When i log into the iLO, the 2 harddrive informations says “fault” which leads me to believe the problem may be with the drives and not the sas cables or the backplane.

Im looking for some suggestions on what would be the best way forward.

How do I copy files from macbook to external harddrive using single user mode?

My MacBook pro shut down due to an error, and now I can’t log in again. I’ve tried creating an image using Disk Utility but it fails every time. I have my hard drive connected to my MacBook but when I type “ls Volumes” into the command line using single user mode. Nothing but the “Macintosh HD” is available. I thought this was odd due the fact that I am capable of accessing my hard drive when using the Disk Utility tool. Any suggestions on how I could access my files and copy them over to an external hard drive before I reset my computer.

Disk Scheduling for a Fragmented Hard-Drive

Recently In class I have been learning about simple disk scheduling algorithms such as FCFS, STTF, LOOK, LOOK-SCAN etc. From my understanding these algorithms schedule I/O requests depending on which cylinder number needs to be read and a process will produce only one I/O request whenever it needs to access a file.

This is confusing because apparently I/O requests are scheduled, but the actual algorithms work only with cylinder numbers. What if an I/O request requests a file which is spread over multiple tracks and therefore cylinders?

How can the algorithm schedule I/O requests when it’s possible for each I/O request to require multiple cylinders to be read (e.g. if the file is fragmented across multiple cylinders).

2nd Harddrive preventing system to boot

I’ve 2 hard drive in my Asus A45V laptop:

  1. 240GB SSD (for OS)
  2. 500GB HDD (for personal data)

I placed my SSD in HDD slot, and replaced DVD RW with HDD (using caddy).

So here’s how my problem showed up:

  1. My SSD have two paritions, I have Windows 10 installed in the first partition.
  2. I turned off windows fast startup.
  3. Then I installed Ubuntu in second parition. Dualboot worked fine using grub as bootloader.
  4. I turned on windows fast startup again
  5. Now my laptop can’t boot, it stuck in Asus logo and I can’t enter BIOS using any key. It’s completely stuck.

And here’s what I’ve done so far:

  1. I removed SSD and reboot. Didn’t work.
  2. I placed again my SSD, removed my HDD and reboot. It works.
  3. I removed Ubuntu and grub. Then placed my HDD again, the problem still exists.
  4. Removed my HDD, boot windows via bootable USB and doing startup repair, Windows said it can’t do a startup repair.
  5. Delete hyberfil.sys from my HDD, didn’t work.
  6. Replaced my HDD with my friend’s HDD. It works fine.
  7. Put my HDD into USB dock (making it external HDD) and plug it in USB port, works fine.

So I think it’s the problem with my HDD but i don’t know what the problem is.

Additional info:

  1. Before I have SSD which is just 3 days ago, my Windows 10 is installed in my HDD. I moved it in SSD using mini tool partition > Migrate Os to SSD.
  2. Before I have SSD, I enabled paging file for C: and D:.
  3. After I moved Windows to SSD, I merged C and D partition on my HDD.
  4. There’s a silver sticky paper, alumunium foil like that ‘protecting’ my HDD, the SSD seller moved it on the new SSD.
  5. Boot mode is UEFI with legacy support enabled.