Ubuntu 18.04.4 LTS live CD screwed up an external hard drive.
by Galane from LinuxQuestions.org on (#51XCS)
I needed to copy a large amount of files from one USB 3.0 hard drive to another, and didn't want Windows 10 popping up with anything to interrupt the process.
So I made an Ubuntu 18.04.4 LTS Desktop DVD, booted off it, started the copy and went to bed. Only around 200 gig or so.
Next morning the copy isn't finished. It's going super crazy slow. Less than 1/4 finished.
So I figure I'll reboot to Windows and disable Defender then sit there and babysit the copy.
Nooooo. Can't read the Seagate ST4000LM016 1N2170-567 4TB destination drive. Plug it in and Windows Explorer wants to hang. I took it out of its case and hooked it up with a USB to SATA cable to see if perhaps the drive's adapter had died. Nope, same problem.
So I launch AOMEI and it takes forever reading K: but finally opens and I see K: (disk 8) is shown as 2TB and there's a disk 9 that's 1.64TB unallocated.
There is no disk 9! It's all supposed to be a single 4TB (3.69TB) drive. What the bleep did Linux do to my drive and how do I un-@#%@ it? Has to be something really whack to make Windows see a single drive as two separate physical drives.
The source drive is connected to the Fresco Logic USB 3.0 controller on the motherboard. The screwed up drive was connected to a Renesas USB 3.0 controller through the built in Genesys hub on a PCIe card. Using the ports that connect directly to the Renesas chip has issues with some 3.0 devices hooking up to its USB 2.0 root hub.
I can't connect anything else to the motherboard's USB 3.0 because some genius at Asrock decided to equip the 770 Extreme 3 with just one USB 3.0 port and no internal header and I don't have a USB 3 hub.
I have an Inateck KTU3FR-5O2I card with a Fresco chip ordered. Some googling reveals that Ubuntu has had issues with super slow (like USB 1.0 slow or worse) transfer speeds with Renesas USB 3.0 controllers for years.
Why Fresco? Because they released new drivers in 2019 for the chip on my motherboard made in 2011! Renesas quit releasing updates for their chips in 2012. The newest available firmware and driver sort of fixed it, now only some devices in the problem ports aren't properly recognized instead of all of them.
So I made an Ubuntu 18.04.4 LTS Desktop DVD, booted off it, started the copy and went to bed. Only around 200 gig or so.
Next morning the copy isn't finished. It's going super crazy slow. Less than 1/4 finished.
So I figure I'll reboot to Windows and disable Defender then sit there and babysit the copy.
Nooooo. Can't read the Seagate ST4000LM016 1N2170-567 4TB destination drive. Plug it in and Windows Explorer wants to hang. I took it out of its case and hooked it up with a USB to SATA cable to see if perhaps the drive's adapter had died. Nope, same problem.
So I launch AOMEI and it takes forever reading K: but finally opens and I see K: (disk 8) is shown as 2TB and there's a disk 9 that's 1.64TB unallocated.
There is no disk 9! It's all supposed to be a single 4TB (3.69TB) drive. What the bleep did Linux do to my drive and how do I un-@#%@ it? Has to be something really whack to make Windows see a single drive as two separate physical drives.
The source drive is connected to the Fresco Logic USB 3.0 controller on the motherboard. The screwed up drive was connected to a Renesas USB 3.0 controller through the built in Genesys hub on a PCIe card. Using the ports that connect directly to the Renesas chip has issues with some 3.0 devices hooking up to its USB 2.0 root hub.
I can't connect anything else to the motherboard's USB 3.0 because some genius at Asrock decided to equip the 770 Extreme 3 with just one USB 3.0 port and no internal header and I don't have a USB 3 hub.
I have an Inateck KTU3FR-5O2I card with a Fresco chip ordered. Some googling reveals that Ubuntu has had issues with super slow (like USB 1.0 slow or worse) transfer speeds with Renesas USB 3.0 controllers for years.
Why Fresco? Because they released new drivers in 2019 for the chip on my motherboard made in 2011! Renesas quit releasing updates for their chips in 2012. The newest available firmware and driver sort of fixed it, now only some devices in the problem ports aren't properly recognized instead of all of them.