Wairning: No Solaris Fdisk Partition when managing disks in SMC

I just setup Solaris 10 on an old Dual Ultra Sparc II 400mhz system and I'm having a strange problem with the Solaris Management Console.
I'm using the SMC to manage my disks but everytime I select a disk I get the error "Warning: No Solaris Fdisk Partition" IF I continue and attempt to create the paritition it just fails. This is really strange. All of the disks give me this error, including the disk that I'm booting from.
Also, all the disks just say NAME as their label. Under Solaris 9 it actually showed me c0t1d0 etc..
All of the disks show up and operate fine when using other commands such as format or probe-scsi at the open boot prompt. As well all of the devices are present in /dev/rdsk.
Any help would be greatly apprecaited.

Instead of using SMC - why not use the format command - this utility has traditionally allowed the sysadmin to perform disk related tasks. If you plan to be "playing around" with disks on a solaris system - smc is not the tool. If you had intended to use ZFS - you're stuck with the command line (really sucks if you're dependent on GUIs). Either use the free SVM command line or get a copy of Veritas Foundation Basic Suite "free" (but crippled - limited to 4 volumes and 4 filesystems) - http://www.symantec.com/enterprise/sfbasic/index.jsp. At least with Veritas - the GUI will step you thru the entire process of disk management. I can't say that for SVM, with a bit of persistence and skill - you might not be disappointed. I prefer the command line because you can specify a myriad of parameters that the GUIs can't initutively tell you.
Storage Foundation Basic 4.1 is available on the following platforms:
* Solaris 10 x64
* RHEL 4 (Xeon, EM64T and AMD Opteron) and Itanium 2
* SLES 9 (Xeon, EM64T and AMD Opteron) and Itanium 2
Storage Foundation Basic 5.0 is available on the following platforms:
* Solaris 8, 9, 10 (SPARC)
* AIX 5.2/5.3
* Red Hat Enterprise Linux 4 (RHEL 4) on EM64T/Opteron
* Novell SUSE Enterprise Linux Server 9 (SLES) on EM64T/Opteron

Similar Messages

Formatting a HDD with the Solaris 8 install when the disk space is locked.

I added memory, a printer, and a CD Writer to my PC, and then I reinstalled solaris 8. At the point where it asks which drive to use, the only available drive, which is my C: drive, shows up with a negative disk space value. However, when I look at the partition size, it is 20 GB, and if I change it, it has no effect on the negative value. This is a reinstall of Solaris 8 onto the same drive. Is there a way to fdisk the drive. Solaris 8 won't do it, and Partition Magic seems to only work with linux, which does not seem compatible with Solaris?

I added memory, a printer, and a CD Writer to my PC, and then I reinstalled solaris 8. At the point where it asks which drive to use, the only available drive, which is my C: drive, shows up with a negative disk space value. However, when I look at the partition size, it is 20 GB, and if I change it, it has no effect on the negative value. This is a reinstall of Solaris 8 onto the same drive. Is there a way to fdisk the drive. Solaris 8 won't do it, and Partition Magic seems to only work with linux, which does not seem compatible with Solaris?

OK to use fdisk/100% "SOLARIS System" partition for RAID6 Virtual Drive?

Solaris newb, here - I am configuring an x4270 with 16 135 GB drives. Basic approach is
D0, D1: RAID 1 (Boot volume, Solaris, Oracle Software)
D2-D13: RAID 6 (Oracle dB files)
D14, D15: global spares
After configuring the RAID's w/WebBIOS Utility, I am now trying to format/partition the RAID 6 Virtual Drive, which shows up as 1.327 TB 'Optimal' in the MegaRAID Storage Manager. After hunting around the ether for advice on how to do this, I came across http://docs.oracle.com/cd/E23824_01/html/821-1459/disksxadd-50.html#disksxadd-54639
"Creating a Solaris fdisk Partition That Spans the Entire Drive"
which is painfully simple: after 'format', just do an 'fdisk' and accept the default 100% "SOLARIS System" partition. After doing this, partition>print and prtvtoc show this:
partition> print
Current partition table (original):
Total disk cylinders available: 59125 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 0 0 (0/0/0) 0
1 unassigned wm 0 0 (0/0/0) 0
2 backup wu 0 - 59124 1.33TB (59125/0/0) 2849529375
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 - 0 23.53MB (1/0/0) 48195
9 unassigned wm 0 0 (0/0/0) 0
# prtvtoc /dev/dsk/c0t1d0s2
* /dev/dsk/c0t1d0s2 partition map
* Dimensions:
* 512 bytes/sector
* 189 sectors/track
* 255 tracks/cylinder
* 48195 sectors/cylinder
* 59127 cylinders
* 59125 accessible cylinders
* Flags:
* 1: unmountable
* 10: read-only
* Unallocated space:
* First Sector Last
* Sector Count Sector
* 48195 2849481180 2849529374
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
2 5 01 0 2849529375 2849529374
8 1 01 0 48195 48194
My question: is there anything inherently wrong with this default partitioning? Database is for OLTP & fairly small (<200 GB), with about 140 GB being LOB images.
Thanks,
Barry

First off, RAID-5 or RAID-6 is fine for database performance unless you have some REALLY strict and REALLY astronomical performance requirements. Requirements that someone with lots of money is willing to pay to meet.
You're running a single small x86 box with only onboard storage.
So no, you're not operating in that type of environment.
Here's what I'd do, based upon a whole lot of experience with Solaris 10 and not so much with Solaris 11, and also assuming this box is going to be around for a good long time as an Oracle DB server:
1. Don't use SVM for your boot drives. Use the onboard RAID controller to make TWO 2-disk RAID-1 mirrors. Use these for TWO ZFS root pools. Why two? Because if you use live upgrade to patch the OS, you want to create a new boot environment in a separate ZFS pool. If you use live upgrade to create new boot environments in the same ZFS pool, you wind up with a ZFS clone/snapshot hell. If you use two separate root pools, each new boot environment is a pool-to-pool actual copy that gets patched, so there are no ZFS snapshot/clone dependencies between the boot environments. Those snapshot/clone dependencies can cause a lot of problems with full disk drives if you wind up with a string of boot environments, and at best they can be a complete pain in the buttocks to clean up - assuming live upgrade doesn't mess up the clones/snapshots so badly you CAN'T clean them up (yeah, it has been known to do just that...). You do your first install with a ZFS rpool, then create rpool2 on the other mirror. Each time you do an lucreate to create a new boot environment from the current boot environment, create the new boot environment in the rpool that ISN'T the one the current boot environment is located in. That makes for ZERO ZFS dependencies between boot environments (at least in Solaris 10. Although with separate rpools, I don't see how that could change....), and there's no software written that can screw up a dependency that doesn't exist.
2. Create a third RAID-1 mirror either with the onboard RAID controller or ZFS, Use those two drives for home directories. You do NOT want home directories located on an rpool within a live upgrade boot environment. If you put home directories inside a live upgrade boot environment, 1) that can be a LOT of data that gets copied, 2) if you have to revert back to an old boot environment because the latest OS patches broke something, you'll also revert every user's home directory back.
3. That leaves you 10 drives for a RAID-6 array for DB data. 8 data and two parity. Perfect. I'd use the onboard RAID controller if it supports RAID-6, otherwise I'd use ZFS and not bother with SVM.
This also assumes you'd be pretty prompt in replacing any failed disks as there are no global spares. If there would be significant time before you'd even know you had a failed disk (days or weeks), let alone getting them replaced, I'd rethink that. In that case, if there were space I'd probably put home directories in the 10-disk RAID-6 drive, using ZFS to limit how big that ZFS file system could get. Then use the two drives freed up for spares.
But if you're prompt in recognizing failed drives and getting them replaced, you probably don't need to do that. Although you might want to just for peace of mind if you do have the space in the RAID-6 pool.
And yes, using four total disks for two OS root ZFS pools seems like overkill. But you'll be happy when four years from now you've had no problems doing OS upgrades when necessary, with minimal downtime needed for patching, and with the ability to revert to a previous OS patch level with a simple "luactivate BENAME; init 6" command.
If you have two or more of these machines set up like that in a cluster with Oracle data on shared storage you could then do OS patching and upgrades with zero database downtime. Use lucreate to make new boot envs on each cluster member, update each new boot env, then do rolling "luactivate BENAME; init 6" reboots on each server, moving on to the next server after the previous one is back and fully operational after its reboot to a new boot environment.

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

I partitioned my MacBook Pro and installed Windows 8 in it.....now I can't find my partition when I pressed option key when booting up.....so how can I do to find the partition to boot...I can see it in the disk manager in Mac....any ideas? thanks..!..

I partitioned my MacBook Pro and installed Windows 8 in it.....now I can't find my partition when I pressed option key when booting up.....so how can I do to find the partition to boot...I can see it in the disk manager in Mac....any ideas? thanks..!..

Hi LamboMong,
just try this:
http://refit.sourceforge.net
install, reboot twice and choose the Windows-Partition on next startup.
(The apple-bootloader doesn't display all bootable harddisks.
With rEFIt you can boot from all partitions/harddisks on your computer.)
I hope that will solve your problem.
Daniel Fernau

How do I undo BC Partition repair in disk utility?

Here's the summary:
8-core MacPro2,1 running 10.6.8, Paragon NTFS for Mac, Bootcamp Win7.
4 internal HDD drives: two 1.5TBs for data, one 1TB for MacOS, one 1.5TB for Win7 bootcamp.
I mostly use the Mac side for music production (but rarely), and the Win side for business and everything else. Scores and scores of Win apps installed over the years. [4 monitor system], well over 500K files on the drive.
I just backed up the data from the two data-only drives, and made a bootable clone of the MacOS drive (SuperDuper). I have never successfully been able to clone the Win7 Bootcamp NTFS drive (even with Winclone back in 2009) because of volume sizes (or something). I decided to try again, from WITHIN Windows this time (all other attempts were from the Mac OS side).
I bought, downloaded, and installed Acronis True image from within the Win7 bootcamp system. [I obviously did not know that it was gonna modify my MBR, and I had no idea at the time that the GPT and MBR areas were somehow 'mingled' on a bootcamp drive.]
So, when I performed the Acronis-requested reboot (my default boot is into the Bootcamp/Win7 drive), it failed to boot and requested some Windows recovery media or something. I was concerned that anything i put in the DVD drive would sabotage my priceless (in retrospect) stable/optimized Win7 bootcamp system. So, i just hard-powered down the Mac and tried to restart.
I did the Alt/option key, and i was presented with the Mac or Win drive icons. I selected Win, and then I got a different boot error message--'no MBR found'.
But this time i realized that Acronis had stepped where it shouldn't have, and I figured the Mac side could fix the boot problem (maybe with bootcamp assistant or something).
If i had stopped THERE, and searched the forums i could have found how to fix THAT problem--that has been answered tons of times…
But, instead, i went to Disk Utility and asked it to repair my Bootcamp partition (I have Paragon NTFS and it has worked for years, and so I did not have a reason to doubt Disk Utility's ability to Repair an NTFS volume--not that i have tried it before, of course).
Disk Utility repair ran for about 10-15 minutes and said it fixed about 10-20 things.
The drive information (in the side bar and below) still had the BOOTCAMP partition, reported that it was NTFS, said that there was 308 GB still available of the 1.5TB drive, and that it contained 1.19TB 'used'. Looked normal to me.
I closed Disk Utility and then opened a Finder window to see if DU left any 'artifacts' of its 'fixes' on the BOOTCAMP partition, and all the files were gone! Even though DU said it had 1.19TB 'used', all of my files are gone. [I rebooted also, to verify that it was not some 'delayed reporting' issue.]
When I enable 'hidden files' to show, what I get on the Bootcamp partition are these three entries:
.DS_Store (16KB), .fseventsd folder (with a 1KB UUID file inside it), and a .Trashes folder with zero KB.
At this point, I panic and assume the position of despair. There is no 'undo' key for the D/U that I can find. I do an orderly shut down of the system, physically remove the Win7 BC drive, and make/verify a sector-by-sector clone of the drive (on a Win7 laptop, using Acronis--22 hours).
In Win7 Disk Management, the GPT partition (on the original drive) shows up and the BOOTCAMP partition shows up--with the proper size--but windows does NOT recognize the partition as being NTFS. It reports it as being RAW and 'urges' me to format it (yeah, right…).
So, I place the sector-by-sector duplicate back into the Mac, boot up (only the Mac OS is given as an option), and am ready to 'work on' recovering the Win7 BC partition (if possible).
I am avoiding trying to fix the booting problem, because recovery of the 1.2TB of a working system is much more critical for me.
The clone HDD reports the same in DU, except now the GPT partition shows up as greyed-out 'disk1s1', right above the "BOOTCAMP" partition in the sidebar. [I understand from researching this that disk1s1 is somehow related to the bootloader for BC?]
I used the demo version of Data Rescue 3 to scan for recoverable files from the drive, but it doesn't even report the .files. (I am running the deep scan now, but will take about another 9 hours to complete that).
Has anybody got any suggestions on how to reclaim this partition and its system?
Here are a couple of other details from diagnostic tools:
Model Name:    Mac Pro
Model Identifier:    MacPro2,1
Processor Name:    Quad-Core Intel Xeon
Processor Speed:    3 GHz
Number Of Processors:    2
Total Number Of Cores:    8
L2 Cache (per processor):    8 MB
Memory:    13 GB
Bus Speed:    1.33 GHz
Boot ROM Version:    MP21.007F.B06
newmac:~ gmmx2$ sudo gpt -r show disk1
       start        size index contents
           0           1         PMBR
           1           1         Pri GPT header
           2          32         Pri GPT table
          34      262144      1 GPT part - E3C9E316-0B5C-4DB8-817D-F92DF00215AE
      262178        2014
      264192      409600      2 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
      673792 2929602560      3 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
2930276352         783
2930277135          32         Sec GPT table
2930277167           1         Sec GPT header
newmac:~ gmmx2$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            999.9 GB   disk0s2
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.5 TB     disk1
   1:         Microsoft Reserved                         134.2 MB   disk1s1
   2:                        EFI                         209.7 MB   disk1s2
   3:       Microsoft Basic Data BOOTCAMP               1.5 TB     disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.5 TB     disk2
   1:                        EFI                         209.7 MB   disk2s1
   2:                  Apple_HFS D3                      750.0 GB   disk2s2
   3:       Microsoft Basic Data DATA3                  749.9 GB   disk2s3
/dev/disk3
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *1.5 TB     disk3
   1:               Windows_NTFS SSDSUB                 1.5 TB     disk3s1
[Disk 1 is obviously the BC one]
newmac:~ gmmx2$ sudo fdisk /dev/disk1
Password:
Disk: /dev/disk1    geometry: -5415437/4/63 [-1364690128 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE    0   0   2 - 1023 254 63 [         1 - -1364690129] <Unknown ID>
2: 00    0   0   0 -    0   0   0 [         0 -          0] unused
3: 00    0   0   0 -    0   0   0 [         0 -          0] unused
4: 00    0   0   0 -    0   0   0 [         0 -          0] unused
I cannot be the only one who has much such a catastrophic error, so I am hoping that there is something I have overlooked (being only a part-time Mac user) or there is some utility somewhere which can fix this--
Or if you need more data, let me know...
thank you for your time--gmm

Additional information: I found the DU Repair log for that session, in case it helps:
2013-01-28 04:31:00 -0700: Disk Utility started.
2013-01-28 04:31:30 -0700: Verify and Repair volume “BOOTCAMP2013-01-28 04:31:30 -0700: Starting repair tool:
2013-01-28 04:31:30 -0700: Verifying files...
2013-01-28 04:31:57 -0700: Adjusting instance tags to prevent rollover on file 0x606f0.
2013-01-28 04:31:57 -0700: Adjusting instance tags to prevent rollover on file 0x606f2.
2013-01-28 04:31:57 -0700: Adjusting instance tags to prevent rollover on file 0x606f4.
2013-01-28 04:32:01 -0700: Files verification completed.
2013-01-28 04:32:01 -0700: Verifying meta files...
2013-01-28 04:32:01 -0700: Meta files verification completed.
2013-01-28 04:32:01 -0700: Veryfing $AttrDef.
2013-01-28 04:32:01 -0700: Veryfing $Boot.
2013-01-28 04:32:01 -0700: Verifying $UpCase.
2013-01-28 04:32:01 -0700: Correcting $UpCase data.
2013-01-28 04:32:01 -0700: Verifying $LogFile.
2013-01-28 04:32:01 -0700: Verifying $Volume.
2013-01-28 04:32:02 -0700: Verifying files with EAs...
2013-01-28 04:32:02 -0700: EAs verification completed.
2013-01-28 04:32:02 -0700: Verifying folders...
2013-01-28 04:41:54 -0700: Folders verification completed.
2013-01-28 04:41:54 -0700: Minor inconsistencies are detected on the volume.
2013-01-28 04:41:54 -0700: Creating root directory
2013-01-28 04:41:54 -0700: Verifying security descriptors...
2013-01-28 04:41:54 -0700: Clearing invalid security descriptor 0x25e
2013-01-28 04:41:54 -0700: Clearing invalid security descriptor 0x260
2013-01-28 04:41:54 -0700: Clearing invalid security descriptor 0x797
2013-01-28 04:41:54 -0700: Clearing invalid security descriptor 0x1538
2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SII entry 0x25e
2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SII entry 0x260
2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SII entry 0x797
2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SII entry 0x1538
2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SDH entry Id=0x797
2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SDH entry Id=0x25e
2013-01-28 04:41:55 -0700: Deleting orphan $Secure::$SDH entry Id=0x260
2013-01-28 04:41:55 -0700: Deleting orphan $Secure::$SDH entry Id=0x1538
2013-01-28 04:41:55 -0700: Verifying files security...
2013-01-28 04:41:55 -0700: Record 0x97c contains invalid security Id (0x260)
2013-01-28 04:41:55 -0700: Record 0x99b contains invalid security Id (0x260)
2013-01-28 04:41:55 -0700: Record 0xb88 contains invalid security Id (0x260)
2013-01-28 04:41:55 -0700: Record 0xb91 contains invalid security Id (0x260)
2013-01-28 04:41:55 -0700: Record 0xb92 contains invalid security Id (0x260)
2013-01-28 04:41:55 -0700: Record 0x5633 contains invalid security Id (0x260)
2013-01-28 04:41:55 -0700: Record 0x5635 contains invalid security Id (0x260)
2013-01-28 04:41:55 -0700: Record 0x5637 contains invalid security Id (0x260)
2013-01-28 04:41:57 -0700: Record 0xe1d4 contains invalid security Id (0x25e)
2013-01-28 04:41:57 -0700: Record 0xe1d5 contains invalid security Id (0x25e)
2013-01-28 04:41:57 -0700: Record 0xe1d6 contains invalid security Id (0x260)
2013-01-28 04:41:58 -0700: Record 0x111c9 contains invalid security Id (0x260)
2013-01-28 04:41:58 -0700: Record 0x111ca contains invalid security Id (0x260)
2013-01-28 04:41:58 -0700: Record 0x111cb contains invalid security Id (0x260)
2013-01-28 04:41:58 -0700: Record 0x111dc contains invalid security Id (0x260)
2013-01-28 04:41:58 -0700: Record 0x11285 contains invalid security Id (0x260)
2013-01-28 04:41:58 -0700: Record 0x11297 contains invalid security Id (0x260)
2013-01-28 04:41:58 -0700: Record 0x113c4 contains invalid security Id (0x260)
2013-01-28 04:41:58 -0700: Record 0x113c5 contains invalid security Id (0x260)
2013-01-28 04:41:58 -0700: Record 0x12528 contains invalid security Id (0x260)
2013-01-28 04:42:00 -0700: Record 0x1cfe2 contains invalid security Id (0x260)
2013-01-28 04:42:00 -0700: Record 0x1dce1 contains invalid security Id (0x260)
2013-01-28 04:42:00 -0700: Record 0x1f6a8 contains invalid security Id (0x260)
2013-01-28 04:42:00 -0700: Record 0x1f6a9 contains invalid security Id (0x260)
2013-01-28 04:42:00 -0700: Record 0x1f6c4 contains invalid security Id (0x260)
2013-01-28 04:42:00 -0700: Record 0x21d57 contains invalid security Id (0x797)
2013-01-28 04:42:03 -0700: Record 0x3220d contains invalid security Id (0x260)
2013-01-28 04:42:06 -0700: Record 0x4bc2a contains invalid security Id (0x260)
2013-01-28 04:42:10 -0700: Record 0x64ff9 contains invalid security Id (0x1538)
2013-01-28 04:42:11 -0700: Can't read $SDS
2013-01-28 04:42:12 -0700: Security verification completed
2013-01-28 04:42:12 -0700: Verifying $MFT.
2013-01-28 04:42:12 -0700: Verifying $MFTMirr.
2013-01-28 04:42:12 -0700: Verifying $Bitmap.
2013-01-28 04:42:18 -0700: Volume repair complete.
2013-01-28 04:42:18 -0700: Updating boot support partitions for the volume as required.
2013-01-28 04:42:18 -0700: Repair tool completed: 2013-01-28 04:42:18 -0700:
2013-01-28 04:42:18 -0700:

How do I install dual-boot Solaris 8 and Solaris 9 on one hard disk ?

I tried to install Solaris 8 and Solaris 9 on same disk using CDs, but
the second installation overwrote the first Solaris which was installed
previoudly on the half-disk size partition of same disk.
How do I install two Solarises on one hard disk ?
Thanks
Yakov

There are no tricks to get Solaris to dual boot on the same drive. Just allocate and pick the free slices not used by the first Solaris install when you put in the second install. Technically speaking there is nothing preventing you from running seven separately bootable Solaris instances on the same drive (one of 8 available slices is overlap -- slice 2) provided you use a swap file on a root partition instead of reserving a whole slice for swap.

[SOLVED] Partition "outside of disk"

I got a new hard drive, with the intention of having an Arch Linux/Windows 7 dualboot. Somewhere along the line when I made all the partitions before installing anything, I screwed up the partition table, and now when I try to use cfdisk or parted it says "Can't have partition outside the disk!" GParted gives me the same problem. I've only installed Windows 7, and it boots fine, but I can't make any new partitions because of this stupid error.
I really don't give a damn about any of the data outside of the Windows partition at the moment, which only takes up the first 197 GB of the 1 TB disk. Is there a way to just clear out these other partitions giving me trouble? Can I dd zero it or will that make things worse?
EDIT: (solution) I fixed the problem by using fdisk instead of cfdisk or parted/gparted. In fdisk, I deleted the problematic partitions, then wrote a new partition table to the disk. I accomplished this by using d and w commands in fdisk. If you are reading this and would like to rescue the partitions while keeping this data instead, refer to http://ubuntuforums.org/archive/index.p … 38943.html
Last edited by Ferrenrock (2010-12-09 19:20:32)

delete the non windows partitions before trying to make new partition, you most likely have used all disk space already.
Then make new linux partitions from unsigned space

2nd Solaris 8 partition

I would like to use a 2nd partition on my disk for another Solaris patition. All the documentation seems to assume that there will be only one Solaris patition on a single disk with maybe another partition being used for windows or some other os. That's what I have now but I have acquired second (they are removable) disk for windows and now want to use the full disk for Solaris without a reload.
Can I do this? How would I do this?

I haven't seen any Partition Manager for Solaris x86, specially for Solaris 10 which has changed its partition number because it used to be equal to Linux Swap File, I've tryied Partition Manager, Partition Magic and none seems to works, if somebody knows about a partition manager that detects Solaris partition let us know

Is it possible to resize Solaris (8) partition and move it?

Hi,
I have a multiboot machine (w2k, RH9, Solaris8), on which solaris partition has some extra space. I need to resize Solaris (shrink it) and also move its location on the disk so that I can use the extra space by expanding the linux root partition.
Is this possible without a solaris reinstall? I don't have the CD's and reinstalling is not an option.
Can this be done using some of the partition tool and disk editors?
Any pointers will be appriciated!

I haven't seen any Partition Manager for Solaris x86, specially for Solaris 10 which has changed its partition number because it used to be equal to Linux Swap File, I've tryied Partition Manager, Partition Magic and none seems to works, if somebody knows about a partition manager that detects Solaris partition let us know

Damaged partition on USB disk. Please help me reconstruct it.

Hello,
I have a Seagate 2TB USB 3.0 disk that suddenly has stopped working under Mac OS X Mavericks. The system won't recognise it. The funny thing is that if I attach the disk to my QNAP NAS, the disk is seen just fine by the OS. I've read multiple websites with similar experiences; it seems to me as if the Mac OS X isn't as permisive as linux OS... and boy, is that annoying
I came across this article: http://perrohunter.com/repair-a-mac-os-x-hfs-partition-table/#comment-4644 . I must say that I got my hopes high when I started reading the post, because I felt it described my very same situation. Unfortunatelly, when I got to step #8, Mavericks would complain about the resource being busy, thus getting me stuck in there
When the disk is hooked up on my NAS, I can see the data just fine. I just want to be able to mount the disk one last time under OS X in order to transfer all the Time Machine backups I have there...
A few details:
fdisk
macminiserver:testdisk-7.0-WIP marc$ sudo fdisk /dev/rdisk5
Disk: /dev/rdisk5          geometry: 243201/255/63 [3907029167 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: AF 1023 254 63 - 1023 254 63 [         2 - 3907029165] HFS+
2: 00    0   0   0 -    0   0   0 [         0 -          0] unused
3: 00    0   0   0 -    0   0   0 [         0 -          0] unused
4: 00    0   0   0 -    0   0   0 [         0 -          0] unused
macminiserver:testdisk-7.0-WIP marc$ sudo fdisk -d /dev/rdisk5
2,-387938131,0xAF,-,1023,254,63,1023,254,63
0,0,0x00,-,0,0,0,0,0,0
0,0,0x00,-,0,0,0,0,0,0
0,0,0x00,-,0,0,0,0,0,0
macminiserver:testdisk-7.0-WIP marc$ sudo gpt -r -vv show /dev/rdisk5
Password:
gpt show: /dev/rdisk5: mediasize=2000398933504; sectorsize=512; blocks=3907029167
gpt show: /dev/rdisk5: MBR at sector 0
       start        size index contents
           0           1         MBR
           1           1
           2 3907029165      1 MBR part 175
gdisk
macminiserver:testdisk-7.0-WIP marc$ sudo sudo gdisk /dev/rdisk5
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: MBR only
BSD: not present
APM: not present
GPT: not present
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by
typing 'q' if you don't want to convert your MBR partitions
to GPT format!
Warning! Main partition table overlaps the first partition by 32 blocks!
You will need to delete this partition or resize it in another utility.
Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Command (? for help): r
Recovery/transformation command (? for help): ?
b          use backup GPT header (rebuilding main)
c          load backup partition table from disk (rebuilding main)
d          use main GPT header (rebuilding backup)
e          load main partition table from disk (rebuilding backup)
f          load MBR and build fresh GPT from it
g          convert GPT into MBR and exit
h          make hybrid MBR
i          show detailed information on a partition
l          load partition data from a backup file
m          return to main menu
o          print protective MBR data
p          print the partition table
q          quit without saving changes
t          transform BSD disklabel partition
v          verify disk
w          write table to disk and exit
x          extra functionality (experts only)
?          print this menu
Recovery/transformation command (? for help): o
Disk size is 3907029167 sectors (1.8 TiB)
MBR disk identifier: 0x00000000
MBR partitions:
Number Boot Start Sector   End Sector   Status      Code
   1                     1   3907029166   primary     0xEE
Recovery/transformation command (? for help): p
Disk /dev/rdisk5: 3907029167 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 12A8F4C9-1F60-4D7A-8109-96F6D0A1596F
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029133
Partitions will be aligned on 8-sector boundaries
Total free space is 0 sectors (0 bytes)
Number Start (sector)    End (sector) Size       Code Name
   1               2      3907029166   1.8 TiB     AF00 Apple HFS/HFS+
Recovery/transformation command (? for help): w
Warning! Main partition table overlaps the first partition by 32 blocks!
You will need to delete this partition or resize it in another utility.
Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Aborting write of new partition table.
pdisk
macminiserver:testdisk-7.0-WIP marc$ sudo pdisk /dev/rdisk5
Password:
pdisk: No valid block 1 on '/dev/rdisk5'
Edit /dev/rdisk5 -
Command (? for help): i
pdisk: can't open file '/dev/rdisk5' for writing (Resource busy)
I would appreciate your help very much.
Thanks in advance

Christopher Murphy wrote:
Yeah I'm not sure the problem is partition related at all. It might be file system corruption that OS X's fsck sees but can't fix, while it goes unnoticed on the NAS. But then this message is confusing:
May 21 21:30:25 macminiserver kernel[0]: disk3s1: device/channel is not attached.
May 21 21:30:25 macminiserver kernel[0]: disk3s1: media is not present.
When it's connected, what result do you get for 'diskutil list' is the drive in question listed? And if so what do you get for 'diskutil verifydisk /dev/diskX'? Use diskX not diskXsY.
diskutil list displays the disk and partition just fine:
macminiserver:~ marc$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage                         121.0 GB   disk0s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:          Apple_CoreStorage                         799.3 GB   disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
   4:                  Apple_HFS Macintosh HD2           199.9 GB   disk1s4
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           *911.8 GB   disk2
/dev/disk5
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *2.0 TB     disk5
   1:                  Apple_HFS TimeMachine Macs Casa   2.0 TB     disk5s1
The disk in quesiton is the one in red. The rest of disks and partitions are system disks (Fusion Drive); they are not relevant.
The result I get when I attempt to verify the disk is rather annoying given that I pretty much had assumed it did not contain any GPT scheme:
macminiserver:~ marc$ diskutil verifydisk /dev/disk5
Unable to verify this whole disk: A GUID Partition Table (GPT) partitioning scheme is required (-69773)
I thought this could also help shed some light on the issue:
macminiserver:~ marc$ diskutil info /dev/disk5
   Device Identifier:        disk5
   Device Node:              /dev/disk5
   Part of Whole:            disk5
   Device / Media Name:      Seagate Expansion Desk Media
   Volume Name:              Not applicable (no file system)
   Mounted:                  Not applicable (no file system)
   File System:              None
   Content (IOContent):      FDisk_partition_scheme
   OS Can Be Installed:      No
   Media Type:               Generic
   Protocol:                 USB
   SMART Status:             Not Supported
   Total Size:               2.0 TB (2000398933504 Bytes) (exactly 3907029167 512-Byte-Units)
   Volume Free Space:        Not applicable (no file system)
   Device Block Size:        512 Bytes
   Read-Only Media:          No
   Read-Only Volume:         Not applicable (no file system)
   Ejectable:                Yes
   Whole:                    Yes
   Internal:                 No
   OS 9 Drivers:             No
   Low Level Format:         Not supported
macminiserver:~ marc$ diskutil info /dev/disk5s1
   Device Identifier:        disk5s1
   Device Node:              /dev/disk5s1
   Part of Whole:            disk5
   Device / Media Name:      Untitled 1
   Volume Name:              TimeMachine Macs Casa
   Escaped with Unicode:     TimeMachine%FF%FE%20%00Macs%FF%FE%20%00Casa
   Mounted:                  No
   File System Personality: HFS+
   Type (Bundle):            hfs
   Name (User Visible):      Mac OS Extended
   Journal:                  Unknown (not mounted)
   Owners:                   Disabled
   Partition Type:           Apple_HFS
   OS Can Be Installed:      No
   Media Type:               Generic
   Protocol:                 USB
   SMART Status:             Not Supported
   Volume UUID:              CF26012D-A428-3A4C-9E0F-D18A1AAB0CFC
   Total Size:               2.0 TB (2000398932480 Bytes) (exactly 3907029165 512-Byte-Units)
   Volume Free Space:        0 B (0 Bytes) (exactly 0 512-Byte-Units)
   Device Block Size:        512 Bytes
   Read-Only Media:          No
   Read-Only Volume:         Not applicable (not mounted)
   Ejectable:                Yes
   Whole:                    No
   Internal:                 No
Message was edited by: marc.garcia. Added "diskutil info" output.

Partition the boot disk...

Ok I have a little test (vmware) with 20Gb assigned to it.
It sees this as one disk.
I've installed solaris 10, creating a partion of 10Gb.
The remaining 10Gb, I wanted to create a couple of slices of 5Gb - but when I go into format utility --> select disk --> partition --> modify I get the message:
"Cannot modify disk partitions while it has mounted partitions"
Can I get round this? There didn't seem to be a way of creating the other partitions when I installed the OS.
It is only a test box but my aim is the root area, and two further partitions which I mess around with and practise software mirroring.
Thanks

Please show your disk partition output here. You might have created partition other than root in the disk during installation.
Edited by: Soorya on Nov 18, 2011 5:14 AM

Solaris version that RAID Manager 6.22.1 supported

I am currently running Solaris 9 operating environment, I would like to know if RAID Manager 6.22.1 supports Solaris 9.
When I search in SUN website, one page mentioned that RM 6.22.1 supports Solaris 9(http://www.sun.com/storage/disk-drives/raid.html) while the other page is different (http://www.sun.com/storage/software/raid_manager.html).
If anyone has RM 6.22.1 running on Solaris 9, please tell me. Thanks in advance.

Yes it work fine.
Just make sure the firmware and patches are up-to date to avoid problems.
Iain

How do I repair a Windows 7 partition when it is after Windows 8 partition in a Dual Boot Setup

I have a laptop that I purchased a year ago and which came pre-installed with Windows 8.
Recently, I successfully added Windows 7 as a dual-boot, and this worked OK. To obtain the space for Windows 7, I shrunk the Windows 8 partition.
In Disk Management, the Windows 8 partition is physically located after OEM and EFI partitions; Windows 7 partition is is adjacent to Windows 8.
All went well until I shrunk the Windows 8 partition further to increase the size of the Windows 7 partition, after which Windows 7 came up with a boot error....Windows 8 still boots OK.
I inserted my Windows 7 disk to perform a Startup/Repair, which failed because the first OS partition it sees is Windows 8 and a message tells me that I need to install the correct media for that system.
I searched for advice and assistance to solve the problem....to no avail - and had to completely re-install Windows 7 and the associated applications.....and I really don't want to have to go through this again.
I actually use Windows 7 more than 8, and if I have to lose one or the other, I would dump Windows 8.
So....is there a manageable way I can keep the two systems recoverable and migrateable to another disk in the future. If not, how do I safely remove the Windows 8 partition without damaging Windows 7? Ideally, I would just like to swap the partitions
round....but with EFI and BCD partitions, I am reluctant to go into the unknown.
Sorry....bit of a saga....but would appreciate any advice.
Rob Nick

Hi Rob,
Above all, as the purpose is to enlarge Windows 7 partition, please understand that shrink Windows 8 partition again cannot help on it. A partition can be expanded only if there is free space "after" it.
So you will still need to delete Windows 7 partition for expanding purpose.
If it is fine to just make Windows 7 back to boot order. Please try following command lines.
Note: Please run CMD in Administrator mode.
bcdedit /export “c:\boot”
This is a backup. You can delete it if things go successfully.
Then please create a new entry for Windows 7:
bcdedit /copy {current} /d “Windows 7”
It will provide an entry ID. Copy it and it will be used in following 2 command lines.
bcdedit /set {identifier} device partition=X
Replace X with the drive letter of Windows 7 system located.
bcdedit /displayorder {identifier} /addlast
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Hello Everyone, I have a MacBook older model with me.I am running 10.7.6 on that, I was trying to use BootCamp to install windows on my mac. Since BootCamp can only work on a single Volume, I partitioned my Hard Disk to one volume. Using BootCamp I

Hello Everyone,
I have a MacBook older model with me.I am running 10.7.6 on that, I was trying to use BootCamp to install windows on my mac. Since BootCamp can only work on a single Volume, I partitioned my Hard Disk to one volume.
Using BootCamp I installed windows and everything worked fine. After installing windows and testing everything, I switched back to OS X and this time I tried to make another partition on my single portioned Mac volume and named it Backup. That too worked. Now I have three Volumes
1)Development2)Backup3)BootCamp.
Next when I switched to Windows, It should the classic error, No Bootable device found, please insert a Bootable CD and press any key. When I tried to enter my Mac OS X install DVD and by pressing option key, it does not show me the proper Mac OS X development volume. It keeps going back to the No bootable device found message.
Any help will be much appreciated
Regards
Mithun

you can't add a partition in between - you put Windows to a new partition number.
GPT (GUID)
EFI
Mac HFS
Lion Recovery
Windows
And now you have two HFS
One partition and one Windows (plus Lion Recovery).
If you were to have more, it can't be before Windows for one thing.

Wairning: No Solaris Fdisk Partition when managing disks in SMC

Similar Messages

Maybe you are looking for