Hello,
Lately I've been trying to install FreeBSD onto a USB 3 drive. So far I've had three different results from three different drives, and I will list them bellow, as well as the motherboard model and versions of FreeBSD.
The PNY drive was also tested on Arch Linux with Badblocks and returned 0 errors after a write/read test on all sectors.
Whenever I use a USB 2.0 drive, everything works smoothly and I never encounter any issues aside from slow file transfers.
Motherboard: Asus P8P67 Pro
RAM: 8GB Mushkin (Non ECC) (4x2)
CPU: Intel i7 Xeon 3.2ghz
Does anyone agree that this seems specifically like a USB 3.0 issue? Is there anything else I could try and check? I've looked around quite a bit and have googled these individual errors but have yet to find a specific solution.
Lately I've been trying to install FreeBSD onto a USB 3 drive. So far I've had three different results from three different drives, and I will list them bellow, as well as the motherboard model and versions of FreeBSD.
- SanDisk 32GB - Died within a week of use. Not really much else to say. FreeBSD 10.1
- Lexar 16GB - Installation went fine with FreeBSD 11 RC2 but the server would randomly reboot, dmesg showed that it was detecting the drive as 'disconnected' which caused a paging buffer error, kernel panic and thus a reboot.
- PNY 16GB - During installation, as well as regular operation after installation, will randomly throw the following error:
Code:
WRITE(10), CDB: 2a 00 00 00 04 a2 00 00 08 00
CAM status: CCB request completed with an error
Retrying Command
The PNY drive was also tested on Arch Linux with Badblocks and returned 0 errors after a write/read test on all sectors.
Whenever I use a USB 2.0 drive, everything works smoothly and I never encounter any issues aside from slow file transfers.
Motherboard: Asus P8P67 Pro
RAM: 8GB Mushkin (Non ECC) (4x2)
CPU: Intel i7 Xeon 3.2ghz
Does anyone agree that this seems specifically like a USB 3.0 issue? Is there anything else I could try and check? I've looked around quite a bit and have googled these individual errors but have yet to find a specific solution.