Sophos User Bulletin Board has been retired and remains here for reference purposes only. Please use our Unified Threat Management forums on Sophos Community. See article 123010 for details.

Welcome to the Sophos User Bulletin Board.
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

LinkBack Thread Tools
Junior Member
Join Date: Oct 2012
Posts: 9
#1 (permalink)  
Old 10-21-2012, 04:28 PM
Cool UTM 9 Install - Multiple Hard Drives

As a home user, I'm looking to re-install UTM 9 aft er adding an SSD drive as the boot drive for UTM 9. I want to keep the larger mechanical drive and have it write log files there. Since I've already got things working great as is, I want to re-install using my backup file.
Once installed, how to get UTM 9 to write all logs to the second mechanical drive?
Your input will be greatly appreciated
Reply With Quote
BrucekConvergent's Avatar
Master of Reality
Join Date: Oct 2005
Location: SC, USA
Posts: 4,882
#2 (permalink)  
Old 10-21-2012, 05:06 PM

The UTM only supports 1 hard drive.

The only exception is the ability to use a hardware mirror when using very specific RAID controllers (the built-in hybrid RAID on Intel boards is NOT one of them).
Convergent Information Security Solutions, LLC
Sophos Platinum Solution Partner
Reply With Quote
Junior Member
Join Date: Oct 2012
Posts: 9
#3 (permalink)  
Old 10-21-2012, 05:14 PM

Really! Well so much for that idea then!
Reply With Quote
Junior Member
Join Date: Feb 2007
Posts: 11
#4 (permalink)  
Old 12-03-2012, 01:36 AM

Here is a somewhat quick and dirty way to accomplish this. I just did this so I know it works. You'll need a copy of gparted or some other live linux so that you can edit partition labels before booting into you UTM9 install.

1. Do a full install of UTM9 on the spinning disk
2. Do a full install of UTM9 on the SSD
3. Before rebooting after the SSD install Alt-F2 to drop to a command line
4. Run '/dest/bin/blkid' to print out the UUIDs of the spinning disk's partitions
5. Edit '/dest/etc/fstab' and replace the existing UUIDs of the SSD with the spinning disk's UUIDs for those that you want to use. (I mapped /var/storage, /var/log, /tmp, and swap all to the spinning disk)
6. Reboot, boot gparted live CD (or your choice of live CD for partition editing)
7. Change the partition labels on the spinning disk and the SSD so that there only exists a single version of the UTM9 partitions. (In my case I just add '-no' after the existing partition labels. Example: spinning disk - 'root' renamed to 'root - no', ssd - 'log' renamed 'log-no').

Now when you boot the system for the first time the correct partitions should mount and everything should get prepared correctly. This process doesn't make the best use of the disks from an allocation perspective I just didn't take the time to attempt deleting and resizing partitions.
Reply With Quote
Join Date: May 2003
Location: Brunswick, Maryland, USA
Posts: 7,301
#5 (permalink)  
Old 12-03-2012, 03:47 AM

3ware cards work well for astaro and raid whatever level you want....
Owner: Emmanuel Technology Consulting
My Installed Configs
Microsoft Partner
Sophos Silver Solution Reseller
Sophos Certified Architect - UTM
Reply With Quote

install, multiple drives, seperate log disk

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

All times are GMT. The time now is 02:42 PM.

Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2015, Jelsoft Enterprises Ltd.

These pages are specifically maintained for the discussion of firewall issues within the Open Source community, and might already reflect new alpha/beta releases under development. Please refer to our product specifications for the functionality of the actual release. Discussions of new/enhanced functionality does not constitute a commitment of Astaro, to integrate this functionality into future releases.