Not really sure if this is a bug or not but it might be worth looking at for migration purposes. The following thread refers : http://forums.contribs.org/index.php/topic,46531.0.html In the process of testing an upgrade from 7.5.1 to 8 I wanted to upgrade the disks at the same time. USB is slow compared, and I don't have a USB disk big enough to do the backup, plus I didn't want to use a contrib if possible, and Affa as suggested is both a contrib and requires another machine to hold the backups which I don't have. I remembered doing something similar before - see links below : http://forums.contribs.org/index.php?topic=39892.0 http://forums.contribs.org/index.php?topic=37686.0 http://wiki.contribs.org/UpgradeDisk I did a new install of 8b6, signal-event pre-backup on the old disks, removed one and inserted it in the new box. Booted with the V8 CD in rescue mode. However, following this process doesn't seem to work as follows : mdadm -AR /dev/md5 /dev/hdc2 mdadm: no devices found for /dev/md5 Only one old drive and a CDrom in the machine and have checked I am using the correct drive - /dev/hdc mdadm --examine --scan reveals : ARRAY /dev/md1 level=raid1 num-devices=2 UUID=e612cfc4 etc ARRAY /dev/md2 level=raid1 num-devices=2 UUID=558aae94 etc I guess this is the old array information read from the drive that is plugged in. But why it fails I do not understand. Decided to boot the old drive with a 7.5.1 CD. Ran the commands as per the Wiki and managed to change the LVM name from 'main' to 'oldmain' : mdadm -AR /dev/md5 /dev/hdc2 lvm vgscan lvm vgs -v lvm vgchange -a n lvm vgrename main oldmain All seems to change OK. Rebooted with the new drives plugged in with the old drive as well which is now actually /dev/hdd2 However, you can mount it as a raid device : mkdir /mnt/old mount /dev/oldmain/root /mnt/old Followed the rest of the wiki - currently it is copying over - my guess is it will be OK but I'll report back. Has something changed with mdadm or lvm between 7.5.1 & 8 ? B. Rgds John
(In reply to Terry Fage from comment #14) > See comments 11, 12, 13 Closing.
See comments 11, 12, 13
This is complete, if agree can be CLOSED
Tis a thing of beauty. Close as you see fit.
As suggested http://wiki.contribs.org/UpgradeDisk
(In reply to Terry Fage from comment #9) > Changes to relevant page > http://wiki.contribs.org/UpgradeDisk#Recovering_a_system_where_pre- > backup_could_not_be_run > > Close if agree Only comment would be the headings for the last two sections should be the same as above them I think. Also the section I originally did on the 3rd drive is double spaced as I hadn't a clue what I was doing. Doesn't look like the rest and could be better formatted.
Changes to relevant page http://wiki.contribs.org/UpgradeDisk#Recovering_a_system_where_pre-backup_could_not_be_run Close if agree
(In reply to Terry Fage from comment #7) > Can somoene who understands this please see the discussion here: > http://wiki.contribs.org/Talk:UpgradeDisk > > Is this relevant to this wiki page, where should it be inserted if it is. > > Otherwise this actual doc bug is addressed in the updated contents. Suggest you add this in a warning block at the end, and possibbly a note link from the words 'pre-backup' to this section Possible heading similar to : Recovering a system where you were unable to run pre-backup Blah....
Can somoene who understands this please see the discussion here: http://wiki.contribs.org/Talk:UpgradeDisk Is this relevant to this wiki page, where should it be inserted if it is. Otherwise this actual doc bug is addressed in the updated contents.
I beleive that this is a documentation but and is recorded in : http://wiki.contribs.org/UpgradeDisk I am happy if it is moved to docs, page checked and then closed.
(In reply to comment #4) > > AFAIK it should be sdX Depends how the machine picks up the drive - in my case for the move from 8b6 to 8b6 the old drive was on an IDE cable and was hda. The new disks were on SATA as sda, sdb & sdc
(In reply to comment #3) > > Thanks for that Filipo. I'll add it to the wiki when I get a moment. Still begs > the question as to what is happening ?! are you sure the hd is seen as hdc? AFAIK it should be sdX what's the output of: fdisk -l
(In reply to comment #2) > As a workaround to use 8.x rescue mode, you could use: > > mdadm -A -R -m 2 /dev/md2 > > omitting array member, telling mdadm to use minor 2 (that means component of > md2). > Another way is using the uuid (-u nnnn...), but it's tedious to write. Thanks for that Filipo. I'll add it to the wiki when I get a moment. Still begs the question as to what is happening ?!
> mdadm -AR /dev/md5 /dev/hdc2 > mdadm: no devices found for /dev/md5 As a workaround to use 8.x rescue mode, you could use: mdadm -A -R -m 2 /dev/md2 omitting array member, telling mdadm to use minor 2 (that means component of md2). Another way is using the uuid (-u nnnn...), but it's tedious to write.
As a follow up to this, I just tried the same thing moving an installation from 8b6 to 8b6 as I was changing hardware. I had exactly the same problem again with renaming the volumes and had to use a 7.x disk to do it.