Firmware: A-410 [01 Apr. 2014] | A-400 [12 Mar. 2014] | C-300 [13 Feb. 2014] | A-300 [24 Feb. 2014] | C-200 [11 July 2013] | A-200/A-210 [11 July 2013] | Popbox V8 [3 Dec 2013]

Just got your NMT | WIKI has the answers | Search the forum | Forum Rules/Policy | Firmware & Official NMT News | Popcornhour manuals



User(s) browsing this thread: 1 Guest(s)
Post Reply 
Common 300 series problems and solutions.
08-05-2012, 11:07 AM (This post was last modified: 02-04-2013 04:58 AM by accident.)
Post: #1
Common 300 series problems and solutions.
The 200 series thread seems to be really helping out some users who have discovered a lot of their long term problems were fixable. I'm hoping to start the same type of thread here.

Some information is going to be overlapping. I figured for a novice it would be best if all the information is in 1 place even if it's the same information. Makes it easier then "click here, ignore 3,4,5 but add this step 6".

PLEASE HELP ADD TO THIS. I ONLY HAVE AN A300 AND TO BE HONEST RARELY USE IT.

Topics in this post:

Tips:
0. Things all users should do
  1. Follow the install instructions
  2. The release note have what was fixed and what they know is still a problem
  3. Look over your setup as a whole and see if you can make your life better
  4. CSI and oPKG apps are not made or supported by syabas and cause stability and bugs.
  5. Factory resetting is good
  6. Make a great post if you need more help
  7. Tell Support



Problems:
  1. Player that are unstable, crashing, rebooting often, poor playback that used to work and problems nobody else seems to have
  2. No internet connection, internet error messages, wrong time/date on the clock and unable to scan with NMJ among other network related issues
  3. My network has a strange ip address that starts with 169.254
  4. Slow network, poor network playback, poor app playback (youtube)
  5. I can't use GIG/AUTO for networking
  6. The pch gig speed is not gig throughput/full speed copies
  7. Problem with wireless
  8. SMB (samba) login with username and password doesn't work anymore
  9. My 3tb or larger drive is not detected by the pch
  10. My 3TB or larger drive does not work when I use the tether/slave usb mode of my a series model
  11. I have a WD Green Drive installed in my player
  12. My PCH Is really slow



Tips:

0) Things all users should do

See #4 below, it will make life better.
Also see #12 below if you installed NMT (or recently updated it)

A) Follow the install instructions for an update

All firmwares have install instructions and they do change. Even if your updating online after the player told you there was an update, you'll find the instructions on the tv screen before you start. It's easy to avoid headaches just taking the 2 extra minutes to do it right the first time.

B) The release note have what was fixed and what they know is still a problem

Updating is not always smart. If the player is perfect to you, it doesn't mean the next version will still be perfect to you. Take a moment and read over what changed, what is still broken. A feature you use non-stop could be in the broken list.

C) Look over your setup as a whole and see if you can make your life better

You'll find there are certain people who are always happy with the updates, myself included. Over the years, we've adjusted how we rip, dl, record, and save videos to the drive. We tend to go with file formats, codecs and quality that we are happy to use and tend to work all the time. For those of us who are automated with more powerful nas or similar devices doing the work, we also have it clean up the video files for us so they will work the first time, every time.

I'd love to have a longer discussion on this, but it does not belong in this thread but it does impact how well upgrades go for you.

D) CSI and oPKG apps are not made or supported by syabas and cause stability and bugs.

Fellow Users are making the additional apps, updates and things you may be enjoying on your setup. They are hacked in using a method that is fairly safe and does not void your warranty. They are only tested by the users that make and use them. They consume memory, take away cpu power and things that your player may need just to play a video.

Some apps also fix previous firmware bugs. When firmwares update they might actually break an official fix for the problem. Asking in the threads for those apps before you update is the best way to know if it should be removed.

I'm not saying throw them out, they shouldn't be used but you need to keep in mind that your extra software might be your bugs and problems. Disabling them will help you figure out if it's a bug in your applications or a bug with the player itself.

These apps are the #1 reason why firmwares fail to update. This is why syabas has instructiosn to remove the drive forcing the apps to no longer be running so it can safely update the player

E) Factory resetting is good

Settings change, some bug cause settings to change automatically, some settings are internal and you cannot change them yourself.

  • Factory resetting before and after a firmware update will make sure your player is almost as close to how syabas made it for that firmware as possible.
  • Factory resetting when your player starts to feel sluggish or unstable can get all the settings back in line to be stable again.
  • When you find yourself factory resetting for sluggish/unstable rather often, then you should consider a full system reset. You'll find reset information and steps in problems #1.


Just like D, you'll get the hang of how to make sure you setup streamlined so resetting isn't a big deal.

F) Make a great post if you need more help

The people who get the fastest and best help make really good first posts about the problem.

Suggestions:
  • Choose the best forum, posting a 300 series video problem in the General nmt forum probably won't get many to see it who can help.
  • Pick a subject that quickly informs others what the core problem is. If your having a network problem, PLEASE HELP is not a good subject. Need help with network is better, but Wireless network problem is even better.
  • If you have multiple problems, post multiple threads. People read threads if the subject interests them. If you piggy back too many problems in 1 thread, you don't get all the help available here. Also some problems are better posted in different sections. Put the video problems in the video thread, the nmj problems in the nmj thread.
  • Make 1000% sure an old thread is really the same problem, if your not sure, don't reply to it. The people who read the whole forum will go out of their way to help a thread with almost no posts, but will avoid threads with hundreds of posts.
  • Your message should be information overload. Model numbers, version numbers, brands, things you've tried already, similar information asked in other threads. Anything you think can help out so the first reply is exactly how to fix it instead of a week of asking for more information.
  • This is an international forum. The person who can help you might be on the other side of the world. give it a day or two to get a reply. Weekends are quiet, give it longer on the weekend.
  • If you see 100 reads and no replies, it might be 100 people with the same problem hoping you posted an answer. It might also be 100 different search engines indexing your new thread. Don't get discouraged because it's being read but no replies.
  • Answer the questions asked. It's very common that people ask a few things and only part of them get answered. If you don't know how to answer them, SAY THAT. Some questions might seem unrelated but it's exactly what is needed to tell you how to fix it in your setup.


G) Tell Support

This is a user forum sponsored by Syabas. Just assume they do not read a single thing here. Support on the other hand they pay to reply to you and they would prefer to fix a problem then hiring more people for the extra calls. Also it gives them a trend for what is important to the most people. It will help prioritize fixes in your favor if you get counted by the company.

Support is found at http://support.popcornhour.com/


Problems:

1: Player that are unstable, crashing, rebooting often, poor playback, that used to work and problems nobody else seems to have, and settings are lost after a reboot/power cycle.

It's best to full reset the player. It's possible for the firmware to get something corrupted over time and this is the fastest way to ensure that is not your problem.

When doing these steps, it's best to not have NMT or other apps running.
  1. If you have a drive with NMT installed on it, shutdown and remove it.
  2. Factory reset and reboot
  3. Follow the firmware recovery instructions. You want to follow the numbered instructions to make a recovery thumbdrive and then follow the lettered instructions to force the player into recovery mode and do the recovery
  4. Factory reset and reboot
  5. Install the latest firmware. if you need to alter any settings to get online to do the update, use the usb instructions and do not alter any settings.
  6. Factory reset and shutdown
  7. Reinstall any removed drives and power on
  8. Add your settings and enjoy.




Technical Reason:

The internal flash drive storage in the pch units are NAND. NAND is very standard in all devices, mobile phones, tvs, tablets, car computers, gps, you get the idea. Like all other flash drive storage (SSD, THUMBDRIVES, etc), NAND eventually has bad "sectors" which are completely dead or can not longer be written too. The standard procedure is to map out the bad sectors and avoid them.

The firmware recovery procedure is designed to "rescue" a player when something went horribly wrong with an update. Because the most likely cause of this is a problem with the NAND storage, it completely wipes it, retests and puts a nice clean copy of the firmware onto it. It basically ensures your problems are not because something is corrupted in the firmware.

The additional factory resets are just to make sure the player ends up with firmware defaults before you start to add your settings back in. Some bug fixes are changes to the defaults, you can wait for a problem, post about it, maybe someone else who did reset knows what changed or you can just get the new defaults now and not worry about it.

Advanced user alternative option:

You can turn any firmware into a recovery firmware. While I have not personally tried this with the current firmware releases, if you have the time, you might want to find the old recovery instructions in the wiki and do both the recovery and update in 1 step. Keep in mind, stepstone/online only updates this will probably not work for.

2: No internet connection, internet error messages, wrong time/date on the clock and unable to scan with NMJ among other network related issues

IF YOUR PROBLEM IS POOR VIDEO PLAYBACK, YOU SHOULD ALSO TRY #1 and #4 IF THIS DOESN'T HELP

Check your network settings:
  • if you factory reset and switched to static, check the subnet it's probably wrong and needs to be adjusted to 255.255.255.0
  • If you see 1 dns server. Try editing the dns only (it's an option) and put in the same server for dns1 and dns2. save and reboot the pch.
  • if you see dns servers that start with 208, some routers do not like multicast-dns with open dns. Edit the dns servers and put in your home dns server twice (usually the router/gateway ip), or try googles dns servers which are 8.8.8.8 and 8.8.4.4. You may need to reboot for it to fully kick in.
  • You can also try your providers dns servers, they can easily be found in your routers status screen under the wan network status. Some providers like to block things.
  • If your pch ip starts with 169, see #3 Below


CISCO ROUTER OWNERS:

A user recently found that a cisco home router firewall defaulted to only 10 devices on the network talking to the internet. You may want to check your router logs and see if you need to increase the number of hosts limit in your home. It's possible a rebooted devices and computers could appear double to the router for some time and push you over the limit even if you don't have 10 devices on your network

Technical reason:

There are 4 main problems happening here.
  1. dns lookup on low end hardware adds seconds to any communication to a device. This is the time it takes to look up the hostname or url and turn it into an ip address before it can even start to communicate with the world. in the last firmwares, syabas switched to an mdns setup which caches and speeds up this avoidable slowdown. It also works using multicast. Multicast is not worldwide on the internet yet and some ultra low end routers or older routers may not process it right. while a good move for speed, it can negatively work for many people.
  2. large hosts with datacenters all over the world use something known as global load balancing to send you to the center that would offer you the best performance. About a year ago, a project was started to expand dns itself to do this verses very expensive datacenter hardware. opendns and googledns both added it to their public dns servers the same day when it was announced. Syabas also changed defaults to opendns partially to fix some users with major dns problems in the past but also to get you better online video streaming in the apps making sure you get to the best possible playback with least amount of effort. Just like 2, some routers and providers don't talk correctly with opendns.
  3. There is a bug with some parts of the player. Some parts of the player use the first dns server then the second if that is not available. Other parts use the second and sometimes never try the first. This is why you can have part of the player working with the internet and part of it not. Making sure you 2 dns servers that work with your router and isp is how you get the whole player to work. Again a bug that is mostly fixed in the current RC of the C200 firmware, but not in all the players yet. It's a bug you can fix yourself while you wait for the full robust solution.
  4. Some home firewalls, generally found in small office or gaming routers have some added security features you may not have known were in them. They might actually limit the number of devices that can talk to the internet. this is a good way to help contain a possible virus or worm that might get into your computers from really impact the internet as a whole. Unfortunately even with just a couple devices on your home network, their is timeouts to say "this device is no longer here" so some rebooting of a device or several can easily go over the low limits.



3: My network has a strange ip address that starts with 169.254

This would only happen with dhcp enabled and it means the pch isn't getting an address to use or the address it was given is already in use on the network.

There's no simple, "do this" to fix it. but you'll want to verify your cables are ok, you have link, link is staying stable, your dhcp server (probably your router) didn't run out of ips.

There is always a chance of some bug in your router dhcp server which other os's might be able to handle. Don't forget to look for a router firmware update and/or use a static IP on the pch. WIKI HELP FOR DHCP AND STATIC IP.

Technical:

The network range starting with 169.254 is know as a link-local address. It's an address range that is used when devices don't know what ip address to use for a network connection to avoid conflicting with other devices. This is an indication that there is trouble talking to the device on your network providing the DHCP server and the first place you should check.

It's possible there is a specific bug between your DHCP device and the pch and static IP might be your only choice, directions above in the link to the wiki.

4: Slow network, poor network playback, poor app playback (youtube)

There are a couple possible problems here:
  1. Do not use AUTO video setting, see this thread for help
  2. Poor quality network equipment, see #5 for more help
  3. Bad RWIN settings, keep reading for how to fix that.



NOTE: YOU MAY NEED TO FIX ALL 3 TO GET IT WORKING SMOOTH

THIS IS SPECIFIC TO THE 300 SERIES, DO NOT TRY THIS WITH A 200 THINKING YOU'LL MAKE IT BETTER.

I am not happy with the defaults in an area of networking but luckily we can change enough of them to really get the most out of the bus and network port without syabas. Special thanks to sfortis for originally finding this solution

This is a change that you only need to do once. After any factory reset or firmware update you'll need to verify it wasn't reverted back to default on you and put it back in.

  1. Telnet into your pch
  2. type: pflash set tcp_recv_mem 131070
  3. type: reboot



How do I telnet???


How to check if it needs to be adjusted again?

  1. telnet into your pch
  2. type: pflash get tcp_recv_mem
  3. If you do not see 131070
    1. type: pflash set tcp_recv_mem 131070
    2. type: reboot
  4. close the telnet window.



Technical Information:

The part of TCP/IP that this impacts is how much data to burst out at a time. The way it works is it sends some data, waits to be told it's safe to send more and then repeats. As the server gets further and further away and/or the data your transferring needs more data per second to arrive safely it needs more data sent in each burst. This setting is how much data to send in each burst.

The only reason your computer can max out a gig network single file copy is because of these settings. Modern tcp/ip stacks have automatic ways that dynamically adjust the settings in real time for your connection. There's no real single standard to this, and of course microsoft invented there own they will not share with non-windows computers. The embedded linux is very behind on this, although some new projects by some linux makers have been started to make new base systems so I suspect this will be 1 key area it might get better in the next couple years.

Side note: There's more options to tune a device which are not accessible to us. In the business world for large websites, especially those with streaming video it's a very closely guarded trade secret.

Professional opinion:

This is an area where it takes so much expert knowledge in multiple areas to really do it well that it's always a problem in these types of devices. The companies that make them don't need employees who are experts, and we're snatched up by major companies so nobody is really available to consult to help fix this.

5: I can't use GIG/AUTO for networking

Some common problems that indicate this section will be helpful to you:
  • You can't get a link or ip address is always 169.254.x.x
  • The link light on the pch goes on and off often
  • You get a link but everything else you tried is poor performance
  • You just can't use the auto setting
  • Another section of this post told you to read this.


There are a few solutions to these problems but it's not as easy as giving you a list of things to try.

Wiring:

First thing to check is your wires. gig networking uses all 8 wires, where 10/100 uses only 4. Some low cost cables may not have 8 wires in them and if you move around the cables often, they will eventually break over time.

The second is some green switches can be tricked to output more power and fix up your pch problems. Use a longer than needed cable (1.5meter or longer) and see if that fixes you up. (5 feet for americans). People have reported really good success with this, espeically on problem brands.

Brands to avoid:

Nobody likes spending more money to fix problems but we've just learned there are certain brands that work horrible and cause hundreds of problems with the pch. I also held out replacing some switches but I have to say, night and day difference when I finally did. The switches are still good so sell them, give them to a neighbor or family member, donate them to a local youth group, you don't have to consider it a waste to change it.
  • DLINK
  • Newer budget/home cisco/linksys models. I need to disclaimer this one. It appears the newest models of home cisco made gear are coming up more and more often in peoples problems posts. It's too early to really say if this brand is an avoid, but I'm letting you know that this brand is starting to appear more and more.


brands that seem to work great:
  • Netgear (some models, see wiki)
  • trendnet (accidents choice)
  • tplink
  • HP


BRAND WARNING: As noted in the cisco warning, just because a brand is good today, doesn't mean it will be good tommorrow. Do not use this list as the guide for what to buy. Also ask others what they recently purchased that appears to work great for them before buying.

GREEN Related problems:

Green, lower powered and friendly always on devices is a big trend right now. There are 2 things going on in networking gear, especially newest networking gear to lower the power.
  1. Turning off ports they think aren't in use/connected to something
  2. Lowering the power used on a port when shorter wires are being used



The PCH is also green friendly but sometimes not friendly with the switch. Generally you'll see the no link or link going on and off to indicate your having an issue with the green features. Unfortunately, some of these methods are not technical standards yet so it's causing us headaches.

NOTE: Even htpc forums are starting to be filled with instructions to disable green features on network ports inside computers, it's not just a PCH problem.

Fixes for green related problems (is your switch a GREEN switch?):
  • Managed Switches: Switches you can connect to and adjust settings
    • Adjust any power output settings. These are not POE (power over ethernet setting)
    • Disable Green features of a specific port or the entire switch
    • try the unmanaged options
  • Unmanaged Switches:
    • A user found out if they used a longer cable it forced their switch into a higher power mode that worked. The used a 5 meter cable even though they only needed a .5 meter one
    • Consider replacement for a different brand
    • Add a tiny low cost different brand. Connect it to your existing router/switch and then connect to the pch to this switch.



6: The pch gig speed is not gig throughput/full speed copies

If your copies to drives in your 300 series are slower than 17MB/second, please see #4. You should see at least 17. Keep in mind, the pch doing things like torrent and usenet you have to add the speed they are transfering to your copy to know if your speed is under 17.

There is a lot of arguments about if syabas should be marketing that it supports gig. To networking experts, this is gig but i'm not here to start another argument and you can think whatever you like.

The facts about the PCH and why it's not 70MB or higher:
  • The sigma chipset has an internal bus speed of 250Mbps, It can never go higher than this number. Just like you have certain sized pipes for your street feed, and smaller pipes for showers and even smaller pipes for kitchen and garden hoses. Only so much data can flow.
  • 100mbps/Fast Ethernet networking is 11MB max. Network ports link in speeds, after 100 is 1000 aka gigabit. There is no lower choice to put in the units. If it was advertised gigabit and never wen faster than 11MB I would be all over this with you, but it does transfer faster than 100
  • Windows Server 2003 and XP cannot go 70MB. Most older devices cannot go 70MB. The hardware and software changes to make this happen are just starting to get into embedded chipsets. Sigma has not released a unit with higher performance yet.


Why is it ok that it doesn't do 70MB+ speeds?
  • The highest standards for video you can buy in a retail store is a bluray. The max speed of a bluray is 54mbps including video and audio combined. In copy speed terms this is 6.75MB. Even with 10/100 you can still play blurays over a network connection with room to spare.
  • This is really an issue that's most annoying to users who have their media stored in drives and network copy to them. You want to get your media on the device asap so you can enjoy it and turn off your computer that's doing the copy. There is a hardware limitation in the chipset, as well as all other embedded player chipsets at this time. It's just not possible to go faster. This is starting to improve in new chipsets so future players might be better, hopefully they will still be lower cost.


7: Problem with wireless

Some users have mentioned problems connecting their wireless to some access points. It does not appear to be widespread.

1 user reported they could get it to connect using WPA2 instead of wpa+wpa2. I do not have wireless so I am unsure if this is a mode in the pch settings or their router/access point. I'm thinking it's a pch setting and you should try that first.

8: SMB login with username and password doesn't work anymore

I believe it's mostly synology owners that see this but it's not limited to just synology, that's just the really popular brand here. There is a thread about it for the 200 series, it is the same issue on the 300 series. the thread.

Short answer is enable guest on the nas/computer OR switch to nfs/nfs-tcp which can be secured so only the pch can access just like using a username/password.

9: My 3tb or larger drive is not detected by the pch

Manufacturers are starting to pre-format >2tb drives for old windows xp compatibility.

NOTE: This method may work for USB 3TB and larger drives also. I've seen some posts for other brands where they do the same thing with a usb external and they work with sigma chipsets.

It's pretty simple to fix, but I only have windows so I do not know how for other os's:
- install the drive into a computer
- select start->right click computer->manage
- scroll down to disk management and find the drive
- delete all partitions
- convert the drive to GPT (right click the drive info get to convert to gpt)
- format the drive, if it has an option for sector size, make sure you pick the 4K/4096 option.
- put the drive back into the pch.
- If you plan to install NMT onto the drive, do that before copying any data to the drive as the pch will reformat it for a native linux ext3 formatting.

Alternative (should work on any computer):
- put the drive into a computer
- follow the instructions in this thread to use gparted live to format the drive

Technical explanation:

MBR is how all drives are formated for many many years. But it's limitations do not allow drives larger than 2TB. When 3TB drives came out, 4K sectors (aka advanced format) and GPT was invented to overcome the limitation. Because of how it works, some aged computers and OSs can't support GPT.

Drive makers have come up with a way to trick these old computers and operating systems to work. There is a couple methods to do this but one of them is the reason your having the problem. It's only friendly on old windows computers and the pch is unable to detect and convert it for you at this time. You just need to remove the "trick" drive makers are using to stop returns of good drives and redo the partition table to modern >2TB standards.

10: My 3TB or larger drive does not work when I use the tether/slave usb mode of my a series model

A slave chip update to support GPT drives of 2tb or larger has been put out for testing. You'll find the test in this thread: http://www.networkedmediatank.com/showth...#pid595385

Please read and follow everything carefully, it's not a firmware update to support this.

NOTE: Deus_Ex_Machina discovered an issue with the Marvell USB 3.0 controller. Unclear if this chipset just has problems on it's own or some slight compatibility mode with the udpate. If you have that chipset in your computer, you may find usb 2.0 ports work better for you while it's investigated for chipset problem or a compatibility fixable bug.

11: I have a WD Green Drive installed in my player

Some issues you may be experiencing:
  • Drive is unusable after the PCH was in standby, sometimes requiring power off and on the machine several times to make it work.
  • Playback issues with lower bitrate videos and music stored on your drive
  • Incredibly slow browsing of files on the drive
  • Very Sluggish jukebox or NMJ
  • Starting to play a video seems to take a longer time than it should.


The Spindown setting in the WD drive is not friendly with media usage needs. Besides making a slower PCH experience, it actually wears the drive out faster.

The Tivo community put together a little boot disk an instructions for how to adjust the idle timeout higher. You'll need to move your drive to a computer. If your unable too, perhaps your companies IT team or friend with a desktop could.

Instructions on the TV Site

Special thanks to fsmit for originally posting this

An additional fix might be with older revisions of these drives. some of the sata3 models have buggy backwards compatibility for other sata controllers. If your model supports the jumpers, pins 7&8 will force it into the older and compatible with the pch sata mode. You may need to do this AND the above timer fix.

Technical Reason:

1 of WD Green methods to reduce power of a drive is to keep turning it off when not in use. Depending on when you purchased the drive, this time is anywhere from 1 to 8 seconds. So the few seconds your reading the screen and the drive has already spun itself down. In order to access the drive again, this means you first need to wait for it to spinup fast enough to start reading it, and then the delay to do what your requesting.

Some models can take a really long time to spin back up and this is why the pch thinks the drive is missing. It's taking longer than the pch is willing to wait for it.

This change raises the drive timeout from seconds to an hour. Some models it'll completely disable it. This allows the PCH to control when it's ok to spin down.

More information on this problem can be found at this web report. A link to WD saying "this drive isn't good for every type of usage" is in that article

NAS NOTE:

This can have a huge impact on raid array based nas units. You should check with your NAS maker or their forums if doing something similar to this recommendation would increase your nas success and speed.

12: My PCH is really slow

Symptoms:
  • Your PCH interface is really slow and doesn't sound like others on the forum experience it.
  • After awhile (a couple hours) the interface begins to speed up.
  • you installed NMT
  • playback of videos just after a reboot/boot seems to be unreliable and stutters a lot but later in the day or the second movie plays just fine.


Problem:

there is a myihome server running which syncs your media files with other upnp/dnla servers and devices. It can take many hours depending on the size of your media library to finish. 99.9999999% of users do not use this feature and you should disable it. There is no method on the screen to disable it. Refer to the following thread for simple instructions: http://www.networkedmediatank.com/showth...?tid=64946

NOTE: It is unknown if you need to keep disabling this after nmt upgrades. Chances are, yes you need to keep disabling it.
Find all posts by this user
Add Thank You Quote this message in a reply
[+] 24 users say Thank You to accident for this post
12-30-2012, 12:23 PM (This post was last modified: 12-30-2012 12:24 PM by accident.)
Post: #2
RE: Common 300 series problems and solutions.
Updated for #12: Your PCH is slow.

It was discovered myihome server is installed and active by default with nmt. There is nothing on teh screen to disable it and it'll try to sync with other media devices and servers. this results in a very slow pch and playback issues just after a reboot for 1+ hours.

If you use NMT, everyone should disable it. I reported it to syabas.
Find all posts by this user
Add Thank You Quote this message in a reply
01-09-2013, 08:20 AM
Post: #3
RE: Common 300 series problems and solutions.
#10 updated for usb slave of larger GPT partitioned drives.. (3tb+ slave mode)
Find all posts by this user
Add Thank You Quote this message in a reply
01-15-2013, 09:25 PM
Post: #4
RE: Common 300 series problems and solutions.
Updated teh WD section to include an article of a third party saying the same thing (and links to WD's site with their "oh it's not for everything") response.
Find all posts by this user
Add Thank You Quote this message in a reply
01-20-2013, 04:56 AM
Post: #5
RE: Common 300 series problems and solutions.
* Added marvell usb 3.0 controller issue found by Deus_Ex_Machina (usb slave mode)
* removed the note to PM werner for the 3tb+ test. the update is that test completed.
* Updated WD green drive to also mention the pin 7&8 jumper for sata 3 models that are older and may be buggy detecting a non-sata3 controller in the pch.
* adjusted the gig networking part to mention the oversized cable may fix random drops with using a green switch.
Find all posts by this user
Add Thank You Quote this message in a reply
02-01-2013, 04:11 AM
Post: #6
RE: Common 300 series problems and solutions.
EXCELLENT thread -- keep up the good work. We all appreciate it.

Nicely detailed and easy to follow explanations and problem resolution.

Party1
Find all posts by this user
Add Thank You Quote this message in a reply
02-04-2013, 04:45 AM
Post: #7
RE: Common 300 series problems and solutions.
Instructions for telnet with OSX
http://m.wikihow.com/Use-Telnet-on-Mac-OS-X

[Image: all-banner.jpg]

MacPro(2008) running MacOSX 10.6.8 / C-200 with Apps / YAMJ+evZap+Legion Mod / DroboFS 5 Bay (NAS) / Cat6 / Onkyo TX-NR609 / Panny 65VT30

Find all posts by this user
Add Thank You Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  HDD instal problems (WD) Flix 5 212 04-10-2014 08:30 PM
Last Post: szkzsolt
  big problems Sje 1 207 04-04-2014 12:21 AM
Last Post: Szunyi84
  Problems with ethernet wireless adapter pingone 0 334 11-25-2013 06:46 PM
Last Post: pingone
  A-300 harddisk problems ghostpost34 2 599 11-17-2013 01:57 PM
Last Post: ghostpost34
  having problems with C300 pace508 3 621 10-30-2013 08:11 PM
Last Post: pace508
  Problems after the installation of new firmware of A 300 dionisis 2 827 10-01-2013 08:55 AM
Last Post: dionisis
  Wifi problems with A300 mikropoulos 0 725 05-23-2013 01:49 PM
Last Post: mikropoulos
  A-300 disk problems ghostpost34 1 886 03-22-2013 05:07 PM
Last Post: ladra
Exclamation A300 various common issues and problems theother 33 5,933 01-27-2013 03:00 AM
Last Post: accident
  wifi problems kingevil 14 1,226 12-24-2012 12:11 AM
Last Post: ambrosejga

Forum Jump: