Streaming bits…

Flush Cache OS X

Decided to post this here, since I need it too often:

dscacheutil – flushcache

Time Capsule Firmware 7.4.1 problems

Well, I updated my TC this evening to firmware version 7.4.1 and had issues with a Macbook @ OS X 10.5.6 reconnecting to the TC.  Couldn’t see it at all.  Also an older iBook G4 @ 10.4.4 could no longer see the wifi network, but my Macbook @ 10.4.11 could see and connect to it just fine (sometimes).

I discovered others were having similar issues so I had to downgrade back to 7.3.2 and all is fine again.  I’ll see what other posts turn up.  The very first move to 7.4.1 and the TC had trouble restarting, so I tried unplugging for about 1 minute and then replugging in, not much luck there.

Downgrading was the only answer for me.  If you get to the option Base Station->Upload Firmware, that is where you can downgrade to a previous version firmware.  Nice option,btw!!

FreeNAS RAID-5, the Saga Continues…

What a nightmare at this point.  I am having a real hard time getting access back to my RAID-5.  I’ve rebuilt this RAID-5 a half dozen times now.  The issue is when I try to set a mount point back to the rebuilt RAID, I get a message about the “/mnt/bigdisk” (the original mount point of my RAID-5) not being properly dismounted and then FreeNAS panics and we go into a continuous reboot.

So, at this point I’m confident that the data is still intact, but I can’t figure out the process to get back to it.  I’ve moved the 3 RAIDed drives to another system, installed the most recent version of FreeNAS and have tried to access it and I can’t get to it.

So, I’ve downgraded back to an older version of FreeNAS trying to see if that will help, but now there are complaints of wrong disk size: expected vs. real.

Finding the time to deal with it is the hardest part at this point.

I’d certainly appreciate any comments in this area that may be helpful to me and the RAID-5 situation.

Clients Speak Out

Hi,

Please leave a comment about your experience with Capnet / Lake Mary Macs.

Continued trouble with Free NAS

My Free NAS server decided to reboot and guess what?  The annoying truncated device name issue appeared again.  I’m rebuilding the RAID 5 for the 3rd time now.  Once it’s back I will copy all of this data over to the new  Drobo.  Then I will upgrade the Free NAS software and see if things appear any better.   At this point once the RAID 5 is rebuilt and even if I correctly restart the server I get the same “truncated device name” issues.

Then I have to pull drive 0 (or 1 if you’re not an array based programmer) of the RAID 5 and format it with a MS DOS partition so that the NAS server will pick up the drive again.  Then I insert it from the RAID Management interface of the Free NAS software.  Then it rebuilds fine and I can re-mount the mount points.  Don’t reboot because it will go bonkers again!!

More to come…

Drobo Installed and ready to go…

My Drobo is LIVE now!  It has to be one of the easiest things to install and get going.  I was going to post a step-by-step guide, but it’s so easy there’s really no need for it.

Here are the basics though:

1. Un-pack the Drobo and DroboShare.
2. Stack the Drobo on the DroboShare.
3. Connect 1ft USB cable from Drobo to DroboShare.
4. Connect ethernet from DroboShare to your network (Switch/Router), it will DHCP for an IP by default.
5. Connect the Y-power cord to both the Drobo and DroboShare, then to the power brick cord.
6. Insert your drives into the empty bays on the Drobo.
7. Plug in your power brick – recommend plugging into a battery backed UPS.
8. Install the software from the Resource CD.
9. Launch the Drobo Dashboard (After software install).
10. Configure your Drobo, let it format and you’re done!

I’ve been copying my Music over the weekend and will continue to load mine with all types of Media.  I used 3 x 1 TB drives to get 1.8TB of formatted usable space when all was done.  I have an empty bay so I can add a drive at another time.  I’ll probably get one of the newer 1.5TB drives so I can hopefully get about 2.8TB out of the 4 drives.

Stay tuned for more about the Drobo and DroboShare.

Free NAS annoyance, again…

Last night there was a general power outage to about 1,000 residents and thankfully all my APC UPSes were acting in good manor and kept my private office NOC running long enough for me to gracefully bring down all the servers. Well, the recently recovered NAS box (powered by Free NAS) was powered off correctly, but upon start up I encountered the NOW annoying “WARNING: device name truncated c9c9c9c9c9c9c9c….” and then we get caught in a reboot loop.

Remember in a previous post of mine I had to basically determine which drive was causing the issue at start-up. I’m now wondering if this is a bug in the Free NAS version I have. I’ll get to the recovery procedures later and report back. I guess I’ll upgrade to a more recent version to see if this has been fixed.

In the meantime I’ve powered off the NAS box (RAID-5) and it awaits intervention.

Drobo ordered!

I’ve ordered my DROBO, it will be here this week. I plan to document the install/setup process here for others to see.
I ordered it from newegg.com and it has a $50 rebate with it. I also ordered the share module.
stay tuned…

Capnet, LLC launches LakeMaryMacs.com and OrlandoMacs.com

Although still in the build out phase of content, Capnet, LLC has launched two new websites to help sprout business dedicated and devoted to Apple Computer Sales, Upgrades, Support and Repair.

Although Capnet is based out of Lake Mary this consulting firm caters to all of Central Florida. You can reach the new website at www.lakemarymacs.com

FreeNAS RAID-5 shines!

Talk about scary… Walked into the server room and saw horrible messages screaming by on my FreeNAS console stating WARNING: device name truncated (c9c9c9c9c9c9c9c9c9c9c9c9a9a9a9a9a9a9)

Checked the network for all NFS / AFP / SMB connectivity and all was GONE!! The system just get rebooting over and over. Well, Free NAS really shined through on this one.

Before I get to the solution, here’s my setup. 2U server w/ 1 bootable IDE drive and 3 x 400 GB IDE drives for the RAID-5. OK, enough already, here’s the solution.

I had to first determine which HD was causing the issue, so upon a reboot I paused the boot-up screen while booting in logging mode. I used the brute force method, but it worked. Brute force method goes something like this….

RAID-5 drive 3, swap with a new 400 GB drive, reboot FreeNAS… still had the issue… plug back in old drive.

RAID-5 drive 2, swap with the new drive, reboot FreeNAS… still had the issue… plug back in old drive.

RAID-5 drive 1, swap with the new drive, reboot FreeNAS… guess what, FreeNAS picked up and started booting. So, drive 1 went bad.

Once you have a booting system, log into the GUI and do an insert of the new drive into the RAID-5 and that initiates a rebuild of the RAID-5. Yes even an 800 GB RAID-5 takes all night to rebuild.

Once you rebuild, you can remount the RAID-5 and all should be fine.

It worked well for me and my faith continues strong in FreeNAS.