Topic: Moving SME to new hardware, the shortest path...

[raem]

thomasch

DON'T TRY TO DO THIS ON PRODUCTION SERVER WITHOUT FULL BACKUP!

That comment applies to ANYTHING you do a on a production server !!!

If you are about to adjust hard disk partitions, it would be even more prudent to do a backup first.

If you are aware of problems with the method, please post them to the appropriate discussion page on the wiki.

Assuming you were using RAID1 software array, then it would have been wise (& easy) to remove one disk first, as a full system backup.

[kruhm]

http://wiki.contribs.org/Raid#Upgrading_the_Hard_Drive_Size
Works for me. I never had any problems with it.

[bloodshoteye]

Hi

SME Server 7.3 up-to-date.
I have a small panic - I'm attempting the above migration to larger drives, same server.
So I pulled a drive from the RAID1 array, replaced it with a larger, and restarted.
Su Admin / Manage Disk redundancy gave a message partly containing the following words:

The free disk count must equal one.
Manual intervention may be required.
I can't remember the disk descriptions.

I then put the old drive back, thinking I would try again tomorrow, after consulting the forums.
With original disks in exactly the same position, etc, Su Admin reports:

Personalities : [raid1]
md2 : active raid1 sda2[0]
         244091520 blocks [2/1] [U_]
md1 : active raid1 sda1[0]
         104320 blocks [2/1] [U_]
unused devices: <none>

The free disk count must equal one.
Manual intervention may be required.
Current disk status:

Installed disks: sdc sda sdb
Unused disks: sda
Free disks: sdc sdb

The same message has been there for about an hour.
What does this mean, please - do I have a problem?
Thanks for you time,
         

[bloodshoteye]

Answer my own post

I read elsewhere to add back partitions like this:

/dev/md2 -a /dev/sdb2 and /dev/md1 -a /dev/sdb2

if the raid array has been broken by a removed drive

Well, I did that in stages and sme immediately started syncing disks and now all is well