Jumpstart: Fdisk Partition Table Invalid

Hi,
I'm jumpstarting a Sun server with Solaris 10.
But during the jumpstart I received the next error:
Error: fdisk partition table invalid (c0t1d0)
Has someone an idea how I can fix this?

the previous jumpstart code would overwrite the entire disk.
what if i just want to fresh install (initial_install) the already existing Solaris partition.
The following jumpstart profile produce the same error message : "ERROR: fdisk partition table invalid" :
install_type initial_install
fdisk rootdisk solaris maxfree
pool root_pool auto 4g 4g rootdisk.s0
...Here is the console log :
Processing profile
        - Saving Boot Environment Configuration
        - Selecting cluster (SUNWCall)
       - Selecting geographic region (N_America)
        - Selecting geographic region (S_Europe)
        - Selecting geographic region (W_Europe)
        - Selecting geographic region (N_Europe)
        - Selecting geographic region (E_Europe)
        - Selecting geographic region (C_Europe)
        - Selecting all disks
        - Configuring boot device
        - Using disk (c1d0) for "rootdisk"
        - Creating "maxfree" Solaris fdisk partition (c1d0)
        - Using existing Solaris fdisk partition (c1d0)
ERROR: fdisk partition table invalid (c1d0)
ERROR: System installation failed
Solaris installation program exited.
...Note that fdisk is able to read the partitions :
fdisk -W - /dev/rdsk/c1d0p0
* /dev/rdsk/c1d0p0 default fdisk table
* Dimensions:
*    512 bytes/sector
*     63 sectors/track
*    255 tracks/cylinder
*   30400 cylinders
* systid:
* Id    Act  Bhead  Bsect  Bcyl    Ehead  Esect  Ecyl    Rsect       Numsect
  6     128  1         1        0         254      63      6        63            112392 
  7     0     0         1        7          254      63     1023    112455     102414375
  191  0    254      63       1023    254      63     1023    102526830 102382245
  15    0    254      63       1023    254     63      1023    204909075 283482990

Similar Messages

  • "Invalid segment" when shrinking a partitioned table

    I'm encountering the following error when trying to shrink space compact for a partitioned table. Would you know how can I go about this?
    I need to make it work.
    SQL> alter table PS_SGSN_1_MONTH modify partition P_201304 shrink space compact;
    alter table PS_SGSN_1_MONTH modify partition P_201304 shrink space compact
    ERROR at line 1:
    ORA-10635: Invalid segment or tablespace type
    My Oracle DB version is 11gR2

    Yes, that would be the right thing to do to check how and where MV is being used and what downtime you can get to fix this. Check if you can change the Materialized view to create based on primary key instead of Row id.
    Steps would be
    1 drop the materialized views related
    2 drop the materialized views logs
    3 shrink the tables and indexes
    4 recreate the materialized views log
    5 recreate the materialized views
    Also, there is a bug with the primary key as well. Check this
    Bug 13709220 - ORA-10663 when shrinking a master table of an MVIEW with primary key (Doc ID 13709220.8)

  • Can the command ADD partition (in table )invalid procedures,packages. ??

    Hi Folks.
    I know that drop a partition make invalid public synonyms, packages, functions.
    But.
    Add partition, can make invalid some object?
    I tested and didnt find objects invalid.
    Tks

    >
    I tested and didnt find objects invalid.
    >
    Please confirm that your tests included these steps
    1. created a partitioned table
    2. create at least one of every possible type of object that might depend on that table
    3. performed an ADD PARTITION that succeeded
    4. confirmed that NONE of the objects from step #2 were invalidated
    5. performed an ADD PARTITION that failed in various ways (local index partition can't be created, tablespace can't be extended, non-existent tablespace, etc)
    6. confirmed that NONE of the objects from step #2 were invalidated.
    See ALTER TABLE in the SQL Language Reference
    http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_3001.htm
    >
    Note:
    If you alter a table that is a master table for one or more materialized views, then Oracle Database marks the materialized views INVALID. Invalid materialized views cannot be used by query rewrite and cannot be refreshed. For information on revalidating a materialized view, see ALTER MATERIALIZED VIEW.
    >
    Did you test that the above MV is not invalidated?
    Did you test that adding a partition did not invalidate any local or global indexes?

  • Fdisk not creating correct partition table

    Hi,
    I am trying to use fdisk to create a couple of partitions on an external USB disk but it doesn't do correctly what I ask it to. It seems the problem is the difference in what the CHS (cylinder head sector) info says and what the start/size info says. For example for a 160GB disk with two partitions I would like to have it be (disk geometry is 7296/255/63 [117210240 sectors]):
    #: id cyl hd sec - cyl hd sec [ start - size]
    1: 12 0 1 1 - 763 254 63 [ 63 - 12273597] Compaq Diag.
    *2: 07 764 0 1 - 1023 254 63 [ 12273660 - 104936580] HPFS/QNX/AUX
    3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
    4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
    But if I try using fdisk this is what I end up with:
    #: id cyl hd sec - cyl hd sec [ start - size]
    1: 12 0 1 1 - 1023 254 63 [ 63 - 12273597] Compaq Diag.
    *2: 07 1023 254 63 - 1023 254 63 [ 12273660 - 104936580] HPFS/QNX/AUX
    3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
    4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
    So as you can see the start/size info is right, but the CHS numbers are not (the end of partition 1 is not correct and the begining and end of partition 2 is not correct). The commands that I gave to fdisk to do this were:
    fdisk:*1> edit 1
    Starting Ending
    #: id cyl hd sec - cyl hd sec [ start - size]
    1: 12 0 1 1 - 1023 254 63 [ 63 - 12273597] Compaq Diag.
    Partition id ('0' to disable) [0 - FF]: [12] (? for help)
    Do you wish to edit in CHS mode? [n] y
    BIOS Starting cylinder [0 - 7295]: [0]
    BIOS Starting head [0 - 254]: [1]
    BIOS Starting sector [1 - 63]: [1]
    BIOS Ending cylinder [0 - 7295]: [1023] 763
    BIOS Ending head [0 - 254]: [254]
    BIOS Ending sector [1 - 63]: [63]
    and
    fdisk:*1> edit 2
    Starting Ending
    #: id cyl hd sec - cyl hd sec [ start - size]
    *2: 07 1023 254 63 - 1023 254 63 [ 12273660 - 104936580] HPFS/QNX/AUX
    Partition id ('0' to disable) [0 - FF]: [7] (? for help)
    Do you wish to edit in CHS mode? [n] y
    BIOS Starting cylinder [0 - 7295]: [1023] 764
    BIOS Starting head [0 - 254]: [254] 0
    BIOS Starting sector [1 - 63]: [63] 1
    BIOS Ending cylinder [0 - 7295]: [1023] 7295
    BIOS Ending head [0 - 254]: [254]
    BIOS Ending sector [1 - 63]: [63]
    How can I fix this? I have tried both the CHS method and the default (start/size) method when creating the partitions and neither give the completely correct results. I have tried completely erasing the partition table and recreating it, but nothing seems to give me what I would think should be no big deal. I am puzzled as to how one set of info (ie CHS) does not agree with the start/size info??? I think the 1023 value for cylinders is OK for the end of partition 2 due to some funny WIndows bit of trivia, but the CHS for end of part 1 and start of part 2 should be correct since they are less than 1023.
    The disk does have an MBR type partition table. I am doing this on a SATA external drive attached to a USB DriveWire if that makes a difference.
    What am I doing wrong? Can I get there using fdisk on my MacBook?
    Thanks ....
    -Bob

    Well, I have given up on using fdisk and just decided to edit the raw disk with a hex editor and modify the appropriate bytes of the partition table. The first 512 bytes of the disk contain this info in the following format:
    446 bytes of boot code and other stuff
    64 bytes of partition info (16 bytes for each of four partitions)
    2 bytes with special 0x55 0xAA values
    512 bytes total
    Each partition table entry has the structure:
    Boot flag - 1 byte which is either 0x0 or 0x80
    CHS Begin - 3 bytes for cylinder, head, sector
    Type - 1 byte for what type of filesystem partition 1 is
    CHS End - 3 bytes for cylinder, head, sector
    LBA Begin - 4 bytes
    # of sectors - 4 bytes
    I found explanations at http://www.viralpatel.net/taj/tutorial/partition_table.php and http://www.ata-atapi.com/hiwtab.html had a couple of examples to study.
    So thanks for everyone's suggestions. I just wish that fdisk really worked like it is supposed to without the funny business!!
    -Bob

  • Getting a Invalid Partition Table! message

    Getting this message: Invalid Partition Table! after I ran a Windows Update downloads and install. My laptop is looping in start up. Not able to press F(, because the function is not activated. Anyway, I am not able to make a repair. The only thing I'm able
    to run is the DOS-promt. And I can find this OS drive (C:\). I tested the SSHD with succes.
    How did this happen? And how to solve this problem without a reinstall of Windows?

    Do you have a Windows 8.1 media or a bootable USB drive?If then you can repair Start up/MBR.
    Insert the Windows 8 Installation Disc in your system’s optical drive/a bootable USB
    Select Repair option.
    Choose Troubleshoot > Advanced.
    From Advanced option,launch Command Prompt.
    Enter the following command:
    bootrec.exe /fixmbrReboot after the completion of the above command.
    S.Sengupta, Windows Entertainment and Connected Home MVP

  • "No partition table found" Can't access to my DATA partition

    Hello friends! It's happened a catastrophe! Yesterday I was resizing partitions on my hard drive, divided in this way:
    1: ext4 containing CHAKRA
    2: swap
    3: extended
         3rd: DATA
         And here there were all the other partiotions containing ARCH (/ / var / home)
    I decided to delete all partitions of Arch, and to extend the DATA partition with the space available obtained by the elimination of arch ... I have done these steps on chakra, the extended partition was unmounted and free to work, I left my computer on all night without even using it so as not to interfere, but 10 minutes ago I go to check and I discover that my computer is off (do not know why because the battery was attached, maybe electricity went down for a considerable period of time and in any case my battery lasts a very little so it has not resisted until the return of electricity).
    I turn my computer on, I sign in it with Chakra and I find out that the extended partition is gone! Partitionmanager tells me "No partition table found" and all my data are disappeared!
    Is there a way to remedy this apocalypse? I truly don't know what to do, apart committing suicide!
    Last edited by TheImmortalPhoenix (2012-01-18 05:30:20)

    There is no drive! There is only free space, and all i can do is to create a new partition...
    This is the output of fdisk -l
    > sudo fdisk -l
    Warning: ignoring extra data in partition table 5
    Warning: ignoring extra data in partition table 5
    Warning: ignoring extra data in partition table 5
    Warning: invalid flag 0x131b of partition table 5 will be corrected by w(rite)
    Disk /dev/sda: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x0006fdf9
    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 31459327 15728640 83 Linux
    /dev/sda2 35653632 976766975 470556672 f W95 Ext'd (LBA)
    /dev/sda3 31459328 35653631 2097152 82 Linux swap / Solaris
    /dev/sda5 ? 3648605328 6213431608 1282413140+ fb VMware VMFS
    Partition table entries are not in disk order

  • [Solved] corrupted partition table

    Yours truly was experimenting with alternative bootloaders today and ended up with a corrupted partition table. Yours truly had backed up the bootloader part of the MBR today but neglected to copy the rest. Guess who is feeling very stupid right now.
    Here is what fdisk has to say about my disk,
    root@sysresccd /root % fdisk -l /dev/sdb
    Warning: ignoring extra data in partition table 5
    Warning: ignoring extra data in partition table 5
    Warning: ignoring extra data in partition table 5
    Warning: invalid flag 0x2404 of partition table 5 will be corrected by w(rite)
    Disk /dev/sdb: 30.0 GB, 30020272128 bytes
    255 heads, 63 sectors/track, 3649 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x4b36bdea
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 895 3444 20482875 7 HPFS/NTFS
    /dev/sdb2 1 894 7181023+ b W95 FAT32
    /dev/sdb3 3445 7476 32387040 5 Extended
    /dev/sdb5 ? 142349 151007 69551332+ 19 Unknown
    Partition table entries are not in disk order
    This looks somewhat promising. I had only three partitions on the disk (I don't remember if any were logical), one swap, one large thing for pacman stuff and of course root.
    By suggestion of this I will try testdisk (version 6.11 from Sys Resc CD).
    Last edited by fsckd (2011-09-17 21:22:59)

    Unfortunately my copy of sys resc cd does not have fixparts.
    testdisk worked like a charm and my partitions were recovered, one swap, one JFS and one ext4.
    (Incidentally it was Windows which damaged the MBR in the first place.)

  • An interesting error: "recursive partition table"

    So I just found an old 8 Gb SD card I had forgotten about (and was overjoyed because I had just said "if only I had a bigger SD card". Why do good things happen to bad people?). Several months ago I'd used some Windows tool, I think, to make a live USB for ArchBang, which hadn't worked. I put it in my computer and ran `fdisk -l` and got this:
    # fdisk -l
    Disk /dev/sdd: 7948 MB, 7948206080 bytes
    64 heads, 32 sectors/track, 7580 cylinders, total 15523840 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x0c7e5ddb
    Device Boot Start End Blocks Id System
    /dev/sdd1 * 0 1003519 501760 17 Hidden HPFS/NTFS
    Disk /dev/sdd1: 513 MB, 513802240 bytes
    64 heads, 32 sectors/track, 490 cylinders, total 1003520 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x0c7e5ddb
    Device Boot Start End Blocks Id System
    /dev/sdd1p1 * 0 1003519 501760 17 Hidden HPFS/NTFS
    When I ran gparted (a graphical partition editor), it threw up "Invalid partition table: recursive partition on /dev/sdd". Gparted then treats the disk as unformatted, which is presumably its "fallback" behaviour.
    This isn't actually a problem for me as I don't need any of the data on the card, but I thought it was a pretty interesting error, so I'd post it here for discussion. I can't work out what's going on, but it seems to me that someething is seriously bawsled up here! Perhaps there was a bug in the library the Windows utility used? I haven't found anything similar online, although this was interesting.
    Today may be a day for me to read up on partition tables and the heads/disks/cylinders/sectors/tracks abstractions!

    I get the same result when using dd to write the archlinux installer image to usb. It's nothing really. it can easily have a new partition table made with gparted. It's likely the tool you used in Windows also wrote the bootable image with a low level utility similar to dd. dd generally starts at the very beginning of a disk when pointed at the device and not a partition number. /dev/sdb instead of /dev/sdb1. Meaning it overwrites the first 512byte sector too(mbr) With whatever the image/ISO contains. I've never regarded it as an issue. Just kinda confusing to tools that expect data like a partition table to be present in a normal structure.

  • How can I create my own tag name while creating a partition table.

    I have X4500 running Solaris 10. I have formatted a disk and created partition table as given below.
    Specify disk (enter its number): 0
    selecting c0t0d0
    [disk formatted]
    /dev/dsk/c0t0d0s0 is part of active ZFS pool zpool1. Please see zpool(1M).
    FORMAT MENU:
    disk - select a disk
    type - select (define) a disk type
    partition - select (define) a partition table
    current - describe the current disk
    format - format and analyze the disk
    fdisk - run the fdisk program
    repair - repair a defective sector
    label - write label to the disk
    analyze - surface analysis
    defect - defect list management
    backup - search for backup labels
    verify - read and display labels
    inquiry - show vendor, product and revision
    volname - set 8-character volume name
    !<cmd> - execute <cmd>, then return
    quit
    format> partition
    PARTITION MENU:
    0 - change `0' partition
    1 - change `1' partition
    2 - change `2' partition
    3 - change `3' partition
    4 - change `4' partition
    5 - change `5' partition
    6 - change `6' partition
    select - select a predefined table
    modify - modify a predefined partition table
    name - name the current table
    print - display the current table
    label - write partition map and label to the disk
    !<cmd> - execute <cmd>, then return
    quit
    partition> print
    Current partition table (original):
    Total disk sectors available: 1953508749 + 16384 (reserved sectors)
    Part Tag Flag First Sector Size Last Sector
    0 usr wm 34 4.00GB 8388641
    1 usr wm 8388642 2.00GB 12582945
    2 usr wm 12582946 200.00GB 432013345
    3 usr wm 432013346 175.00GB 799014945
    4 usr wm 1166180386 375.43GB 1953508748
    5 usr wm 799014946 175.00GB 1166016545
    6 usr wm 1166016546 80.00MB 1166180385
    8 reserved wm 1953508749 8.00MB 1953525132
    partition>
    I am unable to specify my own tag name. How can I change the tag name to one of my interest.
    I need to create 3 partitions as told below
    partitions:
    /earth
    /mars
    /work
    /earth and /work should be roughly equal in size, /mars should be twice the size of the others, if that is possible. If not 3 partitions of equal size will do.
    Please, help me .
    Thank you.

    Exactly 1TB? Slightly under/slightly over?
    Traditional Solaris disk labels are in VTOC format, but this format cannot describe disks larger than 1TB. So EFI labels must be used on disks larger than 1TB. Setup is slightly different.
    Are these physical disks or LUNs from a SAN array? If they are array LUNS, it is often the case that they don't have a Sun label of any type. So...
    #1 Apply a Solaris label
    If the LUNS don't have a label (when selected in 'format', it gives a warning that no label is present and offers to apply a label immediately). When run non-interactively, format assumes "yes" for any questions. So all you'd have to do is select every disk to have it apply labels to any unlabled disk. Run 'format' once and find the highest number (maybe it's 50 for you). Create a text file that looks like this:
    disk 1
    disk 2
    disk 3
    disk 50Then feed that to format like this:
    # format -f /tmp/disklist or whatever you've named the file.
    #2 Apply the partition layout to all disks you want.
    You asked if you should do the same procedure, but I don't see that you've actually done anything above other than print out the existing layout. Take one of your 48 drives and partition it the way you want manually (set the slices to the sizes that you want). Then you can copy the layout of that disk to others. You only want to do this between disks/LUNs of the same size. As an example, if you've explicitly partitioned c1t0d0 and you want to apply this to c1t1d0, do this:
    # prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2Repeat for all of your other disks.
    Darren

  • Domain index on list-partitioned table?

    Hi,
    I have a list-partitioned table, and wanted to create a partitioned Oracle Text index on it. I keep getting an error, and am now wondering if it's possible to do. Here is my syntax:
    CREATE INDEX SCHEMA1.IDX_ALL_TEXT_LOCAL ON SCHEMA1.TABLE1(ALL_TEXT)
    INDEXTYPE IS CTXSYS.CONTEXT
    LOCAL
    (PARTITION PTN1 PARAMETERS('sync (on commit) storage ptn1'),
    PARTITION PTN2 PARAMETERS('sync (on commit) storage ptn2'),
    PARTITION PTN3 PARAMETERS('sync (on commit) storage ptn3'),
    PARTITION PTN4 PARAMETERS('sync (on commit) storage ptn4'),
    PARTITION PTN5 PARAMETERS('sync (on commit) storage ptn5'),
    PARTITION PTN6 PARAMETERS('sync (on commit) storage ptn6'),
    PARTITION PTN7 PARAMETERS('sync (on commit) storage ptn7'),
    PARTITION PTN8 PARAMETERS('sync (on commit) storage ptn8')
    PARAMETERS('section group my_group lexer new_lexer');
    ERROR at line 1:
    ORA-29850: invalid option for creation of domain indexes
    Any advice would be much appreciated.
    Thanks,
    Nora

    ... will it spread the index across the tablespaces that are associated with each partition?No, as demonstrated below.
    SCOTT@orcl_11gR2> CREATE TABLE table1
      2       ( id         NUMBER(6),
      3         all_text      VARCHAR2 (20)
      4       )
      5  PARTITION BY LIST (id)
      6   (PARTITION ptn1 VALUES (2,4) TABLESPACE example,
      7    PARTITION ptn2 VALUES (3,9) TABLESPACE example
      8   )
      9  /
    Table created.
    SCOTT@orcl_11gR2> INSERT ALL
      2  INTO table1 VALUES (2, 'test2')
      3  INTO table1 VALUES (3, 'test3')
      4  INTO table1 VALUES (4, 'test4')
      5  INTO table1 VALUES (9, 'test9')
      6  SELECT * FROM DUAL
      7  /
    4 rows created.
    SCOTT@orcl_11gR2> CREATE INDEX IDX_ALL_TEXT_LOCAL
      2  ON TABLE1 (ALL_TEXT)
      3  INDEXTYPE IS CTXSYS.CONTEXT
      4  /
    Index created.
    SCOTT@orcl_11gR2> SELECT table_name, tablespace_name
      2  FROM   user_tab_partitions
      3  WHERE  table_name = 'TABLE1'
      4  /
    TABLE_NAME                     TABLESPACE_NAME
    TABLE1                         EXAMPLE
    TABLE1                         EXAMPLE
    2 rows selected.
    SCOTT@orcl_11gR2> SELECT table_name, tablespace_name
      2  FROM   user_tables
      3  WHERE  table_name LIKE '%IDX_ALL_TEXT_LOCAL%'
      4  /
    TABLE_NAME                     TABLESPACE_NAME
    DR$IDX_ALL_TEXT_LOCAL$I        USERS
    DR$IDX_ALL_TEXT_LOCAL$R        USERS
    DR$IDX_ALL_TEXT_LOCAL$N
    DR$IDX_ALL_TEXT_LOCAL$K
    4 rows selected.
    SCOTT@orcl_11gR2>

  • Is my partition table corrupt? Why does Boot Camp hate me?

    Hi folks
    I have an iMac (27-inch, Mid 2010) (iMac11,3, with Boot ROM IM112.0057.B01).
    I replaced the internal SuperDrive with an SSD, which is now my primary boot device:
    iMac:/ michthom$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *250.1 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS SSD                     248.1 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    iMac:/ michthom$ sudo gpt -r -vv show disk0
    Password:
    gpt show: disk0: mediasize=250059350016; sectorsize=512; blocks=488397168
    gpt show: disk0: PMBR at sector 0
    gpt show: disk0: Pri GPT at sector 1
    gpt show: disk0: Sec GPT at sector 488397167
          start       size  index  contents
              0          1         PMBR
              1          1         Pri GPT header
              2         32         Pri GPT table
             34          6       
             40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
         409640  484620800      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      485030440    1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      486299976    2097159       
      488397135         32         Sec GPT table
      488397167          1         Sec GPT header
    So far so good.
    I want to use the original internal HDD both to run Windows in Boot Camp mode, and to have a partition for my bulk data that doesn't need to be on the SSD.
    I reformatted the HDD as a single HFS+ partition, GUID partition table.
    I used BCA to create a Windows USB boot device from the Windows 8.1 media after following the hacking in this link.
    When the iMac restarted after creating the 250Gb Windows partition on the internal HDD, I got the "no boot device" screen.
    I restarted holding Option/Alt and booted from EFI Boot on the USB stick. Windows installer started, at least. Serial number accepted, on to picking a location.
    The installation balked when I tried to select the BOOTCAMP partition, with the warning that the disk was formatted as MBR - eh? Why?
    So, the current state of the internal HDD must be wrong somehow, but I don't see how to fix it (confidently) and would like someone to point me in the right direction (please!)
    iMac:/ michthom$ diskutil list
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.0 TB     disk1
       1:                        EFI EFI                     209.7 MB   disk1s1
       2:                  Apple_HFS Internal                751.9 GB   disk1s2
       3:       Microsoft Basic Data BOOTCAMP                248.0 GB   disk1s3
    iMac:/ michthom$ sudo gpt -r -vv show disk1
    gpt show: disk1: mediasize=1000204886016; sectorsize=512; blocks=1953525168
    gpt show: disk1: Suspicious MBR at sector 0
    gpt show: disk1: Pri GPT at sector 1
    gpt show: disk1: Sec GPT at sector 1953525167
           start        size  index  contents
               0           1         MBR
               1           1         Pri GPT header
               2          32         Pri GPT table
              34           6        
              40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
          409640  1468478336      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      1468887976      263256        
      1469151232   484372480      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      1953523712        1423        
      1953525135          32         Sec GPT table
      1953525167           1         Sec GPT header
    gdisk has this to say:
    iMac:/ michthom$ sudo gdisk /dev/disk1
    Password:
    GPT fdisk (gdisk) version 0.8.10
    Warning: Devices opened with shared lock will not have their
    partition table automatically reloaded!
    Partition table scan:
      MBR: hybrid
      BSD: not present
      APM: not present
      GPT: present
    Found valid GPT with hybrid MBR; using GPT.
    Command (? for help): x
    Expert command (? for help): o
    Disk size is 1953525168 sectors (931.5 GiB)
    MBR disk identifier: 0x4F5BB38B
    MBR partitions:
    Number  Boot  Start Sector   End Sector   Status      Code
       1                     1       409639   primary     0xEE
       2                409640   1468887975   primary     0xAF
       3            1469151232   1953523711   primary     0x0B
    Expert command (? for help): p
    Disk /dev/disk1: 1953525168 sectors, 931.5 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 3E1D7EF9-F86E-4552-8F40-BE9754C3C73F
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 1953525134
    Partitions will be aligned on 8-sector boundaries
    Total free space is 264685 sectors (129.2 MiB)
    Number  Start (sector)    End (sector)  Size       Code  Name
       1              40          409639   200.0 MiB   EF00  EFI System Partition
       2          409640      1468887975   700.2 GiB   AF00  Internal
       3      1469151232      1953523711   231.0 GiB   0700  BOOTCAMP
    Any help / pointers gratefully accepted!
    Mike

    Thanks to Loner T and some more reading, I think I'm now sorted out.
    I found that marking the first partition on the USB stick as Active made no difference - my only option was to boot from the "EFI boot" option at startup (when holding down the alt/option key).
    So to get the Windows installer to behave, I used gdisk to write a new protective MBR before rebooting to the USB stick, as shown below.
    With the protective MBR in place (rather than hybrid), the Windows installer was happy to reformat the chosen partition and the installation began.
    I'll try to report back once all is installed and working, but once again I owe my sanity to the generosity and patience of strangers!
    Mike
    bash-3.2# gdisk /dev/disk0
    GPT fdisk (gdisk) version 0.8.10
    Warning: Devices opened with shared lock will not have their
    partition table automatically reloaded!
    Partition table scan:
      MBR: hybrid
      BSD: not present
      APM: not present
      GPT: present
    Found valid GPT with hybrid MBR; using GPT.
    Command (? for help): x
    Expert command (? for help): o
    <snipped>
    Number  Boot  Start Sector  End Sector  Status      Code
      1                    1      409639  primary    0xEE
      2                409640  1468887975  primary    0xAF
      3            1469151232  1953523711  primary    0x0B
    Expert command (? for help): p
    <snipped>
    Number  Start (sector)    End (sector)  Size      Code  Name
      1              40          409639  200.0 MiB  EF00  EFI System Partition
      2          409640      1468887975  700.2 GiB  AF00  Internal
      3      1469151232      1953523711  231.0 GiB  0700  BOOTCAMP
    Expert command (? for help): v
    No problems found. 264685 free sectors (129.2 MiB) available in 3
    segments, the largest of which is 263256 (128.5 MiB) in size.
    Expert command (? for help): x
    <snipped>
    n create a new protective MBR
    <snipped>
    Expert command (? for help): n
    Expert command (? for help): w
    Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
    PARTITIONS!!
    Do you want to proceed? (Y/N): y
    OK; writing new GUID partition table (GPT) to /dev/disk0.
    Warning: Devices opened with shared lock will not have their
    partition table automatically reloaded!
    Warning: The kernel may continue to use old or deleted partitions.
    You should reboot or remove the drive.
    The operation has completed successfully.
    bash-3.2# gdisk /dev/disk0
    GPT fdisk (gdisk) version 0.8.10
    Warning: Devices opened with shared lock will not have their
    partition table automatically reloaded!
    Partition table scan:
      MBR: protective
      BSD: not present
      APM: not present
      GPT: present
    Found valid GPT with protective MBR; using GPT.
    Command (? for help): x
    Expert command (? for help): o
    Disk size is 1953525168 sectors (931.5 GiB)
    MBR disk identifier: 0x00000000
    MBR partitions:
    Number  Boot  Start Sector  End Sector  Status      Code
      1                    1  1953525167  primary    0xEE
    Expert command (? for help): p
    <snipped>
    Number  Start (sector)    End (sector)  Size      Code  Name
      1              40          409639  200.0 MiB  EF00  EFI System Partition
      2          409640      1468887975  700.2 GiB  AF00  Internal
      3      1469151232      1953523711  231.0 GiB  0700  BOOTCAMP

  • Unrecognized partition table for drive 80 error??

    Currently running leopard on a macbook pro.
    Formatted w bootcamp and running Windows Vista Ultimate.
    Installation went fine reformated drive to ntfs 45gigs.
    But when booting into windows I get this error message
    "unrecognized partition table for drive 80"
    Then the system boots into vista as normal but that error message is annoying.
    Tells me to fix bootmgr using fdisk. How do I do that?
    Thanks.

    I previously had Vista installed under the beta with Tiger and there was no issues at all regarding boot times or error messages. (Boot times being quite nippy considering)
    I did reformat the hard drive space partitioned in side Vista installation as NTFS. As I am only a switcher for a year or so I imagine there may be something I am missing but given the text when I try to boot into Vista, it looks to be the boot loader that is erroring and that looks the same as a GRUB loader failing.
    I just do not get why a BETA product would work fine, then after a fresh installation of the new Mac OSX 10.5 with the final version of boot camp I would receive errors like this.
    I have reclaimed the hard drive space and split the disk again but the same error persists. Previously I was showing off my Macbook to work mates showing how it handled Windows as well as the user friendly OSX. Now all I can show them is a 5 minute loading screen full of non booting Vista as they look at me like some kind of idiot. (Which depending on who you ask is possibly correct)

  • Correcting a bad block on ext4 and with GTP partition table

    Hello,
    I ran a SMART offline test today which came back as a bad block:
    # 1  Extended offline    Completed: read failure       30%      8363         3212759896
    This is my first run-in with a bad block, and since these drives are big and relatively new, I want to be proactive and fix any problems as they arise. Here is my setup:
    * I have 2x 2TB HDDs of same make and model, with the device link being /dev/sdc and /dev/sdd. /dev/sdc is the one with the error.
    * These two disks are linked via a Linux RAID 1 array under /dev/md0 which is then mounted on /storage.
    * Both drives have only 1 partition under a GUID Partition Table (GPT)
    I've looked around to try to find info on fixing bad blocks, and I came across this: smartmontools.sourceforge.net/badblockhowto.html
    However, it seems to be out-dated and geared for tools like fdisk (which I cannot use for GPT) and filesystems ext2/3 (although, due to the backwards compatibility, I'm sure it works with ext4 as well), and a lot fo the commands gives things like "Couldn't find valid filesystem superblock."
    Can someone point me in the right direction as to how I can fix this issue?
    EDIT:
    My noob is showing. I got the commands above to work, and when I check to see which file is using the bad block it shows this (after all the calculations involved, the block was 401594731):
    debugfs:  icheck 401594731
    Block   Inode number
    401594000       <block not found>
    So i'm assuming that there isn't a file assigned to it (empty space?). But then, when I use dd to read from it, it seems to read just fine:
    sudo dd if=/dev/md0 of=my.block skip=401594731 bs=4096 count=1
    1+0 records in
    1+0 records out
    4096 bytes (4.1 kB) copied, 0.0222587 s, 184 kB/s
    I think it's able to read it since the other disk in the RAID1 array doesn't have the bad block. But I just want to make absolutely sure that there is no file assigned to that block before I nuke it. Given the above information, would it be safe to remove this block from service?
    Last edited by XtrmGmr99 (2012-01-26 01:17:51)

    Yes I think the block is not in use. You can do
    debugfs: testb 401594731
    which will state it clearly ("not in use" vs "marked in use")

  • Create a GPT partition table and format with a large volume (solved)

    Hello,
    I'm having trouble creating a GPT partition table for a large volume (~6T). It is a RAID 5 (hardware) with 3 hard disk drives having a size of 3T each (thus the resulting 6T volume).
    I tried creating a GPT partition table with gdisk but it just fails at creating it, stopping here (I've let it run for like 3 hours...):
    Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
    PARTITIONS!!
    Do you want to proceed? (Y/N): y
    OK; writing new GUID partition table (GPT) to /dev/md126.
    I also tried with parted but I get the same result. Out of luck, I created a GPT partition table from Windows 7 and  2 NTFS partitions (15G and the rest of space for the other) and it worked just fine. I then tried to format the 15G partition as ext4 but, as for gdisk, mkfs.ext4 will just never stop.
    Some information:
    fdisk -l
    Disk /dev/sda: 256.1 GB, 256060514304 bytes, 500118192 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk label type: dos
    Disk identifier: 0xd9a6c0f5
    Device Boot Start End Blocks Id System
    /dev/sda1 * 2048 104861695 52429824 83 Linux
    /dev/sda2 104861696 466567167 180852736 83 Linux
    /dev/sda3 466567168 500117503 16775168 82 Linux swap / Solaris
    Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk label type: dos
    Disk identifier: 0x00000000
    Device Boot Start End Blocks Id System
    /dev/sdb1 1 4294967295 2147483647+ ee GPT
    Partition 1 does not start on physical sector boundary.
    Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk /dev/sdd: 3000.6 GB, 3000592982016 bytes, 5860533168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk label type: dos
    Disk identifier: 0x00000000
    Device Boot Start End Blocks Id System
    /dev/sdd1 1 4294967295 2147483647+ ee GPT
    Partition 1 does not start on physical sector boundary.
    Disk /dev/sde: 320.1 GB, 320072933376 bytes, 625142448 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk label type: dos
    Disk identifier: 0x5ffb31fc
    Device Boot Start End Blocks Id System
    /dev/sde1 * 2048 625139711 312568832 7 HPFS/NTFS/exFAT
    Disk /dev/md126: 6001.1 GB, 6001143054336 bytes, 11720982528 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 65536 bytes / 131072 bytes
    Disk label type: dos
    Disk identifier: 0x00000000
    Device Boot Start End Blocks Id System
    /dev/md126p1 1 4294967295 2147483647+ ee GPT
    Partition 1 does not start on physical sector boundary.
    WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
    gdisk -l on my RAID volume (/dev/md126):
    GPT fdisk (gdisk) version 0.8.7
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/md126: 11720982528 sectors, 5.5 TiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 8E7D03F1-8C3A-4FE6-B7BA-502D168E87D1
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 11720982494
    Partitions will be aligned on 8-sector boundaries
    Total free space is 6077 sectors (3.0 MiB)
    Number Start (sector) End (sector) Size Code Name
    1 34 262177 128.0 MiB 0C01 Microsoft reserved part
    2 264192 33032191 15.6 GiB 0700 Basic data partition
    3 33032192 11720978431 5.4 TiB 0700 Basic data partition
    To make things clear: sda is an SSD on which Archlinux has been freshly installed (sda1 for root, sda2 for home, sda3 for swap), sde is a hard disk drive having Windows 7 installed on it. My goal with the 15G partition is to format it so I can mount /var on the HDD rather than on the SSD. The large volume will be for storage.
    So if anyone has any suggestion that would help me out with this, I'd be glad to read.
    Cheers
    Last edited by Rolinh (2013-08-16 11:16:21)

    Well, I finally decided to use a software RAID as I will not share this partition with Windows anyway and it seems a better choice than the fake RAID.
    Therefore, I used the mdadm utility to create my RAID 5:
    # mdadm --create --verbose /dev/md0 --level=5 --raid-devices=3 /dev/sdb1 /dev/sdc1 /dev/sdd1
    # mkfs.ext4 -v -m .1 -b 4096 -E stride=32,stripe-width=64 /dev/md0
    It works like a charm.

  • Ubuntu wrecked partition table. Help to fix?

    (Macbook Pro 2013 15" Crystalwell 4 Core, 500GB SSD 16GB RAM)
    I should have known that installing Ubuntu next to Bootcamp was a bad idea.
    So here's what's up... Before this whole debacle began I had two separate partitions on my SSD. The primary partition was for Mavericks with 300GB. The second partition was to a Bootcamped Windows 7 with 150 GB of space. I left 50GB free between the two, which still left me at
    disk0s1 for EFI, ~200 MB
    disk0s2 for Macintosh HD, 300 GB
    disk0s3 for Recovery HD 650 MB
    disk0s4 for Bootcamp 148 GB
    Here's where my problem began. Genius me decided to attempt to install Ubuntu via live USB onto the 50GB space in between. I have reFIT installed so this wasn't a problem. After loading into Ubuntu and realizing that it wouldn't load into the 50GB space, I rebooted and installed alongside Windows (through the Ubuntu live usb) following the install GUI Prompt.
    The installation failed after it got hung on a CRON command and drained the battery from my unplugged computer sitting next to me in my bed (I fell asleep waiting for it to finish, even though it was at 100% battery when it started the installation). When I woke up my computer was dead, so I plugged it in. I started reFIT and booted into Windows after seeing that Ubuntu wasn't there. I was given the "Choose OS" prompt from Windows and Ubuntu wouldn't load, so I said screw it and went back to Mavericks. When I opened my Disk utility partitions table to see where it might have gone wrong....
    Great Odin's Raven.
    I now had ext4 partitions sitting above my bootcamp partition and linux-swap partitions below it. Absolutely no free space. I switched back to Windows, avoiding the failed Ubuntu OS, and uninstalled wubi from Windows (the universal uninstall for ubuntu, I used the Windows "uninstall application" application from Control Center), hopefully deleting the mess it had made of my drive table.
    It didn't.
    Since I couldn't delete the partitions back to free space around my bootcamp volume using Disk utility (insufficient hfs+ permissions or something like that), I decided to take a more agressive option. I installed partedMagic onto a live USB and once again rebooted my computer into the live USB. I went in and using gParted removed the partitions in front of the bootcamp volume and behind it reducing them to empty space. Good! Hoping for the best I went back to reFIT and booted into Windows...
    "No bootable device -- insert boot disk and press any key"
    Well crap.
    After some more research into why this wasn't working, I was sure that somehow my EFI wasn't loading the right area of my hard drive. Then I think I found out what happened. I ran diskutil list from terminal and saw this..
    IceMan-HomeBase:~ Tim$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.3 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            300.2 GB   disk0s2
       3:                  Apple_HFS Recovery HD             650.0 MB   disk0s3
       4:       Microsoft Basic Data BOOTCAMP                148.0 GB   disk0s6
    disk0s6. There's the problem. Mac doesn't like anything beyond disk0s4, which is where Bootcamp was originally and where it should be now, at disk0s4.
    If it were merely an issue of copying the bootcamp volume and repartitioning the hard drive, that wouldn't be a problem, but even WinClone doesn't like this volume. When I tried to do a copy, it threw an error saying "Invalid partition ID of 6"
    Here is my question.
    Is there a way to change the IDENTIFIER back to disk0s4 from disk0s6 and save my Windows 7 partition, is there some other way to save my files to a backup and clean install, or is he dead, Jim?
    Sorry if this was a little long-winded, but I figured too much information would be better than not enough.
    Thank you in advance for anyone brave enough to read this.
    TL;DR
    Partition table went bogus because of a bad Ubuntu OS install. Windows can't find a bootable device. Disk0s4 is now disk0s6. Possible way to change this?

    Problem solved, I used iPartition to resize the partition back to its original size after which I could copy all data off.

Maybe you are looking for