Line 139: |
Line 139: |
| | | |
| All the usual warnings apply. Remember that any old contribs & templates will have to be reinstalled (assuming that they will work with V8) | | All the usual warnings apply. Remember that any old contribs & templates will have to be reinstalled (assuming that they will work with V8) |
| + | |
| + | === Moving from SME 8.x to SME 9.x === |
| + | |
| + | SME 9 entails the same issues as SME 8 (see above): |
| + | |
| + | With SME 8 being based on CentOS 5, assembling the RAID in rescue mode must be specified using the disk's UUID. If you have the SME 7 CD it will be easier to rename the Volume Group using it per the instructions below. Otherwise use the SME 8 procedure. |
| + | |
| + | {{Note box|Before you start, It might be worth fscking the disk/s to ensure that there are no errors.}} |
| + | |
| + | # Make sure you have a very good backup |
| + | # signal-event [[UpgradeDisk#Recovering_a_system_where_pre-backup_could_not_be_run|pre-backup]] on the old installation |
| + | # Boot with a SME7 CD or SME 8 CD and only one of your original disks (in the case of a RAID1 arrangement) |
| + | # As per instructions in "Boot from SME Server 7.1 (or newer) install CD" above : |
| + | |
| + | Type "sme rescue" at the command prompt and hit enter |
| + | |
| + | Note: don't start the network and skip mounting the filesystem. |
| + | |
| + | If using SME 7 CD |
| + | mdadm -AR /dev/md5 /dev/sdx2 |
| + | |
| + | If using SME 8 CD (see [[bugzilla: 6195]]) |
| + | mdadm --examine /dev/sda# | grep 'UUID' |
| + | mdadm -AR --uuid '''the:uuid:value:from:above''' /dev/md5 |
| + | |
| + | If using SME 9 CD (see [[bugzilla: 6195]]) |
| + | mdadm --examine /dev/sda# | grep 'UUID' |
| + | mdadm -AR --uuid '''the:uuid:value:from:above''' /dev/md5 |
| + | |
| + | Next Steps |
| + | lvm vgscan |
| + | lvm vgs -v |
| + | lvm vgchange -a n |
| + | lvm vgrename main new_vg_name |
| + | exit |
| + | |
| + | Now remove the CD and reboot into SME 9 : |
| + | |
| + | mdadm -AR /dev/md5 /dev/sdx2 (n.b. you may find that /dev/md5 already exists) |
| + | vgscan |
| + | vgchange -a y new_vg_name |
| + | mkdir /mnt/tmp |
| + | mount /dev/new_vg_name/root /mnt/tmp |
| + | |
| + | {{Note box|In some rare cases your VolumeGroup name listed in the last line might be different, more information can be found in [[[[bugzilla: 3883]]]].}} |
| + | |
| + | You should now be able to view all your old data under /mnt/tmp |
| + | |
| + | db configuration setprop backup Program CopyFromDisk status enabled |
| + | signal-event pre-restore |
| + | signal-event restore-tape /mnt/tmp (note: this step may take a long time depending on how much data is being restored |
| + | signal-event post-upgrade |
| + | signal-event reboot |
| + | |
| + | Shutdown and remove old drive and reboot |
| + | |
| + | All the usual warnings apply. Remember that any old contribs & templates will have to be reinstalled (assuming that they will work with V9) |
| | | |
| ===Using a third drive=== | | ===Using a third drive=== |