You are not logged in.

Announcement

[2017.09.08] DeployStudio build v1.7.8 (checksum, release note).
[2016.08.26] DeployStudio build v1.6.19 (release note).
[2013.02.23] DeployStudio last universal build v1.5.17 (release note).

#1 2012-11-19 22:49:30

bcarter5876
Member
Registered: 2012-01-13

Any known issues with Fusion drive?

We're about to purchase a lab full of Mac Minis.  Does anyone know if there are any issues with DeployStudio and the Fusion drive?

Offline

#2 2012-11-19 23:41:05

admin
Administrator
Registered: 2007-03-29
Website

Re: Any known issues with Fusion drive?

Not tested yet and not sure you can block restore a disk image to this kind of logical volume.

Offline

#3 2012-12-01 00:54:27

Meat
Member
From: SF CA US
Registered: 2009-02-04

Re: Any known issues with Fusion drive?

I've heard a rumor that block restore is possible, but the sticking point I'd imagine, would be using the Disk Utility that shipped on a Fusion Drive configured machine?
Just an idea...

Offline

#4 2012-12-10 16:33:26

mjsanders
Member
From: Delft, Netherlands
Registered: 2008-09-02
Website

Re: Any known issues with Fusion drive?

I have just recieved a mini 2012 with fusion drive, and I have tried to understand the fustion drive and its implications for DeployStudio.

In short: there is a specific version of Disk Utiltiy, and I do not understand yet how to re-create the FusionDrive with recovery partition yet.

Deploystudio can be used to restore images, but if you delete the complete FusionDrive setup you have to use DiskUtility manually (as far as I can tell).
Otherwise internet recovery is your friend..

Let's hope the admin and or genius bar will be able to generate a workflow step to re-create a Fusion drive.

--------------------------------
That is the summary, now for the small notes: :

I used DeployStudio (10.8/rc133) to capture an image before first boot.
-DeployStudio 133 cannot create an image for the Recovery HD partition


The disk utility on the recovery partition is Version 13 (455), while the current 10.8.2 (12c60) has Version 13 (430)

I created a NBI for deploystudio from the Mini (build 12c2034)

I used the terminal command ' diskutil cs delete ' to erase both disks, and if I used Disk Utility (from Utilities menu) it shows a message:
Disk Error, would you like to revert to a working state?
(this will erase the following volumes: disk0s1, Untitled, disk1s1 Untitled)
And If I click 'Fix' I can run deploystudio workflow to restore an image to a volume.
It generates some errors ('iostat: could not record 'disks2' for monitoring)
disk2 is the Fusion drive build by Disk Utility

The OS is bootable, but the recovery partiton is missing (since it was not generated...)..
and at reboot (with option key) you see two volumes with the name Macintosh HD
and both are bootable (?!), but the mini reboots twice after initial selection of HD (this is probably the reason behind this kbase HT5446 note about NVRAM)
After selecting the Macintosh HD in System preferences, there are still 2 local volumes Macintosh HD, but both result in the same boot OS (?!)

The results of diskutil list shows very similar results to the inital setup, so I cannot understand (yet) where the two volumes come from.. I guess from the 2 small Boot OS X partitions (of 134 MB) that are created on any volume with CoreStorage on it.

output of diskutil list:

So this is the situation out of the box when the macmini is in target disk mode to my macbook air:

MauritsAir:~ maurits$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *251.0 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS MacAirSSD               250.1 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:          Apple_CoreStorage                         121.0 GB   disk1s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk2
   1:                        EFI                         209.7 MB   disk2s1
   2:          Apple_CoreStorage                         999.3 GB   disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           *1.1 TB     disk3
------------

after deleting all volumes, and using the Disk Utility 'Fix' option and use DeployStudio to restore the OS (with noted issues) this is the partition list:

MauritsAir:~ maurits$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *251.0 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS MacAirSSD               250.1 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:          Apple_CoreStorage                         121.0 GB   disk1s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk2
   1:                        EFI                         209.7 MB   disk2s1
   2:          Apple_CoreStorage                         999.9 GB   disk2s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk2s3
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD              *1.1 TB     disk3


-
I hope others can help to make DeployStudio capable of restoring to fusion drives!

Offline

#5 2012-12-10 20:18:40

Meat
Member
From: SF CA US
Registered: 2009-02-04

Re: Any known issues with Fusion drive?

Can you boot into single user mode on the mini and do the diskutil command and compare it to the list you got while connected in target disk mode?

Offline

#6 2012-12-10 20:54:40

mjsanders
Member
From: Delft, Netherlands
Registered: 2008-09-02
Website

Re: Any known issues with Fusion drive?

I have not tried single user mode yet, but from the Recovery Partition it was exactely the same (but not disk1 and disk2, but disk0 and disk1)

What detail do you think is most interesting?
The mini does currently a clean install from internet recovery.
Can do some tests tomorrow if you like and put results here.

Offline

#7 2012-12-10 21:57:21

Meat
Member
From: SF CA US
Registered: 2009-02-04

Re: Any known issues with Fusion drive?

The two "...Boot Boot..." partitions, as you mentioned, are certainly weird. Sure seems like there should be a way to restore the machine to "factory" condition in the event of a drive failure. I wonder what Apple's service documents have to say about it. Just thinking "out loud", since that info is probably protected, currently...

Offline

#8 2012-12-11 11:20:28

mjsanders
Member
From: Delft, Netherlands
Registered: 2008-09-02
Website

Re: Any known issues with Fusion drive?

Apple Service documentation that I have access to has no detailed info.
There is stated that in case storage is replaces one should run (internet) recovery, and use the Disk Utilitiy to 'fix' the volume, and re-install software from the recovery partition. (similar as [url]http://support.apple.com/kb/HT5446)[/url]

The mini is doing this right now, and will investigate further when I am back in the office.

Last edited by mjsanders (2012-12-11 11:21:24)

Offline

#9 2012-12-11 13:07:52

mjsanders
Member
From: Delft, Netherlands
Registered: 2008-09-02
Website

Re: Any known issues with Fusion drive?

After booting Internet recovery, and 'fix' the disk, a re install produced this disk layout:

mini6:~ macosx$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:          Apple_CoreStorage                         121.0 GB   disk0s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:          Apple_CoreStorage                         999.3 GB   disk1s2
   3:                 Apple_Boot Boot OS X               650.0 MB   disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           *1.1 TB     disk2
mini6:~ macosx

So there is a Recovery disk on the HD, and a minimal Boot OS X parition on the SSD, similar as there is such a partition if you encrypt a USB flash drive. (i guess a CoreStorage thing)
The Recovery Disk Assistant will not make a backup of my Recovery part ion to a USB stick, with message: "The Recovery HD on this computer is damages or not present......."
I guess it wants the Recovery HD to be on disk0...

Offline

#10 2012-12-19 08:50:14

mjsanders
Member
From: Delft, Netherlands
Registered: 2008-09-02
Website

Re: Any known issues with Fusion drive?

A small update:

I re-did my work with DS NB 121205,, created a netboot set on the mini (10.8.2 12c2034) and overall this has the same result:
-Deploystudio can create image of Macintosh HD,
-but NOT from the recovery partition.
(and restoration has to be done manually)
The version of Disk Utility in the netboot set is the special version for fusion drive (13-444)

So work to be done here!

Offline

#11 2013-01-08 02:01:19

Meat
Member
From: SF CA US
Registered: 2009-02-04

Re: Any known issues with Fusion drive?

Fusion Drive's Macintosh HD captured. Deployed to late model MacBook Pro 13" and booted up fine.
Recovery boot only possible from the interwebs, as I followed my now common practice of repartitioning to a single partition, so not a shock.

Currently restoring to the Fusion Drive's Macintosh HD. We'll see what happens...

Honestly though, if the worst case is always having to get a decent network connection to restore, I can live with that, as we typically have users bring in their computer for troubleshooting. Haven't personally experienced emergency boot recovery being necessary while users are away, but a walk through wouldn't seem to be out of the question in that case anyway.

I'll try the "restore to Apple configuration" dealie after the reimage.

Offline

#12 2013-01-08 17:48:29

gehrked
Member
Registered: 2012-07-05

Re: Any known issues with Fusion drive?

Anyone make any headway on this? I have a new base mac mini with fusion drive that I've been doing some testing on and after severely screwing it up, I have it back in working condition. We can create a separate NBI with the Fusion disk utility and create a fusion image from the "Macintosh HD" partition (made of both drives) and drop it back down to the same location with no issues (as well as configure and post install some pkgs). Any thoughts on how to accomplish dual booting with Boot Camp?

Offline

#13 2013-01-08 18:42:33

Meat
Member
From: SF CA US
Registered: 2009-02-04

Re: Any known issues with Fusion drive?

There's the old fashioned, somewhat laborious option of using Boot Camp assistant to create the Boot Camp partition and creating a Windows master on it, then:
- image a fusion drive,
- use Boot Camp assistant to partition the imaged Fusion Drive,
- image the Windows partition.

I haven't tried it, but it "should" work...

Otherwise, I don't have a clue how you'd automate the entire process for a Fusion Drive. :P

Offline

#14 2013-01-08 21:43:21

lincoln
Member
Registered: 2008-11-19

Re: Any known issues with Fusion drive?

I will through in my tid bits, I can create both recovery and hfs images form a 2012 iMac with a fusion drive but not a 2012 mac mini. Burning those images will destroy the fusion drive in the iMac. I am using rc135, netboot images is off of an 2012 imac with 10.8.2.

edit: some more info: http://jollyjinx.tumblr.com

Last edited by lincoln (2013-01-08 23:37:05)


Out of the IT game, So long and thanks!

Offline

#15 2013-01-09 10:07:35

mjsanders
Member
From: Delft, Netherlands
Registered: 2008-09-02
Website

Re: Any known issues with Fusion drive?

Hi all

what Meat and others state is that they can capture ad Fusion Drive's content.
That is normal, any 10.8.2 system can read Fusion Drives content, so if DeployStudio .nbi set is 10.8.2+ that should work.

What I am missing is the 'easy' way to re-create the fusion drive.
Let me write down what I hope to be possible in future versions of DeployStudio, and what I know so far.

In most workflows you delete all existing partitions, and let DeployStudio create and restore them (including Recovery HD).
The step missing is the creation of the fusion drive (it should be based on the commands in http://jollyjinx.tumblr.com post, example:
  diskutil cs create Fusion disk0 disk1
  diskutil cs createVolume (insert LVG UUID here) jhfs+ MacHD 100%
And then the workflow should be able to select this volume 'MacHD' .

I hope Admin can make this into the GUI for us.
I can do this in the terminal, (see posts above) but am not able to make that into a proper script, specially not able to integrate the recovery HD into the stuff.

Bootcamp should be similar as before, but the command's above should be altered to include a windows partition (on disk1) and I have not tried yet.
The documentation from Apple (http://support.apple.com/kb/HT5446 ) states :
  Can I add a Windows partition?
  You can create one additional partition on the hard disk with Fusion Drive. You can create either a Mac OS X partition or a Windows partition.
  If creating a Windows partition, use Boot Camp Assistant to create it, not Disk Utility. From the Go menu, choose Utilities.
  Then, double-click Boot Camp Assistant and   follow the onscreen instructions. For more information on Boot Camp see the Boot Camp support page.
  Note: Boot Camp Assistant is not supported at this time on 3TB hard drive configurations.

I think the warning is because bootcamp is on disk1, not 0, and the resize commands are different for LVG's
There may be a solution for resizing in the diskutil cs resizeStack (see http://blog.fosketts.net/2011/08/05/undocumented-corestorage-commands/ for more info)

Last edited by mjsanders (2013-01-09 11:22:11)

Offline

#16 2013-01-09 18:39:52

lincoln
Member
Registered: 2008-11-19

Re: Any known issues with Fusion drive?

Hello,
   To what mjsanders wrote, I have found that if I let DS burn both recovery and main partitions, DS will kill the fusion drive and I will seed the two discreet drives on the finished machine. If let DS burn only the main partition*, ds dose not repartition the drive and and will burn the main partition with out issue. This will not fix a busted recovery partition so your mileage may vary.

Additional a 10.8.2 iMac netboot image will not capture the recovery partition of the mac mini. (for me at least) I have not tried the other way around.

* to only burn the main partition I prepend "X_" to the file name.


Out of the IT game, So long and thanks!

Offline

#17 2013-01-15 13:33:35

mjsanders
Member
From: Delft, Netherlands
Registered: 2008-09-02
Website

Re: Any known issues with Fusion drive?

SUMMARY:

In my ongoing research how to script the deployment of Fusion drive I tried to manually restore an image to a FusionDrive, plus a Recovery HD.
Here are my notes how I did this, all we need is a programmer to turn this into some buttons/workflows in DeployStudio.

DETAILS:

I have a Mac Pro 5,1 with 2 disks of 1TB each (this is NO SSD, but the CoreStorage work the same, although CoreStorage takes random choice which disk is the 'primary' (normally the SSD) You can see the primary disk with diskutil cs list, the index 0 is the primary disk.

This is what I did:
I netbooted from a DeployStudio Runtime (rc133/10.8.2) netboot set.
In the terminal I ran these commands: (How can I format this text? BBCode is off for me)

-bash-3.2# diskutil cs create Fusion2 disk0 disk1
--output--
Discovered new Logical Volume Group "330E5E93-E37B-4A14-9061-EA85D678F007"
Core Storage LVG UUID: 330E5E93-E37B-4A14-9061-EA85D678F007
---end output --

the result is :
--------------
-bash-3.2# diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:          Apple_CoreStorage                         999.9 GB   disk0s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:          Apple_CoreStorage                         999.9 GB   disk1s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            DeployStudioRuntime    *5.4 GB     disk3
/dev/disk4

New Volume created:

-bash-3.2# diskutil cs createVolume 330E5E93-E37B-4A14-9061-EA85D678F007 jhfs+ Fusion2HD 100%

--output--
Initialized /dev/rdisk2 as a 2 TB HFS Plus volume with a 155648k journal
Mounting disk
Core Storage LV UUID: C0442C15-2E5D-4ABC-803D-21328D18D593
Core Storage disk: disk2
--end output----

I want to create a Recovery HD partition, too bad this command does not support %, so I make a number 1980GB (was 2 TB in size) I missed a few GB, but for the purpose of this test I don';t care

-bash-3.2# diskutil cs resizeStack C0442C15-2E5D-4ABC-803D-21328D18D593 1980G jhfs+ Rec 1G
Started CoreStorage operation
Checking prerequisites for resizing Logical-Physical volume stack
Shrinking Logical-Physical volume stack
Checking file system
Checking Journaled HFS Plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierarchy
Checking extended attributes file
Checking volume bitmap
Checking volume information
The volume Fusion2HD appears to be OK
Shrinking file system
Shrinking Logical Volume
Resizing Core Storage Logical Volume structures
Resized Core Storage Logical Volume to 1979999997952 bytes
Shrinking Core Storage Physical Volume from 996730531840 to 986730532864 bytes
Shrinking Core Storage data structures
Resizing Core Storage Physical Volume structures
Resized Core Storage Physical Volume to 986730532864 bytes
Copying booter
Shrinking partition for Physical Volume and adding new partitions
Modifying partition map
Initialized /dev/rdisk1s5 as a 954 MB HFS Plus volume with a 8192k journal
Mounting disk
Finished CoreStorage operation

-bash-3.2# diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:          Apple_CoreStorage                         999.9 GB   disk0s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:          Apple_CoreStorage                         986.7 GB   disk1s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3
   4:                  Apple_HFS Rec                     1000.0 MB  disk1s5
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Fusion2HD              *2.0 TB     disk2
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            DeployStudioRuntime    *5.4 GB     disk3
/dev/disk4

Now I restored a recovery Partition to disk1s5 with asr:

-bash-3.2# asr --source /private/var/tmp/DSNetworkRepository/Masters/HFS/10.8.2_configured.i386.recovery.dmg --target /Volumes/Rec --erase

and made this type Recovery:

-bash-3.2# diskutil unmount /Volumes/Recovery\ HD/
-bash-3.2# asr adjust --target /dev/disk1s5 -settype "Apple_Boot"

now it looks like this:

-bash-3.2# diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:          Apple_CoreStorage                         999.9 GB   disk0s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:          Apple_CoreStorage                         986.7 GB   disk1s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3
   4:                 Apple_Boot Recovery HD             1000.0 MB  disk1s5
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Fusion2HD              *2.0 TB     disk2
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            DeployStudioRuntime    *5.4 GB     disk3


Restore the OS:

-bash-3.2# asr --source /private/var/tmp/DSNetworkRepository/Masters/HFS/10.8.2_configured.i386.hfs.dmg --target /Volumes/Fusion2HD --erase

so finally my diskutil list looks like this:

-bash-3.2# diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:          Apple_CoreStorage                         999.9 GB   disk0s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:          Apple_CoreStorage                         986.7 GB   disk1s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3
   4:                 Apple_Boot Recovery HD             1000.0 MB  disk1s5
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS MLionHD                *2.0 TB     disk2
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                            DeployStudioRuntime    *5.4 GB     disk3
/dev/disk4

i know that two Apple_Boot partitions is not good, but at least now CMD-R works on this Mac Pro.

(and booting from the MLionHD with 10.8.2 12c54 works fine on the Mac Pro)

I presume that on a 'real' fusion drive all these command should work too., but have no time to test that.

SUMMARY of commands used:

diskutil cs create Fusion2 disk0 disk1
diskutil cs createVolume LvgUUID jhfs+ Fusion2HD 100%
diskutil cs resizeStack LvUUID size-1G jhfs+ Rec 1G
asr --source /private/var/tmp/DSNetworkRepository/Masters/HFS/10.8.2_configured.i386.recovery.dmg --target /Volumes/Rec --erase
diskutil unmount /Volumes/Recovery\ HD/
asr adjust --target /dev/disk1s5 -settype "Apple_Boot"
asr --source /private/var/tmp/DSNetworkRepository/Masters/HFS/10.8.2_configured.i386.hfs.dmg --target /Volumes/Fusion2HD --erase

Last edited by mjsanders (2013-01-15 14:26:28)

Offline

#18 2013-01-15 17:35:48

Meat
Member
From: SF CA US
Registered: 2009-02-04

Re: Any known issues with Fusion drive?

Awesome, mjsanders! Thanks for the cool info. I hope the DeployStudio developer folk can work that into testing on an Apple Fusion drive setup with success. :)

Offline

#19 2013-01-17 21:15:57

pgsengstock
Member
Registered: 2012-08-13

Re: Any known issues with Fusion drive?

I'm scrambling to deploy a dual boot lab of 2012 iMacs.  I'm using the latest nightly build, but I can't seem to get DS to build the OS X master image.  It chugs along for a while, throwing tons of "iostat: could not record 'disk2' for monitoring" errors, but when it finally gets to 100% from putting the master to the repository, it just hangs.  I only have 16 workstations to build, but I'd hate to do all of them by hand.  I haven't even gotten to mastering the NTFS partition or trying to deploy the whole system.  The fusion drive seems nice, but this is quickly turning into a nightmare.

Last edited by pgsengstock (2013-01-17 21:16:55)

Offline

#20 2013-01-17 21:59:58

Meat
Member
From: SF CA US
Registered: 2009-02-04

Re: Any known issues with Fusion drive?

Mine gives the same iostat messages, yet it completes the image creation process. It means it can't report the drive's read/write progress accurately. 

There are several steps in the process of creating the master image, including capture, conversion, and scan steps. Some steps take quite a while to complete, and really don't give much in the way of log output. When you say it hangs, does that mean you cannot resize the log window on the client, or switch windows (Runtime or log window)? Mouse activities?

Any possibly helpful error messages in the server's logs?

Offline

#21 2013-01-17 23:00:33

pgsengstock
Member
Registered: 2012-08-13

Re: Any known issues with Fusion drive?

> Meat wrote:

> When you say it hangs, does that mean you cannot resize the log window on the client, or switch windows (Runtime or log window)? Mouse activities?

Any possibly helpful error messages in the server's logs?


I just tested it again, and at 38% it turns to an endless list of isotat errors.  The cursor turns to a spinning pinwheel and it sits there for hours without finishing.  I can still ARD into the machine, but I can't launch terminal or reboot.  I did a clean install on one of the machines and performed all the software updates to get it to 1.8.2.  I'm imaging that now to try to rule out my master system.

On the master system, I did already partition the drive using Boot Camp Assistant.  Perhaps that's the issue?  I would think so, because the NTFS partition went to the repository without issue.

Offline

#22 2013-01-18 05:43:57

pgsengstock
Member
Registered: 2012-08-13

Re: Any known issues with Fusion drive?

Updates:

I think my repository was completely borked, which was causing most of my problems.  To rule that out, I set up a new DS server with a new repository on a different box.  Using that, I've successfully mastered a couple vanilla machines (no bootcamp, just the factory OS X) without issue.  It does seem to take a LOT longer than it usually does, but maybe it's just me.  I've also made a master of my bootcamp partition, so now I'm back to attempting a master of the OS X partition.  It's a big master (for a digital media lab), so it's taking quite some time.

If I run into any additional snags or if I reach sweet success, I'll post back.  Thanks for letting me mess up this thread a bit while attempting to regain my sanity!


Pete

Offline

#23 2013-01-18 14:27:21

pgsengstock
Member
Registered: 2012-08-13

Re: Any known issues with Fusion drive?

OK.  I let the master image process run over night for my OS X partition.  After 9+ hours, it still hadn't finished, though it did reach 100% in the logs.  I quit DS on the client, and checked the DS repository.  The sparseimage in the tmp folder mounts fine (unlike previous attempts), but because I prematurely quit DS on the client, it's not being converted.  I'm not sure what else I'm supposed to do from here...

Offline

#24 2013-01-18 20:34:48

Meat
Member
From: SF CA US
Registered: 2009-02-04

Re: Any known issues with Fusion drive?

If the sparse image mounts, you could try the conversion command that DeployStudio uses (editing for any paths if necessary). I'm not sure how helpful it would be if it works manually, but the information might point to a problem/resolution for automation in DeployStudio.
Thanks for the info, pgsengstock. :)

If I'm reading the progress report correctly, you can create a working master if the BootCamp partition doesn't already exist?

Offline

#25 2013-01-18 20:43:02

pgsengstock
Member
Registered: 2012-08-13

Re: Any known issues with Fusion drive?

Right after the 9+ hour master imaging that didn't complete, I started one more mastering task, and it finished!  Now, I have an issue with the size of my NTFS image.

From that image create log:

....
Relocating needed data ...
ERROR: Extended record needed (1176 > 1024), not yet supported!
Please try to free less space.
-> test failed, volume shrinking aborted...
....

So it didn't shrink the NTFS volume for me.  That's not too big an issue.  Imaging OS X, partitioning on each workstation, then imaging Windows seems to get the job done.  Here's hoping for more automation in the near future.  Despite these recent road blocks, DS is still an AMAZING tool, and I would be stuck without it.

Offline

Board footer

Powered by FluxBB