When I installed my system via jumpstart, I managed to create a
mirrored rpool. I didn't want that. If I detach the one disk from the
mirror the system isn't bootable. How do I break the rpool mirror and
still have a bootable single disk system?
TIA
Have you install the boot block on the other disk?
I suspect you could remove the other disk, since there is perhaps only
only a boot block on one of them.
--
I respectfully request that this message is not archived by companies as
unscrupulous as 'Experts Exchange' . In case you are unaware,
'Experts Exchange' take questions posted on the web and try to find
idiots stupid enough to pay for the answers, which were posted freely
by others. They are leeches.
Hi--
Are you detaching the primary boot disk or the secondary disk
in the mirror? If you are detaching the primary boot disk, then you'll
need to boot specifically from the secondary disk, if your system is
not set up to boot automatically from the secondary disk. On my
system, I had to use this syntax:
ok boot /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk@2
If you are detaching the secondary disk, then booting from the
primary disk should work as expected.
If you can't boot specifically from the primary or secondary disk
while
both disks are attached to the pool, check whether both disks are
currently operational by using zpool status. If both disks are
operational, then reapply the boot blocks to both disks and attempt
to boot from either disk.
I just tested this again using the steps below.
Cindy
1. Attached second disk to root pool.
2. Waited for second disk resilvering to complete.
3. Installed the boot blocks on second disk.
4. Booted from primary disk
5. Booted specifically from the secondary disk.
6. Detached the primary root disk from root pool.
7. Booted specifically from secondary disk.
Hi Cindy
How do I know which disk is the primary disk? I have a local disk and
a SAN disk (without mpxio for now). I dettached the local disk, and
then life went all to hell. I thought the zpool detach command just
removed a device from the mirror to "no longer make it a
mirror"....sigh.
I couldn't boot from either disk at the obp. They were not bootable?
This is directly after an installation. I would have thought that
install would have made at least one of the drives bootable. It did
update the boot env correctly at the prom level.
I booted single usermode off net, imported the rpool, but it wouldn't
let me attach any devices to the pool. It would complain that it
wasn't a valid device.
Dam, I need to go to zfs school.
If I can do it, you can do it. :-)
The primary disk is the one you are booting from.
Disks that are selected during the install process are made bootable
automatically, but something went wrong in your case.
Which Solaris release is this?
Disks can be detached from the root pool but then you must
specifically
boot from another disk in the pool. CR 6704717 causes some challenges
if you detach a disk in the root pool and then reboot without booting
specifically from another disk in the pool.
If it booted successfully after the installation, then something else
happened afterwards. If possible, try to reinstall just using the
local
disk and make sure it is bootable.
You might review the ZFS troubleshooting wiki, starting here:
http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide#ZFS_Boot_Issues
Cindy
If you're lazy like me, you'd pull the local disk and re-run
Jumpstart. That said, the procedures already provided will work.
You should be able to remove the second disk from the pool.
Make sure that:
- the system boots from the other disk, not the disk
you just removed from the pool
- make sure that the disk has the proper bootblock
installed (the installer should have done that)
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.