|This forum is proudly powered by Scientific Linux 6||SL website Download SL Help Search Members|
|Welcome Guest ( Log In | Register )||Resend Validation Email|
Posted: Aug 29 2011, 04:39 AM
Member No.: 148
Joined: 10-May 11
I changed some of my USB 2.0 drives over to a USB 3.0 drive -- also adding a USB 3.0 controller to my server.
It *basically* works. IE, I can read the drives, I can mount and work with drives, and I am seeing improvements in speed.
I have 4 drives in the enclosure, and all 4 are added to a single volume group.
But here's the 2 things where I am having problems:
- The drives don't seem to actually be available at boot. IE, the "vgchange -y a" doesn't succeed at boot.
If I wait for the machine to complete booting up, I can re-run a "vgscan", then activate the volume group, and everything is OK.
This is not a deal breaker, but it very annoying. Anytime I reboot, I have to log int and active the volume group just to get the drives and LVs available.
- I am getting this message all of the time in my logs. Any time I access the drives, I get somewhere between 4-5 of these, and sometimes several dozen in a row:
Aug 29 00:19:31 mighty kernel: xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
Aug 29 00:19:32 mighty kernel: xhci_hcd 0000:04:00.0: WARN: Stalled endpoint
This problem could be related to the first problem
After doing some searching, it seems the error messages in the logs have seen by lots of other USB 3.0 users -- but I have yet to find any solution to these messages.
Anyone else ever use USB 3.0 drives, or seen anything like these issues?