Jump to content
Corsair Community

GT Voyager 128gb 3.0 fails to USB 2.0 speed


Psibolt

Recommended Posts

I just sent back my second GT Voyager 128gb 3.0 for RMA replacement.

 

1. RMA 2/4/14 - Ticket 6395874 - CMFVYGT3A-128GB

2. RMA 3/31/14 - Ticket 6447842 - CMFVYGT3B-128GB

 

Both of these drives were formatted NTFS, were purchased in June 2013 at Micro Center.

 

These drives "failed" (no longer would be detected as USB 3.0) at 8 & 9 months respectively.

 

I always close out the drives and waited for the blue lights to stop blinking on the drives prior to removing.

 

1. Do these drives have a 5 year warranty?

 

2. Does Corsair categorize/track/analyze RMA's and if so, is there some common factor when these drives stop working at USB 3.0 and lights no longer function, but they continue to work at USB 2.0 speeds?

 

Symptoms: The drive suddenly started getting a popup message of "this device can perform faster" if attached to a USB 3.0 port.

 

The problem is that all my ports are USB 3.0, all other devices are working properly, the lights stopped displaying on the USB drives and I got this message trying all USB ports after reboots with only keyboard and mouse attached.

 

I *know* it's a drive failure due to the fact that the other USB drive would continue working at USB 3.0/transfer speeds and not get the popup message.

 

I have a couple of other brand 64gb drives that I've had for a while but have never had any issues with them performing at USB 3.0.

 

These drives worked great and flawlessly until they both seemed to corrupt/go south/whatever at about 8/9 months of USB 3.0

 

Are there updates or other steps that can be tried if this happens again (formatting with other software/firmware updates?/etc) or is RMA'ing the only solution once they stop working at USB 3.0 and the lights no longer work appropriately.

 

I've only ever used Win7 64bit formatting (both NTFS & Ex-Fat after failure) and tried quick and full reformats to no effect.

 

Thanks for any help or advice!

Link to comment
Share on other sites

I read a couple of posts that mentioned the rubberized casing trapping heat and can cause glue to melt.

 

I only use these Voyager GT 128gb 3.0 at my home to transfer video and music files.

 

Due to the symptoms, lights quit working appropriately and is only detected once failed to USB2, would anyone hazard to guess if this *might* be more indicative of a hardware issue?

 

I don't really have to keep them in the rubberized casing since they are homebound, would it be better to take them out of it so heat dissipates better?

 

Would doing that only (removing the rubberized case) void the warranty?

 

If all the other devices that are USB 3.0 and the other Voyager GT 128gb 3.0 (That continues to detect/work at USB 3.0) had any issues on detection or operating at USB 3.0 speeds, I would be more *iffy* on it being firmware/formatting/data corruption.

 

When I sent the first one back, was it analyzed to see if it was a hardware failure or what the problem was with it?

 

RMA 2/4/14 - Ticket 6395874 - CMFVYGT3A-128GB

 

I'm going to ask in the tickets to see if someone will reply with the analysis of the returns that failed.

Link to comment
Share on other sites

I will keep the rubber enclosures on them... :-)

 

Another question I have, is should the RMA process be modified to include how it's been formatted for main use and what devices it's used in?

 

For instance, once written the majority of it's time is used plugged into a DVD/BlueRay for video playbacks/sound equalizer or a Samsung Flat Screen.

 

Some have mentioned that NTFS *seems* to be an issue, others have said some of the issues occur regardless of formatting.

 

I *did* try it once in the car, but it's an unrecognized device - think it might be too large for the Kenwood unit in my car or it needs to be partitioned differently to be seen (per other peoples posts). Not that important due to mainly using Ipod 160gb and smaller USB drives for on-the-fly listening.

 

Still curious to see if the questions in the ticket about analysis (Hardware/Software/etc) regarding returned failed USB drives is answered.

 

Are they tested to see why/how they failed?

 

If so, it would be interesting to see the statistics on returned reasons, OS's, formatting and exact failure issue - hardware, corruption, etc.

Link to comment
Share on other sites

They most likely check the devices that are returned and see whats wrong with it but they do not provide any information such as failure rates, causes of failure to the public.

 

IMO, i don't think you need to put in a new comment mentioning how the USB drive was used unless they ask for it. Reason is, the USB should have been able to do what its designed for which is "high performance data storage".

 

As for compatibility, it depends on the unit as they all vary. Have a look in the user's manual for the Kenwood unit and see what is supported and what the limits are.

Link to comment
Share on other sites

 

IMO, i don't think you need to put in a new comment mentioning how the USB drive was used unless they ask for it. Reason is, the USB should have been able to do what its designed for which is "high performance data storage".

 

As for compatibility, it depends on the unit as they all vary. Have a look in the user's manual for the Kenwood unit and see what is supported and what the limits are.

 

1. The reason I asked about this is I notice that when you eject the drive (which I have always done), even though it says it's safe to remove by Win7 64bit, in a second or two the lights on the Voyager GT 128gb will blink real fast then stop. Other devices also do this.

 

I *assume* that this means some finalization of the closing out process is being done and a user should wait until that occurs, even though a message by the OS said it was safe to remove.

 

This also occurs when using in the Sony BDV-E3100 Blu Ray/Surround Sound system - when you power off the Sony (it goes into Standby mode for several seconds), in a second or two the lights on the GT 128gb blink real fast then stop. I wait till that occurs before physically disconnecting.

 

Should a user (which *I* do) wait for the fast blinking to occur on the GT before physically ejecting the GT 128gb to avoid corruption?

 

If so Windows 7 64bit OS message that it's safe could cause issues if you physically remove the device before the fast blinking of the GT occurs and stops.

 

Also some devices write there own small files to the device outside of computer usage (like Flat Screens/DVD-Blu Ray Players) and I was wondering if those might be an issue.

 

I have a Samsung 55 inch Flat Screen (samsung un55f6300af) that also seems to write a file to the GT, cm0013 (contents of CM_DEV_ID|1388808652). - CM devices

 

2. The Kenwood unit in my car did not give specifications on USB limits, I assume it's 64gb since those drives work ok with same formatting

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...