12-09-2010 08:01 PM
This is my second one these in the last three weeks - each of them had the following condition.
When started cold in music mode to play a folder with FLAC music each device would play somewhere between 20 and 35 songs and then mysteriously shut off. If restarted immediately it would then play about ten songs and then quit again; if restarted again it would play 1 or 2 songs at the most and then shut down. I am using the music from the freeagent go drive installed in the bay on the device.
Is this a known issue?
Is it due to overheating?
Is there a solution short of trying another device via warranty again?
Are the devices w/o the drive bay any better - the ones that are $50 a egghead?
Does any other company make one that will play FLAC through my stereo and not shut down?
I really like this device's design and I don't mind the interface but I had similar problems with early Maxtor NAS drives - I finally got Seagate to fork over 2each 2tb hd extreme drives and just started doing everything manually again.
So what is the scoop?
Thanks in advance for any info
Solved! Go to Solution.
12-09-2010 10:27 PM - edited 12-09-2010 10:43 PM
Sorry, there is no scoop. This is the first time someone reports this, AFAIK. Try unplugging the power for more than 30 minutes, and plug it back in. See if the problem'll go away. If not, then reflash the same FW using Cold Method.
This could be a heat problem. BTW, all FAT+ has the insert slot for the GO drive. If it does not then it's not the FAT+. The original FAT also has a slot that you have to push to eject, with the FAT+ you just slide the GO drive in.
If the problem still persists, then try plugging in another USB drive to the front or back USB port and play that. Sometime the inside port has intermitment problems that are probably related to power, and heat. If that's successful, then use the GO drive that way with the USB cable that comes with the GO drive (treat it like other external USB drives).
12-16-2010 03:10 AM
First let me thank you for your reply.
Your suggestion that one unplug one's FAT+ for a long period was the answer.
Do you know why it works and is it something one should do with other devices when one flashes their firmware?
This will make my wife's morning very pleasant as I put all of her Xmas music in .flac format this past month and mixed them up so that she will be able to listen to hours and hours while I work at my wood lathe.
12-16-2010 10:02 PM
Hi again - I thought I had it but after ~2.5 hours of a smiling wife the darn thing locked up again.
I just restarted it and I am wondering if I am expecting too much to have continuous play for more than that period of time?
Is it possible that corrupted files are the problem i.e... Would a corrupted .flac file lock up a FAT+ or would it just skip them?
I am not playing over the network - I have it connected with the optical connection to my Onkyo receiver and an HDMI to the TV - which I turn off after getting the system booted and playing.
I don't use the network for anything in relation to the FAT+ I just want it to be (at least for now) a flac player for my songs. Like everyone else I sneakernet the drive back and forth.
If I can get this one to stop locking up (or another one) since the first level technicians seem to know little about FAT+ and the upper level techs are hard to get to. Then I might consider doing something with my network.
It just conked out again so and it locked up on a Neil Diamond song that it played before.
And the time was about 60 minutes this time.
I just restarted it as not only did it lock up but it shut itself down completely and when I restarted it started reindexing the content. Last night it wasn't doing that - one indexing and then it was fine.
This time we played 29 songs.
Does this bit of info help?
12-16-2010 10:18 PM
I think you should post this as a reply to your original thread. If someone were to read thispost for the first time they would have no idea what you are talking about. Then delete this thread (if you can) or point to your original.
That aside, are you playing from a drive in the bay? If so, can you try is via an external usb connection?
12-16-2010 10:46 PM - edited 12-16-2010 10:59 PM
Sorry to hear you are still having problem. As prairiedog mentioned, it's best to post in this thread so others can follow the conversation and understand the issue.
- You're on to a possible cause: a corrupted flac file. The FAT+ error handling is pretty lousy! any time it plays some file that has some abnormal info, it just crashes, so that's could be a problem. However, I'd do the following first, since tracking down a corrupted flac file could be time consuming (the FAT+ has no visible error log so it's not easy to see the error if you're not familiar with Linux system logging).
1. The next step should be playing another external USB drive, if you don't have another drive just plug the same GO drive into the back USB port (Off-topic, the back is the best one to try, because the front is too close to the remote receiver, but that's another story). Play this way to see if the problem is with the heat or power supply to the inside USB port.
Also, you did not mention the capcity of the GO drive, and whether you use a small drive like 250GB and put the cover on (it's possible for a small GO drive to be completely inside). That would not be recommended. Never put the cover on with the GO drive inside. The heat is too much.
I suspect the heat or the power supply was the problem. And that would cause all types of weird things to electronics. When you unplug for a long time, you will allow the current in the capacitors to dissipate so it's similar to a reset, (all volatile memory already clear when you power down). Even in case it's not heat or power, if the FAT+ has overwritten some memory because of other errors (e.g. corrupted flac file), let it sit would clear them up.
2. I would do number 1 first. If that does not work then reflash the FW using Cold Method. Which FW you're on?
12-18-2010 06:34 PM
I am using 2.2. Firmware and my FAT+ came w/ a 500 gig HD in the dock.
I am troubled because this is the second one in the last several weeks.
I never have trouble w/ Seagate drives BUT anything they put a microprocessor in seems to be a terror for me. I went through four sets of 2 each early release MAxtor 2TB NAS devices. Can you imagine loading 1.3 TB of data 8 times?
Now it is FAT+'s - perhaps my expectation is too high.
I thought I wanted all the features BUT when it comes down to it I don't care about networking since one can not load its HD via one's network. I just want it to play my thousands of .flac files w/o too many hiccups. The problem is the decreasing number that the device plays. This second one since being unplugged does about 70 then 30 then 10 then 1 then~1/2 then none. I don't mind loading them into the drives and in fact I would consider buying two more drives if the player worked w/o locking up.
So I will run the .Flac files through a FLAC encoder again to see if I get any errors. I have been using flac front end and they (the files) work well via both WMP and dbPoweramp. I have never had a hang-up with these two players.
Does the FAT+ have trouble with .flac files that have an embedded image in the tag. Normally I try to completely tag every image that I rip from a CD and I scan in an image of the CD "cover" via an HP scanner and process it through PS and shrink it to between 20K and 40K.
If tagged files w/ images present a problem I can strip them out using Tag&Rename.
I have found that my new Sony BD player is better for internet activities and has more options. I don't have any video files that I ever thought about playing through the player - I am content to play the DVD or the BD and I appreciate the image quality.
So any other comments would be appreciated..
Maybe I should just by a creative Zen or a Cowan w/flac playing ability.
I rate this experience right up with my early days w/neuros mp3 players. I ended up with and Ipod and a zune.
I read about the"cold flash" and I will give that a try as well.
BUT this really is not what the buying experience is all about. It really isn't our job to do their software engineering.
Stuff like this is why Apple's stock is so high.