Hello.
Harry Putnam писал 03.08.2014 23:42:
Which gives these steps to fix it:
1. Get VTOC c0d0
prtvtoc /dev/rdsk/c0d0s0
2. Create same slice on c0d2. Use format or
prtvtoc /dev/rdsk/c0d0s0| fmthard -s - /dev/rdsk/c0d2s0
3. Attach slice.
zpool attach -f rpool c0d0s0 c0d2s0
First, let me ask where the mysterious appended `s0' came from? I
guess it means slice number 0?
Yes, you copied layout of first disk in rpool to the second disk, this
created
partition. Root pool is supposed to be created over partition, not the
raw device.
But anyway, going thru the steps I hit more troubles:
Went smooth until arriving at step 3. And note that after running
step 2:
prtvtoc /dev/rdsk/c0d0s0| fmthard -s - /dev/rdsk/c0d1s0
I checked both disks vtoc with `prtvtoc $disk' on each disk. The
output
looks identical. And I inspected pretty closely.
# zpool attach rpool c0d0s0 c0d1s0
invalid vdev specification
use '-f' to override the following errors:
/dev/dsk/c0d1s0 overlaps with /dev/dsk/c0d1s2
So, is it wise to use the -f flag and override the mismatch?
You should use this flag in this situation. s2 IIRC is a special
"backup" slice which covers the whole disk.
Don't forget to install grub on the newly attached device.
---
System Administrator of Southern Federal University Computer Center
_______________________________________________
openindiana-discuss mailing list
[email protected]
http://openindiana.org/mailman/listinfo/openindiana-discuss
