<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Jeff Blogs &#187; errors</title>
	<atom:link href="http://jeffblogs.com/tag/errors/feed/" rel="self" type="application/rss+xml" />
	<link>http://jeffblogs.com</link>
	<description>Connecting the Dots One Prime Number At a Time</description>
	<lastBuildDate>Mon, 16 Apr 2012 06:22:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Troubleshooting NetGear ReadyNAS Problems</title>
		<link>http://jeffblogs.com/2010/03/troubleshooting-netgear-readynas-problems/</link>
		<comments>http://jeffblogs.com/2010/03/troubleshooting-netgear-readynas-problems/#comments</comments>
		<pubDate>Tue, 02 Mar 2010 22:55:14 +0000</pubDate>
		<dc:creator>Jeff Summers</dc:creator>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[drive]]></category>
		<category><![CDATA[errors]]></category>
		<category><![CDATA[failure]]></category>
		<category><![CDATA[NetGear]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[ReadyNAS]]></category>

		<guid isPermaLink="false">http://jeffblogs.com/?p=714</guid>
		<description><![CDATA[Recently I wrote about having severe problems with the NetGear ReadyNAS. These problems were causing the device to fall off the network requiring a hard re-boot to make it available on the network again. The hard reboot was bad enough but the subsequent media check meant the reboot time would stretch into hours before service [...]]]></description>
			<content:encoded><![CDATA[<p>Recently I wrote about having <a href="http://jeffblogs.com/2010/01/severe-problems-with-the-netgear-readynas/">severe problems with the NetGear ReadyNAS</a>.  These problems were causing the device to fall off the network requiring a hard re-boot to make it available on the network again. </p>
<p>The hard reboot was bad enough but the subsequent media check meant the reboot time would stretch into hours before service was restored.  Not exactly the kind of customer experience I was hoping for when I bought the device.</p>
<p><span id="more-714"></span>Things were getting so bad that I began researching a replacement device that I could purchase to replace the NetGear ReadyNAS.  In the ReadyNAS Pro I have six 1.5 TB drives configured as a RAID 5 enclosure.  That gives me 7.5TB of online storage.</p>
<p>I have been diligent in updating the firmware on the device and give it regular cleanings with compressed air so as far as I was concerned I was being diligent in managing the device.  Despite my best efforts, the device continued to cause me problems.</p>
<p>After yet another hard re-boot my frustration level had reached new heights.  I had about reached the end of my troubleshooting patience when for some reason I decided to change the configuration.</p>
<p>Up to this point I had configured the ReadyNAS Pro with two gigabit Ethernet connections directly to a Cisco switch.  I seemed to remember that I added the second Ethernet connection just recently.  I wondered if perhaps I had a bad cable.</p>
<p>I removed one gigabit connection and waited.  After two weeks I did not have a single drop off by the device.  I wondered if perhaps I had a bad cable. I swapped Ethernet cables and again left the device to run.</p>
<p>Another two weeks went by with no issues with the ReadyNAS device.  It did not appear that the problem was cable since I had used two different cables.  I decided to see if the problem was connecting both Ethernet ports.  I plugged both cables into the device and restarted the ReadyNAS.</p>
<p>Within two hours the problem appeared and the device disconnected itself from the network requiring a hard boot.  After several hours rebuilding and checking the drives the ReadyNAS was back on line.  </p>
<p>This time I am using just a single Ethernet port on the ReadyNAS device.  While I might theoretically only be getting half the throughput in this configuration it is a lot more stable and that is better than raw speed any day of the week.</p>
<div class='wb_fb_bottom'><div style="float:right;"></div></div><div class='wb_fb_comment'><br/></div>]]></content:encoded>
			<wfw:commentRss>http://jeffblogs.com/2010/03/troubleshooting-netgear-readynas-problems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Severe Problems with the NetGear ReadyNAS</title>
		<link>http://jeffblogs.com/2010/01/severe-problems-with-the-netgear-readynas/</link>
		<comments>http://jeffblogs.com/2010/01/severe-problems-with-the-netgear-readynas/#comments</comments>
		<pubDate>Sun, 31 Jan 2010 23:21:39 +0000</pubDate>
		<dc:creator>Jeff Summers</dc:creator>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[drive]]></category>
		<category><![CDATA[errors]]></category>
		<category><![CDATA[failure]]></category>
		<category><![CDATA[NetGear]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[ReadyNAS]]></category>

		<guid isPermaLink="false">http://jeffblogs.com/?p=700</guid>
		<description><![CDATA[It has been nearly five months since I bought a Net Gear ReadyNAS Pro network RAID array. For most of this time the device has worked flawlessly. I am able to access my files across my Ethernet network using a variety of clients including Windows XP, Windows Vista, Macintosh OS X, and Linux. It is [...]]]></description>
			<content:encoded><![CDATA[<p>It has been nearly five months since I bought a <a href="http://jeffblogs.com/2009/09/net-gear-readynas-pro/">Net Gear ReadyNAS Pro</a> network RAID array.  For most of this time the device has worked flawlessly.  </p>
<p>I am able to access my files across my Ethernet network using a variety of clients including Windows XP, Windows Vista, Macintosh OS X, and Linux.  It is hard to express how great this system has been.</p>
<p><span id="more-700"></span>Where I used to burn DVDs and shuttle USB drives from box to box in order to share data between computers now it is as simple as logging onto the ReadyNAS and accessing the information.</p>
<p>Not only is the information always available but it has given me the added benefit of being able to maintain one copy of the information instead of having multiple versions stored on various computers on the network.</p>
<p>The ReadyNAS has been so bulletproof that it has nearly become invisible.  That is the greatest compliment a network device can receive.  It works so well that people just forget it is even there.  It is as reliable as turning on a light switch.</p>
<p>Of course making that statement I immediately jinxed myself to a life of dealing with problems that cannot be resolved.  Such has become the case with the ReadyNAS Pro.  </p>
<p>Recently the device downloaded a new version of the firmware and waited patiently for a reboot.  The rain storm that blanketed Arizona last week offered the perfect opportunity to reboot.  A power outage took down the entire network and I spent the better part of an evening recovering all the devices.</p>
<p>The ReadyNAS booted and went through a diagnostic check due to the power outage.  On an array of six 1.5TB of data that can take a long time.  When the system finally came up things seemed to be working.</p>
<p>The following day the ReadyNAS suddenly just stopped working.  The blue power light on the front of the box was lit but the system was unresponsive.  It required removing the power plug from the wall for a minute before the system would reset.</p>
<p>Upon restoring power it went through another system check taking over an hour to come up.  Approximately two days later the same situation occurred with the ReadyNAS having to be powered off by removing the cord.</p>
<p>This has since happened six times in a week.  My first inclination was the unsettled weather had caused some problems.  In order to eliminate that, I bought an Uninterruptible Power System which I will review at a later date.</p>
<p>After installing the UPS the ReadyNAS seemed to be working and I thought the problem was resolved.  Today the ReadyNAS again hung requiring yet another unplug and subsequent data check.</p>
<p>I began researching the problem and found I <a href="http://www.readynas.com/forum/viewtopic.php?f=21&#038;t=35923&#038;start=0">was not the only one</a> having this problem.  According to the support forums there are a number of Net Gear users having similar issues.  So far the company has not found a solution.</p>
<p>Some are suggesting it is a configuration issue but that seems implausible given the number of people reporting the problem.  Others are suggesting RAM but that too does not seem accurate since many of the people reporting this issue including myself have not upgraded or changed the factory memory.</p>
<p>For now I’ll continue to monitor the issue and in the mean time I will need to find a replacement NAS system that is more stable. I cannot afford to use this as a storage device if it continually fails.  I’ll keep you posted as this progresses.</p>
<div class='wb_fb_bottom'><div style="float:right;"></div></div><div class='wb_fb_comment'><br/></div>]]></content:encoded>
			<wfw:commentRss>http://jeffblogs.com/2010/01/severe-problems-with-the-netgear-readynas/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>IX Web Hosting, Just Say No!</title>
		<link>http://jeffblogs.com/2008/07/ix-web-hosting-just-say-no/</link>
		<comments>http://jeffblogs.com/2008/07/ix-web-hosting-just-say-no/#comments</comments>
		<pubDate>Wed, 02 Jul 2008 00:19:24 +0000</pubDate>
		<dc:creator>Jeff Summers</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[errors]]></category>
		<category><![CDATA[web hosting]]></category>

		<guid isPermaLink="false">http://myexperimentalweb.com/?p=62</guid>
		<description><![CDATA[I have previously lamented about my struggles with IX Web Hosting who I am currently using. When I wrote in March I explained that there may be a bit of downtime to my sites due to being moved to a new server. My sites had to be migrated because the server was still using some [...]]]></description>
			<content:encoded><![CDATA[<p>I have previously <a href="http://jeffblogs.com/2008/03/a_little_bit_of_down_time.html">lamented</a> about my struggles with IX Web Hosting who I am currently using.  When I wrote in March I explained that there may be a bit of downtime to my sites due to being moved to a new server.  My sites had to be migrated because the server was still using some very dated software and I needed something that was actually published this century.  The server migration went fairly well or so I thought.  As I started to dig into the configuration I found <a href="http://jeffblogs.com/2008/04/a_freakin_nightmare.html">modules missing</a> that made my blog unavailable.  This was a simple problem but it took IX Web Hosting a week to get things straightened out.  Finally I was back up and I tried to forget the problems I had had.</p>
<p><span id="more-62"></span><br />
Things had gone fairly well since then until <a href="http://jeffblogs.com/2008/06/wanted_web_hosting.html">Friday June 13th</a>.  At that point I was frustrated enough that I had come to the conclusion that I needed to make a change to my hosting company.  I began to research the various options at my disposal.  At the same time I was maintaining my IX Web Hosting account and the sites hosted there.  I figured that I had a little time so that I didn&#8217;t make a mistake and rush into something I would regret.  Besides, it wasn&#8217;t like my sites were down or anything right?  Yeah I really should not have made that last statement.<br />
This past weekend I got up and turned on the computer.  I was going to post a blog entry here and one on <a href="http://diarydiehard.com">Diary of a Diehard</a>.  I opened a browser window and navigated to my web site.  Instead of the page I was given an error message claiming that the site was unavailable.  Oh great, here we go again I thought.  At first I considered maybe this was a local problem.  I rebooted my computer, my router, and my cable modem.  No such luck, I still could not get to my sites.  Maybe this was a DNS problem.  I instead entered the IP address to my sites expecting to see the page load.  Again I received a network error.  I went to the IX Web Hosting site and attempted to log into my control panel.  I was again presented the network error page.  This was strange.  I went to the support center and entered a problem ticket.  Like usual several hours later I received a reply stating that the server had some emergency problem and that administrators were working on it.  I opened a chat window to talk to a representative to see how long this outage would last.  I was told there was a problem with a RAID controller and that there was an ETA of a couple of hours.  I was irritated that IX Web Hosting didn&#8217;t have on-site spares but a couple more hours wouldn&#8217;t kill me.<br />
I waited rather impatiently for the sites to return.  After two hours I tried again and got the same error message.  I understand that things sometimes happen so I was willing to give them the benefit of the doubt.  I promised myself I would double their allotted time before requesting status.  Two more hours came and went and my sites were still unavailable.  I went back to the chat client and asked for a status update.  I was told the server had drive issues as well as RAID and would only boot into safe mode.  The new ETA was that it would take 4 hours for service to be restored.  This would mean that my sites would be unavailable for 12 hours.  I was not happy but there was not much that I could do.  I found other computer work to do to kill the time until I could get on and update my sites.  I was now sitting on several entries that needed to be posted and data that needed to be updated.<br />
At four hours I checked the sites and they were still unavailable.  I decided I would let it go another couple of hours.  At that time I checked again and continued to receive the error message.  I went back to the chat client for yet another status.  The problem ticket I had initially opened had still not been updated so it was clear that system was not getting me anywhere.  The technician at this point had no idea how much longer this was going to take and suggested that I wait until morning; great, a whole day of outage without an end in sight.  I was seriously ticked off.<br />
The next morning I checked and what a surprise, my sites were still down.  I went back to the chat client and again asked for an update.  I was told 2-4 hours.  Seriously, I was told that again.  I explained that I didn&#8217;t really trust their estimate and asked if they could please just put my sites on a different server while they continued to troubleshoot.  I was told that was not possible.  They cannot move me until they get the server fixed.  They have no idea why they can&#8217;t move me; they just know that can&#8217;t happen.  So there I sat for another 4 hours waiting for a miracle to happen.  The miracle didn&#8217;t show up and I was still down.  I went back to the chat window again and explained that my sites had now been down a day and a half.  There was a canned apology along with an estimate that it would be up in 4 hours.  I don&#8217;t have to tell you that those hours blew by and my site was still unavailable.  I went back to the chat window and demanded that something be done.  In this amount of time you could drive from the IX Web Hosting data center to Dell, buy a server, drive it back to the data center, configure it, and get it on the network.  There is absolutely no way it should take this amount of time.  I was told that the administrators were doing everything they could and that it could be several hours before it was available.  I asked for a definition of &#8220;several&#8221; and was told up to 12.  I went to bed last night thinking at the worst case the sites would be restored by 10 AM which was 2.25 days since I found them down.  Of course 10 AM came and went and the sites are still not available.<br />
This is beyond ridiculous.  When I protested that this downtime went well beyond the 99.9% uptime guarantee I was sent to billing who provided me with a credit of 2 months on my service contract.  What good is that going to do me?  Why do I need to extend my contract when they can&#8217;t even keep a simple server up?  Not only that but the promised credit was not posted to my account so I have no idea where this actually went.  It is now imperative that I find an alternative for web hosting.  The technicians at IX Web Hosting obviously have no clue what they are doing or are not empowered to solve the problems they encounter.  The customer service is grossly understaffed and incapable of fixing anything.  Further they do not seem to know what the administrators are doing and set false expectations with the customer.  What they lack in customer focus they make up for with rudeness.  I cannot put into words how bad their service is.  If you are a current customer I suggest monitoring your service closely.  If you are considering web hosting I suggest you look elsewhere as the aggravation is not worth the cost savings you may receive.</p>
<div class='wb_fb_bottom'><div style="float:right;"></div></div><div class='wb_fb_comment'><br/></div>]]></content:encoded>
			<wfw:commentRss>http://jeffblogs.com/2008/07/ix-web-hosting-just-say-no/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

