Unable to expand/extend partition after growing SAN-based iSCSI target

Hello, all. I have odd situation regarding how to expand iSCSI-based partitions.
Here is my setup:
I use the GlobalSAN iSCSI initiator on 10.6.x server (Snow Leopard).
The iSCSI LUN is formatted with the GPT partition table.
The filesystem is Journaled HFS+
My iSCSI SAN has the ability to non-destructively grow a LUN (iSCSI target).
With this in mind, I wanted to experiment with growing a LUN/target on the SAN and then expanding the Apple partition within it using disk utility. I have been unable to do so.
Here is my procedure:
1) Eject the disk (iSCSI targets show up as external hard drives)
2) Disconnect the iSCSI target using the control panel applet (provided by GlobalSAN)
3) Grow the LUN/target on the SAN.
4) Reconnect the iSCSI initiator
5) Expand/extend the partition using Disk Utility to consume the (newly created) free space.
It works until the last step. When I reconnect to the iSCSI target after expanding it on the SAN, it shows up Disk Utility as being larger than it was (so far, so expected). When I go to expand the partition, however, it errors out saying that there is not enough space.
Investigating further, I went the command line and performed a
"diskutil resizeVolume <identifier> limits"
to determine what the limit was to the partition. The limits did NOT reflect the newly-created space.
My suspicion is that the original partition map, since it was created as 100% of the volume, does not allow room for growth despite the fact that the disk suddenly (and, to the system, unexpectedly) became larger.
Is this assumption correct? Is there any way around this? I would like to be able to expand my LUNs/targets (since the SAN can grow with the business), but this has no value if I cannot also extend the partition table to use the new space.
If anyone has any insight, I would greatly appreciate it. Thank you!

I have exactly the same problem that you describe above. My iSCSI LUN was near capacity and therefore i extended the iSCSI LUN from 100G to 150G. No problem so far.
Disk Utility shows the iSCSI device as 150G but i cannot extend the volume to the new size. It gives me the same error (in Dutch).
Please someone help us out !

Similar Messages

  • I have recently downloaded Bootcamp onto my MBP.  However, when i try to expand it from "downloads" it says "Unable to expand BootCamp5.0.5033 into downloads.  Error 2-no such file or directory.  I have tried changing the partition and Zipeg. didnt work

    I have recently downloaded Bootcamp onto my MBP.  However, when i try to expand it from "downloads" it says "Unable to expand BootCamp5.0.5033 into downloads.  Error 2-no such file or directory.  I have tried changing the partition and Zipeg. didnt work.

    You need to read and follow the Boot Camp instructions. Boot Camp Assistant is already on your computer in the utilities forderf. You run Boot Camp Assistant. Part of the process is to to then download the Windows Support software. This download is then installed from within Windows.
    There is no Boot Camp download that needs to be installed or unzipped from within OSx which you seem to be doing.

  • Unable to Adjust Partition after BootCamp

    Hi
    I use Boot Camp Assistant (BCA) to remove Windows 7 and ended with a message "Your disk could not be restored to a single partition". I am not sure if the Windows 7 is successfully removed.
    I use Disk Utility (DU) to try to "re-partition" the Mac HD to 250GB (from 218GB) but after checking catalog file and other processes, it ended with a message "Could't modify partition map because the file system verification failed"
    I use the First Aid to verify disk and reported the partition map appears to be ok
    I use the Repair Disk and it reported  the partition map appears to be ok
    Below is the map of the partition after I remove the Windows 7. I dragged the white color region (botton right) to extend to 250GB and click Apply and failed with the error message "Could't modify partition map because the file system verification failed"

    So just clone the volume and then erase and restore.
    If you created Windows with BCA and  you didn't do anything else in Windows or Mac OS to add change or shrink etc BCA should have.
    In some cases that error happens when creating or attempting to create Windows partition not on removal.
    Paragon CampTune is handy but for what you want just use Carbon Copy Cloner.
    I always advise using a dedicated drive just for Windows.
    You will find more on Boot Camp forum.

  • Is there any way to expand both the OSX and Bootcamp partitions after imaging the drive to a larger HDD?

    Hey all.  I have been searching forums and racking my brain to find a way to fix an issue I am having with my Late 2011 13" MBP.  SInce I wasn't able to find an answer, I figured it was time for reach out to the community.
    I purchased a Late 2011 13" Core i5 MBP that had a bad HDD from a friend.  I replaced the HDD with an old 100GB SATA drive I had lying around.  My mistake was thinking that it was a 1TB drive.  Regardless, I was able to reinstall Lion to the new HDD and get the machine up and running.  Once that was working, I went ahead and upgraded to Mountain Lion with no issues, then I unstalled Boot Camp and Windows 8.  Everything installed without a hitch and was working great.  Right about that time I realized that I had almost no free hard drive space and discovered my error (the 100GB HDD).
    I pulled the HDD and put in in my ASUS G74SX laptop along with a Seagate 750GB Hybrid Drive and used Clonezilla to do a hardware-to-hardware clone of the drive.  When it was completed, I put the 750GB Hybrid drive in the MBP and it booted right up with no problems.  I was also able to switch back and forth from my Boot Camp drive and everything appears to be working as it should.
    The only problem I have is that both the OSX partition and the Boot Camp partition are still the same size as they were before I cloned the drive.  Try as I might, I can't find any way to expand either one to use the additional 650GB of space that is sitting on the drive unused.  Disk Utility won't allow me to expand the partitions unless the free space is contiguous with the drives.
    Does anyone know of a utility that I can use to fix my problem?  I really don't want to reload everything from scratch.
    Thanks,
    Scott

    You need to combine the libraries on one computer. Otherwise you'll be constantly erasing your iTunes content as you switch computers. iPhone will only sync or manually manage iTunes content with ONE computer at a time.

  • Boot Camp: Is it possible to expand the size of the partition after install

    I loaded Boot Camp several years ago and did not allow enough hard drive space for the Windows side. Is it possible to expand the partition without erasing everything and starting from scratch?

    A. Backup first no matter what - both partitions - so you can restore if needed.
    B. Try Paragon CampTune
    If it was several years, then it was under Tiger and I would definitely backup and reformat your drive with 10.5.7. Tiger does not support resizing, and systems upgraded from Tiger to Leopard w/o reformat often ran into trouble, so it is more likely. And because they were using Boot Camp 1.4 beta.

  • Unable to resize a partition.

    Hello everyone
    I `ve recently created a new partition on my MacBook Pro running  OS X 10.9.4, and that was for install the public Beta of Yosemite, then i decided to delete that partition with Utility disks, then that space now appear gray, but the problem is when i tried to resized the partition dragging the lower right conner above, and then i clic "apply", nothing pass, So i was unable to resized the partition.
    Could someone please help me .
    here is a picture of UD.

    As I suggested on your first post of this topic:
    Install Mavericks, Lion/Mountain Lion Using Internet Recovery
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    Boot to the Internet Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND-OPTION- R keys until a globe appears on the screen. Wait patiently - 15-20 minutes - until the Recovery main menu appears.
    Partition and Format the hard drive:
    Select Disk Utility from the main menu and click on the Continue button.
    After DU loads select your newly installed hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed. Quit DU and return to the main menu.
    Reinstall Lion/Mountain Lion. Mavericks: Select Reinstall Lion/Mountain Lion, Mavericks and click on the Install button. Be sure to select the correct drive to use if you have more than one.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
    After you have installed OS X you can use Boot Camp Assistant to create a new Boot Camp partition for Windows. Do not attempt to use Disk Utility or Boot Camp Assistant to create a third partition. You can have at most two partitions: OS X and Windows. You created a third partition which you then removed, and that is why this problem arose.

  • TM2 unable to restore Windows 7 after Windows 8 Release Preview - have restore DVDs, still fails.

    Hello!  I've pretty much run out of idea's on how to troubleshoot this so I'll do a summary of what I changed with the machine and then troubleshooting details further on.  The particular hp touchsmart notebook I have is a TM2 1079cl,  Product Number: WA812UA#ABA.  I've only had it for the length of 2012, I purchased it used from another person about 1 year ago now specifically to toy with Windows 8 before it's release.  As far as the hardwares actual age I can tell from the warrenty information that it was manufactured in late 2009, it states the warranty period was from January 2010 to Jan 2011.
    Alright, so my history with the OS changes goes:
    -> Purchased this TM2 in early 2012, ran the recovery partition to wipe it clean of the previous owners use and it ran through installation perfectly fine, then on a clean Windows 7 as if it were new.  I'd also made use of a bootable Acronis True Image 2010 disk to make a hard disk image of the three other partitions for recovery (though I did not include the freshly installed windows 7 partition, figured it wouldn't matter if recovery could do it's thing right?)
    -> Some days later I loaded the second of the three preview releases for Windows 8 onto it (Customer Preview build I believe).   All worked fine and it dual booted between the two without issue, afaik the only real changes it made amounted to converting the primary partition Windows 7 was installed on to an extended partition and splitting the existing Windows 7 partition equally 50/50 inside that extended partition.  It had also overriden the boot manager / bootloader that was there before but again not surprised.
    -> When Release Preview build came out over summer I did an update from inside windows 8 and all seemed fine still.  The change between the two preview builds did develop an issue where I couldn't shut windows 8 down without a handful of error boxes poping up but I'm pretty sure that was unrelated.
    -> More recently about thanksgiving time I decided to give the laptop to a family member with a archiac desktop that's got issues and general old factor that makes it not worth updating.   This person is pretty adverse to change so that whole "Win8-vs-what people are used to" thing comes into play.   I decided to wipe the TM2 clean back to the OS it shipped with.    Here's where I'm now stuck:
    => Before doing anything I made another True Image of the HDD as a just incase, glad I did.
    => Tried F11 to load the recovery partition only to find that because of the bootloader being tampered with by Windows 8 it doesn't actually go to the HP recovery partition anymore despite still being on the hard drive.
    => Grabbed the hard disk image from the beginning of the year with the recovery partition on it before windows 8 touched the machine, wiped the hdd completely clean, restored the disk image.   I could now get into HP recovery fine but....
    => I got a dialog error right off the bat saying that the recovery partition could not install and instructing me to insert disc 1 of the recovery software.  Well I never made the dvd's myself with the one-time use burning feature when it worked so that's out and I had not bought the discs from HP's support site.   At this point I'm puzzled though why the recovery partition can't install despite the computer loading up into recovery just fine.  For example command prompt in the Windows PE environment is functional and all files seem to be present.   Maybe some verification that the recovery partition isn't pirated might have been triggered by hard disk imaging, i'm really not sure?
    => I then made used of the HDD image I'd just created before trying this and restored the other copy of the drive (Win8 tampered bootloader, Win8 release preview, win7, the inaccessible recovery partition and all).   Windows 7 and 8-RP could still boot.   Googled around a bit about the recovery partition key (F11) getting messed up by Windows 8 and came to find I only needed to set recovery as the "Active" partition to get it to start.  Sure enough that got it to start but I'm running into the same issue where the actual recovery partition loads up but now refuses to begin the restore process without HP dvd's.  Since I know for certain this worked months ago I guess once again since I ended up restoring that version of the recovery partition it may have also declared itself tampered with... great.
    => Contemplated what to do for a bit and then finally just ordered the DVD's from HP in December, I specifically got the recovery DVD's for my model and they did come from HP directly, not second hand from ebay or another person.  Wasn't really that bad, $16, very reasonable price.  Should be set right, legit OEM DVD's to use?  Nope....
    => The DVD's came.  Two discs for main recovery and a third for applications and drivers.   Boot off disc one and it states it's formatting the drive how it wants (good, i'm liking this so far), copies all of the contents of the three discs to the hdd and begins it's reboot and install cycle.    Reboots a handful of times, you can tell it gets well past copying the contents of any of the discs and into installing windows.  You see the Windows 7 boot logo a few times and even the standard "preparing your things" background that's similar to the Windows 7 login screen.  The screen definitely gets as far as installing the proper graphics driver (and others I assume at that time) as the resolution changes to native for the TM2's LCD near the end.
    =>  Suddenly on the 3rd or 4th (I think) reboot of installing windows it starts for a moment then says shutting down, it reboots and it's back in the windows PE environment of recovery setup again (this time coming from the hard drive, not the DVDs) and says it's failed to restore and offers to start everything over from the very beginning.
    That's where I'm stuck.  The Recovery Partition died on me post-Windows 8 and the offical HP recovery DVD's are failing me (and oddly they're failing me seemingly in the very last steps of windows 7 restore, well after the DVD's themselves are no longer being read from).
    >> Question 1:  Does the HP recovery partition "self destruct" if it gets imaged by hard drive imaging software and restored?  I can confirm mine worked fine once and then dead after going through Acronis True Image.  Another possibility is maybe there's some ID's or tattooing of the hard drive or specific partitions that was lost when Windows 8 put it's newer bootloader into the machine or lost from Acronis?  This is still the oem hdd that came with the computer, it has not been switched out.
    >> Question 2:  Are there any known problems with the official Windows 7 recovery DVD's for a late 2009 TM2 1079cl?  I'm also aware of the Cyberlink recovery software patch / pre-install disc and tried this with results that were no different to without it.  That said my machine does have the Cyberlink version of the recovery software, I read there's something like 3 different companies software for recovery depending on time period the laptop was made and sold.
    Reference: [ http://h10025.www1.hp.com/ewfrf/wc/softwareDownloa​dIndex?cc=us&lc=en&softwareitem=pv-80183-1 ]
    >> Question 3:  Plainly put, what now?  Anything else to try or do I need to go find an RTM windows 7 disc and scrounge all the driver zips together?  (Very much hoping to avoid that, I'm actually pretty curious to really understand what happened here and while that'll work it would answer nothing.  hehe).
    Maybe related things as well:  Some searches led me to believe having the WLAN switch off at the start of recovery causes driver installation to flip out (and indeed win7 seems to drop dead during the last steps of driver install) however it's not possible it would seem to turn the WLAN card "on" before this point.  Switch won't bring it to enabled state anyways.   As I mentioned above the Cyberlink recovery software patch has no effect on things.   No parts have ever been changed in this machine, original hdd, wlan card, ram modules, ect.   I doubt the motherboard bios / firmware has ever been updated, machine states it's revision F.02.
    I have at my disposal:
    * A lot of time, actually, hense why I really want to know what happened and not use the Win7 RTM disc.
    * hdd image of HP recovery before Win8 touched the machine.
    * hdd image of recovery after Win8 and a kinda buggy but still bootable Win8-RP.
    * The correct HP-made recovery DVD's for my laptop, ordered recently (December 2012).
    * Confident enough to toy with partition editing tools should it be a suggestion, never really used much outside of gparted on linux live discs however.  Considering the current state of the machine there's nothing to risk losing anymore though.
    Sorry for the text wall!  I like being very detailed!
    This question was solved.
    View Solution.

    I have the tm2 and have not experience an issue with the recovery and wifi being off, but it certainly is in the realm of possibility.  I just had not encountered it on my own tm2, so I subconsciously dismissed it or just didn't think of it as a result. 
    Thank you for sharing your solution with the community. 
    ↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

  • Unable to expand drop down by index UI element

    Hi,
    I have got one Drop down by index in my webdynpro form and I want to bind this to backend data. For this purpose, I created one adaptive rfc model  and also did all this model binding, context mapping etc.
    Now my context in view  looks like this :- GetDropDown_Mn (parent node) , this has got child Output_DropDown which again has two value attributes Name and Text.
    This is component controller code where you bind and invalidate
    __Shell__Ca_Read_Cr_Drbox_Val_Input dropdown = new __Shell__Ca_Read_Cr_Drbox_Val_Input();
            wdContext.nodeGetDropDown_Mn().bind(dropdown);
            wdContext.currentGetDropDown_MnElement().modelObject().execute();
            wdContext.nodeOutput_DropDown().invalidate();
    I then tried to bind my UI element in view with Name attribute , but when I try to run my application , the field appears as read only, kind of non editable (blocked) and I am unable to expand my dropdown.
    The readonly property of UI element is false. I have hard coded one value like " Please select from drop down list " and I want the backend values to come below this. For this, I have written code to append the backend values with the hardcoded value. Now the problem is my dropdown is blocked  and not able to expand ( unable to click the arrow button), and I cannot see the other values in dropdown except the hard coded value.
    Can someone please help me on this. 
    The cardinality of context node is 1..n, selection = 0..1 and I have set Leadselection = -1.
    Thanks and regards,
    Sai

    Hi Sai,
    You can use the below code to add the please select in ur drop down in wdInit() method
    wdContext.nodeVn_Node().currentVn_NodeElement().setVa_Attribute("-Please Select-");
    please use the name of node as u have created in the context.
    and after that please check if yoy are getting values from RFC call or not.
    if you are getting the values then try to change the selection property of that node to 1..n and comment the lead selection line that you have written.
    hope this will help.
    Regards
    Narendra

  • Unable to expand Tree in EP   (e.g. Portal Content)

    Dear Portal Gurus,
    We are on EP 6.0,SP12.
    We are unable to expand any tree structure (including stanadard Tree Structure) inside EP.
    I get the following message :
    Could not load or refresh node Tree creation failed on node: pcd:portal_content .
    Pls let me know what needs to be done.
    Thx.

    when I exported a transport package I saved it on Portal conect and after doing all the transporting, when I opened the content administration and try to expand the portal content, I get the following error:
    Could not load or refresh node Tree creation failed on node: pcdportal_content
    <a href="http://ing.perez.googlepages.com/portal.jpg" target="_blank"><img src="http://ing.perez.googlepages.com/portal.jpg" border="0" /></a>
    I get this error from the log
    1.5#0011856BDDE1006D00000086000011B000042238FAC1E7DA#1163528027322#com.sap.portal.pcd.Gl.Notification.Engine#sap.com/irj#com.sap.portal.pcd.Gl.Notification.Engine#IENAFS02#197##091402wb79_EPD_2059550#IENAFS02#0a01e440740b11dba4e00011856bdde1#Thread[T-IMPORT-1114_121327_931_71801fdd2c1d2d9b,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server#Java###[XfsNotificationEngine.register] Exception occured: 
    [EXCEPTION]
    {0}#1#PcdRuntimeException: SQLException is not transient, error code = 0, sql state = HY000
    [SAP_NWMss][SQLServer JDBC Driver]IO Error creating temp file: null
    com.sapportals.portal.pcd.pl.PlRuntimeException: SQLException is not transient, error code = 0, sql state = HY000
    [SAP_NWMss][SQLServer JDBC Driver]IO Error creating temp file: null
         at com.sapportals.portal.pcd.pl.PlFactory.handleUnexpectedSQLError(PlFactory.java:2428)
         at com.sapportals.portal.pcd.pl.PlFactory.checkDeadlockResolution(PlFactory.java:2436)
         at com.sapportals.portal.pcd.pl.PlContext.lookupSubtree(PlContext.java:280)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.<init>(XfsContext.java:128)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.<init>(XfsContext.java:85)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getXfsChildFromPlChild(XfsContext.java:590)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.readXfsObjectFromPersistence(XfsContext.java:535)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getChildAtomicName(XfsContext.java:433)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getChild(XfsContext.java:277)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getChild(XfsContext.java:280)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.getChild(XfsContext.java:280)
         at com.sapportals.portal.pcd.gl.xfs.XfsContext.lookup(XfsContext.java:228)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.triggerInformDanglingDeltalinks(XfsNotificationEngine.java:463)
         at com.sapportals.portal.pcd.gl.xfs.notif.XfsNotificationEngine.register(XfsNotificationEngine.java:302)
         at com.sapportals.portal.pcd.gl.transport.PcdGlTransportAdapter.endElement(PcdGlTransportAdapter.java:346)
         at com.sapportals.portal.pcd.gl.xml.ContentHandlerManager.endElement(ContentHandlerManager.java:204)
         at com.sapportals.portal.pcd.gl.xml.PcdXMLContentHandler.endElement(PcdXMLContentHandler.java:107)
         at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:154)
         at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1913)
         at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1809)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2792)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:278)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:340)
         at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
         at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
         at com.sapportals.portal.pcd.gl.xml.PcdXMLParser.parse(PcdXMLParser.java:85)
         at com.sapportals.portal.pcd.gl.xml.PcdXMLParser.parse(PcdXMLParser.java:54)
         at com.sapportals.portal.pcd.gl.transport.PcdGlTransportManager.importObject(PcdGlTransportManager.java:612)
         at com.sapportals.portal.transport.Transport.importObject(Transport.java:110)
         at com.sapportals.portal.transport.app.ImportRunner.importObject(ImportRunner.java:322)
         at com.sapportals.portal.transport.app.ImportRunner.run(ImportRunner.java:164)
         at java.lang.Thread.run(Thread.java:534)
    Caused by: java.sql.SQLException: [SAP_NWMss][SQLServer JDBC Driver]IO Error creating temp file: null
         at com.sap.nwmss.jdbc.base.BaseExceptions.createException(Unknown Source)
         at com.sap.nwmss.jdbc.base.BaseExceptions.getException(Unknown Source)
         at com.sap.nwmss.jdbc.base.BaseImplClobEmulated.<init>(Unknown Source)
         at com.sap.nwmss.jdbc.sqlserver.SQLServerImplResultSet.getData(Unknown Source)
         at com.sap.nwmss.jdbc.base.BaseResultSet.getClob(Unknown Source)
         at com.sap.sql.jdbc.basic.BasicResultSet.getClob(BasicResultSet.java:432)
         at com.sap.sql.jdbc.direct.DirectResultSet.getClob(DirectResultSet.java:1060)
         at com.sap.sql.jdbc.common.dispatch.ClobResultColumn.getClob(ClobResultColumn.java:138)
         at com.sap.sql.jdbc.common.CommonResultSet.createClob(CommonResultSet.java:1035)
         at com.sap.sql.jdbc.common.CommonResultSet.getClob(CommonResultSet.java:302)
         at com.sap.sql.jdbc.common.dispatch.ClobResultColumn.dispatchGetString(ClobResultColumn.java:114)
         at com.sap.sql.jdbc.common.CommonResultSet.getString(CommonResultSet.java:448)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.readStringValue(AttributeHeadersTable.java:934)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.readFirstValue(AttributeHeadersTable.java:657)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.readAttributeHeader(AttributeHeadersTable.java:639)
         at com.sapportals.portal.pcd.pl.AttributeHeadersTable.selectSubtreeObjectsAttributeHeaders(AttributeHeadersTable.java:762)
         at com.sapportals.portal.pcd.pl.PlFactory.getSubtreeSegment(PlFactory.java:878)
         at com.sapportals.portal.pcd.pl.PlFactory.getSubtree(PlFactory.java:804)
         at com.sapportals.portal.pcd.pl.PlContext.lookupSubtree(PlContext.java:253)
         at com.sapportals.portal.pcd.pl.PlContext.lookupSubtree(PlContext.java:274)
         ... 33 more

  • [Solved] unable to mount harddisk partition or flash drive

    After recent updates to gnome 3.4.2,i am unable to mount  harddisk partition or flash drive .I have 2 year old arch installation with gnome.
    When i click on partitions in nautilus,it says "Unable to mount program files \n Not authorized to perform operation"
    Problem is not only while mounting partitions.
    Wherever we need authorization .Like changing date and time ,changing user accounts using gnome UI etc.The unlock button is greyed out permanently.
    even i am not able to shutdown using gnome menus. it just log me out only ,do not restart or shutdown.Though i can shutdown using shutdown command on commandline.
    i run gnome using daemon method. not through xinitrc .
    https://bugs.archlinux.org/task/25031?p … ekit#close
    I found a similar discussion in this bug. But since, i do not use xinitrc, it is unlikely they will help me.
    Can someone be kind enough to help me on this?
    Thanks in advance.
    Last edited by piyushbhatt (2012-09-11 05:48:57)

    maybe changes in udev or any other package
    you have polkit polkit-gnome
    and you user is in optical, disks and wheel groups?
    for me those above work in every sitation

  • Can I put the HP recovery (D:) partition in an extended partition?

    I recently had to replace my HDD and HP sent a recovery disk set with my OEM replacement HDD which I used to returm my laptop to "factory original" condition. My problem is that it created 4 primary partitions on the HDD, and now I'm looking for a way to non-distructivly increase the number of partitions on the HDD so I can dual boot Windows 7 64-bit and one or more distros of linux. My computer is a Pavilion dv7-3165dx Entertainment Notebook. I would like to preserve all 4 of the partitions that the recovery disks installed. I had an extended partition with logical drives in it on the drive that failed, and while I don't recall the exact configuration of the partitions I'm sure that I didn't delete any of the factory original partitions to make room for the extended partition, I only had to resize the (C: ) partition to make space for my additional partitions.
    So, can the HP recovery (D: ) partition be placed inside an extended partition and still function as intended?
    I asked the same question about the (C: ) partition on the Microsoft support forums, and ended up with opposing answers, 1 from a "Support Engineer" saying no, and another ftom a Microsoft tech page showing a diagram of partitions in a configuration that would imply that the answer is yes. Since it's a diagram and not a screenshot I can't decide if I want to risk the attempt on it. To tell the truth I would rather have the (C: ) in the extended partition, but i'm ready to do the job by converting the recovery (D: )  partition if the functionality will still be there.
    The configuration of the partitions that the recovery disks created is as follows:
    As you can see there is plenty of empty space in the (C: ) partition that I can use for my other plans.
    BTW, I'm posting this question here because I couldn't find a partitioning section of these forums, and it is about the recovery partition, If there is a more appropriate section maybe a mod will move it, and inform me of where it is.
    IF what I post solves your problem please click the "Problem solved" button on my post.
    Oh, and if I have helped you, clicking the 'Kudos' star on my post would not hurt my feelings ether.

    Those are the standard partitions.  All systems should have the system partition as this is necessary for Windows to boot.  The large partition is of course the main partition. 
    In my experiencing, modifying the recovery partition has not had a happy ending.  Others may have a different experience, but I have seen the recovery partition fail to function properly after it is modified.
    Furthermore, you can run into issues down the road if a dive has more than 4 partitions.  Windows, by default, will convert a drive to dynamic if it has more than four partitions.  The recovery, either from the HDD or from the disks, is designed for a basic disk and will not recover a dynamic drive.  If a fifth partition is added, instead of removing one to make room for one more, then there will be issues with the recovery down the road.  There are ways around it, but I recommend avoiding that scenario if possible. 
    As long as you have the recovery disks, which sound like you do, I would recommend removing the recovery partition so that there will be room for a partition of your choice.  The same can be said for HP_Tools.  If you really need the advanced diagnostics, a bootable media containing them can be made by downloading the UEFI support environment from the support and drivers page for your unit.  The installer will give you the choice to install to the HDD (make a partition) or to make a USB flash drive that is bootable with them.  The HP_Tools partition is small, but the purpose is to keep the number of partitions to four or less.  Removing the recovery partition (make sure to keep the recovery disks) and the HP_Tools would give the option to add two partitions and keep it under five to avoid the issue of a dynamic drive.  A third party tool can be used to resize the C partition to give you the space you need for the other partitions. 
    ↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

  • Solaris 10 on extended partition?

    Hey all
    I need your help in something, as I'm a Linux junkie but a Solaris noob. I'm currently working with an 80 GB hard drive with Windows XP (ugh) installed on the primary partition and Linux (Fedora Core 4) on extended partitions. Needless to say I'm using the Linux bootloader.
    I'm downloading Solaris 10 at the moment. I read somewhere that you can't install Solaris 10 on an extended partition. Is that so? Because I was originally considering installing Solaris in Linux's place (not that I'm sick of Linux, but because of a lack of free space on my drive).
    If I have to install it on the primary partition, that means I have to get rid of Windows instead. Is that a risky thing to do? Because I can't afford losing the important data I have, which is all on extended partitions. And will there be any issues concerning booting Linux and Solaris?
    I also have this old 10GB hard drive lying around somewhere that doesn't work. Would it be the best idea to have it repaired and installing Solaris on it and keep the old systems?
    Please help me out
    Thanks in advance
    -A

    Hey all
    I need your help in something, as I'm a Linux junkie
    but a Solaris noob. I'm currently working with an 80
    GB hard drive with Windows XP (ugh) installed on the
    primary partition and Linux (Fedora Core 4) on
    extended partitions. Needless to say I'm using the
    Linux bootloader.
    I'm downloading Solaris 10 at the moment. I read
    somewhere that you can't install Solaris 10 on an
    extended partition. Is that so? Because I was
    originally considering installing Solaris in Linux's
    place (not that I'm sick of Linux, but because of a
    lack of free space on my drive).
    If I have to install it on the primary partition,
    that means I have to get rid of Windows instead. Is
    that a risky thing to do? Because I can't afford
    losing the important data I have, which is all on
    extended partitions. And will there be any issues
    concerning booting Linux and Solaris?
    I also have this old 10GB hard drive lying around
    somewhere that doesn't work. Would it be the best
    idea to have it repaired and installing Solaris on it
    and keep the old systems?
    Please help me out
    Thanks in advance
    -AHi,
    I've just got this working fairly well, Windows XP Pro-
    50gb, FC4-10gb, Solaris 10-9gb, and Fat32- 7gb.
    That is the correct order to install them. Originally, I
    was going to use BootMagic as the boot loader. So
    I installed FC4 to the first sector of the boot partition.
    That works well for Linux and Win XP but Solaris 10
    required the "Advanced" BootMagic configuration.
    Then I decided to try to make this work with boot.ini
    I used the dd command to copy the first 512 bits of
    the first sector of the Linux boot partition, linux.bin.
    Here is my boot.ini and linux.bin is on C:\
    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
    c:\linux.bin="Linux"
    So when I choose "Linux from the boot.ini options, the
    grub boot loader presents me with Windows as the
    default, or I can choose FC4 or Solaris 10. I read that
    Solaris 10 requires the "makeactive" switch and I
    included it for Windows XP so that I wouldn't have to
    make Win XP active since I use it the most; it saves
    the Solaris 10 boot loader screen most of the time.
    # grub.conf generated by anaconda
    # Note that you do not have to rerun grub after #making changes to this
    # file NOTICE: You do not have a /boot partition. #This means that
    # all kernel and initrd paths are relative to /, eg.
    # root (hd0,1)
    # kernel /boot/vmlinuz-version ro root=/dev/hda2
    # initrd /boot/initrd-version.img
    #boot=/dev/hda2
    default=1
    timeout=10
    splashimage=(hd0,1)/boot/grub/splash.xpm.gz
    hiddenmenu
    title Fedora Core (2.6.11-1.1369_FC4)
         root (hd0,1)
         kernel /boot/vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/ rhgb quiet
         initrd /boot/initrd-2.6.11-1.1369_FC4.img
    title Windows
         rootnoverify (hd0,0)
    makeactive
         chainloader +1
    title Solaris
         rootnoverify (hd0,2)
         makeactive
         chainloader +1
    SH: I think you could use Mepis as a much smaller
    Linux that would provide the grub boot loader -- Boot
    Magic is 13mb and costs money. Also remember to
    conserve on separate primary boot partitions since
    you only have 4. Solaris 10 cannot be installed in an
    extended partition nor does trying to make it boot
    directly out of boot.ini work, but indirectly thru grub.
    I used Partition Magic at first but it gets hosed after
    the Solaris 10 install and it is a bit of work to fix it so
    I used Win XP Computer Management--> Disk
    Management later to create the fat32 parition and
    bootit Ng to create the swap partition, which is free
    as long as you don't install it to the hard drive. (trial)
    This is easier with two master hard drives connected
    to two different ide connectors on the motherboard,
    slave the cdrom(s), if both disks are working well,
    since you can use the MBRs without worry.
    Good luck,
    Cyberdiction at hotmail dot com

  • Lost one primary and two extended partitions - testdisk isn't working

    Hey everyone... long time no see. I needed a break
    ("Conclusion" below if the following is TL;DR)
    Background:
    First up... don't pull the plug on your PC, even if you are over-fatigued, and try to minimize the number of times you have to force-switch your system off. Read on if you would like to know why.
    About four days ago, I was working on something, and everything was all good. Nothing was wrong, awry, or weird, and the only thing I could've written home about my partition structure was that cfdisk showed all the metadata for my extended entries.
    That all changed one simple reboot later.
    Three days ago, I greeted a system that booted up perfectly, and before entering X I decided to work on a document in textmode. Once I'd had enough of that, I fired up X and continued working on some changes to the QEMU VGA BIOS that makes it look like an old 512K VGA card from 1991 that I have. Or rather, tried to. I fired up my editor and a console and tried to compile... and /stuff, /dev/sda4, wasn't mounted. No problem; it isn't in my fstab. I should get around to adding it one da--whoa, what the...? /dev/sda4 is SWAP?!
    It got worse from there. Three days ago I was extremely fatigued because I left a CRT plugged in that I don't usually plugged in (and I didn't know until the next morning!), and being tragically sensitive to radiation, I was rather unreasonable (and had been all day, even while away from the computer), so didn't think clearly about what I did next.
    First, I proceeded to use cfdisk to change the partition type from 82 (Swap/Solaris) to 83 (Linux). The partition table decided not to "catch", so cfdisk pointed out that the prudent thing to do would be to reboot, which I ignored (major failure #1) and fired up TestDisk to try and fix (major failure #2) and was like "Enter, enter, enter, enter, enter, enter, ^C, reboot" (catastrophic failure #1).
    ***************** FILESYSTEM CHECK FAILED ****************
    * Please repair manually and reboot. Note that the root *
    * file system is currently mounted read-only. To remount *
    * it read-write type: mount -n -o remount,rw / *
    * When you exit the maintenance shell the system will *
    * reboot automatically. *
    The rest was history, unfortunately.
    I had a 26GB "hole" of free space in my hard disk and... eek. Deciding I'd done enough damage, I fought off my OCD/Autistic "GAH, the computer is DEAD, DO SOMETHING" and got some sleep.
    The next day (the day I discovered the CRT was off but plugged in) I decided to have a crack at fixing the problem.
    Conclusion:
    Worst case scenario, I thought, would be that the 26GB of data was simply gone, and best case, I'd have a ~5GB hole in the disk someplace that would hold my two Syllable AFS partitions (partition type 2A), which I was sure no utility I knew of would be able to figure out. I was almost completely correct: I got my 17GB /storage partition back (WHEW), but I lost my two Syllable partitions as well as a third primary partition of unknown filesystem type.
    Here's my evidence:
    Going through /var/log reveals files showing lines like
    messages.log.2:May 14 10:27:53 hornet sda1 sda2 sda3 < sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda12 sda13 > sda4
    This proves that sda4 did once exist as a real partition and wasn't mountable as the result of a freak accident on the disk.
    In addition, sda4 is indicated to be a primary partition at the end of my extended partitions. This makes me wonder what on earth's happened here, because I only have a single "Free Space" hole inside my extended header, not after it. Did the extended partition header somehow manage to get resized? :S
    I remember - and have the .bash_history to prove - that I chowned and chgrp'd /stuff (ie /dev/sda4) such that I could read/write it as my own user, and this isn't possible with FAT* partitions - you have to dive into /etc/fstab to make them user-writable, and I know I didn't do that. So this partition is possibly ext2, ext3, or JFS (and I'm thinking JFS).
    While probably not useful, the fact that the "Free Space" hole is after sda9 but before sda10 lines up with the fact that I had to move sda12 and 13 (a FAT32 partition as well as a JFS partition, the one I mount at /storage) down two notches in order for my system to boot up without complaint.
    TestDisk is only listing what I've already got fixed and in working order at this point. In other words, it isn't seeing the other partition. Incidentally, PhotoRec, a program analogous to TestDisk, probably wouldn't be useful here since I doubt that partition contains images.
    -dav7
    Last edited by dav7 (2009-06-24 04:10:59)

    You really got yourself into a big mess ....
    As for the partitions magically changing places .... have you recently used gparted (or parted which I believe is the program that actually does the changes) to resize or move any partitions? If you have that's the reason why the partition table is so messed up.
    If testdisk can't fix that I have no idea of what can ... once I had a similar problem and testdisk saved the day but I had only ntfs/ext3/swap/extended primary partitions and logical ext3/ntfs partitions.

  • Download error: Unable to expand "___" into "Downloads". (Error 2 - No such file or directory).

    I keep on getting the message "Download error: Unable to expand "___" into "Downloads". (Error 2 - No such file or directory)" when I try to unarchive zip files that I have just downloaded. Can anyone walk me through how to fix this?

    Possible solution if dealling with MobileMe gallery. 
    I ran into this problem while downloading my mobileme gallery albums and videos. I can't tell if that is where you ran into your problem or not, but if it is, this is what worked for me. Most of my albums downloaded and expanded successfully, however about 5 downloaded and would not expland giving the error you got. After several retries, I selected one of the albums, clicked the settings icon, changed the name (added "-2" to the name). This time the downloaded zip file expanded successfully. This worked for all of the albums that I had problems with.

  • Extended partition on old MBR HDD makes Windows 7 UEFI boot fail

    There seems to be a bug in Windows 7 Pro x64 that prevents it from booting on a GPT partitioned HDD when the same machine also has an MBR partitioned HDD with an extended partition.
    I have a UEFI bootable PC with two HDDs:
    Disk 0 is GPT partitioned and contains Windows 7 Pro x64 and openSUSE systems.
    Disk 1 is MBR partitioned and contains Windows XP Pro x64 systems and bootable ISO images.
    Both the disks also have separate partitions for data and for booting.
    They are normally booted via rEFInd on disk 0 as follows:
    UEFI => rEFInd  => Windows 7 or GRUB2.
    UEFI => rEFInd => disk 1 MBR => GRUB4DOS.
    I had previously installed Windows 7 when it was first released, but abandoned it in favour of XP and openSUSE instead.  With the end of support for XP I decided to re-install W7.  Before doing so I unplugged disk 1 to ensure that W7 booted completely
    independently of XP.  After installing W7 I installed SP1 and all the Windows updates.  The new W7 system could be booted without problem via rEFInd => \EFI\Microsoft\Boot\bootmgfw.efi
    However when I plugged in disk 1 W7 would no longer boot.  It displayed the message "Windows is Loading Files" as the bar progressed twice before returning to the rEFInd menu.  On selecting W7 again it presented the option to "Launch
    Startup Repair", but on doing so it too just displayed "loading files" and returned to the reEFInd menu. 
    I UEFI booted from the installation DVD and ran Repair.  When re-booted W7 presented a menu with choice of new and recovered systems, but both failed as before.  Neither could be booted in safe mode.  Booting directly from the UEFI firmware menu
    into W7, instead of via rEFInd, gave similar results. 
    Investigations showed that the problem is caused by the extended partition on disk 1.  If it is deleted, or just hidden by changing the partition type from 0x0F to 0x00, then W7 boots OK.  Plugging in an external USB HDD with logical partitions also
    prevents W7 from booting.
    This all seemed to be similar to the problem described in KB979374, so I downloaded the hotfix (404153_intl_x64_zip.exe), which is supposed to be applicable to Windows 7 as well as WindowsServer 2008 R2.  However when the hotfix was run it displayed "The
    update is not applicable to your computer" and logged the following error:
       error 2149842967 "" (Command line: ""C:\Windows\system32\wusa.exe" "<pathname>\Windows6.1-KB979374-x64.msu" ")
    Is this because the version of files mentioned in KB979374 is older (6.1.7600.20617) than the version of Winload.exe in my system (6.1.7601.17556)? 
    According to http://www.techienewsnetwork.com/247/22/ SP1 included hotfix 979374, but it doesn't appear in the list of Installed Updates given in my W7 control panel.  Should it, are hotfixes included in a service pack listed individually?  If
    not is there any way to tell whether or not hotfix 979374 has been applied? 
    How can W7 be booted without having to change the partition type code of  extended partitions every time, is there a newer hotfix that will fix the problem in Windows 7 SP1?
    Almost all the references I can find to this problem are at least 2 years old, which suggests it might have been fixed.  Does anyone else with an up to date Windows 7 SP1 have this problem with extended partitions.  An easy test is to plug in an external
    HDD with logical partitions and see if W7 will still boot.
    I don't want to convert disk 1 to GPT as that would make XP un-bootable.  Also GRUB4DOS only supports MBR, and it is very useful for booting ISO images as well as XP. 
    Cheers.

    Hi Wade,
    To be sure that openSUSE, XP, or any other software on my PC isn't part of the problem I decided to do a new install of Windows 7 on a blank HDD.  As I don't have a spare one I had to backup everything on disk 1 (MBR) and then wipe it, including the MBR,
    with zeros (using AOMEI Partition Assistant).
    I unplugged the original disk 0 so that the PC had just single completely blank HDD (previously disk 1),  UEFI booted the Windows 7 DVD and installed W7 again.  Unfortunately at this first attempt W7 partitioned the blank HDD as an MBR disk and booted
    in legacy BIOS mode, even though I had booted the DVD in UEFI mode.  So I deleted all the partitions it had just created and converted the disk to a GPT one.
    The next time I installed W7 it was a UEFI one, with an EFI system partition.  After installing SP1 and re-booting it a few times to make sure it was working OK I plugged in the external HDD with an extended partition before re-booting.  The result
    was exactly the same as reported above for the main GPT disk: it briefly flashed "Starting Windows" then displayed "Loading files" for a few seconds as the bars progressed; when Startup Repair was launched it failed as well.
    After removing the HDD I booted the new W7 and added some missing drivers and installed all the Windows Updates, including the optional ones.  Many hours later the result was a new up to date installation of Windows that worked perfectly (no errors in
    any log files), with no other software on the PC.  However as soon as the external HDD was plugged in it failed to boot, as described previously.
    I then ran Bootrec from the DVD, trying all the commands,  but the results were exactly the same: everything worked successfully but no Windows installations were found, and it didn't fix the problem. 
    The documentation on how to use Bootrec describes how to backup the BCD store that is on the C: drive (e.g. "ren c:\boot\bcd bcd.old").  However the BCD store for UEFI based systems is in the EFI system partition, NOT on the C: drive.  This suggest
    that Bootrec does not apply to UEFI based systems.
    Are you sure that the MBR is used when booting in UEFI mode?  From what I have read in several places (not MS pages) the protective MBR on the GPT isn't used, but instead the UEFI firmware runs \EFI\Microsoft\Boot\bootmgfw.efi which looks in the BCD store
    in the EFI partition.  Can you point me to any MS documentation please that explains exactly how UEFI booting works for Window 7, including its use of the MBR.
    Do you have a Windows 7 system that can boot from UEFI when an MBR disk with an extended partition is attached.  If so how is your installation different from the one I have just set up, i.e. Windows 7 installed on a PC with just
    a single empty GPT HDD?
    Do you work at Microsoft?  If so perhaps you could find out if anybody with a straightforward UEFI booted Windows 7 has problems when an MBR HDD with an extended partition is attached.
    Sorry for the delay in responding, but a lot of work was involved.

Maybe you are looking for