Archive for December, 2007

ReadyNAS NV+ Expansion

Within the last week or so, I’ve gone back through my kids DVD collection and ripped a good number of videos for them. Since they are on young side, I find the DVDs will last longer if the kids don’t touch them. This added many Gigabytes of data to my NAS, though. Initially, I bought two 500 GB Seagate ES series drives. This gave me somewhere north of 450 GB of capacity, but after this recent ripping fest, I was down to around 60 GB free.

Newegg.com had the same model of Seagate ES drive that I had originally bought for $149.99, and while I know I could have gotten away with a lower end drive and saved about $25 or so, I stuck with the ES. The ES drives have a very good warranty also, so that’s a plus.

Anyhow, the drive arrived today. Around 4PM, I inserted it into the NV+ and within a minute or so, it had started the “Initialization” process. It was kind enough to warn me that this would take several hours. During the initialization process, the NV+ was still actively handling requests, but the next step required it to be off-line. Around 8PM, I see that it had completed that part of the process and was waiting for me to reboot the NV+ to perform the expansion. After the reboot, it checked the disk, which took a bit, then the status screen changed to “Expanding… Expansion: 0.0%”. After probably 30 minutes of it sitting on this status, I started to panic! I went to the Infrant website and started looking around. Now, weeks ago, I had installed the latest 4.00 release software. Low and behold, I see that they have released another new version. In the release notes for this new version, I saw this gem:

Fixed X-RAID volume expansion failing when there are more than a million files in the volume. This problem affected volume check as well.

Finding this didn’t help the panic mode I had entered, as I was performing this very operation. I did some more searching around the forums and couldn’t find anyone complaining of this exact issue.

About another 15 or 20 minutes passed and I noticed it started counting up, so I felt relieved. It’s up to 96.0% complete now, so chances are it will be done in the next half hour. In retrospect, the release notes said that this problem affected the volume check as well, so I should have realized that I had already passed that part of the expansion process.

In my case, I was expanding a two drive system consisting of 500 GB drives to a three drive system and it looks like the entire process (including initialization)  took about 8 hours. I imagine that if you are dealing with TB drives it would probably take twice as long for the expansion portion.

So, if you plan to expand your drive, be aware that it will be off-line for several hours, but in the end you should have more storage with very little work, just a bit of tense waiting… 🙂

Update: My expansion completed a bit shy of the 8 hour mark. I now have 907 GB of redundant storage on my NV+.

December 20, 2007 at 11:58 pm Leave a comment

Follow up on my issues with FWD

I mentioned issues in a previous post with my FreeWorldDialup connection.  I’m not sure if the issues I see are problems with FWD, or between my ISP and theirs, but the below is a good example of the issues I have been seeing.  Note that I did have one instance of lag at 21:00:31 tonight with sipphone.com, but no where near the issues that I have with FWD.

Dec 8 02:35:27    chan_sip.c:15460 in sip_poke_noanswer: Peer ‘FWD’ is now UNREACHABLE! Last qualify: 71
Dec 8 02:35:37    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (71ms / 2000ms)
Dec 8 03:58:48    chan_sip.c:15460 in sip_poke_noanswer: Peer ‘FWD’ is now UNREACHABLE! Last qualify: 92
Dec 8 03:58:58    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (71ms / 2000ms)
Dec 8 04:17:04    chan_sip.c:7326 in sip_reg_timeout: — Registration for ‘874551@fwd.pulver.com’ timed out, trying again (Attempt #2)
Dec 8 04:24:24    chan_sip.c:7326 in sip_reg_timeout: — Registration for ‘874551@fwd.pulver.com’ timed out, trying again (Attempt #1)
Dec 8 05:27:09    chan_sip.c:15460 in sip_poke_noanswer: Peer ‘FWD’ is now UNREACHABLE! Last qualify: 70
Dec 8 05:27:19    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (72ms / 2000ms)
Dec 8 07:56:34    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Lagged. (2071ms / 2000ms)
Dec 8 07:56:44    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (71ms / 2000ms)
Dec 8 08:50:52    chan_sip.c:15460 in sip_poke_noanswer: Peer ‘FWD’ is now UNREACHABLE! Last qualify: 71
Dec 8 08:51:11    chan_sip.c:7326 in sip_reg_timeout: — Registration for ‘874551@fwd.pulver.com’ timed out, trying again (Attempt #1)
Dec 8 08:51:30    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (71ms / 2000ms)
Dec 8 08:51:32    chan_sip.c:7326 in sip_reg_timeout: — Registration for ‘874551@fwd.pulver.com’ timed out, trying again (Attempt #2)
Dec 8 09:04:35    chan_sip.c:15460 in sip_poke_noanswer: Peer ‘FWD’ is now UNREACHABLE! Last qualify: 71
Dec 8 09:04:45    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (85ms / 2000ms)
Dec 8 09:24:51    chan_sip.c:15460 in sip_poke_noanswer: Peer ‘FWD’ is now UNREACHABLE! Last qualify: 70
Dec 8 09:25:01    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (71ms / 2000ms)
Dec 8 11:03:13    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Lagged. (2132ms / 2000ms)
Dec 8 11:03:23    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (78ms / 2000ms)
Dec 8 12:04:33    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Lagged. (2965ms / 2000ms)
Dec 8 12:04:43    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (108ms / 2000ms)
Dec 8 13:44:48    chan_sip.c:7326 in sip_reg_timeout: — Registration for ‘874551@fwd.pulver.com’ timed out, trying again (Attempt #1)
Dec 8 18:22:26    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Lagged. (3072ms / 2000ms)
Dec 8 18:22:36    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (73ms / 2000ms)
Dec 8 18:52:42    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Lagged. (3072ms / 2000ms)
Dec 8 18:52:52    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (72ms / 2000ms)
Dec 8 19:49:58    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Lagged. (2071ms / 2000ms)
Dec 8 19:50:08    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (71ms / 2000ms)
Dec 8 20:09:11    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Lagged. (2072ms / 2000ms)
Dec 8 20:09:22    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (72ms / 2000ms)
Dec 8 21:00:31    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘sipphone.com’ is now Lagged. (2132ms / 2000ms)
Dec 8 21:00:41    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘sipphone.com’ is now Reachable. (133ms / 2000ms)
Dec 9 00:08:47    chan_sip.c:15460 in sip_poke_noanswer: Peer ‘FWD’ is now UNREACHABLE! Last qualify: 71
Dec 9 00:08:58    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (1072ms / 2000ms)
Dec 9 00:32:03    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Lagged. (3072ms / 2000ms)
Dec 9 00:32:13    chan_sip.c:12336 in handle_response_peerpoke: Peer ‘FWD’ is now Reachable. (72ms / 2000ms)

December 9, 2007 at 1:07 am 1 comment

Apple vs. NBC: Now it’s personal!

Ok, so today the feud between Apple and NBC affected me, personally.  Earlier this year, I purchased season passes to two of my favorite shows from iTunes.  Last night, new episodes of Monk and Psych were aired.  What was different this morning vs. past Saturdays after new airings of these shows?   I didn’t get the usual email from Apple notifying me that I have new episodes available for download.

In addition, I’ve not had any credit added back to my iTunes account.  So, I’ve effectively pre-paid for episodes that are likely to never arrive.  Part of me wonders if Apple pre-paid this money to Universal.  I’m sure Apple will make things right one way or another, but I really just want to watch the shows that I’ve legitimately paid for.

Fortunately, when you go to the “Watch Full Episodes online” link on USA Network’s website, it shows that both the new episodes of Monk and Psych will be available on Monday.   That’s not nearly as convenient as watching them via AppleTV, but it is something.  (And yes, I do know that there is an alternative distribution network out there…)

December 8, 2007 at 10:51 pm Leave a comment

Almost free Phone Service, take two

NEWSFLASH!
Just tonight I found out that the ipKall and FreeWorldDialup steps that I used in my previous write-up on ultra cheap phone service could be skipped with better quality results…

sipphone.com / gizmoproject.com
This website appears to be the corporate side of the Gizmo Project. Think of something like Skype. I looked at them months ago, but quickly dismissed it. My initial take was that this was a Instant Messaging client with Voice capabilities. I didn’t realize that you actually got a real SIP account with Gizmo, which makes it really cool. Basically, you can sign up for a Gizmo account (download and install Gizmo to sign up – you can uninstall Gizmo after you have your account), then sign into the sipphone.com website. There, you’ll see your SIP phone number. Mine started with 1-747, so yours will probably too. Log into your GrandCentral account and add a new number (Under the Settings tab, then the Phones menu item on the left). Select the Add/Edit Number link (far right on the screen) and add your Gizmo account. For the phone number, use the 1-747 number you saw when you sign into sipphone.com. Next, set your PBX or hardware device to receive calls from Gizmo. They have these instructions for configuring your hardware device:

SIP Proxy: proxy01.sipphone.com:5060
STUN server: stun01.sipphone.com:3478
Username: Your SIP number, found by dialing ** in Gizmo
Password: Your password
Codecs: iLBC, GSM, g711a, and g711u (Gizmo Project uses other codecs as well, but you won’t find them in your hardware settings)

Now, Gizmo doesn’t offer outbound services, so you won’t be able to make calls with this account. Using a PBX package like Askozia, however, and you are all set. Just set this up as another provider and tell it which extension (or extension group) to forward calls to. You’ll still need another provider for outgoing calls, but there are several of those around that do a good job.

Quality
Near the top of this entry I mentioned this gives better quality results. I haven’t done enough testing to be sure yet, but in theory it should be better. With my previous config, when someone called GrandCentral, GrandCentral then dialed out on the public phone network to the ipKall.com phone number, which digitized the conversation and forwarded that via SIP to FreeWorldDialup, which forwarded it to my PBX. With the above described configuration, a call to GrandCentral gets digitized at the first hop and goes directly to a SIP account at Gizmo, where it is forwarded to my PBX. By removing the intermediate step across the public phone network, call quality should be a bit better.

In addition, by looking at my PBX logs, I see that FreeWorldDialup is unreachable many times a day. In fact, I just went to look at the logs to see if I could quantify the problem a bit, but found that with all the configuration changes I’ve made, the logs have been cycled out leaving me only about the last two hours to see. Even with that, my FWD account is unreachable as of about 4 minutes ago. I don’t know if Gizmo is any more reliable than FWD, but if they are, that just icing on the cake!

December 8, 2007 at 1:45 am Leave a comment


Calendar

December 2007
S M T W T F S
 1
2345678
9101112131415
16171819202122
23242526272829
3031  

Posts by Month

Posts by Category