3Ware 9000 Series Release Notes page 5

5. Type:
chkconfig --add --level 345 3dm2
6. Change the operating mode by typing:
chmod +x /etc/rc.d/init.d/3dm2
7. Change the permissions on the 3dm2 configuration file:
chmod 600 /etc/3dm2/3dm2.conf
8. Start the 3DM 2 daemon by typing:
/etc/rc.d/init.d/3dm2 start
9. Open the web browser and go to https://localhost:888 or http://localhost:888.
Fedora Core 3 – 3DM 2 crashes when email notification is used
If you use email notification (using sendmail or any other email server) under
Fedora Core 3, the 3DM 2 daemon will crash. You will then have to restart the
3DM 2 daemon (e.g.
problem, you must use the IP address instead of the name in the 'Server (name or
IP)' box to resolve this issue. You can use 127.0.0.1 by default or the actual IP
address of your server.
If you don't know the IP address of your mail server, you can get it by typing:
nslookup <your email server name>
See 3ware KB article 12753
Linux (all versions) - After Migration Additional Steps are Required to Show & Use New
Capacity
To get the new unit capacity to show up on the block device target within Linux,
after the migrate completes, do the following:
If the newly migrated unit is being used as primary storage, then a reboot is
required before seeing the new unit size. Following the reboot proceed to step-4.
If the newly migrated unit is being used as secondary storage, do the following:
1. Unmount all filesystems, swap devices, and stop all processes which have open
file descriptors on the unit that had its capacity expanded
2. Use 3DM 2 or tw_cli to remove the newly migrated unit
720-0123-00 Rev. A
/etc/rc.d/init.d/3dm2 start
http://www.3ware.com/kb/article.aspx?id=12753
5
). To get around this