This creates ambiguity to my troubleshooting process because I want to know where the drive mounting process has failed. Online searching only confirms that the 2015 MBP supports USB 3.0, but doesn't say anything about UAS or streams. I have no idea what streams or UAS are, but I know that it is some kind of optimizing process that has something to do with USB 3.0. I cannot mount the Seagate drive onto my Ubuntu Server VM.įor the record, I've considered other server solutions and tried Docker Desktop, Docker, dual booting, and replacing the MacOS with Linux altogether, but all of these come with their own headaches and problems, and I don't want to make investments while at an experimental stage.I could find the Seagate drive with sudo lsusb, but not sudo fdisk -l.The presence of this error had the following consequences for me: Please try an other USB controller if you wish to use UAS. I formatted the drive to exfat and begun the process, and after encountering and fixing a slew of issues, I ran into this damning error message on the Ubuntu Server startup/or var/logs/syslogs: USB controller 0000:00:0c.0 does not support streams, which are required by the UAS driver. At this point in my homework, if I can connect my Seagate drive to the virtualized server, I am effectively finished. I want to grab a spare Seagate hard drive and turn it to a local network file hosting server, so I started an Ubuntu Server in a VirtualBox VM in the MBP. Lately I've gotten inspired to practice some self-hosting, and my old Early 2015 MBP isn't doing anything while selling for practically no benefit to me.
0 Comments
|