mattgadient.com

Informational blogging by Matthew Gadient.

Browsing Posts published in May, 2010

Installing Snow Leopard on the H55M-UD2H is relatively easy. I’m using an i3, but due to the lack of full support (no Apple Macs use it at present), I’d suggest going with the i5 which has recently gained some support.

I have provided a DSDT which I finished most of – it has all the basic fixes, and adds USB support properly so that 10.6.3 doesn’t choke – the only thing left to add is the sound (which you’ll probably want), and switch the IDE setting to SATA in the DSDT (which you probably won’t care about).

WARNING: USE AT YOUR OWN RISK! No guarantees. It worked for me, but for all I know it might melt down your system!

You can grab it here:
GA-H55M-UD2H – DSDT for F8 BIOS (DSDT.aml.zip)

Unzip it first. Generally, you put the DSDT.aml in your /Extra folder, but it could depend based on your bootloader.

I did the following:
-Minor fixes so it would compile
-CMOS reset fix (so it won’t clear your CMOS every time you shutdown/restart)
-TMR, HPET, PIC fixes
-SBUS fix (for sleep although with the onboard video I couldn’t get it to sleep anyway)
-USB -> UHCI/EHCI fix (so your USB should work properly and won’t break at 10.6.3)

I would strongly recommend using iBoot Supported + MultiBeast. Tony’s also got fantastic tutorials on his site continue reading…

Recently, Apple dropped the price of their developer program to $99.

I decided to grab it. Apple lists the main benefits on their site:
-Mac OS X Pre-Release Software
-Development Videos
-Apple Developer Forums
-Technical Support

I’ll go into a few details (as much as you can while staying within the NDA anyway), but if you’ve come from a Technet background, this isn’t Technet, and certainly isn’t what you’re looking for unless you’re solely interested in checking out the upcoming Mac OSX releases. If however you’re a programmer coming from an MSDN background, this is the program you’re probably looking for.

continue reading…

A quick note: There are plenty of guides out there about taking apart your Mac Mini in order to install/upgrade the RAM, and swap out the hard drive with another. This is meant to be a supplement to those guides, because you’ll notice that the most recent Mac Mini’s (as of this date), are slightly different in a couple areas.

The RAM/HD upgrade was done on the following system:
-Mac Mini 3,1 (MC238LL/A)
-2.26 Ghz Intel Core 2 Duo
-2 GB 1067Mhz DDR3 (upgraded to 4 GB)
-160 GB 5400 RPM DRIVE (upgraded to 500GB Seagate 7200RPM drive)
-nVidia GeForce 9400M video

Note #1: This is laptop DDR3 RAM. You can’t use desktop DDR3. There are 2 memory slots, and each is occupied by a 1GB stick by default. I used some “Lexar” brand stuff from Best Buy (two 2GB sticks). Also note that it’s a 2.5″ laptop hard drive – you can’t use the big clunker from your desktop!

Note #2: If you break something, your warranty’s void. Do it at your own risk.

Note #3: You may want to keep the original components around in case you have to send it in for warranty work and they decide to send you a replacement rather than repair it.

Let’s get started… continue reading…

On the lookout for a small case, capable of holding a typical small motherboard, I came across the IN-WIN BL-631. It’s a small case making it somewhat portable, it can hold a MicroATX motherboard, half-size video cards, 2 hard drives, and a standard CD/DVD-ROM drive.

Unfortunately, if you decide to actually utilize all those things, you’ll notice it gets very, very packed:

To be fair, other small form-factor cases are going to suffer the same problem. If you’ve never owned a small case though, this is certainly something to keep in mind. While the airflow characteristics can be surprisingly good, things get very tight.

-

Component Installation:

The case didn’t come with much. No instructions, just the case, power cord, and 4 plastic pieces which snapped together to form 2 stands.

I won’t lie continue reading…

We’ve got a couple ASUS P5KPL-CM motherboards, and when we’d try to put them to sleep, well they’d wake right back up again. Immediately. Everything powers down, you get the click, then it immediately wakes from sleep. This happened both in Windows 7 as well as in Mac OS X Snow Leopard (a hackintosh install)

I wrote one before about sleep issues in Vista – It’s possible that a similar change in device manager would work in Windows 7, but here’s another way to fix it, in all your operating systems, for good:

It’s the little jumper you see here circled in green, located on your motherboard (I made sure to get the rear ports and CPU fan in the picture to help you locate it). By default, ASUS has in on the left 2 pins.

Pop it off and put it on the right 2 pins (as shown in the picture).

-

For whatever reason, ASUS is addicted to putting this jumper in the other position by default, which always causes problems with sleep. I don’t remember the specifics of what it does, but it’s got something to do with standby voltage being put through the USB ports.

In any case, both Windows 7 and Snow Leopard properly go to sleep after this change, and can still be awoken by hitting a key on your USB keyboard. If your P5KPL-CM doesn’t sleep, give it a try.

Here’s the deal.

I had a pretty low power machine with an i3, integrated video, etc. It’s life long dream was of course to be our new file server so that I could start shutting off my sauna-in-a-case rig that was serving files 24/7 while out-performing our home furnace in heat output.

The i3 got it’s wish. It’s serving files, the other one’s off, and my room’s 10 degrees colder.

-

Enough blathering though.

-

Here’s what I like about FreeNAS:

  1. ZFS – If you don’t know what the ZFS file system is, it’s pretty bloody amazing – look it up. Look up RAIDZ in particular (the RAID5 of ZFS). Yes, FreeNAS supports the other continue reading…

After setting up users and groups in FreeNAS, I found that I wasn’t able to give any users write access.

I could get guests to read.

I could get users to read.

I couldn’t get anyone to write.

-

For whatever reason, it took a few searches before I came across the mac section of the FreeNAS documentation here. In any case, I’m going to guess that not everyone who uses FreeNAS is an SSH guru (although if you are you can just read the above link and skip the rest). Here’s the somewhat-easy-but-I’m-still-not-happy-about-it-way of doing it…

-

1) Hopefully you got to the point where you made users and put them in the same group.
a) If not, find Access/Users_And_Groups in the menu;
b) create a group (name it something easy)
c) create users (at least one for you!) and add them to your new group
It should look something like this afterwards:

In the above example, "family" is the group. Since my name is Matt, "Matt" is the user we'll be focusing on for the rest. The actual UID numbers used for the user and groups don't really matter - just use the defaults.

d) Make sure you’ve also set up an AFP share (Services/AFP/Shares). The next part here might not matter, but may as well do it anyway just in case – stick your username in the Read/Write access part (may be case sensitive, so be sure to capitalize if necessary).

2) Assuming you got everything in #1 done, it’s time to get you some read/write access. Here’s how we do it:
a) First you need the location of the folder. Easiest way to get this is to navigate to Services/AFP/Shares (just like in the step above), and find the Path. Look below to see what mine looked like:

The part we're interested is highlighted. Select it and copy it to the clipboard (Apple-C on your keyboard or right-click and choose "Copy").

In my case it was /mnt/SeagateZFS/MainStorage/ – select whatever yours is and copy it to the keyboard.

3) Next (and finally), we’re going to issue a couple commands, similar to what’s on the page linked at the very beginning. Head to the Advanced/Command menu.
a) Type in:

chown  macuser:macgroup  /mnt/yourvolume/yoursharedfolder

Replace macuser and macgroup with your name and group from step#1. Use the stuff from step#2 as /mnt/yourvolume/yoursharedfolder (you can either Apple-V or right-click paste to get that part in). I used double-spaces in the above to make it easier to read, but just using single spaces. As an example, mine was:


Hit execute. Not much will happen, except that it’ll display the command you just sent.

b) Type in:

chmod 2775 /mnt/yourvolume/yoursharedfolder

Again, similar to the above, except that where it says /mnt/yourvolume/yoursharedfolder, you’re pasting the stuff from your clipboard (from step#2) again.

Mine looked something like this:

Hit execute.

You’re done. Hopefully things should work. At the very least, you should be able to disconnect/reconnect and start copying files or create folders through your own account. Hopefully other people in your group will have access too, but verify to make sure they have the limited (or unlimited as the case may be) access you want them to have.

If you’re completely lost as to what exactly you just did, you basically just took ownership of the folder with your user account, and assigned it to your group on the filesystem / operating system level.

Hopefully in the future, someone makes changes to make things a little less cumbersome. Granted, there’s not a lot that can be done, but if the FreeNAS GUI automated the permissions setttings (or at least presented a GUI to do it), it would make it a little easier for people. A *very* good place for this would be a new item in the Access Menu called “file and folder permissions” or something to that effect. The menu item could list the shares or the dataset and have a “choose owner”, “choose group”, and “set owner/group/user permissions” section for each share. Worst case scenerio, giving the file manager a facelift and doing it there would help too.

While attempting to create a ZFS raid5 pool in FreeNAS, I had an issue where Size, Used, Free, Capacity, and Health all showed as UNKNOWN. In the configuration tab, the pool/virtual_device/dataset showed up under “current” but never under “detected”. Unfortunately there was absolutely zilch out there for information on this issue.

3 hours later….

(warning: before going any further, this is for a clean installation – if you’ve got data on those drives, it’s gonna be gone if you keep reading…)

-

What you need to do to fix it is:

-

0) pre-step: Delete all your entries in the ZFS section. You’ve probably got entries in the Virtual Device (Pools), Management (Pools), and Dataset (Datasets) sections. Remove them all, and don’t forget to update/save. We’re trying to get things in a clean state here.
-
1) Click Disks/Management from the main menu.
2) Delete all the entries for your current drives (then save the changes).
3) Create new entries. HOWEVER, this time for the formatting you’re going to LEAVE ALL THE DEFAULTS and choose NTFS for the “Preformatted File System” (don’t worry, we’ll be changing it back to “ZFS Storage Pool Device” later). Do this for every drive you’re using, and save/apply the changes.
4) Click Disks/Format from the main menu.
5) One at a time, select each disk, choose ZFS Storage Pool Device as the File System, then hit Format disk.
-
6) Now you should be able to create the Virtual Device, and the actual Management Pool. Once the pool’s added, you should be seeing proper numbers instead of “UNKNOWN”, and ideally everything should be working from here on in.

-

-

-

So what causes this behavior?

In the past I’ve run into issues where FileSystem B will not install properly on a drive that currently has FileSystem A on it. In those cases, I’ve either had to do a low-level format first to completely zero everything out, or try to do an intermediate partition/format with a FileSystem C, then try B again. Presumably, a similar thing happened here.

Now, this hasn’t happened for years before now (although the Mac OS X bootloader likes to resist being installed to drives that had other partition types sometimes), but I seem to recall it being an NTFS-FAT-EXT# circle that had issues in the past. As far as the hard drives I was using for this FreeNAS install, one had a Mac HFS+ partition, and I wouldn’t be surprised if that was the culprit that ZFS didn’t like.

In any case, what we’ve done above is essentially partition/format the drives as NTFS first, which ZFS didn’t have a problem overwriting. In the event you don’t have luck with NTFS as your intermediate file system, try the other partition types. If all else fails, I’d recommend grabbing the diagnostic tool from your hard drive manufacturer (SeaTools for Seagate drives for example), and use it to do a low level format and try again.

For those installing FreeNAS to a USB drive, a common error message is as follows:

gzip: stdout: Broken pip
Error: Failed to dd image on ‘/dev/da0′
Unmount CDROM.
There was a problem while copying files.

Fortunately, the fix is easy.

Step 1: Restart the computer WITHOUT the USB drive plugged in.
Step 2: Let the Live CD boot completely until you’re back at the same menu.
Step 3: Plug the USB drive in, then choose the option to install. It should now work.

From what I read when looking around, it looks like while the CD boots it installs some temporary files of some sort to the USB drive if it’s plugged in at the time, which causes the above error. Just wait until it’s finished booting – the installer’s smart enough to find your USB drive once it’s plugged in.

Powered by WordPress Web Design by SRS Solutions © 2010 mattgadient.com Design by SRS Solutions

Powered by CDN Rewrites