Transparent Partition Mapping Error

I havd an ASO source cube and BSO target cube
Source Dimensions:-
Periods
Account
Company
CostCentre
Product
Target Dimensions
Periods
Account
FiscalYear
Scenario
Company
CostCentre
Product
Using MAXL I create a partition but I cannot get the mapped area to work correctly. the syntax I am using is :-
create transparent partition 'SOURCE'.'GrpSrc'
area '@DESCENDANTS("Periods"), @IDESCENDANTS("Account"),@IDESCENDANTS("Company"),@IDESCENDANTS("CostCentre"),@IDESCENDANTS("Product")' sourcearea
to 'TARGET'.'GrpTgt'
area '@LEVMBRS("Periods","Lev0,Periods"),@IDESCENDANTS("Account"),@IDESCENDANTS("Company"),@IDESCENDANTS("CostCentre"),@IDESCENDANTS("Product")' targetarea
mapped targetarea('"Actual"') to ('')
mapped targetarea('"CY"') to ('');
The partition is not being created correctly because the extra dimensions in the target cube [Scenario and Fiscal Year] are not mapped
Please let me know what I should be doing to get this to work!
Essbase 11.1.2.1
Many thanks

Hi ,
This error generally comes when there is an extra dimension in the target datasource.
Yes, you can create a transparent partition between databases having different numbers of dimensions. In your case, you have to create a mapping from 'void' to a member in your extra dimension (i.e. 'Actual') in the target. There is an example in the DBAG.
see the section on this page headed "Mapping Data Cubes with Extra Dimensions": http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_dbag/dotprtbd.html.
Thanks,
KKT
http://www.knowhyperion.com

Similar Messages

  • External Hard Disc won't mount - Partition Map error.  Can't repair with Disk Utility

    Happy New Year all and thanks in advance for any support/advise.
    I have some important data on an external drive that does not seem to want to mount.  The drive is a 500 GB Seagate connected via USB.  I am currently on an iMac 3.06 GHz Intel Core 2 Duo running Yosemity 10.10.1
    What I've tried:
    Multiple computers - connected the drive to various apple computers with the same result.
    New enclosure:  I have removed the actual HD from the enclosure and connected it using a new one.
    Disk Utility:  Verifying Disc reports the following error:  'Error: Partition map check failed because no slices were found.'  Screenshot below:
    I have searched this and other forums and run a few commands in Terminal that seem relevant to the issue, but am out of my depth in terms of interpreting the results.  Thank again for your attention!!!
    Commands run in Terminal:
    diskutil list
    diskutil cs list
    mount
    diskutil info disk1
    Full Results pasted below:
    diskutil list...
    Ethan-Smiths-iMac:~ Ethan$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.0 TB     disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            999.3 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.1 GB   disk1
       1:         Microsoft Reserved                         134.2 MB   disk1s1
    diskutil cs list...
    Ethan-Smiths-iMac:~ Ethan$ diskutil cs list
    No CoreStorage logical volume groups found
    mount...
    Ethan-Smiths-iMac:~ Ethan$ mount
    /dev/disk0s2 on / (hfs, local, journaled)
    devfs on /dev (devfs, local, nobrowse)
    map -hosts on /net (autofs, nosuid, automounted, nobrowse)
    map auto_home on /home (autofs, automounted, nobrowse)
    diskutil info disk1...
    Ethan-Smiths-iMac:~ Ethan$ diskutil info disk1
       Device Identifier:        disk1
       Device Node:              /dev/disk1
       Part of Whole:            disk1
       Device / Media Name:      ST950032 5AS Media
       Volume Name:              Not applicable (no file system)
       Mounted:                  Not applicable (no file system)
       File System:              None
       Content (IOContent):      GUID_partition_scheme
       OS Can Be Installed:      No
       Media Type:               Generic
       Protocol:                 USB
       SMART Status:             Not Supported
       Total Size:               500.1 GB (500107862016 Bytes) (exactly 976773168 512-Byte-Units)
       Volume Free Space:        Not applicable (no file system)
       Device Block Size:        512 Bytes
       Read-Only Media:          No
       Read-Only Volume:         Not applicable (no file system)
       Ejectable:                Yes
       Whole:                    Yes
       Internal:                 No
       OS 9 Drivers:             No
       Low Level Format:         Not supported

    Select the disk1s1 volume under the main drive entry, then click on the Mount icon in the Disk Utility toolbar if it goes active and see if a volume then mounts on your Desktop. If it does not, then you need to reformat the drive. And, you cannot access the volume in order to copy your data somewhere else. If you are willing to spend money on the problem, then you can always try using a software recovery utility:
    General File Recovery
    If you stop using the drive it's possible to recover deleted files that have not been overwritten by using recovery software such as MAC Data Recovery, Data Rescue II, File Salvage or TechTool Pro.  Each of the preceding come on bootable CDs to enable usage without risk of writing more data to the hard drive.  Two free alternatives are Disk Drill and TestDisk.  Look for them and demos at MacUpdate or CNET Downloads. Recovery software usually provide trial versions that enable you to determine if the software would help before actually paying for it. Beyond this or if the drive has completely failed, then you would need to send the drive to a recovery service which is very expensive.
    The longer the hard drive remains in use and data are written to it, the greater the risk your deleted files will be overwritten.
    Also visit The XLab FAQs and read the FAQ on Data Recovery.

  • Problems were encountered during repair of the partition map.

    I had too much time on my hands yesterday and I decided to try to remove an unused kernel extension that I saw in my EtreCheck report. The kext was for the PACE iLok, for Pro Tools, which I no longer use. I found the item that was installing the kext and removed it, and EtreCheck reported that the kext was gone.
    Some time after that I was troubleshooting another issue I have with Mavericks (shutdown time: my shutdown time with ML was almost instantaneous; with Mavericks, it takes about 12 seconds.), and I used the recovery partition and Disk Utility to repair my HD and permissions.
    DU reported that my usual boot volume was OK, and permissions repaired on it without problems.
    When I have DU look at the drive itself, it reported: Problems were encountered during repair of the partition map.
    And then, in ominous red text: error: live file system repair is not supported.
    I tried repairing again, and also got this message: The partition map needs to be repaired because there's a problem with the EFI system partition 's file system.
    I tried a few things to get these error messages to go away. I booted with a DiskWarrior disk and it was unable to do the repair.
    I did a little reading about the EFI partition, and in Macs it appears to be a partition related to firmware updates.
    My mac has not had any symptoms at all during this, aside from the slower shutdown.
    Even so, I did not like the idea of a partition that could not be repaired on my HD, so I did a clean install. Seemed to work, DU reported a healthy drive and volume.
    This morning, as I was preparing for a TM backup, I ran DU again, and the error messages were back. Not good.
    This time I tried TechTool, and it was able to repair the HD from the TechTool eDrive (TechTool's version of the recovery partition).
    I've looked in these discussions and there are some mentions of these error messages, but usually in the context of failing hard drives or drives that must be erased and the OS reinstalled.
    I'm wondering if anyone can shed some light on this for me, what these error messages mean, why they are occurring, and if I can just ignore them. My internal HD is not a stock Apple drive, but a Samsung SSD that I installed some time ago, and which otherwise works fine. My current suspicions are that either:
    there is something inherent in Mavericks that creates some problem with the EFI partition map over time, which then shows up in the error messages in DU
    or there is some incompatibility with this SSD and Mavericks that creates the same error messages.
    Here's my EtreCheck report:
    Hardware Information:
              MacBook Pro (15-inch, Early 2011)
              MacBook Pro - model: MacBookPro8,2
              1 2 GHz Intel Core i7 CPU: 4 cores
              8 GB RAM
    Video Information:
              Intel HD Graphics 3000 - VRAM: 512 MB
              AMD Radeon HD 6490M - VRAM: 256 MB
    Audio Plug-ins:
              BluetoothAudioPlugIn: Version: 1.0
              AirPlay: Version: 1.9
              AppleAVBAudio: Version: 2.0.0
              iSightAudio: Version: 7.7.3
    System Software:
              OS X 10.9 (13A603) - Uptime: 0 days 0:51:29
    Disk Information:
              Samsung SSD 840 PRO Series disk0 : (512.11 GB)
                        EFI (disk0s1) <not mounted>: 209.7 MB
                        Untitled (disk0s2) /: 499.12 GB (418.57 GB free)
                        Recovery HD (disk0s3) <not mounted>: 650 MB
                        eDrive (disk0s4) /Volumes/eDrive: 12 GB (4.65 GB free)
              HL-DT-ST DVDRW  GS31N 
    USB Information:
              MICRONET FANTOM DRIVE     1 TB
                        EFI (disk1s1) <not mounted>: 209.7 MB
                        Fantom (disk1s2) /Volumes/Fantom: 999.86 GB (941.3 GB free)
              Apple Computer, Inc. IR Receiver
              Apple Inc. FaceTime HD Camera (Built-in)
              Apple Inc. Apple Internal Keyboard / Trackpad
              Apple Inc. BRCM2070 Hub
                        Apple Inc. Bluetooth USB Host Controller
    FireWire Information:
    Thunderbolt Information:
              Apple Inc. thunderbolt_bus
    Kernel Extensions:
              at.obdev.nke.LittleSnitch          (4052)
    Problem System Launch Daemons:
    Problem System Launch Agents:
    Launch Daemons:
              [loaded] at.obdev.littlesnitchd.plist
              [loaded] com.adobe.fpsaud.plist
              [loaded] com.raynersw.nshctldo.plist
              [loaded] org.cindori.AuthHelper.plist
    Launch Agents:
              [loaded] at.obdev.LittleSnitchUIAgent.plist
    User Launch Agents:
    User Login Items:
              iTunesHelper
              Dropbox
    3rd Party Preference Panes:
              Flash Player
    Internet Plug-ins:
              Default Browser.plugin
              Flash Player.plugin
              FlashPlayer-10.6.plugin
              QuickTime Plugin.plugin
    User Internet Plug-ins:
    Bad Fonts:
              None
    Time Machine:
              Auto backup: YES
              Volumes being backed up:
                        Untitled: Disk size: 499.12 GB Disk used: 80.55 GB
              Destinations:
                        Fantom [Local] (Last used)
                        Total size: Zero KB
                        Total number of backups: (null)
                        Size of backup disk: Too small
                                  Backup size Zero KB < (Disk used 80.55 GB X 3)
    Top Processes by CPU:
                  13%          WindowServer
                   2%          hidd
                   2%          EtreCheck
                   2%          backupd
                   1%          com.apple.prefs.backup.remoteservice
                   1%          fontd
                   1%          com.apple.WebKit.Networking
                   0%          Safari
                   0%          cookied
                   0%          coreservicesd
    Top Processes by Memory:
              131 MB             backupd
              131 MB             Safari
              115 MB             com.apple.IconServicesAgent
              74 MB              Dropbox
              66 MB              WindowServer
              56 MB              com.apple.WebKit.WebContent
              49 MB              TechTool Pro 7
              49 MB              Messages
              41 MB              App Store
              41 MB              mds
    Virtual Memory Statistics:
              4.65 GB            Free RAM
              1.84 GB            Active RAM
              370 MB             Inactive RAM
              1.13 GB            Wired RAM
              415 MB             Page-ins
              0 B                Page-outs
    thanks

    this is the list it gives, hope it helps
    Verifying and repairing partition map for “ST9160314ASG Media”
    Checking prerequisites
    Checking the partition list
    Checking for an EFI system partition
    Checking the EFI system partition’s size
    Checking the EFI system partition’s file system
    Checking all HFS data partition loader spaces
    Reviewing boot support loaders
    Checking Core Storage Physical Volume partitions
    Checking storage system
    Problems were encountered during repair of the partition map
    Error: Storage system verify or repair failed.

  • Transparent Partition Issue

    Hi All,
    We have Planning BSO cube and it has 16 dimensions (Had to go with that many dim, although the max. is 10), and the aggregation process took abt 1.30 hrs, we've tried all possible fine tuning.. considering the no. of dims, it's fairly ok.
    Now the client wants all the HFR reports to be in real - time, so we've created a reporting cube (ASO) with exactly same dimensions and members, created a transparent partition mapping only level 0 members, and expected it work like once the level 0 members are mapped, it'll automatically aggregate to the parent members since its "ASO".
    Can you please let me know whether this logic will work or I've to go to replicated partition?
    Forgive my ignorance if my judgement is completely wrong.
    Regards,
    Rajeevan D
    Edited by: 865958 on Jun 14, 2011 10:54 PM

    Your question jumped from what sounded like data not being replicated in the partition to the outlines getting out of sync. I'm guess the latter is more likely a problem.
    Is the partition on ASO? BSO -> ASO partitions need to be manually synchronized.
    Regards,
    Robb Salzmann

  • Syntax error Creating Transparent Partition in MaxL

    Hello,
    I'm trying to create a simple transparent partition (no mapping needed, just using all the 3 dimensions and descendants in the source database to the target database. I'm getting a syntax error, I went through the MaxL naming conventions and also tried a couple of diffferent things but to no avail. Please help as to what the error might be:
    My code is as below. The error I get is: Getting a syntax error near '@IDESCENDANTS("Accounts"), @IDESCENDANTS("Products"),@IDESCENDANTS("Market)
    Code:
    create transparent partition student8.coke area '@IDESCENDANTS("Accounts"), @IDESCENDANTS("Products"),@IDESCENDANTS("Market")' sourceArea to student8.cokepart at lab01 as essadmin identified by 'password' area '@IDESCENDANTS("Accounts"), @IDESCENDANTS(Products), @IDESCENDANTS("Market")' targetArea;

    Nobody replied to this, but actually the error was the double quotes on Accounts, Products and Market.

  • Essbase Transparent partitions error

    Hi!
    I'm facing the following error in essbase
    Essbase database error 1023040: msg from remote site [[Wed May 22 11:14:36 2013]preicostos66/PS09/PS09/admin@Native Directory/Warning(1023011) Error asigning remote member [OBJ_537].]
    msg from remote site [[Wed May 22 11:14:36 2013]preicostos66/PS09/PS09/admin@Native Directory/Error(1040023) Unvalid network data.
    The situation is the following
    Three applications have Transparent Partitions PS2008 PS2009 & PS2010 (sources)
    These were referenced in only one application PS (target) with extra dimention (YEAR)
    PS outline is member complete but when retrieved any data that is not in the PS2009 outline unexistent member it shows the error.
    Please help
    Oscar

    Hi-
    It wouldn't be matter if members in current BSO cube partitioned to members existing in historical ASO cube. But if you want to retrieve new members that exist in BSO cube and don't exist in ASO historical cube, it won't show any value since it doesn't exist in the historical cube and of course the partition area from BSO to ASO can't be updated except when you want to map it to another member.
    Regards,
    Will
    Edited by: William Lesmana on 22-Jan-2009 02:37

  • Install error : disk cannot be used to start up your computer [or] MediaKit reports partition (Map) too small

    Greetings,
    I am aware that this problem has been discussed, but in long and vague discussions that I had to sift deeply to find an answer. Therefore I am posting a clear message, as this problem can be very troublesome for someone who just received a Mac OS installation disk and cannot install it.
    Situation : you cannot install/update your new system because the installer does not consider your volume.
    Error message : this disk cannot be used to start up your computer.
    Version française : Ce disque ne peut pas être configuré pour démarrer votre ordinateur.
    Also discussed below error: "MediaKit reports partition (Map) too small"
    Note : although this occurred with a Snow Leopard (10.6) install DVD, it can alo occur with Lion (10.7) according to discussions on Apple web site.
    IF YOUR CONDITIONS ARE AS FOLLOWS :
    - You are using an official Apple installation DVD of Mac OS 10.6 (Snow Leopard) [or 10.7 Lion] or an official download/upgrade of those systems.
    - Your main Mac partition scheme is in GUID as it should be (check with Disk Utility). That partition contains a Mac system that can start-up.
    - Your volume format is: Mac OS Extended (journaled) [the format should not be Case Sensitive.]
    - You have the hardware requirements to install Mac OS 10.6 (Intel processor; internal or external DVD drive or a linked DVD drive; 1 GB of RAM; a screen controlled by your computer graphics card; at least 5 GB space on the hard disk or 7 GB if you install all components).
    - Using Disk Utility, you of course tried the disk Repair Tool and the Repair Permissions tool.
    - Your hard disk does not have a file called Backups.backupdb (if it does, this means Time Machine has once used this hard disk for its back-ups). Anyhow, if it were the case, the installation would give a different error message (with the word TimeMachine). This file may block the installation: Apple Support suggest to place it in the garbage, *without* deleting it, and placing it back on the disk later. Mind you, if you do not use this hard disk as such to save your Time Machine back-ups, you can simply delete this file.
    HOW TO FIX :
    1. Boot with the 10.6 install DVD (Tip: you can either select Mac 10.6 as the boot DVD in your Start-up Preferences or simply press down c during the start-up).
    2. Above the install screen, you have a Utilities tab from where you can run Disk Utility. Select your hard disk and select the Partition tab. Resize the primary Mac partition (don't add a new one) by decreasing it by about 5 GB.
    It will look like this http://i.imgur.com/jHTbr.jpg
    ( That image shows only one partition, but the same principle applies even if you have two or more partitions on your disk.)
    Also see the official Apple how to: http://support.apple.com/kb/TS3926
    Version française: http://support.apple.com/kb/TS3926?viewlocale=fr_FR
    3. Commit the change by hitting "Apply"
    3.b. If you get the error "MediaKit reports partition (Map) too small", this is a rare error where the partition that follows (for example Bootcamp) is slightly overlapping your main Mac partition. You will need to reduce that other following partition. Once you have reduced the other partition, you will probably need to return to step 2 and 3 and try again.
    [ For example, in my case, I had resized my Bootcamp with CampTune software and it would seem that the file system ended-up somehow larger than the actual partition container. I simply asked CampTune to reduce the partition a bit (barely 2 GB) and that fixed it.]
    4. Reboot, again into the 10.6 install DVD.
    5. You can then install 10.6.
    6. Once 10.6 is installed, use the Disk Utility on the desktop (you can boot into the primary HD at this point) to resize the primary partition back to its original or maximum size.
    SOURCE (main fix): http://forums.macrumors.com/showthread.php?t=774410 [and] http://support.apple.com/kb/TS3926
    SOURCE (explaination for MediaKit error): some Apple discussion post.
    nb: in my case, it was on a MacBook Pro (late 2008).

    GasMan4932 wrote:
    When I click on the icon for this drive, the warning message below states "Mac OS X cannot be installed on 'iMac HD', because this disk cannot be used to start up your computer." Obviously that's not true, since that's where the OS is installed.
    How did you partition this drive, if you did that? Does it contain start up or utility partitions for any other OS (for instance Linux)? There have been reports that the "cannot be used to start up your computer" message will appear if a third party utility was used to create a 'triple boot' system or such, apparently because SL is picky about the format GUID partition scheme table info & how partitions are allocated space on the drive by other formatting/partition methods.
    For some users with these partitions, the fix has been as simple as "tickling" (slightly changing) the partition size of some partition with Disk Utility, which apparently updates the GUID partition scheme table info so that the SL installer accepts it as safe to use with SL.( In this sense, the message may be trying to say the installer thinks the disk can't be used to reliably start up your computer with SL, not in general.)
    See the discussions topic Cannot install Snow Leopard over 10.5.8 for more about this.

  • MacBookPro SSD Error- ALERT: The partition map needs to be repaired because there's a problem with the EFI system partition's file system.

    MacBook Pro OS x Mavericks. I have Sandisk 256GB SSD and I am getting a below error message.
    ALERT: The partition map needs to be repaired because there's a problem with the EFI system partition's file system.
    Does anyone know how to resolve this error and fix it ? unfortunately I don't have a Time Machine backup. Thanks!

    Have you tried to run the verify/repair permissions and verify/repair disk through the recovery disk? If that didn't work then I would reinstall the OS after backing up. If that still doesn't work I would take it in.

  • External drive error, does not mount: "Partition map check failed because no slices were found"

    Hardware: MacBook late 2009 (2.26Ghz Core 2 Duo 2 GB RAM 250GB HDD) running 10.9.4, Hackintosh MacPro (3.29Ghz i3 16GB RAM 1TB HDD) running 10.9.4, external 3 TB Seagate Backup+ drive
    As you can can see from the screenshot below,
    The external drive was initially plugged in a Netgear WNDR4500 router by USB to be used as NAS. I was in the middle of updating the firmware when there was a power outage. Upon reboot, the drive no longer mounts, whatever it is plugged in (router, Mac, PC, etc.).
    I ran DiskUtility on the partition map and volume, same errors. Here's an what I see:
    As you can see above, the "Mount" icon is greyed out and I get the error message "Partition map check failed because no slices were found". If I select "the Archive" partition, the "Mount" icon is not greyed out but clicking it doesn't do anything. My HDD is basically unreadable.
    I issued a few Terminal commands to see what was the problem, here are the results:
    What can I do?
    Currently running analysis on TestDisk and it is 50% after 48hrs. Need some help!

    @ Allan Eckert: Unfortunately, reformatting is out of the question, I have 5 years of work on this!
    @ Loner T: Yes, the firmware did successfully upgrade after router reboot and a bit of troubleshoot.
    Thanks for the quick replies. Keep 'em coming!

  • Disk Utility error "Mediakit reports partition map too small. 3TB

    So I have a Mac Pro with a 3TB inside, but Snow Leopard won't recognize the whole 3TB. I can format it, but it only allows 801.23 GB. The remaining space is left as Free Space. When I try to resize the Volume, I get this:
    I get this error: " Partition failed with an error." MediaKit reports partition (map) too small.
    Can someone help me find a way to utilize the 3TB as it was intended to?
    My setup:
    MacPro1,1
    10.6.8
    ST3000DM001-1CH166:
      Capacity:          3 TB (3,000,592,982,016 bytes)
      Model:          ST3000DM001-1CH166 
    Removable Media:          No
      Detachable Drive:          No
      BSD Name:          disk0
      Rotational Rate:          7200
      Medium Type:          Rotational
      Bay Name:          Bay 1
      Partition Map Type:          GPT (GUID Partition Table)
      S.M.A.R.T. status:          Verified
      Volumes:
      Capacity:          209.7 MB (209,715,200 bytes)
      Writable:          Yes
      BSD Name:          disk0s1
    BK:
      Capacity:          801.23 GB (801,225,752,576 bytes)
      Available:          737.7 GB (737,702,121,472 bytes)
      Writable:          Yes
      File System:          Journaled HFS+
      BSD Name:          disk0s2
      Mount Point:          /

    Anyways, i've made it work. My process was this:
    Problem:
    1. I put MacPro into Target Disk Mode to mount to my 2011 MacBook Pro. Disk Utility on MBP would only see 800GB.
    Solution:
    2. Booted the SL CD on the MacPro and ran Disk Utility from there. In the partitions tab, I chose 1 partition, and hit apply.
    3. "could not unmount disk."
    4. So I tried to partition it again, and it worked this time. 3TB Available.
    5. I then booted the MacPro using an external HD with OSX on it to run CarbonCopyCloner to reimage my backup.
    I hope this helps anyone else with the same problem.

  • Transparent Partitioning Error

    Can somebody please help with this error :
    [target] - partition definition is not valid: [unable to process area for slice [1] see server log]

    There are 2 cubes A, B and transparent partition created to third final cube C with both of them. On partition b/w cube B and cube C following error is coming:
    [target] - partition definition is not valid: [unable to process area for slice [1] see server log]
    I read somewhere on google that this error comes when there is problem with other partitions on same cube.
    On partition b/w cube A and cube C following error is coming:
    Partition [sestc01as288.danfoss.net:1423 EssDRS EssDRS] is not valid [Target] - Partition definition is not valid: [Partition definition for slice [1] does not parse]
    Please suggest some solution how to check.

  • Disk utility gives "Error: Partition map repair failed while adjusting structures to fit current whole disk size"

    I am getting the following error when running Disk Utility (under ML) on an exteral USB hard drive:
    Error: Partition map repair failed while adjusting structures to fit current whole disk size.
    I get thsi when I ask Disk Utility to "Repair Disk" at the top level of the disk hierarchy (i.e. not on one of the partitions within the disk but on the disk itself).  I was not getting this error with Lion on the same disk before I upgraded from Lion to ML.
    It seems like a bug in ML.  I found websites where they suggest that you just run Lion's Disk Utility and it will show the disk to be fine.
    Any thoughts?

    So, I finally seemed to have resolved things with the Seagate 4TB Firewire external drive.  If you Google about, you will find a thread on Seagate's own support forum that describes how to disable the sleep function on the drive.  You CANNOT ALLOW THE DRIVE TO SLEEP WHILE CONNECTED TO YOUR MAC.
    After a lot of reading, here's what I think is happening: the drive goes to sleep, after some period of inactivity, and when you shutdown your Mac, OS X tries to write something to the drive as part of the dismount / disconnect / shutdown process.  That fails in some manner, leaving the drive 'corrupted' at the filesystem or partition level.
    Then, on the next boot-up, Mountain Lion tells you that it cannot repair the drive and it mounts as read only.  Your only fix at that point is to re-partition / re-format and start over (which is big fun with 3TB of data to copy back on to the drive).
    If you prevent the drive from sleeping, whenever it's connected to the MacBook, then the above process doesn't occur and voila, the drive just works.  So far, I haven't had any problems with about a week of starting / shutting down my MacBook connected to the offending drive (translation: I was going to return the drive, but the problem is clearly with Mac OS X Mountain Lion).

  • DISK UTILITY Error: Partition map repair failed...

    Hi all,
    I purchased a new SEAGATE BACKUP PLUS 3T USB3.0 drive - and formatted GUID 1 partition - then ran repair disk and it showed with = "Error: Partition map repair failed while adjusting structures to fit current whole disk size"
    And I also tried 4 partitions but no help
    And I also tried formatting same on older 10.6 mac with no errors - then came back to 10.8 and error shows there...
    Can some folks please try this on there own setups to see how widespread this is...
    Criteria...
    1 - ML 10.8.2
    2 - Large external drive 2T or greater
    Q: Has anyone experienced this and has a possible solution?
    Thanks

    HI all,
    This issue has been in discussion (actively) since last August here:
    https://discussions.apple.com/thread/4218970?start=0&tstart=0
    After months and months of new reports, it's pretty clear that this is an Apple Mountain Lion problem and one that Apple needs to address.  As one frustrated user noted :
    >>There is no consistent solution for a user.  Apple has to supply it.  All you can do is submit a bug report to
    >> http://www.apple.com/feedback    
    Please, if you are encountering this problem you will save yourself a lot of wasted time and energy simply by joining me and others in asking Apple to fix this problem: Make a bug report.
    Thanks!

  • How can I reset my macs partition map?

    I have an MBP mid 2012 with 750GB HD (the higher model, with i7 2.9GHz and 8 gigs of ram) which I am possibly passing on to someone. I have the latest version of Mavericks, triple booted to include Windows 8.1 and Linux Ubuntu.
    To reset the computer I will likely use this method:
    Step One - Back up your data:
           A. If you have any Virtual PCs shut them down. They cannot be in their "fast saved" state. They must be shut down from inside Windows.
           B. Clone to an external drive using using Carbon Copy Cloner.
              1. Open Carbon Copy Cloner.
              2. Select the Source volume from the Select a source drop down menu on the left side.
              3. Select the Destination volume from the Select a destination drop down menu on the right
                  side.
              4. Click on the Clone button. If you are prompted about creating a clone of the Recovery HD be
                  sure to opt for that.
                   Destination means a freshly erased external backup drive. Source means the internal
                   startup drive.
    Step Two - Prepare the machine for the new buyer:
              1. De-authorize the computer in iTunes! De-authorize both iTunes and Audible accounts.
              2, Remove any Open Firmware passwords or Firmware passwords.
              3. Turn the brightness full up and volume nearly so.
              4. Turn off File Vault, if enabled.
              5. Use Boot Camp Assistant to remove a Windows partition, if there be one.
              6. Disable iCloud, if enabled: See.What to do with iCloud before selling your computer
    Step Three - Install a fresh OS:
         A. Snow Leopard and earlier versions of OS X
              1. Insert the original OS X install CD/DVD that came with your computer.
              2. Restart the computer while holding down the C key to boot from the CD/DVD.
              3. Select Disk Utility from the Utilities menu; repartition and reformat the internal hard drive.
                  Optionally, click on the Security button and set the Zero Data option to one-pass.
              4. Install OS X.
              5. Upon completion DO NOT restart the computer.
              6. Shutdown the computer.
         B. Lion and Mountain Lion (if pre-installed on the computer at purchase*)
             Note: You will need an active Internet connection. I suggest using Ethernet if possible because
                       it is three times faster than wireless.
              1. Restart the computer while holding down the COMMAND and R keys until the Mac OS X
                  Utilities window appears.
              2. Select Disk Utility from the Mac OS X Utilities window and click on the Continue button.
              3. After DU loads select your startup volume (usually Macintosh HD) from the left side list. Click
                  on the Erase tab in the DU main window.
              4. Set the format type to Mac OS Extended (Journaled.) Optionally, click on the Security button
                  and set the Zero Data option to one-pass.
              5. Click on the Erase button and wait until the process has completed.
              6. Quit DU and return to the Mac OS X Utilities window.
              7. Select Reinstall Lion/Mountain Lion and click on the Install button.
              8. Upon completion shutdown the computer.
    But, due to having three partitions on my computer and multiple operating systems installed, I at some stage needed to mess with the partition map (I remember doing this at one point: Repairing Boot Camp after creating new partition). Will using the above steps completely reset any custom "bios" I had installed and reset the partition maps/remove all partitions (Assuming I likely delete all the partitions and then re allocate all the space to OSX?
    And if the above would not work, what do I need to do to remove these and will it be possible to restore the mac fully to the "factory default"?
    Thanks,

    So this will completely overwrite any of the steps in this process?
    sudo gdisk /dev/disk0
    If you get any error messages at this point, report the error messages, don't proceed further.
    You're now in gdisk interactive mode. Menus/commands are single characters followed by return/enter. So type ? and <enter> and you'll get the main menu listing commands. Type p <enter> and it will print (display) the current GPT. Since you have 5 GPT entries, you can't use a 1 for 1 GPT to MBR scheme like Apple does. The following suggestion is safe, but all hybrid MBRs are non-standard inventions, and therefore I can't tell you how Boot Camp Assistant or Disk Utility will react to this hybrid MBR should you decide to make changes later. What I can tell you is Windows, Linux, and Mac OS X themselves have no problem with this MBR scheme.
    r <enter>        go to the recovery & transformation menu
    h <enter>        create a new hybrid MBR
    5 <enter>        add partion 5 to the MBR
    <enter>          accept the default MBR hex code of 07
    y <enter>        set the bootable flag
    n <enter>        do not protect more partitions
    o < enter>       print (display) the MBR
    You should have two entries. One type EE, one 07, with the 07 entry marked with * under Boot. If you don't, report back. If you do, write out the update partition information, and hope  a power failure doesn't occur for the next few seconds...
    w <enter>     write partition table to disk
    reboot. hold down option - you should be able to boot into either Mac HD, Recovery HD, or Windows.
    I just tested this same five partition GPT and 2 partition MBR on a working system and the instructions above worked.
    Note, so long as CSM-BIOS and thus MBR are required for Boot Camp instead of EFI booting Windows, we're stuck with flaky MBR problems, as well as the 2TB disk limitation for Windows boot disks.
    If so, problem solved, thanks!

  • Seagate external drive: Partition map check failed because no slices were found

    I have a 3TB Seagate Expansion external backup drive connected to my Retina Macbook Pro via USB. The disk will not eject from a regular Finder window - it will only eject from Disk Utility. Backups seem to otherwise be running fine. I tried to verify/repair the disk in Disk Utility, and I got the following error: "Partition map check failed because no slices were found." I am able to verify/repair the partition without any problem, and no errors are found.
    I'm concerned about relying on a backup drive that may be heading south. Here is the output from diskutil info:
    diskutil info disk3
       Device Identifier:        disk3
       Device Node:              /dev/disk3
       Part of Whole:            disk3
       Device / Media Name:      Seagate Expansion Desk Media
       Volume Name:              Not applicable (no file system)
       Mounted:                  Not applicable (no file system)
       File System:              None
       Content (IOContent):      GUID_partition_scheme
       OS Can Be Installed:      No
       Media Type:               Generic
       Protocol:                 USB
       SMART Status:             Not Supported
       Total Size:               3.0 TB (3000592977920 Bytes) (exactly 5860533160 512-Byte-Units)
       Volume Free Space:        Not applicable (no file system)
       Device Block Size:        4096 Bytes
       Read-Only Media:          No
       Read-Only Volume:         Not applicable (no file system)
       Ejectable:                Yes
       Whole:                    Yes
       Internal:                 No
       OS 9 Drivers:             No
       Low Level Format:         Not supported

    @ Allan Eckert: Unfortunately, reformatting is out of the question, I have 5 years of work on this!
    @ Loner T: Yes, the firmware did successfully upgrade after router reboot and a bit of troubleshoot.
    Thanks for the quick replies. Keep 'em coming!

Maybe you are looking for