SVM: migrating to a new disk device

Hello,
We have a 70GB LUN from one SAN disk array on a Solaris 10 server. This LUN has been configured into SVM using a single disk device and then carved up into soft partitions. We will need to migrate this LUN to a new disk array. Since SVM only sees this LUN as a disk slice and not as a metavolume, is there any way to mirror/replace the disk without disabling the applications that have been built on the soft partitions? In this case, we have several active Solaris Containers root file systems living on these soft partitions. Some metastat output to give you a better picture:
# metastat -c
d112 p 1.5GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d111 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d110 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d109 p 1.5GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d108 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d107 p 1.5GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d106 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d105 p 5.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d104 p 1.5GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d103 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d102 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
d101 p 3.0GB /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
# metastat d101
d101: Soft Partition
Device: /dev/dsk/c4t600507630EFE08ED0000000000000105d0s0
State: Okay
Size: 6291456 blocks (3.0 GB)
Device Start Block Dbase Reloc
/dev/dsk/c4t600507630EFE08ED0000000000000105d0s0 0 No Yes
Extent Start Block Block count
0 1 6291456
Device Relocation Information:
Device Reloc Device ID
/dev/dsk/c4t600507630EFE08ED0000000000000105d0 Yes id1,ssd@n600507630efe08ed0000000000000105
I looked at the manual for "metareplace" and the language indicates that it would only work with a metavolume and not directly with the disk device.
Thanks.

Okay, there's two ways to use SPs and mirrors. The easist way in most cases is to create a large mirror, then carve the SPs out of it. But you really have to start off doing that. Trying to convert this layout to that would be annoying, assuming it's possible at all.
The other way is to take the SP, toss a concat/stripe on it, then use that as the submirror base. It's a bit more annoying because you have to create the SPs on the other disk in the same manner.
So you'd take a look at 'metastat -p' output. That shows the commands to recreate the current layout. Use the SP creation items, but run them on the second disk. This sets up a second set of SPs.
Then take all the SPs and put a concat/stripe on them. So for one of the existing SPs (like d101), you'd do like this;
metainit d151 1 1 d101
Do that for all the SPs (on both disks). Now you can create the one-way mirrors from the currently-used side. As an example:
metainit d201 -m d151
Now you've got the mirror. The problem is that the filesystem is still mounted from d101. You've got to unmount from d101 and mount d201 before you can sync the mirror to the other side (that's the only step that can't be done online). Once the side is no longer mounted, you can sync up.
metattach d201 d171 (or whatever you've named it).
Good luck.
Darren

Similar Messages

  • Migrate to a new disk

    I have a PowerMac G4-450 AGP which still meets most of my needs, except disk space. the original 27 Gb drive is constantly maxed out, so I got a new 120 Gb drive and installed it as a slave drive. I moved most of my user files and a lot of apps to the new drive, but still, the main drive is always maxing out due to virtual memory, caches, Library space, etc.
    Is there a way, now that I am in this mess, to install OS X on the big drive, and cleanly move all of the installed software from the small drive to the big one, without having to reinstall everything? Is it necessary to re-jumper the drives to make the big one the master if I do this, or can I just leave it as-is?
    Thanks
    JEH

    Use Carbon Copy Cloner to move the existing Mac OS X installation from the old drive to the new one.
    (23377)

  • Migrating to a new disk

    Sorry if this is the wrong place for this, but I'm not sure where else it will fit.
    The basic story is this: I currently have /home on a huge HDD and everything else on a small SSD. I just got a new SSD and was wondering what the best way to copy everything from the old SSD to the new one without screwing up booting or breaking arch. Anyone have a guide or tool that would help? This is not my area of expertise so anything would be helpful.
    Thanks in advance.
    Last edited by zorkfandm (2011-12-01 18:22:19)

    hello zorkfandm
    Well yes it can be done.
    option 1) if new ssd is equal or bigger than old one - clonezilla
    option 2) use rsync and do not forget to correct fstab and grub/menu.lst in new ssd
    example :
    rsync -avxHAXS --delete --progress /OLDROOT /NEWROOT
    keep in mind it will copy only files that are on root partition but if you have separate /usr or /var or w/e it will not copy them, so you need to repeat for eatch of them same operation aka /OLDROOT/usr /NEWROOT/usr etc.....
    option 3) well many many more ways but IMO they are more complicated
    Last edited by cybertorture (2011-12-01 19:20:44)

  • Aliases failing after migrating to new disk

    I migrated from my original 500GB disk to a new 1TB disk by using Disk Utility's "Restore" function.  For those of you that are not familiar with Restore, it should be the highest fidelity form of coping a partition given that it does a "block copy" - e.g. it copies the data byte-by-byte instead of doing a file based copy.  Also it verifies after the copy is done.  In my opinion, it is the gold standard for copying an entire partition.
    The new disk booted up fine, but I was surprised to find out that about half of my 190 aliases were broken.  When I looked inside the alias files themselves I saw that they contain a lot of data, including a path to the target file.  In all cases where the aliases stopped working on the new drive, this path was not correct.  In other words, I had moved the target file on the old drive before cloning the whole partition onto a new drive.
    I reinstalled the old drive and verified that all my aliases were in fact functioning so this was not an issue in on the source disk.  The aliases were able to work properly even with outdated path data in them.
    After doing some reading on how OS X aliases work, I found out they use multiple ways to find the target file.  If the path inside the alias is not good, OS X has other means to find the original target file.  But somehow this broke after copying to the new disk.
    So the question is if there is a way to force aliases to get refreshed so that all their data is correct?  In other words, before I do a migration to a new disk, can I run some command that causes all the aliases on my existing disk to be resolved to their targets and then have the contents of the aliases be made fully consistent with that resolved target data.  This would fix the broken paths in the aliases which would allow them to work after the migration to the new disk.

    Try this:
    Make a folder on your destop called F.
    Inside folder F make two subfolders called A and B.
    Inside A create a text file called T.
    Now creas an alias to T which we will call T.alais.
    Test out T.alias.  It should open T.
    Now move T to folder B.
    Again, test out T.alias.  It should open T even though it has been moved.
    Now use CCC to copy F to another disk.
    Delete the original F and empty the trash.
    Now try to open T.alias.  It will fail.
    The reason it fails is that you moved the target of an alias (from A to B) then copied the whole thing (both alias and target) to a new disk.
    I just tried it and it failed for me.
    This is what happens to me en-mass when I move from one disk to another.

  • How to migrate to a new 4TB disk (switching from MBR to UEFI)

    I have an HP Pavilion p7-1167c running Windows 7 Home Premium Service Pack 1.
    My 1TB drive ran out of space, so I want to migrate to a new 4TB drive.  However, the current drive is a MBR drive and I understand that I need to use UEFI to be able to utilize the full 4TB (ie I am limited to using 2TB of the 4TB if the 4TB drive is formatted as an MBR drive).
    In the past when migrating to a new drive, I just cloned the drive.  Can I still do this, even though they are formatted differently?  I'm not sure if a cloning process would clone data from a MBR disk to a UEFI disk while keeping the disk formatting, or if a clone requires that the source and target disks be the same formatting.
    If I can clone a drive from a MBR disk to a UEFI disk, how would I get my PC to boot using the new disk?  Do I maybe need to change something in the BIOS to cause the PC to support UEFI?
    If I can't clone the drive due to needing to go from MBR to UEFI, what should I do?  Is the only option to do a build from scratch (ie reinstall the OS from scratch with the UEFI disk installed, then re-install all the apps, and then re-load my data from a backup)?  I'm hoping to avoid this, due to the obvious large amount of effort that would take.
    Thanks in advance for any guidance as to how how I might migrate my system to this new drive, while being able to utilize the full 4TB of space.
    Thanks!

    Hi Steve,
    Another point of clarification.  You should be able to use a 4 TB hard drive for data.  To use it as a replacement boot drive would required some special efforts using retail media and provided that the boot sources will support UEFI boot devices.  If you boot up W8 installation media in UEFI mode then you could try installing W8 to the GPT formatted hard drive.  I haven't tried this on your particular model so I can't say for sure that it will work.
    HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
    HP Photosmart Premium C309G, HP Photosmart 6520
    HP Touchpad, HP Chromebook 11
    Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
    Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
    Windows 7/8 UEFI/Legacy mode, MBR/GPT

  • Photoshop elements 10 will not migrate to my new macbook pro/retina display.  There is no CD/DVD player on this machine.  Any suggestions on how to get Elements onto my machine?  Yes, I have the disk(s).

    Photoshop elements 10 will not migrate to my new macbook pro/retina display.  There is no CD/DVD player on this machine.  Any suggestions on how to get Elements onto my machine?  Yes, I have the disk(s).  Am I going to have to buy an external CD/DVD player to load this one program:(

    I have ordered a USB3 BluRay/DVD/CD player/burner and will use that both with my iMac ( in which the Superdrive seems to be failing ) and the MBPro Retina I just bought .

  • Migrating to new SAN devices

    Hi, we are migrating many of our apps to new SAN devices. There is one system that has an Oracle 8i database on a W2K OS. There are 4 SAN drive letters assigned to this server and since we are moving to a smaller drive configuration we plan on moving all the data via a host copy (XCOPY or ROBOCOPY). We plan on keeping the same drive mappings. Do I need to do any kind or export/import, or (as long as the drive letters are the same) can I just shut down the system, do the host copy and bring the instance back up without any kind of manual recovery needed?
    Thanks

    As long as you don't change the logical structures (Oracle is still able to find all directories,files ... as recorded in the controlfiles), you can modify the physical side. Even if you would change drive letters, you could use ALTER DATABASE ... RENAME FILE ... to tell the controlfiles such a change, there's no need to export any data.
    You may see I/O related changes, but this is another issue.

  • I installed ML on a new disk and didn't get much migration

    I bought a new 750GB HD for my early 2009 MBP. I intalled ML on the new disk using a FW drive enlosure. I took the drive out of this enclosure and put it into my MAC. I took my old drive and put it into the enclosure and used migration assistant to take over all the data. I don't have any of my contacts or email setsups. I have my apps, but that is it. My desktop is also blank.
    I did this once before from Leopard to SN and everyting came over fine and I was able to use my MAC right after the migration.
    Is there anything I did wrong?

    Repeat the process, ensuring that you erase and format the new HD properly, Mao OS Extended and with the GUID partitioning scheme. Install ML and on first boot, use the Setup Assistant to do the migration. See Pondini's Setup New Mac guide, wherein you treat the new HD as a new Mac. Then, swap the HDs.

  • Should I wiat for Snow Leopard to migrate to new disk?

    I have a Macbook Pro 13" and had a repair resulting in anew hardrive. Did an erase and install of original Leopard to at least have the machine up to date. My question is that I will be migrating all my info and setting from my Imac's Time Machine to the new disk on the Macbook Pro, which I did when I first bought it a few months ago. Would it be better to wait a day or two--when my Snow Leopard DVD Upadte Disk--will be arriving and then migrate everything over of is it the same as migrating now and then updating the computer when the new OS arrives either tomorrow or Saturday.

    Hi, again.
    Nobody who's allowed to talk about it knows as of today exactly what's involved in the installation, but all indications are it's not a big deal.
    Purely from past experience, however, I always recommend doing major things one step at a time. If you do one right after the other, you multiply the (small) chances of error, and may have no clue about which step caused any problems.
    I'd say do the migration first. Start Time Machine (or other) backups immediately. Then use the Mac for a while to be sure everything's kosher.
    There are bound to be bugs in Snow Leopard. Probably minor overall, but no major (and few minor) upgrade in the history of the computer has been entirely bug-free. So make sure your Pro is working fine on Leopard, and is properly backed-up, before installing SL.

  • Hard drive volume appears in sidebar Favorites when new disk mounts

    Hard drive on my 17” MacBook Pro Quad Core i7 (2.5 GHz, 8GB SDRAM OS 10.8.2) is partitioned into 4 volumes; I'll call them A-Mountain Lion startup drive, B-Personal, C-Work, D-minimal clean Mt. Lion for emergencies. Problem relates to my regular boot drive.
    I have Finder sidebars set to show 8 or 10 folders in the "Favorites" section and have ticked all boxes in the "Devices" section. Most of the time I have no external disks, CDs, etc., connected to the MBP, so the Devices section generally shows my computer and the four partitions. So far, so good.
    Lately, every time an external volume is mounted and every time a disk image is mounted, the Personal volume (B) of my internal drive, which is already showing under Devices, also pops up in the Favorites section of the sidebar. I remove it from the Favorites, but the next time an external disk or a disk image mounts, there it is again. It's always volume B, never A, C, or D.
    I have tried everything I can think of to cure this odd behavior: Used Disk Utility (verify all disks/volumes; repair volumes; repair permissions; etc.), though nothing seemed wrong. I've run Disk Warrior on all volumes. I cleaned out everything possible on the startup drive (A) with the latest version of Onyx. I've repeatedly trashed the plists I could identify in my user Library that had "sidebar" or "finder" in their names. I've logged in and out; started and restarted; started with shift key down. Still, every time a new volume or disk mounts, up pops this extra volume B among the Favorites (where it shouldn't be). I checked and unchecked various combinations of sidebar items in Finder Preferences. I've Forced Quit the Finder. It doesn't matter whether all, some, or no devices are checked; when a new disk mounts, there's the extra volume B again.
    I have only two other clues to add. (1) I created a new temporary user account on my startup drive (volume A), and this behavior did NOT occur in the new account. (2) This same behavior had arisen once before, a couple of months ago. I went through similar blind attempts to cure it then, but at some point I must have done something right because I it got fixed. For the life of me, I can't remember which of all the things I tried did the trick.
    Many thanks to anyone who can shed light on this annoying behavior.

    I can add a bit to my earlier description. I had said the problem did not occur in a new user account. Well, after using the new account for a while, it showed up. Eventually I erased the startup volume and installed Mountain Lion (plus updates to 10.8.2) fresh. I used migration assistant to transfer only my old user, pared down applications, and network settings -- no preferences, application support stuff. The old user carried over the problem. But I immediately created a new user and have been working from it for the past two weeks, very gradually opening apps, adjusting settings, etc., and testing for the anomaly at each change. In some cases I did move preferences from a backup clone, but was always careful to test after each addition. All was well for a week, until one morning I noticed the data partition had appeared in sidebar Favorites. So I'm back to where I was. I had been documenting each change or introduction I made. The only things my notes said from the day before the sidebar anomaly appeared was launching and struggling to activate QuarkXPress 9.3, and copying over my old prefs and settings for TextWrangler. I completely removed every trace of QXP, but the problem remained. (I did not remove TextWrangler because I just can't believe it could be the culprit -- but could it?)
    I also noticed a similar (though maybe not identical) problem posted in another thread <https://discussions.apple.com/message/20591050#20591050>, but so far no answers there either.

  • Moving ASM-based RAC to new storage device

    We recently installed Oracle 11gR2 RAC on a REH 5.3 cluster. CRS, Voting Disk, and database files are all sitting on an ASM disk group (on a Clarion storage device). A decision is made to move everything to a new storage device (DMX). We are using EMC powerpath.
    Is there an easy way to move this Oracle cluster from one storage device to another.
    We can rsync the grid and RDBMS binaries which are installed on a linux filesystem on each node but I would like to know how to go about moving the shared storage which is hosted on the ASM.
    We used asmlib 2.0 to create the ASM disk and then relied on the clusterware installer and DBCA to create the disk group, the cluster components, and the oracle database.
    Do I need to backup the ASM database as well as our RAC database (using RMAN) into a flat filesystem first and restore them once the new ASM disk is created in the new storage device?
    A step by step procedure will be greatly appreciated.
    Thanks,
    Omer

    Yes its possible without backup/restore.. good to take full back in case of any mishappening.
    Please read metalink note for step by step process..
    Exact Steps To Migrate ASM Diskgroups To Another SAN Without Downtime. [ID 837308.1]
    Regards
    Rajesh

  • Migrate zpools to new storage array

    I am in the process of migrating to a new EMC storage array. I used EMC SRDF to copy all tracks from the current disks to the new disks, so that all new disks look identical except for the actual device path since the WWN is different on the new array. I was hoping I could simply unmask/unmap the old SAN, mask and map the new SAN, and ZFS would be able to import the pools from the new SAN (like you can with veritas), but I didn't take into consideration that the device paths/names would be different and ZFS wouldn't like it. Is there any way to get solaris to see the new ZFS pools that now exist on the the new storage array so that I don't have to mirror and then remove the disks from the pool and pretty much wipeout all of the sync work I've already done with the EMC software?
    Hopefully this makes sense, but please let me know if I need to explain further.

    No issue, works as expected, I just didn't split the synchronization between the old and new devices, so the new disks were still write disabled in EMC land. Once I split the sync, everything imported without a hitch, so it was my stupid mistake.

  • Replacing global disk device

    Hi,
    Looking for suggestions, guidelines, HOWTOs, etc. for the following scenario.
    SC 3.2, Sol 10 08/07
    We have a 50GB global disk device on SANA in a two-node cluster. We need to replace this device with a LUN from SANB as part of our storage migration project. This device is also a quorum device, and it is the data directory for the Oracle application group in the cluster.
    How do I stop the Oracle group but mount the disk for copying the data, and then how do I change the configuration to accept the new disk as the cluster and quorum device?
    Thanks.

    Tim,
    thanks for the information. It's almost exactly what I need, but there's one more bit I need some guidance on. I realize this is kind of basic stuff, but it's been a while since the cluster was created and configured (along with the RG) and the administration has been pretty hands-off during that time period. How do I swap out the disk resource A for B? I was looking at the properties of the RG and the resource yesterday and it only seemed to be based on the mount point rather than the DID, but I would think that there is a setting/dependency configured for the actual DID somewhere in there.
    Resource: epass-db-1-disk-u02
    Type: SUNW.HAStoragePlus:4
    Type_version: 4
    Group: epass-db-1
    R_description:
    Resource_project_name: default
    Enabled{mary}: True
    Enabled{flora}: True
    Monitored{mary}: True
    Monitored{flora}: True
    <resource name="epass-db-1-disk-u02" resourcetypeRef="SUNW.HAStoragePlus:4"
    resourcegroupRef="epass-db-1">
    <resourceNodeList>
    <resourceNode nodeRef="mary">
    <state value="enabled"/>
    <monitoredState value="true"/>
    </resourceNode>
    <resourceNode nodeRef="flora">
    <state value="enabled"/>
    <monitoredState value="true"/>
    </resourceNode>
    </resourceNodeList>
    <propertyList extension="false">
    <property name="R_description" value=""/>
    <property name="Resource_project_name" value="default"/>
    <property name="Resource_dependencies" value=""/>
    <property name="Resource_dependencies_weak" value=""/>
    <property name="Resource_dependencies_restart" value=""/>
    <property name="Resource_dependencies_offline_restart" value=""/>
    <property name="Retry_interval" value="300" type="int"/>
    <property name="Retry_count" value="2" type="int"/>
    <property name="Failover_mode" value="SOFT" type="enum"/>
    <property name="POSTNET_STOP_TIMEOUT" value="1800" type="int"/>
    <property name="PRENET_START_TIMEOUT" value="1800" type="int"/>
    <property name="MONITOR_CHECK_TIMEOUT" value="90" type="int"/>
    <property name="MONITOR_STOP_TIMEOUT" value="90" type="int"/>
    <property name="MONITOR_START_TIMEOUT" value="90" type="int"/>
    <property name="INIT_TIMEOUT" value="1800" type="int"/>
    <property name="UPDATE_TIMEOUT" value="1800" type="int"/>
    <property name="VALIDATE_TIMEOUT" value="1800" type="int"/>
    <property name="STOP_TIMEOUT" value="1800" type="int"/>
    <property name="START_TIMEOUT" value="90" type="int"/>
    </propertyList>
    <propertyList extension="true">
    <property name="Zpools" value="" type="stringarray"/>
    <property name="FilesystemCheckCommand" value="" type="stringarray"/>
    <property name="AffinityOn" value="TRUE" type="boolean"/>
    <property name="FilesystemMountPoints" value="/u02" type="stringarray"/>
    <property name="GlobalDevicePaths" value="" type="stringarray"/>
    </propertyList>
    </resource>
    And on the off chance that it isn't configured to the DID, but should be, how do I set that to make this proper? There is an entry for /u02 in vfstab on both nodes. Is that the correct way? Again, it has been a long time since I set this up. :)

  • Can someone please tell me how to format a new disk to ZFS format?

    I have a Sun v240 with Solaris 10 update 8 installed on a single 73GB harddisk. Everything is working fine. I just purchased a another identical harddisk online. I plugged the disk into my v240 and ran 'devfsadm' and solaris found the new disk. I want to add this disk to my existing ZFS pool as a mirror. However, this disk was originally formatted with a UFS file system. So when I run:
    zpool attach rpool c1t0d0 c1t1d0I get:
    /dev/dsk/c1t1d0s0 contains a ufs filesystem.I understand the error message but I don't know how to format the disk to have a ZFS file system instead. Note that I am extremely new to Solaris, ZFS, and pretty much everything Sun - I bought this server on eBay so that I could learn more about it. It's been pretty fun so far but need some help here and there.
    For some reason I can't find a single hit on Google telling me how to just simply format a disk to ZFS. Can I use the 'format' command? Maybe you don't "format" disks for ZFS? I have no idea. I might not have the right terminology. If so, apologies. Can anyone help me on this?
    Thanks a lot! =D
    Jonathon

    Yes, you were right. The partitions were totally different. Here is what I saw:
    For c1t0d0:
    # format
    Part      Tag    Flag     Cylinders         Size            Blocks
      0       root    wm       0 - 14086       68.35GB    (14087/0/0) 143349312
      1 unassigned    wm       0                0         (0/0/0)             0
      2     backup    wm       0 - 14086       68.35GB    (14087/0/0) 143349312
      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)             0For c1t1d0:
    # format
    Part      Tag    Flag     Cylinders         Size            Blocks
      0       root    wm       0 - 12865       62.43GB    (12866/0/0) 130924416
      1       swap    wu   12866 - 14079        5.89GB    (1214/0/0)   12353664
      2     backup    wm       0 - 14086       68.35GB    (14087/0/0) 143349312
      3 unassigned    wm   14080 - 14086       34.78MB    (7/0/0)         71232
      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)             0So then I ran the following:
    # prtvtoc /dev/rdsk/c1t0d0s0 | fmthard -s - /dev/rdsk/c1t1d0s0
    fmthard:  New volume table of contents now in place.Then I rechecked the partition table for c1t1d0:
    # format
    Part      Tag    Flag     Cylinders         Size            Blocks
      0       root    wm       0 - 14086       68.35GB    (14087/0/0) 143349312
      1 unassigned    wu       0                0         (0/0/0)             0
      2     backup    wm       0 - 14086       68.35GB    (14087/0/0) 143349312
      3 unassigned    wu       0                0         (0/0/0)             0
      4 unassigned    wu       0                0         (0/0/0)             0
      5 unassigned    wu       0                0         (0/0/0)             0
      6 unassigned    wu       0                0         (0/0/0)             0
      7 unassigned    wu       0                0         (0/0/0)             0Woo-hoo!! It matches the first disk now! :)
    Then I tried to attach the new disk to the pool again:
    # zpool attach -f rpool c1t0d0s0 c1t1d0s0
    Please be sure to invoke installboot(1M) to make 'c1t1d0s0' bootable.
    Make sure to wait until resilver is done before rebooting.
    bash-3.00# zpool status
      pool: rpool
    state: ONLINE
    status: One or more devices is currently being resilvered.  The pool will
            continue to function, possibly in a degraded state.
    action: Wait for the resilver to complete.
    scrub: resilver in progress for 0h0m, 0.40% done, 0h58m to go
    config:
            NAME          STATE     READ WRITE CKSUM
            rpool         ONLINE       0     0     0
              mirror-0    ONLINE       0     0     0
                c1t0d0s0  ONLINE       0     0     0
                c1t1d0s0  ONLINE       0     0     0  30.3M resilvered
    errors: No known data errorsBoo-yah!!! ++Does little dance++
    Then, after resilvering completed I ran:
    # installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/c1t1d0s0I think I'm starting to understand this now. I also shutdown the server to the OpenBoot prompt and booted off of the new disk and it worked! Also, my bootup time to login has drastically decreased - I would say it's about half the time it was before I added the mirror disk. So I believe the server is properly reading from both disks simultaneously in order to get better bandwidth. Cool! :)
    Thanks for the help!
    Jonathon

  • Unknown hard disk devices after LVM blunder

    Hi all,
    I have a rather weird hard disk partitioning setup because I always find myself needing to adjust my partitions from time to time. So I decided to create many logical partitions and put my personal data on an LVM partition that spans over multiple logical partitions... so that I could resize easily and create space for other stuff as required.
    The problem - I created a FAT32 file system on one of the partitions (/dev/sda16) that wasn't part of the LVM at the time (no resizing required). After doing this, I now have 2 disk devices (/dev/dm-0 and /dev/dm-1) that weren't / shouldn't be there. Also, the partitions that are part of the LVM setup are detected as FAT32 partitions by fdisk. The non-LVM changes I made with fdisk and parted while for LVM management I use Kvpm. I grew the LVM Volume group and Logical volumes to fill the disk, including the FAT32 partition I created earlier.
    Here is some output:
    [me@arch ~]$ sudo fdisk -l
    Disk /dev/sda: 320.1 GB, 320072933376 bytes
    255 heads, 63 sectors/track, 38913 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00034a0c
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 13 102400 7 HPFS/NTFS
    Partition 1 does not end on cylinder boundary.
    /dev/sda2 13 5100 40857600 7 HPFS/NTFS
    /dev/sda3 5101 38913 271602922+ 5 Extended
    /dev/sda5 5101 7012 15358108+ 83 Linux
    /dev/sda6 7013 8924 15358108+ 83 Linux
    /dev/sda7 8925 12571 29294496 b W95 FAT32
    /dev/sda8 12572 16218 29294496 b W95 FAT32
    /dev/sda9 16219 19865 29294496 b W95 FAT32
    /dev/sda10 19866 23512 29294496 b W95 FAT32
    /dev/sda11 23513 27159 29294496 b W95 FAT32
    /dev/sda12 30807 34453 29294496 b W95 FAT32
    /dev/sda13 34454 38277 30716248+ 83 Linux
    /dev/sda14 38278 38520 1951866 b W95 FAT32
    /dev/sda15 38521 38913 3156741 82 Linux swap / Solaris
    /dev/sda16 27160 30806 29294496 83 Linux
    Partition table entries are not in disk order
    Disk /dev/dm-0: 230.7 GB, 230669942784 bytes
    255 heads, 63 sectors/track, 28044 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000
    Disk /dev/dm-0 doesn't contain a valid partition table
    Disk /dev/dm-1: 10.7 GB, 10737418240 bytes
    255 heads, 63 sectors/track, 1305 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x00000000
    Disk /dev/dm-1 doesn't contain a valid partition table
    [me@arch ~]$ sudo blkid
    /dev/sda15: UUID="6b0ec9ff-af7b-47c9-a7e3-33c860f8c706" TYPE="swap"
    /dev/sda1: LABEL="System Reserved" UUID="FA481A59481A154B" TYPE="ntfs"
    /dev/sda2: UUID="E6AE2D34AE2CFF25" TYPE="ntfs"
    /dev/sda5: UUID="f0cb8bbe-7f41-442e-9f14-7b5aefa10ec0" TYPE="ext4"
    /dev/sda6: UUID="030136d1-7985-4ba8-af33-929bab660c69" TYPE="ext4"
    /dev/sda7: UUID="uuzBuM-OmD2-wvfg-X6cb-tuLY-4JTf-VVCcrJ" TYPE="LVM2_member"
    /dev/sda8: UUID="CoXf98-btzg-Mfm3-pXR9-dHfW-tsmk-LbkTwh" TYPE="LVM2_member"
    /dev/sda9: UUID="eBQ67Z-5RNv-Touw-GIpO-toW1-ZXCr-3uDKvR" TYPE="LVM2_member"
    /dev/sda10: UUID="x8L0nI-MgI8-XZ0B-cm9k-it7J-frxe-AdSMaw" TYPE="LVM2_member"
    /dev/sda11: UUID="FqO1Ca-60X4-br4P-FS3Y-1egf-ICrF-4cXr7W" TYPE="LVM2_member"
    /dev/sda12: UUID="WzWN75-mq6R-D25Y-Mz1n-883n-dsYT-wQrH1B" TYPE="LVM2_member"
    /dev/sda13: UUID="gqdPKd-1QhP-ya28-JmZ0-7hwU-00r1-swKu70" TYPE="LVM2_member"
    /dev/sda14: UUID="1258-EDB5" TYPE="vfat"
    /dev/sda16: UUID="cjdNvq-pm29-B5jE-YU4S-dLAi-N7JJ-RpJKDw" TYPE="LVM2_member"
    /dev/mapper/DataVolumeGroup-DataLogicalVolume: UUID="7eee3ccb-703c-4aad-918e-6e39488ea7b6" TYPE="ext4"
    /dev/mapper/DataVolumeGroup-ProxyCache: UUID="6db398c5-fd22-4998-acc7-10661ac136bc" TYPE="reiserfs"
    [me@arch ~]$ sudo pvdisplay
    --- Physical volume ---
    PV Name /dev/sda7
    VG Name DataVolumeGroup
    PV Size 27.94 GiB / not usable 3.91 MiB
    Allocatable yes (but full)
    PE Size 4.00 MiB
    Total PE 7151
    Free PE 0
    Allocated PE 7151
    PV UUID uuzBuM-OmD2-wvfg-X6cb-tuLY-4JTf-VVCcrJ
    --- Physical volume ---
    PV Name /dev/sda8
    VG Name DataVolumeGroup
    PV Size 27.94 GiB / not usable 3.91 MiB
    Allocatable yes (but full)
    PE Size 4.00 MiB
    Total PE 7151
    Free PE 0
    Allocated PE 7151
    PV UUID CoXf98-btzg-Mfm3-pXR9-dHfW-tsmk-LbkTwh
    --- Physical volume ---
    PV Name /dev/sda9
    VG Name DataVolumeGroup
    PV Size 27.94 GiB / not usable 3.91 MiB
    Allocatable yes (but full)
    PE Size 4.00 MiB
    Total PE 7151
    Free PE 0
    Allocated PE 7151
    PV UUID eBQ67Z-5RNv-Touw-GIpO-toW1-ZXCr-3uDKvR
    --- Physical volume ---
    PV Name /dev/sda10
    VG Name DataVolumeGroup
    PV Size 27.94 GiB / not usable 3.91 MiB
    Allocatable yes (but full)
    PE Size 4.00 MiB
    Total PE 7151
    Free PE 0
    Allocated PE 7151
    PV UUID x8L0nI-MgI8-XZ0B-cm9k-it7J-frxe-AdSMaw
    --- Physical volume ---
    PV Name /dev/sda13
    VG Name DataVolumeGroup
    PV Size 29.29 GiB / not usable 344.50 KiB
    Allocatable yes (but full)
    PE Size 4.00 MiB
    Total PE 7499
    Free PE 0
    Allocated PE 7499
    PV UUID gqdPKd-1QhP-ya28-JmZ0-7hwU-00r1-swKu70
    --- Physical volume ---
    PV Name /dev/sda11
    VG Name DataVolumeGroup
    PV Size 27.94 GiB / not usable 3.91 MiB
    Allocatable yes (but full)
    PE Size 4.00 MiB
    Total PE 7151
    Free PE 0
    Allocated PE 7151
    PV UUID FqO1Ca-60X4-br4P-FS3Y-1egf-ICrF-4cXr7W
    --- Physical volume ---
    PV Name /dev/sda16
    VG Name DataVolumeGroup
    PV Size 27.94 GiB / not usable 3.91 MiB
    Allocatable yes (but full)
    PE Size 4.00 MiB
    Total PE 7151
    Free PE 0
    Allocated PE 7151
    PV UUID cjdNvq-pm29-B5jE-YU4S-dLAi-N7JJ-RpJKDw
    --- Physical volume ---
    PV Name /dev/sda12
    VG Name DataVolumeGroup
    PV Size 27.94 GiB / not usable 3.91 MiB
    Allocatable yes (but full)
    PE Size 4.00 MiB
    Total PE 7151
    Free PE 0
    Allocated PE 7151
    PV UUID WzWN75-mq6R-D25Y-Mz1n-883n-dsYT-wQrH1B
    [me@arch ~]$ sudo lvdisplay
    --- Logical volume ---
    LV Name /dev/DataVolumeGroup/DataLogicalVolume
    VG Name DataVolumeGroup
    LV UUID e7MjVc-JeR8-8Pz2-tiFY-2vwP-dVwq-B4q85K
    LV Write Access read/write
    LV Status available
    # open 1
    LV Size 214.83 GiB
    Current LE 54996
    Segments 8
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 254:0
    --- Logical volume ---
    LV Name /dev/DataVolumeGroup/ProxyCache
    VG Name DataVolumeGroup
    LV UUID LvKsfw-EqZU-gRTh-oZes-nP5c-Iw5I-0jBDja
    LV Write Access read/write
    LV Status available
    # open 2
    LV Size 10.00 GiB
    Current LE 2560
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 254:1
    And a kvpm screenshot
    So far, all partitions mount properly and the system works fine, but the bad output from fdisk and the new devices are unnerving. How can I fix this?
    Thanks in advance.

    bump if i may... sorry ppl.

Maybe you are looking for