19
edits
Changes
From SME Server
Jump to navigationJump to searchAddExtraHardDisk - SCSI (view source)
Revision as of 17:28, 18 October 2011
, 17:28, 18 October 2011no edit summary
== Assumptions ==
== Assumptions ==
* I assume the SCSI drive is already installed and functioning.
* I have assumed that the SCSI drive is already installed and functioning.
* If installed on an array controller the drive has been configured as a single drive RAID 0
* If installed on an array controller the drive has been configured as a single drive RAID 0
=== 1 Preparation ===
=== 1 Preparation ===
1.0 Mount the harddrive and fire up your machine.
1.0 Mount the hard drive and fire up your machine.
1.1 Get direct shell access and login as root.
1.1 Get direct shell access and login as root.
md: raid1 personality registered as nr 3
md: raid1 personality registered as nr 3
md: md1 stopped.
md: md1 stopped.
md: bind<cciss/c1d0p1>
md: bind<cciss/c0d0p1>
raid1: raid set md1 active with 1 out of 2 mirrors
raid1: raid set md1 active with 1 out of 2 mirrors
md: md2 stopped.
md: md2 stopped.
md: bind<cciss/c1d0p2>
md: bind<cciss/c0d0p2>
raid1: raid set md2 active with 1 out of 2 mirrors
raid1: raid set md2 active with 1 out of 2 mirrors
md: Autodetecting RAID arrays.
md: Autodetecting RAID arrays.
md: could not bd_claim cciss/c1d0p1.
md: could not bd_claim cciss/c0d0p1.
md: could not bd_claim cciss/c1d0p2.
md: could not bd_claim cciss/c0d0p2.
md: autorun ...
md: autorun ...
md: ... autorun DONE.
md: ... autorun DONE.
Info I needed was:
Info I needed was:
md: bind<cciss/c1d0p1>
md: bind<cciss/c0d0p1>
md: bind<cciss/c1d0p2>
md: bind<cciss/c0d0p2>
This tells me that I currently have 2 active partitions, p1 & p2, on drive c1d0
This tells me that I currently have 2 active partitions, p1 & p2, on drive c0d0 (controller 0, disk 0); if a secondary disk is added or used it would therefore be c0d1 (controller 0, disk 1); if another SCSI controller is added or used it would therefore be c1d0 (controller 1, disk 0).
Logically my new drive should be on c1d1, & the linux device file to match should be in /dev/cciss, so:
Logically my new drive should be on c0d1 (controller 0, disk 1), & the linux device file to match should be in /dev/cciss, so:
fdisk /dev/cciss/c1d1 (use ? or m to get help)
fdisk /dev/cciss/c0d1 (use ? or m to get help)
Follow the prompts to add a Linux partition
Follow the prompts to add a Linux partition, I usually add a primary partition using the full capacity of the drive.
Use the w key to write the partiton table & exit from fdisk
Use the w key to write the partiton table & exit from fdisk
Lets see if we have a partition to work with:
Lets see if we have a partition to work with:
fdisk -l /dev/cciss/c1d1
fdisk -l /dev/cciss/c0d1
Disk /dev/cciss/c1d1: 299.9 GB, 299992412160 bytes
Disk /dev/cciss/c0d1: 299.9 GB, 299992412160 bytes
255 heads, 63 sectors/track, 36472 cylinders
255 heads, 63 sectors/track, 36472 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
Device Boot Start End Blocks Id System
/dev/cciss/c1d1p1 1 36472 292961308+ 83 Linux
/dev/cciss/c0d1p1 1 36472 292961308+ 83 Linux
Yup, cool, p1 is partition 1 on device c1d1
Yup, cool, p1 is partition 1 on device c0d1
I don't want to add it to lvm to as it helps to make it more portable for me so this is all I need, your requirements may differ.
I don't want to add it to lvm as it helps to make it more portable for me so this is all I need, your requirements may differ.
Hint: if you need to add it into lvm look at the RAID Howto in the wiki.
Hint: if you need to add it into lvm look at the RAID Howto in the wiki.
2.1 Prepare the new partition
2.1 Prepare the new partition
Create filesystem & journal on device
Create the ext3 filesystem & journal on device
mkfs.ext3 -j /dev/cciss/c1d1p1
mkfs.ext3 -j /dev/cciss/c0d1p1
=== 3 Mount ===
=== 3 Mount ===
pico /etc/fstab
pico /etc/fstab
Add the following data to the file (separate columns with a hit on the space-bar):
Add the following data to the file (separate columns with a hit on the space-bar):
/dev/cciss/c1d1p1 /mnt/backupdrive ext3 usrquota,grpquota 1 2
/dev/cciss/c1d1p1 /mnt/backupdrive ext3 usrquota,grpquota 0 2
Make sure you end this line with a newline (with enter).
Make sure you end this line with a newline (with enter).
<br>Hit <ctrl-x> to exit the editor, y and enter to save.
<br>Hit <ctrl-x> to exit the editor, y and enter to save.
3.2 Mount manually (this time) all filesystems listed in /etc/fstab
3.2 Manually mount (this time) all the filesystems listed in /etc/fstab
mount -a
mount -a
/dev/md1 101018 27580 68222 29% /boot
/dev/md1 101018 27580 68222 29% /boot
none 1980264 0 1980264 0% /dev/shm
none 1980264 0 1980264 0% /dev/shm
/dev/cciss/c1d1p1 288362876 98368 273616444 1% /mnt/backupdrive
/dev/cciss/c0d1p1 288362876 98368 273616444 1% /mnt/backupdrive
If you don't see a line for /dev/cciss/c0d1p1, something went wrong. Go back to step 2 and check if you followed all instructions correctly; check for typos.
3.4 Create Quota files
As we enabled quotas in the fstab file for this drive we now need to create data files for the quota system to use
quotacheck -cug /mnt/backupdrive
now run the following to generate up to date quota values for the files on the filesystem
quotacheck -cug /mnt/backupdrive
We're all done, enjoy!
We're all done, enjoy!
=== 4 Notes ===
I noticed that the extra drive wasn't picked up by Sysmon. On looking at /var/log/sysmon I found line after line of:
opening '/var/lib/rrd/drive_cciss/c0d1p1.rrd': No such file or directory
To fix this issue I needed to create the folder /var/lib/rrd/drive_cciss/ & then restart Sysmon, the c0d1p1.rrd then magically appears in this folder.
This applies regardless of whether Sysmon is installed before or after the extra disk is added.
----
----
[[Category:Howto]]
[[Category:Howto]]
[[Category:Administration:Storage]]
