JimboWiki - User contributions [en]

USCSA Race setup with SplitSecond

2019-02-05T16:33:39Z

J: /* Getting help or providing feedback */

== Competitor Classes ==
For each race submission, every participating competitor must be assigned one of 5 classes. This class assignment will determine how scoring is handled for the competitor, and the competitor's team. The classes are:

;A
:For all A-team members. Only USCSA members may be marked with the "A" class, and a USCSA number must be provided with the submission. A-team members with the same team abbreviation make up that school's A-team. This team '''will''' be used to create team results. The team results '''will''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All A-team competitors '''will''' receive USCSA race points.
;B
:For all B-team members. Only USCSA members may be marked with the "B" class, and a USCSA number must be provided with the submission. B-team members with the same team abbreviation make up that school's B-team. This team '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is not eligible''' to score individually. All B-team competitors '''will''' receive USCSA race points.
;Individual
:For all individually qualified members. Only USCSA members may be marked with the "Individual" class, and a USCSA number must be provided with the submission. Individual entries '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All Individual competitors '''will''' receive USCSA race points.
;Unscored/Guest
:For all non-USCSA members, as well as USCSA competitors from divisions other than the division running the event. USCSA or non-USCSA members may be marked with the "Unscored/Guest" class. If the competitor is a USCSA member, then a USCSA number should be provided. Unscored/Guest entries '''will not''' be used to create team results. Each Unscored/Guest competitor '''is not eligible''' to score individually. Unscored/Guest competitors '''will''' receive USCSA race points if they are USCSA members and a USCSA number has been provided. Unscored/Guest competitors '''will not''' receive USCSA race points if a USCSA number has not been provided.
;AA
:For all AA-team members. This class '''should not be used''' by most divisions. Only USCSA members may be marked with the "AA" class, and a USCSA number must be provided with the submission. AA-team members with the same team abbreviation make up that school's AA-team. This team '''will''' be used to create team results for the race. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All AA-team competitors '''will''' receive USCSA race points.

{|style="border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0" border="1"
|+ USCSA scoring classes
! Class
! Times
! Team Result for Race
! Team Result in Divisional Standings
! Individual Result in Divisional Standings
! Receive USCSA Race Points
|-
! A
| Yes
| Yes
| Yes
| Yes
| Yes
|-
! B
| Yes
| No
| No
| No
| Yes
|-
! Individual
| Yes
| No
| No
| Yes
| Yes
|-
! Unscored/Guest
| Yes
| No
| No
| No
| If USCSA member
|-
! AA
| Yes
| Yes
| No
| Yes
| Yes
|}

== How to create a USCSA race in SplitSecond National/FIS ==
==== Download National/FIS ====
[http://www.splitsecond.com SplitSecond National/FIS]

==== Configure National/FIS for USCSA races ====
Fill in the header information as you normally would for a normal USSA race.
Check the following boxes at the bottom
*USCSA Event
*Show USCSA Class on Competitor tab instead of Class
*Show USCSA Number on Competitor tab instead of USSA/FIS Number

[[Image:race_setup.png]]

Select the Factors/Lists tab
Download a USCSA points list and the current USSA points list
*Select the current USSA points list

[[Image:race_setup_points_lists.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Fill in the racer's last name. Select the matching name from the box on the right.
[[Image:racer_registration.png]]

If data from both lists matched the following fields will be filled out correctly
*USSA number
*USCSA number
*Year of birth
*USSA points
*Team (This will be the school abbreviation not 'USA')
*USSA Class

*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. If a racer does not have a USCSA number, verify that you selected the correct USSA athlete. If you are sure that you have the correct athlete [[#Getting_help_or_providing_feedback|Contact the national office]] to resolve the discrepancy.

*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page - not the USSA race code.

[[Image:submit_race2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with National/FIS''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:natfis_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*USSA Number
*USCSA Number
*Bib
*etc...
[[Image:natfis_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:nafis_blockedit.png]]

== How to create a USCSA race in SplitSecond's Ski Club ==
==== Download Ski Club ====
[http://www.splitsecond.com SplitSecond Ski Club]

==== Configure Ski Club for USCSA races ====
Fill in the header information as you normally would for a normal race.
Check the following boxes at the top and bottom
*USCSA Event
*This race includes team scoring (using USCSA Team Scoring)
*Click on the button labeled "Download USCSA List"

[[Image:race_registration_sc.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Make separate race files for Ladies' and Men's racer (Otherwise the team scoring will include both men and women)
*Fill in the racer's last name. Ski Club will search the USCSA list for a matching name. Select the correct racer/team entry from the box on the right. This will fill in all the fields except for class.
*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. [[#Getting_help_or_providing_feedback|Contact the national office]] if a racer does not appear on the USCSA list.
[[Image:racer_registration_sc.png]]
*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration_sc2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race_sc.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page.
[[Image:submit_race_sc2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with Ski Club''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:skiclub_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*Member#
*Bib
*etc...
[[Image:skiclub_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:skiclub_blockedit.png]]

== How to lookup USCSA numbers ==
It is '''critically important''' that your race contains ''USCSA numbers'' for '''ALL''' USCSA members and proper ''team abbreviations'' for '''ALL''' USCSA members scored as class "A" or "B" competitors. The easiest way to find the USCSA numbers and team abbreviations is to look them up in SplitSecond using the USCSA competitor list '''(see the instructions above)'''.

'''If you cannot find the competitor in SplitSecond or you have errors for a particular competitor when submitting the results:'''
*Do '''not''' make up a USCSA number
*Do '''not''' put in some place holder value
*Do '''not''' change the competitor's class to "Guest" (unless they really are a guest)
*'''Do''' contact the national office - there is probably an issue with the competitor's registration that is causing them to not show up in the list.

If SplitSecond is not the right answer for you, there are other methods described below.

==== Individual racer lookup on uscsa.com ====
Use the competitor search function on [http://www.uscsa.com/uscsa-results this page]


==== Download the USCSA member csv ====
This is the same list that SplitSecond uses. If you have an updated list in SplitSecond, you won't find any additional information in here. This might be useful for people who want to generate running orders or other automated tasks.

[http://results.uscsa.com:8080/RaceNetData/CompetitorList/ Download CSV list]

== After submitting the race ==
An e-mail will be sent to the race organizer within a few minutes which will detail the status of scoring. If there are problems with the submission, a report detailing all the problems will be included. You may correct the errors and resubmit (see the section below). If there are no problems, then the e-mail will note that the submission was successful, and the results will be available on the [http://www.uscsa.com/conferences/uscsa-results.html Results Page]. If you don't receive an e-mail within an hour, get in touch with James (see [[#Getting_help_or_providing_feedback|this section]]), and note the race code.

=== Correcting Errors ===
Here are some common errors, and hints on how to fix them.

;Must supply USCSA number for all scored racers
:If a competitor is assigned any [[#Competitor_Classes|class]] besides Unscored/Guest, a USCSA number must be supplied. This is used to match up all the results for the season and across seasons.
;No such USCSA Competitor or wrong USCSA ID
:Check to make sure that the USCSA you supplied is correct for the racer. Maybe you missed a digit, or got some numbers out of order. It is also possible that the competitor recently registered and the scoring system has not received an updated competitor list yet.
;Competitor does not exist for this Division and Season.
:The USCSA number you entered is valid, but that competitor is not a member of this division. This could mean: a) that you mistyped the USCSA number and it matched someone else's USCSA number, in which case you should correct the number, b) the competitor is registered incorrectly, in which case you should [[#Getting_help_or_providing_feedback|contact James and the national office]] to correct the issue, c) the competitor is a guest from a different division, in which case you should change the competitor's class to Unscored/Guest, or d) you got your male/female race codes for the weekend backwards.
;Team abbreviation does not exist for this Division and Season
:The abbreviation used is not recognized. You must use the [[#How_to_lookup_USCSA_numbers|assigned abbreviation]]. If you don't like the assigned abbreviations, [[#Getting_help_or_providing_feedback|get in touch with James]] to change them.
;Incomplete submission. Fill all required fields and try again.
:Make sure the USCSA header (USCSA race code, race date, race type, description line 1, race admin's name, email and phone number) is filled out, and that there are results in the race you are submitting.
;Invalid race code format OR Race does not exist for that race code
:Use the race code that was assigned when you [[#How_to_create_a_USCSA_race_from_the_registration_website|created the race]].
;Results for this race have already been submitted.
:If you meant to make a change to results that you already posted, [[#Getting_help_or_providing_feedback|get in touch with James]] and let him know. If not, make sure you have your race codes straight.
;Malformed time.
:Assuming you are using SplitSecond, you should never get this error. [[#Getting_help_or_providing_feedback|Get in touch with James]] immediately if you do.

== Setting up combined scoring rules ==
In order for combined results (qualifications, rankings, divisional overall standings) to be calculated, your division must select scoring rules. For this season, send your selections to James Cialdea by e-mail (see [[#Getting_help_or_providing_feedback|this section]]). You may have different rules for the Men and Ladies - that is not a problem, just provide information for each and we will take care of the rest.

The available rules are described below. If you use a different rule, include that information in the e-mail. You may select one rule and up to three tie breakers for Individual and Team combined scoring. You do not need to select three tie breakers if your division does not have rules for three levels of ties.

In other words, fill in this grid:
* Conference Name:
* Division Name:
* Team Combined Rules
** Rule: (select one from Team Combined Rules)
** Tiebreaker 1: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Team Combined Rules, or leave blank)
* Individual Combined Rules
** Rule: (select one from Individual Combined Rules)
** Tiebreaker 1: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Individual Combined Rules, or leave blank)

Example:
<pre>
Conference Name: Rocky Mountain
Division Name: Rocky Mountain

Team Combined Rules
Rule: Team Finish Place Sum

Individual Combined Rules
Rule: World Cup Top 30
</pre>

=== Individual Combined Rules ===
For Individual Combined scoring, the following rules are available:
;Linear, top 30
:Points are assigned to the top 30 finishers, counting down linearly from 30. (1st = 30, 2nd = 29, ... , 29th = 2, 30th = 1, 31st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Linear, top 15
:Points are assigned to the top 15 finishers, counting down linearly from 15. (1st = 15, 2nd = 14, ... , 14th = 2, 15th = 1, 16st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;World Cup, top 30
:Points are assigned to the top 30 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "current system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Continental, top 15
:Points are assigned to the top 15 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "top 15 system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Race Points
:Sum of race points from FIS/USSA/USCSA formula, lowest score wins. Racers who do not participate in a race are counted as "DNS", and will take 990.00 points for that race. (Note: USCSA points are calculated and displayed in results for all USCSA-scored races regardless of whether this option is used.)
;No scoring
:Combined results are not calculated

=== Team Combined Rules ===
For Team Combined scoring, the following rules are available:
;Team Finish Place Sum
:Each team is assigned place points for each race equal to the team ranking at that race. The sum of finish places for all races is used for combined ranking. The lowest sum wins.
;Individual Finish Place Sum
:Sum of finish places for all racers using in scoring for all races. Dummy finish places will be applied for teams that do not have enough finishers, per USCSA scoring rules. The lowest sum wins.
;Individual Race Point Sum
:Sum of race points (FIS/USSA/USCSA formula) for all racers used in scoring. Dummy points will be added for teams that do not have enough finishers. The dummy points will be the points that would be assigned if a racer finished with the dummy time for the race where the team did not have enough finishers. The lowest sum wins.
;No scoring
:Combined results are not calculated

== Regional and National Events ==
The process for scoring Regional and National events is very similar to regular divisional events. Read the instructions above (if you haven't already) before reading this section.

'''Note that the scoring system is currently limited to alpine events,''' so disregard everything on this page if you are looking for information about scoring other events.

There are some small changes for scoring Regional and National events:
# Information about which competitors and teams will be attending each Regional Championship and National Championship event must be sent to James (see below for contact information) in advance. Include the following information in an e-mail as soon as possible:
#* Region name (if not the national event)
#* Qualified Men's teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Qualified Ladies' teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Abbreviations for each team, including teams represented by an individual competitor. (If not provided, abbreviations will be assigned by using the team's abbreviations from within their home division. Any conflicts will be addressed manually.)
#* Individual Men and Ladies (include USCSA number and name. You may include "alternate" individuals if you are not sure who will be at the race. Competitors will not show up in the standings unless they show up at the race, but the results will be rejected unless all competitors are registered in the scoring system.)
# [[#Download_the_USCSA_member_csv|CSV files]] for populating the running order will be available AFTER the list of qualified teams and individuals has been processed by James. He will probably e-mail you when they are ready.
# When creating a race code for a regional event, the "conference" will be "Regional Championships", and the "division" will be the name of the region followed by the proper gender for the race
# When creating a race code for a national event, the "conference" will be "National Championships", and the "division" will be the proper gender for the race

For most regions - competitors should be assigned to either "A" or "Individual" [[#Competitor_Classes|classes]] for team member status or individual competitor status, respectively. However, there is nothing restricting the use of other classes, and all classes will be scored as they are described [[#Competitor_Classes|above]].

== Getting help or providing feedback ==
If you have problems, questions, praise, or suggestions contact the results team:
* Contact the USCSA results team ( results at uscsa dot com )
** About adding new races with the [http://www.uscsa.com/conferences-events/add-race Add Race] Page
** About errors in posted results or questions about how results are scored
** About suggestions for features or new result summaries
** About using SplitSecond
** About setting up USCSA races in SplitSecond
** About inserting USCSA Numbers and Team Abbreviations into SplitSecond races
** About formatting of results on the [http://www.uscsa.com/conferences/uscsa-results.html Results] Page
** About errors appearing on the Add Race or Results Pages

* Contact the National Office ( help at uscsa dot com )
** If you cannot find a USCSA number for a USCSA competitor
** If you cannot find a team abbreviation for a USCSA team
** You should also copy the results team

== How to setup your race to be on Live-Timing.org ==

==== Setup your race ====
Open SplitSecond and click on the "Live Timing" tab

[[Image:example1.png]]

Insert the following information

*Race Date
*Start Time
*State
*Ski Area Name
*Race Name
*Race Type

Now click on "Load Logos from Live-Timing" and select "USCSA-LiveTiming.gif" for the Location Logo and Race Logo.
Put in an easy to remember user name and password.

[[Image:example2.png]]

Now click on "Register Race"

[[Image:example3.png]]

Your race is now registered. Click on "Upload Competitors" to publish the racers on the Live-Timing website.
Remember to register both the Ladies' and Men's races.

==== Viewing you race on Live-Timing.org ====

[[Image:example4.png]]

==== Editing race infomation after you have registered ====

Click on the "tools for resorts" link near the top of the page.
[[Image:example5.png]]

Find your race and click on "Edit". You will need the username and password you created earlier.
[[Image:example6.png]]

USCSA Race setup with SplitSecond

2019-02-05T16:28:41Z

J: /* Getting help or providing feedback */

== Competitor Classes ==
For each race submission, every participating competitor must be assigned one of 5 classes. This class assignment will determine how scoring is handled for the competitor, and the competitor's team. The classes are:

;A
:For all A-team members. Only USCSA members may be marked with the "A" class, and a USCSA number must be provided with the submission. A-team members with the same team abbreviation make up that school's A-team. This team '''will''' be used to create team results. The team results '''will''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All A-team competitors '''will''' receive USCSA race points.
;B
:For all B-team members. Only USCSA members may be marked with the "B" class, and a USCSA number must be provided with the submission. B-team members with the same team abbreviation make up that school's B-team. This team '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is not eligible''' to score individually. All B-team competitors '''will''' receive USCSA race points.
;Individual
:For all individually qualified members. Only USCSA members may be marked with the "Individual" class, and a USCSA number must be provided with the submission. Individual entries '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All Individual competitors '''will''' receive USCSA race points.
;Unscored/Guest
:For all non-USCSA members, as well as USCSA competitors from divisions other than the division running the event. USCSA or non-USCSA members may be marked with the "Unscored/Guest" class. If the competitor is a USCSA member, then a USCSA number should be provided. Unscored/Guest entries '''will not''' be used to create team results. Each Unscored/Guest competitor '''is not eligible''' to score individually. Unscored/Guest competitors '''will''' receive USCSA race points if they are USCSA members and a USCSA number has been provided. Unscored/Guest competitors '''will not''' receive USCSA race points if a USCSA number has not been provided.
;AA
:For all AA-team members. This class '''should not be used''' by most divisions. Only USCSA members may be marked with the "AA" class, and a USCSA number must be provided with the submission. AA-team members with the same team abbreviation make up that school's AA-team. This team '''will''' be used to create team results for the race. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All AA-team competitors '''will''' receive USCSA race points.

{|style="border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0" border="1"
|+ USCSA scoring classes
! Class
! Times
! Team Result for Race
! Team Result in Divisional Standings
! Individual Result in Divisional Standings
! Receive USCSA Race Points
|-
! A
| Yes
| Yes
| Yes
| Yes
| Yes
|-
! B
| Yes
| No
| No
| No
| Yes
|-
! Individual
| Yes
| No
| No
| Yes
| Yes
|-
! Unscored/Guest
| Yes
| No
| No
| No
| If USCSA member
|-
! AA
| Yes
| Yes
| No
| Yes
| Yes
|}

== How to create a USCSA race in SplitSecond National/FIS ==
==== Download National/FIS ====
[http://www.splitsecond.com SplitSecond National/FIS]

==== Configure National/FIS for USCSA races ====
Fill in the header information as you normally would for a normal USSA race.
Check the following boxes at the bottom
*USCSA Event
*Show USCSA Class on Competitor tab instead of Class
*Show USCSA Number on Competitor tab instead of USSA/FIS Number

[[Image:race_setup.png]]

Select the Factors/Lists tab
Download a USCSA points list and the current USSA points list
*Select the current USSA points list

[[Image:race_setup_points_lists.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Fill in the racer's last name. Select the matching name from the box on the right.
[[Image:racer_registration.png]]

If data from both lists matched the following fields will be filled out correctly
*USSA number
*USCSA number
*Year of birth
*USSA points
*Team (This will be the school abbreviation not 'USA')
*USSA Class

*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. If a racer does not have a USCSA number, verify that you selected the correct USSA athlete. If you are sure that you have the correct athlete [[#Getting_help_or_providing_feedback|Contact the national office]] to resolve the discrepancy.

*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page - not the USSA race code.

[[Image:submit_race2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with National/FIS''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:natfis_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*USSA Number
*USCSA Number
*Bib
*etc...
[[Image:natfis_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:nafis_blockedit.png]]

== How to create a USCSA race in SplitSecond's Ski Club ==
==== Download Ski Club ====
[http://www.splitsecond.com SplitSecond Ski Club]

==== Configure Ski Club for USCSA races ====
Fill in the header information as you normally would for a normal race.
Check the following boxes at the top and bottom
*USCSA Event
*This race includes team scoring (using USCSA Team Scoring)
*Click on the button labeled "Download USCSA List"

[[Image:race_registration_sc.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Make separate race files for Ladies' and Men's racer (Otherwise the team scoring will include both men and women)
*Fill in the racer's last name. Ski Club will search the USCSA list for a matching name. Select the correct racer/team entry from the box on the right. This will fill in all the fields except for class.
*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. [[#Getting_help_or_providing_feedback|Contact the national office]] if a racer does not appear on the USCSA list.
[[Image:racer_registration_sc.png]]
*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration_sc2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race_sc.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page.
[[Image:submit_race_sc2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with Ski Club''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:skiclub_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*Member#
*Bib
*etc...
[[Image:skiclub_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:skiclub_blockedit.png]]

== How to lookup USCSA numbers ==
It is '''critically important''' that your race contains ''USCSA numbers'' for '''ALL''' USCSA members and proper ''team abbreviations'' for '''ALL''' USCSA members scored as class "A" or "B" competitors. The easiest way to find the USCSA numbers and team abbreviations is to look them up in SplitSecond using the USCSA competitor list '''(see the instructions above)'''.

'''If you cannot find the competitor in SplitSecond or you have errors for a particular competitor when submitting the results:'''
*Do '''not''' make up a USCSA number
*Do '''not''' put in some place holder value
*Do '''not''' change the competitor's class to "Guest" (unless they really are a guest)
*'''Do''' contact the national office - there is probably an issue with the competitor's registration that is causing them to not show up in the list.

If SplitSecond is not the right answer for you, there are other methods described below.

==== Individual racer lookup on uscsa.com ====
Use the competitor search function on [http://www.uscsa.com/uscsa-results this page]


==== Download the USCSA member csv ====
This is the same list that SplitSecond uses. If you have an updated list in SplitSecond, you won't find any additional information in here. This might be useful for people who want to generate running orders or other automated tasks.

[http://results.uscsa.com:8080/RaceNetData/CompetitorList/ Download CSV list]

== After submitting the race ==
An e-mail will be sent to the race organizer within a few minutes which will detail the status of scoring. If there are problems with the submission, a report detailing all the problems will be included. You may correct the errors and resubmit (see the section below). If there are no problems, then the e-mail will note that the submission was successful, and the results will be available on the [http://www.uscsa.com/conferences/uscsa-results.html Results Page]. If you don't receive an e-mail within an hour, get in touch with James (see [[#Getting_help_or_providing_feedback|this section]]), and note the race code.

=== Correcting Errors ===
Here are some common errors, and hints on how to fix them.

;Must supply USCSA number for all scored racers
:If a competitor is assigned any [[#Competitor_Classes|class]] besides Unscored/Guest, a USCSA number must be supplied. This is used to match up all the results for the season and across seasons.
;No such USCSA Competitor or wrong USCSA ID
:Check to make sure that the USCSA you supplied is correct for the racer. Maybe you missed a digit, or got some numbers out of order. It is also possible that the competitor recently registered and the scoring system has not received an updated competitor list yet.
;Competitor does not exist for this Division and Season.
:The USCSA number you entered is valid, but that competitor is not a member of this division. This could mean: a) that you mistyped the USCSA number and it matched someone else's USCSA number, in which case you should correct the number, b) the competitor is registered incorrectly, in which case you should [[#Getting_help_or_providing_feedback|contact James and the national office]] to correct the issue, c) the competitor is a guest from a different division, in which case you should change the competitor's class to Unscored/Guest, or d) you got your male/female race codes for the weekend backwards.
;Team abbreviation does not exist for this Division and Season
:The abbreviation used is not recognized. You must use the [[#How_to_lookup_USCSA_numbers|assigned abbreviation]]. If you don't like the assigned abbreviations, [[#Getting_help_or_providing_feedback|get in touch with James]] to change them.
;Incomplete submission. Fill all required fields and try again.
:Make sure the USCSA header (USCSA race code, race date, race type, description line 1, race admin's name, email and phone number) is filled out, and that there are results in the race you are submitting.
;Invalid race code format OR Race does not exist for that race code
:Use the race code that was assigned when you [[#How_to_create_a_USCSA_race_from_the_registration_website|created the race]].
;Results for this race have already been submitted.
:If you meant to make a change to results that you already posted, [[#Getting_help_or_providing_feedback|get in touch with James]] and let him know. If not, make sure you have your race codes straight.
;Malformed time.
:Assuming you are using SplitSecond, you should never get this error. [[#Getting_help_or_providing_feedback|Get in touch with James]] immediately if you do.

== Setting up combined scoring rules ==
In order for combined results (qualifications, rankings, divisional overall standings) to be calculated, your division must select scoring rules. For this season, send your selections to James Cialdea by e-mail (see [[#Getting_help_or_providing_feedback|this section]]). You may have different rules for the Men and Ladies - that is not a problem, just provide information for each and we will take care of the rest.

The available rules are described below. If you use a different rule, include that information in the e-mail. You may select one rule and up to three tie breakers for Individual and Team combined scoring. You do not need to select three tie breakers if your division does not have rules for three levels of ties.

In other words, fill in this grid:
* Conference Name:
* Division Name:
* Team Combined Rules
** Rule: (select one from Team Combined Rules)
** Tiebreaker 1: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Team Combined Rules, or leave blank)
* Individual Combined Rules
** Rule: (select one from Individual Combined Rules)
** Tiebreaker 1: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Individual Combined Rules, or leave blank)

Example:
<pre>
Conference Name: Rocky Mountain
Division Name: Rocky Mountain

Team Combined Rules
Rule: Team Finish Place Sum

Individual Combined Rules
Rule: World Cup Top 30
</pre>

=== Individual Combined Rules ===
For Individual Combined scoring, the following rules are available:
;Linear, top 30
:Points are assigned to the top 30 finishers, counting down linearly from 30. (1st = 30, 2nd = 29, ... , 29th = 2, 30th = 1, 31st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Linear, top 15
:Points are assigned to the top 15 finishers, counting down linearly from 15. (1st = 15, 2nd = 14, ... , 14th = 2, 15th = 1, 16st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;World Cup, top 30
:Points are assigned to the top 30 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "current system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Continental, top 15
:Points are assigned to the top 15 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "top 15 system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Race Points
:Sum of race points from FIS/USSA/USCSA formula, lowest score wins. Racers who do not participate in a race are counted as "DNS", and will take 990.00 points for that race. (Note: USCSA points are calculated and displayed in results for all USCSA-scored races regardless of whether this option is used.)
;No scoring
:Combined results are not calculated

=== Team Combined Rules ===
For Team Combined scoring, the following rules are available:
;Team Finish Place Sum
:Each team is assigned place points for each race equal to the team ranking at that race. The sum of finish places for all races is used for combined ranking. The lowest sum wins.
;Individual Finish Place Sum
:Sum of finish places for all racers using in scoring for all races. Dummy finish places will be applied for teams that do not have enough finishers, per USCSA scoring rules. The lowest sum wins.
;Individual Race Point Sum
:Sum of race points (FIS/USSA/USCSA formula) for all racers used in scoring. Dummy points will be added for teams that do not have enough finishers. The dummy points will be the points that would be assigned if a racer finished with the dummy time for the race where the team did not have enough finishers. The lowest sum wins.
;No scoring
:Combined results are not calculated

== Regional and National Events ==
The process for scoring Regional and National events is very similar to regular divisional events. Read the instructions above (if you haven't already) before reading this section.

'''Note that the scoring system is currently limited to alpine events,''' so disregard everything on this page if you are looking for information about scoring other events.

There are some small changes for scoring Regional and National events:
# Information about which competitors and teams will be attending each Regional Championship and National Championship event must be sent to James (see below for contact information) in advance. Include the following information in an e-mail as soon as possible:
#* Region name (if not the national event)
#* Qualified Men's teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Qualified Ladies' teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Abbreviations for each team, including teams represented by an individual competitor. (If not provided, abbreviations will be assigned by using the team's abbreviations from within their home division. Any conflicts will be addressed manually.)
#* Individual Men and Ladies (include USCSA number and name. You may include "alternate" individuals if you are not sure who will be at the race. Competitors will not show up in the standings unless they show up at the race, but the results will be rejected unless all competitors are registered in the scoring system.)
# [[#Download_the_USCSA_member_csv|CSV files]] for populating the running order will be available AFTER the list of qualified teams and individuals has been processed by James. He will probably e-mail you when they are ready.
# When creating a race code for a regional event, the "conference" will be "Regional Championships", and the "division" will be the name of the region followed by the proper gender for the race
# When creating a race code for a national event, the "conference" will be "National Championships", and the "division" will be the proper gender for the race

For most regions - competitors should be assigned to either "A" or "Individual" [[#Competitor_Classes|classes]] for team member status or individual competitor status, respectively. However, there is nothing restricting the use of other classes, and all classes will be scored as they are described [[#Competitor_Classes|above]].

== Getting help or providing feedback ==
If you have problems, questions, praise, or suggestions contact the results team:
* Contact James Cialdea ( results at uscsa dot com )
** About adding new races with the [http://www.uscsa.com/conferences-events/add-race Add Race] Page
** About errors in posted results or questions about how results are scored
** About suggestions for features or new result summaries
** About using SplitSecond
** About setting up USCSA races in SplitSecond
** About inserting USCSA Numbers and Team Abbreviations into SplitSecond races
** About formatting of results on the [http://www.uscsa.com/conferences/uscsa-results.html Results] Page
** About errors appearing on the Add Race or Results Pages
** You should also copy James

* Contact the National Office ( help at uscsa dot com )
** If you cannot find a USCSA number for a USCSA competitor
** If you cannot find a team abbreviation for a USCSA team
** You should also copy the results team

== How to setup your race to be on Live-Timing.org ==

==== Setup your race ====
Open SplitSecond and click on the "Live Timing" tab

[[Image:example1.png]]

Insert the following information

*Race Date
*Start Time
*State
*Ski Area Name
*Race Name
*Race Type

Now click on "Load Logos from Live-Timing" and select "USCSA-LiveTiming.gif" for the Location Logo and Race Logo.
Put in an easy to remember user name and password.

[[Image:example2.png]]

Now click on "Register Race"

[[Image:example3.png]]

Your race is now registered. Click on "Upload Competitors" to publish the racers on the Live-Timing website.
Remember to register both the Ladies' and Men's races.

==== Viewing you race on Live-Timing.org ====

[[Image:example4.png]]

==== Editing race infomation after you have registered ====

Click on the "tools for resorts" link near the top of the page.
[[Image:example5.png]]

Find your race and click on "Edit". You will need the username and password you created earlier.
[[Image:example6.png]]

USCSA Race setup with SplitSecond

2017-01-04T04:51:41Z

J: /* Regional and National Events */

== Competitor Classes ==
For each race submission, every participating competitor must be assigned one of 5 classes. This class assignment will determine how scoring is handled for the competitor, and the competitor's team. The classes are:

;A
:For all A-team members. Only USCSA members may be marked with the "A" class, and a USCSA number must be provided with the submission. A-team members with the same team abbreviation make up that school's A-team. This team '''will''' be used to create team results. The team results '''will''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All A-team competitors '''will''' receive USCSA race points.
;B
:For all B-team members. Only USCSA members may be marked with the "B" class, and a USCSA number must be provided with the submission. B-team members with the same team abbreviation make up that school's B-team. This team '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is not eligible''' to score individually. All B-team competitors '''will''' receive USCSA race points.
;Individual
:For all individually qualified members. Only USCSA members may be marked with the "Individual" class, and a USCSA number must be provided with the submission. Individual entries '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All Individual competitors '''will''' receive USCSA race points.
;Unscored/Guest
:For all non-USCSA members, as well as USCSA competitors from divisions other than the division running the event. USCSA or non-USCSA members may be marked with the "Unscored/Guest" class. If the competitor is a USCSA member, then a USCSA number should be provided. Unscored/Guest entries '''will not''' be used to create team results. Each Unscored/Guest competitor '''is not eligible''' to score individually. Unscored/Guest competitors '''will''' receive USCSA race points if they are USCSA members and a USCSA number has been provided. Unscored/Guest competitors '''will not''' receive USCSA race points if a USCSA number has not been provided.
;AA
:For all AA-team members. This class '''should not be used''' by most divisions. Only USCSA members may be marked with the "AA" class, and a USCSA number must be provided with the submission. AA-team members with the same team abbreviation make up that school's AA-team. This team '''will''' be used to create team results for the race. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All AA-team competitors '''will''' receive USCSA race points.

{|style="border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0" border="1"
|+ USCSA scoring classes
! Class
! Times
! Team Result for Race
! Team Result in Divisional Standings
! Individual Result in Divisional Standings
! Receive USCSA Race Points
|-
! A
| Yes
| Yes
| Yes
| Yes
| Yes
|-
! B
| Yes
| No
| No
| No
| Yes
|-
! Individual
| Yes
| No
| No
| Yes
| Yes
|-
! Unscored/Guest
| Yes
| No
| No
| No
| If USCSA member
|-
! AA
| Yes
| Yes
| No
| Yes
| Yes
|}

== How to create a USCSA race in SplitSecond National/FIS ==
==== Download National/FIS ====
[http://www.splitsecond.com SplitSecond National/FIS]

==== Configure National/FIS for USCSA races ====
Fill in the header information as you normally would for a normal USSA race.
Check the following boxes at the bottom
*USCSA Event
*Show USCSA Class on Competitor tab instead of Class
*Show USCSA Number on Competitor tab instead of USSA/FIS Number

[[Image:race_setup.png]]

Select the Factors/Lists tab
Download a USCSA points list and the current USSA points list
*Select the current USSA points list

[[Image:race_setup_points_lists.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Fill in the racer's last name. Select the matching name from the box on the right.
[[Image:racer_registration.png]]

If data from both lists matched the following fields will be filled out correctly
*USSA number
*USCSA number
*Year of birth
*USSA points
*Team (This will be the school abbreviation not 'USA')
*USSA Class

*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. If a racer does not have a USCSA number, verify that you selected the correct USSA athlete. If you are sure that you have the correct athlete [[#Getting_help_or_providing_feedback|Contact the national office]] to resolve the discrepancy.

*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page - not the USSA race code.

[[Image:submit_race2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with National/FIS''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:natfis_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*USSA Number
*USCSA Number
*Bib
*etc...
[[Image:natfis_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:nafis_blockedit.png]]

== How to create a USCSA race in SplitSecond's Ski Club ==
==== Download Ski Club ====
[http://www.splitsecond.com SplitSecond Ski Club]

==== Configure Ski Club for USCSA races ====
Fill in the header information as you normally would for a normal race.
Check the following boxes at the top and bottom
*USCSA Event
*This race includes team scoring (using USCSA Team Scoring)
*Click on the button labeled "Download USCSA List"

[[Image:race_registration_sc.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Make separate race files for Ladies' and Men's racer (Otherwise the team scoring will include both men and women)
*Fill in the racer's last name. Ski Club will search the USCSA list for a matching name. Select the correct racer/team entry from the box on the right. This will fill in all the fields except for class.
*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. [[#Getting_help_or_providing_feedback|Contact the national office]] if a racer does not appear on the USCSA list.
[[Image:racer_registration_sc.png]]
*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration_sc2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race_sc.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page.
[[Image:submit_race_sc2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with Ski Club''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:skiclub_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*Member#
*Bib
*etc...
[[Image:skiclub_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:skiclub_blockedit.png]]

== How to lookup USCSA numbers ==
It is '''critically important''' that your race contains ''USCSA numbers'' for '''ALL''' USCSA members and proper ''team abbreviations'' for '''ALL''' USCSA members scored as class "A" or "B" competitors. The easiest way to find the USCSA numbers and team abbreviations is to look them up in SplitSecond using the USCSA competitor list '''(see the instructions above)'''.

'''If you cannot find the competitor in SplitSecond or you have errors for a particular competitor when submitting the results:'''
*Do '''not''' make up a USCSA number
*Do '''not''' put in some place holder value
*Do '''not''' change the competitor's class to "Guest" (unless they really are a guest)
*'''Do''' contact the national office - there is probably an issue with the competitor's registration that is causing them to not show up in the list.

If SplitSecond is not the right answer for you, there are other methods described below.

==== Individual racer lookup on uscsa.com ====
Use the competitor search function on [http://www.uscsa.com/uscsa-results this page]


==== Download the USCSA member csv ====
This is the same list that SplitSecond uses. If you have an updated list in SplitSecond, you won't find any additional information in here. This might be useful for people who want to generate running orders or other automated tasks.

[http://results.uscsa.com:8080/RaceNetData/CompetitorList/ Download CSV list]

== After submitting the race ==
An e-mail will be sent to the race organizer within a few minutes which will detail the status of scoring. If there are problems with the submission, a report detailing all the problems will be included. You may correct the errors and resubmit (see the section below). If there are no problems, then the e-mail will note that the submission was successful, and the results will be available on the [http://www.uscsa.com/conferences/uscsa-results.html Results Page]. If you don't receive an e-mail within an hour, get in touch with James (see [[#Getting_help_or_providing_feedback|this section]]), and note the race code.

=== Correcting Errors ===
Here are some common errors, and hints on how to fix them.

;Must supply USCSA number for all scored racers
:If a competitor is assigned any [[#Competitor_Classes|class]] besides Unscored/Guest, a USCSA number must be supplied. This is used to match up all the results for the season and across seasons.
;No such USCSA Competitor or wrong USCSA ID
:Check to make sure that the USCSA you supplied is correct for the racer. Maybe you missed a digit, or got some numbers out of order. It is also possible that the competitor recently registered and the scoring system has not received an updated competitor list yet.
;Competitor does not exist for this Division and Season.
:The USCSA number you entered is valid, but that competitor is not a member of this division. This could mean: a) that you mistyped the USCSA number and it matched someone else's USCSA number, in which case you should correct the number, b) the competitor is registered incorrectly, in which case you should [[#Getting_help_or_providing_feedback|contact James and the national office]] to correct the issue, c) the competitor is a guest from a different division, in which case you should change the competitor's class to Unscored/Guest, or d) you got your male/female race codes for the weekend backwards.
;Team abbreviation does not exist for this Division and Season
:The abbreviation used is not recognized. You must use the [[#How_to_lookup_USCSA_numbers|assigned abbreviation]]. If you don't like the assigned abbreviations, [[#Getting_help_or_providing_feedback|get in touch with James]] to change them.
;Incomplete submission. Fill all required fields and try again.
:Make sure the USCSA header (USCSA race code, race date, race type, description line 1, race admin's name, email and phone number) is filled out, and that there are results in the race you are submitting.
;Invalid race code format OR Race does not exist for that race code
:Use the race code that was assigned when you [[#How_to_create_a_USCSA_race_from_the_registration_website|created the race]].
;Results for this race have already been submitted.
:If you meant to make a change to results that you already posted, [[#Getting_help_or_providing_feedback|get in touch with James]] and let him know. If not, make sure you have your race codes straight.
;Malformed time.
:Assuming you are using SplitSecond, you should never get this error. [[#Getting_help_or_providing_feedback|Get in touch with James]] immediately if you do.

== Setting up combined scoring rules ==
In order for combined results (qualifications, rankings, divisional overall standings) to be calculated, your division must select scoring rules. For this season, send your selections to James Cialdea by e-mail (see [[#Getting_help_or_providing_feedback|this section]]). You may have different rules for the Men and Ladies - that is not a problem, just provide information for each and we will take care of the rest.

The available rules are described below. If you use a different rule, include that information in the e-mail. You may select one rule and up to three tie breakers for Individual and Team combined scoring. You do not need to select three tie breakers if your division does not have rules for three levels of ties.

In other words, fill in this grid:
* Conference Name:
* Division Name:
* Team Combined Rules
** Rule: (select one from Team Combined Rules)
** Tiebreaker 1: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Team Combined Rules, or leave blank)
* Individual Combined Rules
** Rule: (select one from Individual Combined Rules)
** Tiebreaker 1: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Individual Combined Rules, or leave blank)

Example:
<pre>
Conference Name: Rocky Mountain
Division Name: Rocky Mountain

Team Combined Rules
Rule: Team Finish Place Sum

Individual Combined Rules
Rule: World Cup Top 30
</pre>

=== Individual Combined Rules ===
For Individual Combined scoring, the following rules are available:
;Linear, top 30
:Points are assigned to the top 30 finishers, counting down linearly from 30. (1st = 30, 2nd = 29, ... , 29th = 2, 30th = 1, 31st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Linear, top 15
:Points are assigned to the top 15 finishers, counting down linearly from 15. (1st = 15, 2nd = 14, ... , 14th = 2, 15th = 1, 16st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;World Cup, top 30
:Points are assigned to the top 30 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "current system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Continental, top 15
:Points are assigned to the top 15 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "top 15 system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Race Points
:Sum of race points from FIS/USSA/USCSA formula, lowest score wins. Racers who do not participate in a race are counted as "DNS", and will take 990.00 points for that race. (Note: USCSA points are calculated and displayed in results for all USCSA-scored races regardless of whether this option is used.)
;No scoring
:Combined results are not calculated

=== Team Combined Rules ===
For Team Combined scoring, the following rules are available:
;Team Finish Place Sum
:Each team is assigned place points for each race equal to the team ranking at that race. The sum of finish places for all races is used for combined ranking. The lowest sum wins.
;Individual Finish Place Sum
:Sum of finish places for all racers using in scoring for all races. Dummy finish places will be applied for teams that do not have enough finishers, per USCSA scoring rules. The lowest sum wins.
;Individual Race Point Sum
:Sum of race points (FIS/USSA/USCSA formula) for all racers used in scoring. Dummy points will be added for teams that do not have enough finishers. The dummy points will be the points that would be assigned if a racer finished with the dummy time for the race where the team did not have enough finishers. The lowest sum wins.
;No scoring
:Combined results are not calculated

== Regional and National Events ==
The process for scoring Regional and National events is very similar to regular divisional events. Read the instructions above (if you haven't already) before reading this section.

'''Note that the scoring system is currently limited to alpine events,''' so disregard everything on this page if you are looking for information about scoring other events.

There are some small changes for scoring Regional and National events:
# Information about which competitors and teams will be attending each Regional Championship and National Championship event must be sent to James (see below for contact information) in advance. Include the following information in an e-mail as soon as possible:
#* Region name (if not the national event)
#* Qualified Men's teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Qualified Ladies' teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Abbreviations for each team, including teams represented by an individual competitor. (If not provided, abbreviations will be assigned by using the team's abbreviations from within their home division. Any conflicts will be addressed manually.)
#* Individual Men and Ladies (include USCSA number and name. You may include "alternate" individuals if you are not sure who will be at the race. Competitors will not show up in the standings unless they show up at the race, but the results will be rejected unless all competitors are registered in the scoring system.)
# [[#Download_the_USCSA_member_csv|CSV files]] for populating the running order will be available AFTER the list of qualified teams and individuals has been processed by James. He will probably e-mail you when they are ready.
# When creating a race code for a regional event, the "conference" will be "Regional Championships", and the "division" will be the name of the region followed by the proper gender for the race
# When creating a race code for a national event, the "conference" will be "National Championships", and the "division" will be the proper gender for the race

For most regions - competitors should be assigned to either "A" or "Individual" [[#Competitor_Classes|classes]] for team member status or individual competitor status, respectively. However, there is nothing restricting the use of other classes, and all classes will be scored as they are described [[#Competitor_Classes|above]].

== Getting help or providing feedback ==
If you have problems, questions, praise, or suggestions:
* Contact James Cialdea ( j at jimbodude dot net OR jamescialdea at gmail dot com )
** About adding new races with the [http://www.uscsa.com/conferences-events/add-race Add Race] Page
** About errors in posted results or questions about how results are scored
** About suggestions for features or new result summaries

* Contact Eric Millbrandt ( emillbrandt at coldhaus dot com )
** About using SplitSecond
** About setting up USCSA races in SplitSecond
** About inserting USCSA Numbers and Team Abbreviations into SplitSecond races
** You should also copy James and Andy

* Contact Andy Rangen ( arangen at uscsa dot com )
** About formatting of results on the [http://www.uscsa.com/conferences/uscsa-results.html Results] Page
** About errors appearing on the Add Race or Results Pages
** You should also copy James

* Contact the National Office ( LauraSullivan at uscsa dot com )
** If you cannot find a USCSA number for a USCSA competitor
** If you cannot find a team abbreviation for a USCSA team
** You should also copy James and Andy

== How to setup your race to be on Live-Timing.org ==

==== Setup your race ====
Open SplitSecond and click on the "Live Timing" tab

[[Image:example1.png]]

Insert the following information

*Race Date
*Start Time
*State
*Ski Area Name
*Race Name
*Race Type

Now click on "Load Logos from Live-Timing" and select "USCSA-LiveTiming.gif" for the Location Logo and Race Logo.
Put in an easy to remember user name and password.

[[Image:example2.png]]

Now click on "Register Race"

[[Image:example3.png]]

Your race is now registered. Click on "Upload Competitors" to publish the racers on the Live-Timing website.
Remember to register both the Ladies' and Men's races.

==== Viewing you race on Live-Timing.org ====

[[Image:example4.png]]

==== Editing race infomation after you have registered ====

Click on the "tools for resorts" link near the top of the page.
[[Image:example5.png]]

Find your race and click on "Edit". You will need the username and password you created earlier.
[[Image:example6.png]]

USCSA Race setup with SplitSecond

2017-01-04T04:49:51Z

== Competitor Classes ==
For each race submission, every participating competitor must be assigned one of 5 classes. This class assignment will determine how scoring is handled for the competitor, and the competitor's team. The classes are:

;A
:For all A-team members. Only USCSA members may be marked with the "A" class, and a USCSA number must be provided with the submission. A-team members with the same team abbreviation make up that school's A-team. This team '''will''' be used to create team results. The team results '''will''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All A-team competitors '''will''' receive USCSA race points.
;B
:For all B-team members. Only USCSA members may be marked with the "B" class, and a USCSA number must be provided with the submission. B-team members with the same team abbreviation make up that school's B-team. This team '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is not eligible''' to score individually. All B-team competitors '''will''' receive USCSA race points.
;Individual
:For all individually qualified members. Only USCSA members may be marked with the "Individual" class, and a USCSA number must be provided with the submission. Individual entries '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All Individual competitors '''will''' receive USCSA race points.
;Unscored/Guest
:For all non-USCSA members, as well as USCSA competitors from divisions other than the division running the event. USCSA or non-USCSA members may be marked with the "Unscored/Guest" class. If the competitor is a USCSA member, then a USCSA number should be provided. Unscored/Guest entries '''will not''' be used to create team results. Each Unscored/Guest competitor '''is not eligible''' to score individually. Unscored/Guest competitors '''will''' receive USCSA race points if they are USCSA members and a USCSA number has been provided. Unscored/Guest competitors '''will not''' receive USCSA race points if a USCSA number has not been provided.
;AA
:For all AA-team members. This class '''should not be used''' by most divisions. Only USCSA members may be marked with the "AA" class, and a USCSA number must be provided with the submission. AA-team members with the same team abbreviation make up that school's AA-team. This team '''will''' be used to create team results for the race. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All AA-team competitors '''will''' receive USCSA race points.

{|style="border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0" border="1"
|+ USCSA scoring classes
! Class
! Times
! Team Result for Race
! Team Result in Divisional Standings
! Individual Result in Divisional Standings
! Receive USCSA Race Points
|-
! A
| Yes
| Yes
| Yes
| Yes
| Yes
|-
! B
| Yes
| No
| No
| No
| Yes
|-
! Individual
| Yes
| No
| No
| Yes
| Yes
|-
! Unscored/Guest
| Yes
| No
| No
| No
| If USCSA member
|-
! AA
| Yes
| Yes
| No
| Yes
| Yes
|}

== How to create a USCSA race in SplitSecond National/FIS ==
==== Download National/FIS ====
[http://www.splitsecond.com SplitSecond National/FIS]

==== Configure National/FIS for USCSA races ====
Fill in the header information as you normally would for a normal USSA race.
Check the following boxes at the bottom
*USCSA Event
*Show USCSA Class on Competitor tab instead of Class
*Show USCSA Number on Competitor tab instead of USSA/FIS Number

[[Image:race_setup.png]]

Select the Factors/Lists tab
Download a USCSA points list and the current USSA points list
*Select the current USSA points list

[[Image:race_setup_points_lists.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Fill in the racer's last name. Select the matching name from the box on the right.
[[Image:racer_registration.png]]

If data from both lists matched the following fields will be filled out correctly
*USSA number
*USCSA number
*Year of birth
*USSA points
*Team (This will be the school abbreviation not 'USA')
*USSA Class

*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. If a racer does not have a USCSA number, verify that you selected the correct USSA athlete. If you are sure that you have the correct athlete [[#Getting_help_or_providing_feedback|Contact the national office]] to resolve the discrepancy.

*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page - not the USSA race code.

[[Image:submit_race2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with National/FIS''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:natfis_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*USSA Number
*USCSA Number
*Bib
*etc...
[[Image:natfis_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:nafis_blockedit.png]]

== How to create a USCSA race in SplitSecond's Ski Club ==
==== Download Ski Club ====
[http://www.splitsecond.com SplitSecond Ski Club]

==== Configure Ski Club for USCSA races ====
Fill in the header information as you normally would for a normal race.
Check the following boxes at the top and bottom
*USCSA Event
*This race includes team scoring (using USCSA Team Scoring)
*Click on the button labeled "Download USCSA List"

[[Image:race_registration_sc.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Make separate race files for Ladies' and Men's racer (Otherwise the team scoring will include both men and women)
*Fill in the racer's last name. Ski Club will search the USCSA list for a matching name. Select the correct racer/team entry from the box on the right. This will fill in all the fields except for class.
*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. [[#Getting_help_or_providing_feedback|Contact the national office]] if a racer does not appear on the USCSA list.
[[Image:racer_registration_sc.png]]
*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration_sc2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race_sc.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page.
[[Image:submit_race_sc2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with Ski Club''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:skiclub_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*Member#
*Bib
*etc...
[[Image:skiclub_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:skiclub_blockedit.png]]

== How to lookup USCSA numbers ==
It is '''critically important''' that your race contains ''USCSA numbers'' for '''ALL''' USCSA members and proper ''team abbreviations'' for '''ALL''' USCSA members scored as class "A" or "B" competitors. The easiest way to find the USCSA numbers and team abbreviations is to look them up in SplitSecond using the USCSA competitor list '''(see the instructions above)'''.

'''If you cannot find the competitor in SplitSecond or you have errors for a particular competitor when submitting the results:'''
*Do '''not''' make up a USCSA number
*Do '''not''' put in some place holder value
*Do '''not''' change the competitor's class to "Guest" (unless they really are a guest)
*'''Do''' contact the national office - there is probably an issue with the competitor's registration that is causing them to not show up in the list.

If SplitSecond is not the right answer for you, there are other methods described below.

==== Individual racer lookup on uscsa.com ====
Use the competitor search function on [http://www.uscsa.com/uscsa-results this page]


==== Download the USCSA member csv ====
This is the same list that SplitSecond uses. If you have an updated list in SplitSecond, you won't find any additional information in here. This might be useful for people who want to generate running orders or other automated tasks.

[http://results.uscsa.com:8080/RaceNetData/CompetitorList/ Download CSV list]

== After submitting the race ==
An e-mail will be sent to the race organizer within a few minutes which will detail the status of scoring. If there are problems with the submission, a report detailing all the problems will be included. You may correct the errors and resubmit (see the section below). If there are no problems, then the e-mail will note that the submission was successful, and the results will be available on the [http://www.uscsa.com/conferences/uscsa-results.html Results Page]. If you don't receive an e-mail within an hour, get in touch with James (see [[#Getting_help_or_providing_feedback|this section]]), and note the race code.

=== Correcting Errors ===
Here are some common errors, and hints on how to fix them.

;Must supply USCSA number for all scored racers
:If a competitor is assigned any [[#Competitor_Classes|class]] besides Unscored/Guest, a USCSA number must be supplied. This is used to match up all the results for the season and across seasons.
;No such USCSA Competitor or wrong USCSA ID
:Check to make sure that the USCSA you supplied is correct for the racer. Maybe you missed a digit, or got some numbers out of order. It is also possible that the competitor recently registered and the scoring system has not received an updated competitor list yet.
;Competitor does not exist for this Division and Season.
:The USCSA number you entered is valid, but that competitor is not a member of this division. This could mean: a) that you mistyped the USCSA number and it matched someone else's USCSA number, in which case you should correct the number, b) the competitor is registered incorrectly, in which case you should [[#Getting_help_or_providing_feedback|contact James and the national office]] to correct the issue, c) the competitor is a guest from a different division, in which case you should change the competitor's class to Unscored/Guest, or d) you got your male/female race codes for the weekend backwards.
;Team abbreviation does not exist for this Division and Season
:The abbreviation used is not recognized. You must use the [[#How_to_lookup_USCSA_numbers|assigned abbreviation]]. If you don't like the assigned abbreviations, [[#Getting_help_or_providing_feedback|get in touch with James]] to change them.
;Incomplete submission. Fill all required fields and try again.
:Make sure the USCSA header (USCSA race code, race date, race type, description line 1, race admin's name, email and phone number) is filled out, and that there are results in the race you are submitting.
;Invalid race code format OR Race does not exist for that race code
:Use the race code that was assigned when you [[#How_to_create_a_USCSA_race_from_the_registration_website|created the race]].
;Results for this race have already been submitted.
:If you meant to make a change to results that you already posted, [[#Getting_help_or_providing_feedback|get in touch with James]] and let him know. If not, make sure you have your race codes straight.
;Malformed time.
:Assuming you are using SplitSecond, you should never get this error. [[#Getting_help_or_providing_feedback|Get in touch with James]] immediately if you do.

== Setting up combined scoring rules ==
In order for combined results (qualifications, rankings, divisional overall standings) to be calculated, your division must select scoring rules. For this season, send your selections to James Cialdea by e-mail (see [[#Getting_help_or_providing_feedback|this section]]). You may have different rules for the Men and Ladies - that is not a problem, just provide information for each and we will take care of the rest.

The available rules are described below. If you use a different rule, include that information in the e-mail. You may select one rule and up to three tie breakers for Individual and Team combined scoring. You do not need to select three tie breakers if your division does not have rules for three levels of ties.

In other words, fill in this grid:
* Conference Name:
* Division Name:
* Team Combined Rules
** Rule: (select one from Team Combined Rules)
** Tiebreaker 1: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Team Combined Rules, or leave blank)
* Individual Combined Rules
** Rule: (select one from Individual Combined Rules)
** Tiebreaker 1: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Individual Combined Rules, or leave blank)

Example:
<pre>
Conference Name: Rocky Mountain
Division Name: Rocky Mountain

Team Combined Rules
Rule: Team Finish Place Sum

Individual Combined Rules
Rule: World Cup Top 30
</pre>

=== Individual Combined Rules ===
For Individual Combined scoring, the following rules are available:
;Linear, top 30
:Points are assigned to the top 30 finishers, counting down linearly from 30. (1st = 30, 2nd = 29, ... , 29th = 2, 30th = 1, 31st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Linear, top 15
:Points are assigned to the top 15 finishers, counting down linearly from 15. (1st = 15, 2nd = 14, ... , 14th = 2, 15th = 1, 16st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;World Cup, top 30
:Points are assigned to the top 30 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "current system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Continental, top 15
:Points are assigned to the top 15 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "top 15 system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Race Points
:Sum of race points from FIS/USSA/USCSA formula, lowest score wins. Racers who do not participate in a race are counted as "DNS", and will take 990.00 points for that race. (Note: USCSA points are calculated and displayed in results for all USCSA-scored races regardless of whether this option is used.)
;No scoring
:Combined results are not calculated

=== Team Combined Rules ===
For Team Combined scoring, the following rules are available:
;Team Finish Place Sum
:Each team is assigned place points for each race equal to the team ranking at that race. The sum of finish places for all races is used for combined ranking. The lowest sum wins.
;Individual Finish Place Sum
:Sum of finish places for all racers using in scoring for all races. Dummy finish places will be applied for teams that do not have enough finishers, per USCSA scoring rules. The lowest sum wins.
;Individual Race Point Sum
:Sum of race points (FIS/USSA/USCSA formula) for all racers used in scoring. Dummy points will be added for teams that do not have enough finishers. The dummy points will be the points that would be assigned if a racer finished with the dummy time for the race where the team did not have enough finishers. The lowest sum wins.
;No scoring
:Combined results are not calculated

== Regional and National Events ==
The process for scoring Regional and National events is very similar to regular divisional events. Read the instructions above (if you haven't already) before reading this section.

'''Note that the scoring system is currently limited to alpine events,''' so disregard everything on this page if you are looking for information about scoring other events.

There are some small changes for scoring Regional and National events:
# Information about which competitors and teams will be attending each Regional Championship and National Championship event must be sent to James (see below for contact information) in advance. Include the following information in an e-mail as soon as possible:
#* Region name (if not the national event)
#* Qualified Men's teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Qualified Ladies' teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Abbreviations for each team, including teams represented by an individual competitor. (If not provided, abbreviations will be assigned by using the team's abbreviations from within their home division. Any conflicts will be addressed manually.)
#* Individual Men and Ladies (include USCSA number and name. You may include "alternate" individuals if you are not sure who will be at the race. Competitors will not show up in the standings unless they show up at the race, but the results will be rejected unless all competitors are registered in the scoring system.)
# [[#Download_the_USCSA_member_csv|CSV files]] for populating the running order will be available AFTER the list of qualified teams and individuals has been processed by James. He will probably e-mail you when they are ready.
# When [[#How_to_create_a_USCSA_race_from_the_registration_website|creating a race code]] for a regional event, the "conference" will be "Regional Championships", and the "division" will be the name of the region followed by the proper gender for the race
# When [[#How_to_create_a_USCSA_race_from_the_registration_website|creating a race code]] for a national event, the "conference" will be "National Championships", and the "division" will be the proper gender for the race

For most regions - competitors should be assigned to either "A" or "Individual" [[#Competitor_Classes|classes]] for team member status or individual competitor status, respectively. However, there is nothing restricting the use of other classes, and all classes will be scored as they are described [[#Competitor_Classes|above]].

== Getting help or providing feedback ==
If you have problems, questions, praise, or suggestions:
* Contact James Cialdea ( j at jimbodude dot net OR jamescialdea at gmail dot com )
** About adding new races with the [http://www.uscsa.com/conferences-events/add-race Add Race] Page
** About errors in posted results or questions about how results are scored
** About suggestions for features or new result summaries

* Contact Eric Millbrandt ( emillbrandt at coldhaus dot com )
** About using SplitSecond
** About setting up USCSA races in SplitSecond
** About inserting USCSA Numbers and Team Abbreviations into SplitSecond races
** You should also copy James and Andy

* Contact Andy Rangen ( arangen at uscsa dot com )
** About formatting of results on the [http://www.uscsa.com/conferences/uscsa-results.html Results] Page
** About errors appearing on the Add Race or Results Pages
** You should also copy James

* Contact the National Office ( LauraSullivan at uscsa dot com )
** If you cannot find a USCSA number for a USCSA competitor
** If you cannot find a team abbreviation for a USCSA team
** You should also copy James and Andy

== How to setup your race to be on Live-Timing.org ==

==== Setup your race ====
Open SplitSecond and click on the "Live Timing" tab

[[Image:example1.png]]

Insert the following information

*Race Date
*Start Time
*State
*Ski Area Name
*Race Name
*Race Type

Now click on "Load Logos from Live-Timing" and select "USCSA-LiveTiming.gif" for the Location Logo and Race Logo.
Put in an easy to remember user name and password.

[[Image:example2.png]]

Now click on "Register Race"

[[Image:example3.png]]

Your race is now registered. Click on "Upload Competitors" to publish the racers on the Live-Timing website.
Remember to register both the Ladies' and Men's races.

==== Viewing you race on Live-Timing.org ====

[[Image:example4.png]]

==== Editing race infomation after you have registered ====

Click on the "tools for resorts" link near the top of the page.
[[Image:example5.png]]

Find your race and click on "Edit". You will need the username and password you created earlier.
[[Image:example6.png]]

USCSA Race setup with SplitSecond

2016-01-23T18:40:48Z

== How to create a USCSA race from the registration website ==
In order for scoring to occur, the results of your race must be associated with a race code provided by USCSA's scoring system.
==== Multi-division Races ====
'''If your race is going contribute to the season results of multiple divisions''' - [[#Getting_help_or_providing_feedback|contact James]] to create a special multi-divisional race code for you.

'''If not''' (usually the case) - follow the instructions for the race registration website, below.

==== Race Registration Website ====
*Go to the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page
*Fill in '''ALL''' information (Use an easily distinguishable race name)
*Select "Add Race"
*The race code will be emailed to you. Use this code when submitting the race to USCSA (later in the process)
[[Image:web_registration.png]]

==== I Need to Make a Change to an Existing Race Code ====
The following values will be updated with whatever you set in SplitSecond, so you don't have to do anything in advance:
* Race administrator name / e-mail / phone
* Race date
* Race Discipline (SL/GS)

For anything else, [[#Getting_help_or_providing_feedback|Contact James]].

==== I Forgot My Race Code... ====
[[#Getting_help_or_providing_feedback|Contact James]], he can find it for you.

== Competitor Classes ==
For each race submission, every participating competitor must be assigned one of 5 classes. This class assignment will determine how scoring is handled for the competitor, and the competitor's team. The classes are:

;A
:For all A-team members. Only USCSA members may be marked with the "A" class, and a USCSA number must be provided with the submission. A-team members with the same team abbreviation make up that school's A-team. This team '''will''' be used to create team results. The team results '''will''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All A-team competitors '''will''' receive USCSA race points.
;B
:For all B-team members. Only USCSA members may be marked with the "B" class, and a USCSA number must be provided with the submission. B-team members with the same team abbreviation make up that school's B-team. This team '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is not eligible''' to score individually. All B-team competitors '''will''' receive USCSA race points.
;Individual
:For all individually qualified members. Only USCSA members may be marked with the "Individual" class, and a USCSA number must be provided with the submission. Individual entries '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All Individual competitors '''will''' receive USCSA race points.
;Unscored/Guest
:For all non-USCSA members, as well as USCSA competitors from divisions other than the division running the event. USCSA or non-USCSA members may be marked with the "Unscored/Guest" class. If the competitor is a USCSA member, then a USCSA number should be provided. Unscored/Guest entries '''will not''' be used to create team results. Each Unscored/Guest competitor '''is not eligible''' to score individually. Unscored/Guest competitors '''will''' receive USCSA race points if they are USCSA members and a USCSA number has been provided. Unscored/Guest competitors '''will not''' receive USCSA race points if a USCSA number has not been provided.
;AA
:For all AA-team members. This class '''should not be used''' by most divisions. Only USCSA members may be marked with the "AA" class, and a USCSA number must be provided with the submission. AA-team members with the same team abbreviation make up that school's AA-team. This team '''will''' be used to create team results for the race. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All AA-team competitors '''will''' receive USCSA race points.

{|style="border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0" border="1"
|+ USCSA scoring classes
! Class
! Times
! Team Result for Race
! Team Result in Divisional Standings
! Individual Result in Divisional Standings
! Receive USCSA Race Points
|-
! A
| Yes
| Yes
| Yes
| Yes
| Yes
|-
! B
| Yes
| No
| No
| No
| Yes
|-
! Individual
| Yes
| No
| No
| Yes
| Yes
|-
! Unscored/Guest
| Yes
| No
| No
| No
| If USCSA member
|-
! AA
| Yes
| Yes
| No
| Yes
| Yes
|}

== How to create a USCSA race in SplitSecond National/FIS ==
==== Download National/FIS ====
[http://www.splitsecond.com SplitSecond National/FIS]

==== Configure National/FIS for USCSA races ====
Fill in the header information as you normally would for a normal USSA race.
Check the following boxes at the bottom
*USCSA Event
*Show USCSA Class on Competitor tab instead of Class
*Show USCSA Number on Competitor tab instead of USSA/FIS Number

[[Image:race_setup.png]]

Select the Factors/Lists tab
Download a USCSA points list and the current USSA points list
*Select the current USSA points list

[[Image:race_setup_points_lists.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Fill in the racer's last name. Select the matching name from the box on the right.
[[Image:racer_registration.png]]

If data from both lists matched the following fields will be filled out correctly
*USSA number
*USCSA number
*Year of birth
*USSA points
*Team (This will be the school abbreviation not 'USA')
*USSA Class

*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. If a racer does not have a USCSA number, verify that you selected the correct USSA athlete. If you are sure that you have the correct athlete [[#Getting_help_or_providing_feedback|Contact the national office]] to resolve the discrepancy.

*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page - not the USSA race code.

[[Image:submit_race2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with National/FIS''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:natfis_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*USSA Number
*USCSA Number
*Bib
*etc...
[[Image:natfis_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:nafis_blockedit.png]]

== How to create a USCSA race in SplitSecond's Ski Club ==
==== Download Ski Club ====
[http://www.splitsecond.com SplitSecond Ski Club]

==== Configure Ski Club for USCSA races ====
Fill in the header information as you normally would for a normal race.
Check the following boxes at the top and bottom
*USCSA Event
*This race includes team scoring (using USCSA Team Scoring)
*Click on the button labeled "Download USCSA List"

[[Image:race_registration_sc.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Make separate race files for Ladies' and Men's racer (Otherwise the team scoring will include both men and women)
*Fill in the racer's last name. Ski Club will search the USCSA list for a matching name. Select the correct racer/team entry from the box on the right. This will fill in all the fields except for class.
*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. [[#Getting_help_or_providing_feedback|Contact the national office]] if a racer does not appear on the USCSA list.
[[Image:racer_registration_sc.png]]
*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration_sc2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race_sc.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page.
[[Image:submit_race_sc2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with Ski Club''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:skiclub_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*Member#
*Bib
*etc...
[[Image:skiclub_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:skiclub_blockedit.png]]

== How to lookup USCSA numbers ==
It is '''critically important''' that your race contains ''USCSA numbers'' for '''ALL''' USCSA members and proper ''team abbreviations'' for '''ALL''' USCSA members scored as class "A" or "B" competitors. The easiest way to find the USCSA numbers and team abbreviations is to look them up in SplitSecond using the USCSA competitor list '''(see the instructions above)'''.

'''If you cannot find the competitor in SplitSecond or you have errors for a particular competitor when submitting the results:'''
*Do '''not''' make up a USCSA number
*Do '''not''' put in some place holder value
*Do '''not''' change the competitor's class to "Guest" (unless they really are a guest)
*'''Do''' contact the national office - there is probably an issue with the competitor's registration that is causing them to not show up in the list.

If SplitSecond is not the right answer for you, there are other methods described below.

==== Individual racer lookup on uscsa.com ====
Use the competitor search function on [http://www.uscsa.com/uscsa-results this page]


==== Download the USCSA member csv ====
This is the same list that SplitSecond uses. If you have an updated list in SplitSecond, you won't find any additional information in here. This might be useful for people who want to generate running orders or other automated tasks.

[http://results.uscsa.com:8080/RaceNetData/CompetitorList/ Download CSV list]

== After submitting the race ==
An e-mail will be sent to the race organizer within a few minutes which will detail the status of scoring. If there are problems with the submission, a report detailing all the problems will be included. You may correct the errors and resubmit (see the section below). If there are no problems, then the e-mail will note that the submission was successful, and the results will be available on the [http://www.uscsa.com/conferences/uscsa-results.html Results Page]. If you don't receive an e-mail within an hour, get in touch with James (see [[#Getting_help_or_providing_feedback|this section]]), and note the race code.

=== Correcting Errors ===
Here are some common errors, and hints on how to fix them.

;Must supply USCSA number for all scored racers
:If a competitor is assigned any [[#Competitor_Classes|class]] besides Unscored/Guest, a USCSA number must be supplied. This is used to match up all the results for the season and across seasons.
;No such USCSA Competitor or wrong USCSA ID
:Check to make sure that the USCSA you supplied is correct for the racer. Maybe you missed a digit, or got some numbers out of order. It is also possible that the competitor recently registered and the scoring system has not received an updated competitor list yet.
;Competitor does not exist for this Division and Season.
:The USCSA number you entered is valid, but that competitor is not a member of this division. This could mean: a) that you mistyped the USCSA number and it matched someone else's USCSA number, in which case you should correct the number, b) the competitor is registered incorrectly, in which case you should [[#Getting_help_or_providing_feedback|contact James and the national office]] to correct the issue, c) the competitor is a guest from a different division, in which case you should change the competitor's class to Unscored/Guest, or d) you got your male/female race codes for the weekend backwards.
;Team abbreviation does not exist for this Division and Season
:The abbreviation used is not recognized. You must use the [[#How_to_lookup_USCSA_numbers|assigned abbreviation]]. If you don't like the assigned abbreviations, [[#Getting_help_or_providing_feedback|get in touch with James]] to change them.
;Incomplete submission. Fill all required fields and try again.
:Make sure the USCSA header (USCSA race code, race date, race type, description line 1, race admin's name, email and phone number) is filled out, and that there are results in the race you are submitting.
;Invalid race code format OR Race does not exist for that race code
:Use the race code that was assigned when you [[#How_to_create_a_USCSA_race_from_the_registration_website|created the race]].
;Results for this race have already been submitted.
:If you meant to make a change to results that you already posted, [[#Getting_help_or_providing_feedback|get in touch with James]] and let him know. If not, make sure you have your race codes straight.
;Malformed time.
:Assuming you are using SplitSecond, you should never get this error. [[#Getting_help_or_providing_feedback|Get in touch with James]] immediately if you do.

== Setting up combined scoring rules ==
In order for combined results (qualifications, rankings, divisional overall standings) to be calculated, your division must select scoring rules. For this season, send your selections to James Cialdea by e-mail (see [[#Getting_help_or_providing_feedback|this section]]). You may have different rules for the Men and Ladies - that is not a problem, just provide information for each and we will take care of the rest.

The available rules are described below. If you use a different rule, include that information in the e-mail. You may select one rule and up to three tie breakers for Individual and Team combined scoring. You do not need to select three tie breakers if your division does not have rules for three levels of ties.

In other words, fill in this grid:
* Conference Name:
* Division Name:
* Team Combined Rules
** Rule: (select one from Team Combined Rules)
** Tiebreaker 1: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Team Combined Rules, or leave blank)
* Individual Combined Rules
** Rule: (select one from Individual Combined Rules)
** Tiebreaker 1: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Individual Combined Rules, or leave blank)

Example:
<pre>
Conference Name: Rocky Mountain
Division Name: Rocky Mountain

Team Combined Rules
Rule: Team Finish Place Sum

Individual Combined Rules
Rule: World Cup Top 30
</pre>

=== Individual Combined Rules ===
For Individual Combined scoring, the following rules are available:
;Linear, top 30
:Points are assigned to the top 30 finishers, counting down linearly from 30. (1st = 30, 2nd = 29, ... , 29th = 2, 30th = 1, 31st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Linear, top 15
:Points are assigned to the top 15 finishers, counting down linearly from 15. (1st = 15, 2nd = 14, ... , 14th = 2, 15th = 1, 16st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;World Cup, top 30
:Points are assigned to the top 30 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "current system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Continental, top 15
:Points are assigned to the top 15 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "top 15 system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Race Points
:Sum of race points from FIS/USSA/USCSA formula, lowest score wins. Racers who do not participate in a race are counted as "DNS", and will take 990.00 points for that race. (Note: USCSA points are calculated and displayed in results for all USCSA-scored races regardless of whether this option is used.)
;No scoring
:Combined results are not calculated

=== Team Combined Rules ===
For Team Combined scoring, the following rules are available:
;Team Finish Place Sum
:Each team is assigned place points for each race equal to the team ranking at that race. The sum of finish places for all races is used for combined ranking. The lowest sum wins.
;Individual Finish Place Sum
:Sum of finish places for all racers using in scoring for all races. Dummy finish places will be applied for teams that do not have enough finishers, per USCSA scoring rules. The lowest sum wins.
;Individual Race Point Sum
:Sum of race points (FIS/USSA/USCSA formula) for all racers used in scoring. Dummy points will be added for teams that do not have enough finishers. The dummy points will be the points that would be assigned if a racer finished with the dummy time for the race where the team did not have enough finishers. The lowest sum wins.
;No scoring
:Combined results are not calculated

== Regional and National Events ==
The process for scoring Regional and National events is very similar to regular divisional events. Read the instructions above (if you haven't already) before reading this section.

'''Note that the scoring system is currently limited to alpine events,''' so disregard everything on this page if you are looking for information about scoring other events.

There are some small changes for scoring Regional and National events:
# Information about which competitors and teams will be attending each Regional Championship and National Championship event must be sent to James (see below for contact information) in advance. Include the following information in an e-mail as soon as possible:
#* Region name (if not the national event)
#* Qualified Men's teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Qualified Ladies' teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Abbreviations for each team, including teams represented by an individual competitor. (If not provided, abbreviations will be assigned by using the team's abbreviations from within their home division. Any conflicts will be addressed manually.)
#* Individual Men and Ladies (include USCSA number and name. You may include "alternate" individuals if you are not sure who will be at the race. Competitors will not show up in the standings unless they show up at the race, but the results will be rejected unless all competitors are registered in the scoring system.)
# [[#Download_the_USCSA_member_csv|CSV files]] for populating the running order will be available AFTER the list of qualified teams and individuals has been processed by James. He will probably e-mail you when they are ready.
# When [[#How_to_create_a_USCSA_race_from_the_registration_website|creating a race code]] for a regional event, the "conference" will be "Regional Championships", and the "division" will be the name of the region followed by the proper gender for the race
# When [[#How_to_create_a_USCSA_race_from_the_registration_website|creating a race code]] for a national event, the "conference" will be "National Championships", and the "division" will be the proper gender for the race

For most regions - competitors should be assigned to either "A" or "Individual" [[#Competitor_Classes|classes]] for team member status or individual competitor status, respectively. However, there is nothing restricting the use of other classes, and all classes will be scored as they are described [[#Competitor_Classes|above]].

== Getting help or providing feedback ==
If you have problems, questions, praise, or suggestions:
* Contact James Cialdea ( j at jimbodude dot net OR jamescialdea at gmail dot com )
** About adding new races with the [http://www.uscsa.com/conferences-events/add-race Add Race] Page
** About errors in posted results or questions about how results are scored
** About suggestions for features or new result summaries

* Contact Eric Millbrandt ( emillbrandt at coldhaus dot com )
** About using SplitSecond
** About setting up USCSA races in SplitSecond
** About inserting USCSA Numbers and Team Abbreviations into SplitSecond races
** You should also copy James and Andy

* Contact Andy Rangen ( arangen at uscsa dot com )
** About formatting of results on the [http://www.uscsa.com/conferences/uscsa-results.html Results] Page
** About errors appearing on the Add Race or Results Pages
** You should also copy James

* Contact the National Office ( LauraSullivan at uscsa dot com )
** If you cannot find a USCSA number for a USCSA competitor
** If you cannot find a team abbreviation for a USCSA team
** You should also copy James and Andy

== How to setup your race to be on Live-Timing.org ==

==== Setup your race ====
Open SplitSecond and click on the "Live Timing" tab

[[Image:example1.png]]

Insert the following information

*Race Date
*Start Time
*State
*Ski Area Name
*Race Name
*Race Type

Now click on "Load Logos from Live-Timing" and select "USCSA-LiveTiming.gif" for the Location Logo and Race Logo.
Put in an easy to remember user name and password.

[[Image:example2.png]]

Now click on "Register Race"

[[Image:example3.png]]

Your race is now registered. Click on "Upload Competitors" to publish the racers on the Live-Timing website.
Remember to register both the Ladies' and Men's races.

==== Viewing you race on Live-Timing.org ====

[[Image:example4.png]]

==== Editing race infomation after you have registered ====

Click on the "tools for resorts" link near the top of the page.
[[Image:example5.png]]

Find your race and click on "Edit". You will need the username and password you created earlier.
[[Image:example6.png]]

USCSA Race setup with SplitSecond

2015-01-28T04:18:10Z

== Setting up combined scoring rules ==
In order for combined results (qualifications, rankings, divisional overall standings) to be calculated, your division must select scoring rules. For this season, send your selections to James Cialdea by e-mail (see [[#Getting_help_or_providing_feedback|this section]]). You may have different rules for the Men and Ladies - that is not a problem, just provide information for each and we will take care of the rest.

The available rules are described below. If you use a different rule, include that information in the e-mail. You may select one rule and up to three tie breakers for Individual and Team combined scoring. You do not need to select three tie breakers if your division does not have rules for three levels of ties.

In other words, fill in this grid:
* Conference Name:
* Division Name:
* Team Combined Rules
** Rule: (select one from Team Combined Rules)
** Tiebreaker 1: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Team Combined Rules, or leave blank)
* Individual Combined Rules
** Rule: (select one from Individual Combined Rules)
** Tiebreaker 1: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Individual Combined Rules, or leave blank)

Example:
<pre>
Conference Name: Rocky Mountain
Division Name: Rocky Mountain

Team Combined Rules
Rule: Team Finish Place Sum

Individual Combined Rules
Rule: World Cup Top 30
</pre>

=== Individual Combined Rules ===
For Individual Combined scoring, the following rules are available:
;Linear, top 30
:Points are assigned to the top 30 finishers, counting down linearly from 30. (1st = 30, 2nd = 29, ... , 29th = 2, 30th = 1, 31st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Linear, top 15
:Points are assigned to the top 15 finishers, counting down linearly from 15. (1st = 15, 2nd = 14, ... , 14th = 2, 15th = 1, 16st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;World Cup, top 30
:Points are assigned to the top 30 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "current system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Continental, top 15
:Points are assigned to the top 15 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "top 15 system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Race Points
:Sum of race points from FIS/USSA/USCSA formula, lowest score wins. Racers who do not participate in a race are counted as "DNS", and will take 990.00 points for that race. (Note: USCSA points are calculated and displayed in results for all USCSA-scored races regardless of whether this option is used.)
;No scoring
:Combined results are not calculated

=== Team Combined Rules ===
For Team Combined scoring, the following rules are available:
;Team Finish Place Sum
:Each team is assigned place points for each race equal to the team ranking at that race. The sum of finish places for all races is used for combined ranking. The lowest sum wins.
;Individual Finish Place Sum
:Sum of finish places for all racers using in scoring for all races. Dummy finish places will be applied for teams that do not have enough finishers, per USCSA scoring rules. The lowest sum wins.
;Individual Race Point Sum
:Sum of race points (FIS/USSA/USCSA formula) for all racers used in scoring. Dummy points will be added for teams that do not have enough finishers. The dummy points will be the points that would be assigned if a racer finished with the dummy time for the race where the team did not have enough finishers. The lowest sum wins.
;No scoring
:Combined results are not calculated

== How to create a USCSA race from the registration website ==
In order for scoring to occur, the results of your race must be associated with a race code provided by USCSA's scoring system.
==== Multi-division Races ====
'''If your race is going contribute to the season results of multiple divisions''' - [[#Getting_help_or_providing_feedback|contact James]] to create a special multi-divisional race code for you.

'''If not''' (usually the case) - follow the instructions for the race registration website, below.

==== Race Registration Website ====
*Go to the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page
*Fill in '''ALL''' information (Use an easily distinguishable race name)
*Select "Add Race"
*The race code will be emailed to you. Use this code when submitting the race to USCSA (later in the process)
[[Image:web_registration.png]]

==== I Need to Make a Change to an Existing Race Code ====
The following values will be updated with whatever you set in SplitSecond, so you don't have to do anything in advance:
* Race administrator name / e-mail / phone
* Race date
* Race Discipline (SL/GS)

For anything else, [[#Getting_help_or_providing_feedback|Contact James]].

==== I Forgot My Race Code... ====
[[#Getting_help_or_providing_feedback|Contact James]], he can find it for you.

== Competitor Classes ==
For each race submission, every participating competitor must be assigned one of 5 classes. This class assignment will determine how scoring is handled for the competitor, and the competitor's team. The classes are:

;A
:For all A-team members. Only USCSA members may be marked with the "A" class, and a USCSA number must be provided with the submission. A-team members with the same team abbreviation make up that school's A-team. This team '''will''' be used to create team results. The team results '''will''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All A-team competitors '''will''' receive USCSA race points.
;B
:For all B-team members. Only USCSA members may be marked with the "B" class, and a USCSA number must be provided with the submission. B-team members with the same team abbreviation make up that school's B-team. This team '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is not eligible''' to score individually. All B-team competitors '''will''' receive USCSA race points.
;Individual
:For all individually qualified members. Only USCSA members may be marked with the "Individual" class, and a USCSA number must be provided with the submission. Individual entries '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All Individual competitors '''will''' receive USCSA race points.
;Unscored/Guest
:For all non-USCSA members, as well as USCSA competitors from divisions other than the division running the event. USCSA or non-USCSA members may be marked with the "Unscored/Guest" class. If the competitor is a USCSA member, then a USCSA number should be provided. Unscored/Guest entries '''will not''' be used to create team results. Each Unscored/Guest competitor '''is not eligible''' to score individually. Unscored/Guest competitors '''will''' receive USCSA race points if they are USCSA members and a USCSA number has been provided. Unscored/Guest competitors '''will not''' receive USCSA race points if a USCSA number has not been provided.
;AA
:For all AA-team members. This class '''should not be used''' by most divisions. Only USCSA members may be marked with the "AA" class, and a USCSA number must be provided with the submission. AA-team members with the same team abbreviation make up that school's AA-team. This team '''will''' be used to create team results for the race. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All AA-team competitors '''will''' receive USCSA race points.

{|style="border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0" border="1"
|+ USCSA scoring classes
! Class
! Times
! Team Result for Race
! Team Result in Divisional Standings
! Individual Result in Divisional Standings
! Receive USCSA Race Points
|-
! A
| Yes
| Yes
| Yes
| Yes
| Yes
|-
! B
| Yes
| No
| No
| No
| Yes
|-
! Individual
| Yes
| No
| No
| Yes
| Yes
|-
! Unscored/Guest
| Yes
| No
| No
| No
| If USCSA member
|-
! AA
| Yes
| Yes
| No
| Yes
| Yes
|}

== How to create a USCSA race in SplitSecond National/FIS ==
==== Download National/FIS ====
[http://www.splitsecond.com SplitSecond National/FIS]

==== Configure National/FIS for USCSA races ====
Fill in the header information as you normally would for a normal USSA race.
Check the following boxes at the bottom
*USCSA Event
*Show USCSA Class on Competitor tab instead of Class
*Show USCSA Number on Competitor tab instead of USSA/FIS Number

[[Image:race_setup.png]]

Select the Factors/Lists tab
Download a USCSA points list and the current USSA points list
*Select the current USSA points list

[[Image:race_setup_points_lists.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Fill in the racer's last name. Select the matching name from the box on the right.
[[Image:racer_registration.png]]

If data from both lists matched the following fields will be filled out correctly
*USSA number
*USCSA number
*Year of birth
*USSA points
*Team (This will be the school abbreviation not 'USA')
*USSA Class

*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. If a racer does not have a USCSA number, verify that you selected the correct USSA athlete. If you are sure that you have the correct athlete [[#Getting_help_or_providing_feedback|Contact the national office]] to resolve the discrepancy.

*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page - not the USSA race code.

[[Image:submit_race2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with National/FIS''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:natfis_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*USSA Number
*USCSA Number
*Bib
*etc...
[[Image:natfis_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:nafis_blockedit.png]]

== How to create a USCSA race in SplitSecond's Ski Club ==
==== Download Ski Club ====
[http://www.splitsecond.com SplitSecond Ski Club]

==== Configure Ski Club for USCSA races ====
Fill in the header information as you normally would for a normal race.
Check the following boxes at the top and bottom
*USCSA Event
*This race includes team scoring (using USCSA Team Scoring)
*Click on the button labeled "Download USCSA List"

[[Image:race_registration_sc.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Make separate race files for Ladies' and Men's racer (Otherwise the team scoring will include both men and women)
*Fill in the racer's last name. Ski Club will search the USCSA list for a matching name. Select the correct racer/team entry from the box on the right. This will fill in all the fields except for class.
*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. [[#Getting_help_or_providing_feedback|Contact the national office]] if a racer does not appear on the USCSA list.
[[Image:racer_registration_sc.png]]
*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration_sc2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race_sc.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page.
[[Image:submit_race_sc2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with Ski Club''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:skiclub_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*Member#
*Bib
*etc...
[[Image:skiclub_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:skiclub_blockedit.png]]

== How to lookup USCSA numbers ==
It is '''critically important''' that your race contains ''USCSA numbers'' for '''ALL''' USCSA members and proper ''team abbreviations'' for '''ALL''' USCSA members scored as class "A" or "B" competitors. The easiest way to find the USCSA numbers and team abbreviations is to look them up in SplitSecond using the USCSA competitor list '''(see the instructions above)'''.

'''If you cannot find the competitor in SplitSecond or you have errors for a particular competitor when submitting the results:'''
*Do '''not''' make up a USCSA number
*Do '''not''' put in some place holder value
*Do '''not''' change the competitor's class to "Guest" (unless they really are a guest)
*'''Do''' contact the national office - there is probably an issue with the competitor's registration that is causing them to not show up in the list.

If SplitSecond is not the right answer for you, there are other methods described below.

==== Individual racer lookup on uscsa.com ====
Use the competitor search function on [http://www.uscsa.com/uscsa-results this page]


==== Download the USCSA member csv ====
This is the same list that SplitSecond uses. If you have an updated list in SplitSecond, you won't find any additional information in here. This might be useful for people who want to generate running orders or other automated tasks.

[http://results.uscsa.com:8080/RaceNetData/CompetitorList/ Download CSV list]

== After submitting the race ==
An e-mail will be sent to the race organizer within a few minutes which will detail the status of scoring. If there are problems with the submission, a report detailing all the problems will be included. You may correct the errors and resubmit (see the section below). If there are no problems, then the e-mail will note that the submission was successful, and the results will be available on the [http://www.uscsa.com/conferences/uscsa-results.html Results Page]. If you don't receive an e-mail within an hour, get in touch with James (see [[#Getting_help_or_providing_feedback|this section]]), and note the race code.

=== Correcting Errors ===
Here are some common errors, and hints on how to fix them.

;Must supply USCSA number for all scored racers
:If a competitor is assigned any [[#Competitor_Classes|class]] besides Unscored/Guest, a USCSA number must be supplied. This is used to match up all the results for the season and across seasons.
;No such USCSA Competitor or wrong USCSA ID
:Check to make sure that the USCSA you supplied is correct for the racer. Maybe you missed a digit, or got some numbers out of order. It is also possible that the competitor recently registered and the scoring system has not received an updated competitor list yet.
;Competitor does not exist for this Division and Season.
:The USCSA number you entered is valid, but that competitor is not a member of this division. This could mean: a) that you mistyped the USCSA number and it matched someone else's USCSA number, in which case you should correct the number, b) the competitor is registered incorrectly, in which case you should [[#Getting_help_or_providing_feedback|contact James and the national office]] to correct the issue, c) the competitor is a guest from a different division, in which case you should change the competitor's class to Unscored/Guest, or d) you got your male/female race codes for the weekend backwards.
;Team abbreviation does not exist for this Division and Season
:The abbreviation used is not recognized. You must use the [[#How_to_lookup_USCSA_numbers|assigned abbreviation]]. If you don't like the assigned abbreviations, [[#Getting_help_or_providing_feedback|get in touch with James]] to change them.
;Incomplete submission. Fill all required fields and try again.
:Make sure the USCSA header (USCSA race code, race date, race type, description line 1, race admin's name, email and phone number) is filled out, and that there are results in the race you are submitting.
;Invalid race code format OR Race does not exist for that race code
:Use the race code that was assigned when you [[#How_to_create_a_USCSA_race_from_the_registration_website|created the race]].
;Results for this race have already been submitted.
:If you meant to make a change to results that you already posted, [[#Getting_help_or_providing_feedback|get in touch with James]] and let him know. If not, make sure you have your race codes straight.
;Malformed time.
:Assuming you are using SplitSecond, you should never get this error. [[#Getting_help_or_providing_feedback|Get in touch with James]] immediately if you do.

== Regional and National Events ==
The process for scoring Regional and National events is very similar to regular divisional events. Read the instructions above (if you haven't already) before reading this section.

'''Note that the scoring system is currently limited to alpine events,''' so disregard everything on this page if you are looking for information about scoring other events.

There are some small changes for scoring Regional and National events:
# Information about which competitors and teams will be attending each Regional Championship and National Championship event must be sent to James (see below for contact information) in advance. Include the following information in an e-mail as soon as possible:
#* Region name (if not the national event)
#* Qualified Men's teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Qualified Ladies' teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Abbreviations for each team, including teams represented by an individual competitor. (If not provided, abbreviations will be assigned by using the team's abbreviations from within their home division. Any conflicts will be addressed manually.)
#* Individual Men and Ladies (include USCSA number and name. You may include "alternate" individuals if you are not sure who will be at the race. Competitors will not show up in the standings unless they show up at the race, but the results will be rejected unless all competitors are registered in the scoring system.)
# [[#Download_the_USCSA_member_csv|CSV files]] for populating the running order will be available AFTER the list of qualified teams and individuals has been processed by James. He will probably e-mail you when they are ready.
# When [[#How_to_create_a_USCSA_race_from_the_registration_website|creating a race code]] for a regional event, the "conference" will be "Regional Championships", and the "division" will be the name of the region followed by the proper gender for the race
# When [[#How_to_create_a_USCSA_race_from_the_registration_website|creating a race code]] for a national event, the "conference" will be "National Championships", and the "division" will be the proper gender for the race

For most regions - competitors should be assigned to either "A" or "Individual" [[#Competitor_Classes|classes]] for team member status or individual competitor status, respectively. However, there is nothing restricting the use of other classes, and all classes will be scored as they are described [[#Competitor_Classes|above]].

== Getting help or providing feedback ==
If you have problems, questions, praise, or suggestions:
* Contact James Cialdea ( j at jimbodude dot net OR jamescialdea at gmail dot com )
** About adding new races with the [http://www.uscsa.com/conferences-events/add-race Add Race] Page
** About errors in posted results or questions about how results are scored
** About suggestions for features or new result summaries

* Contact Eric Millbrandt ( emillbrandt at coldhaus dot com )
** About using SplitSecond
** About setting up USCSA races in SplitSecond
** About inserting USCSA Numbers and Team Abbreviations into SplitSecond races
** You should also copy James and Andy

* Contact Andy Rangen ( arangen at uscsa dot com )
** About formatting of results on the [http://www.uscsa.com/conferences/uscsa-results.html Results] Page
** About errors appearing on the Add Race or Results Pages
** You should also copy James

* Contact the National Office ( LauraSullivan at uscsa dot com )
** If you cannot find a USCSA number for a USCSA competitor
** If you cannot find a team abbreviation for a USCSA team
** You should also copy James and Andy

== How to setup your race to be on Live-Timing.org ==

==== Setup your race ====
Open SplitSecond and click on the "Live Timing" tab

[[Image:example1.png]]

Insert the following information

*Race Date
*Start Time
*State
*Ski Area Name
*Race Name
*Race Type

Now click on "Load Logos from Live-Timing" and select "USCSA-LiveTiming.gif" for the Location Logo and Race Logo.
Put in an easy to remember user name and password.

[[Image:example2.png]]

Now click on "Register Race"

[[Image:example3.png]]

Your race is now registered. Click on "Upload Competitors" to publish the racers on the Live-Timing website.
Remember to register both the Ladies' and Men's races.

==== Viewing you race on Live-Timing.org ====

[[Image:example4.png]]

==== Editing race infomation after you have registered ====

Click on the "tools for resorts" link near the top of the page.
[[Image:example5.png]]

Find your race and click on "Edit". You will need the username and password you created earlier.
[[Image:example6.png]]

USCSA Race setup with SplitSecond

2015-01-28T04:16:31Z

J: /* Race Registration Website */

== Setting up combined scoring rules ==
In order for combined results (qualifications, rankings, divisional overall standings) to be calculated, your division must select scoring rules. For this season, send your selections to James Cialdea by e-mail (see [[#Getting_help_or_providing_feedback|this section]]). You may have different rules for the Men and Ladies - that is not a problem, just provide information for each and we will take care of the rest.

The available rules are described below. If you use a different rule, include that information in the e-mail. You may select one rule and up to three tie breakers for Individual and Team combined scoring. You do not need to select three tie breakers if your division does not have rules for three levels of ties.

In other words, fill in this grid:
* Conference Name:
* Division Name:
* Team Combined Rules
** Rule: (select one from Team Combined Rules)
** Tiebreaker 1: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Team Combined Rules, or leave blank)
* Individual Combined Rules
** Rule: (select one from Individual Combined Rules)
** Tiebreaker 1: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Individual Combined Rules, or leave blank)

Example:
<pre>
Conference Name: Rocky Mountain
Division Name: Rocky Mountain

Team Combined Rules
Rule: Team Finish Place Sum

Individual Combined Rules
Rule: World Cup Top 30
</pre>

=== Individual Combined Rules ===
For Individual Combined scoring, the following rules are available:
;Linear, top 30
:Points are assigned to the top 30 finishers, counting down linearly from 30. (1st = 30, 2nd = 29, ... , 29th = 2, 30th = 1, 31st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Linear, top 15
:Points are assigned to the top 15 finishers, counting down linearly from 15. (1st = 15, 2nd = 14, ... , 14th = 2, 15th = 1, 16st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;World Cup, top 30
:Points are assigned to the top 30 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "current system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Continental, top 15
:Points are assigned to the top 15 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "top 15 system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Race Points
:Sum of race points from FIS/USSA/USCSA formula, lowest score wins. Racers who do not participate in a race are counted as "DNS", and will take 990.00 points for that race. (Note: USCSA points are calculated and displayed in results for all USCSA-scored races regardless of whether this option is used.)
;No scoring
:Combined results are not calculated

=== Team Combined Rules ===
For Team Combined scoring, the following rules are available:
;Team Finish Place Sum
:Each team is assigned place points for each race equal to the team ranking at that race. The sum of finish places for all races is used for combined ranking. The lowest sum wins.
;Individual Finish Place Sum
:Sum of finish places for all racers using in scoring for all races. Dummy finish places will be applied for teams that do not have enough finishers, per USCSA scoring rules. The lowest sum wins.
;Individual Race Point Sum
:Sum of race points (FIS/USSA/USCSA formula) for all racers used in scoring. Dummy points will be added for teams that do not have enough finishers. The dummy points will be the points that would be assigned if a racer finished with the dummy time for the race where the team did not have enough finishers. The lowest sum wins.
;No scoring
:Combined results are not calculated

== How to create a USCSA race from the registration website ==
In order for scoring to occur, the results of your race must be associated with a race code provided by USCSA's scoring system.
==== Multi-division Races ====
'''If your race is going contribute to the season results of multiple divisions''' - [[#Getting_help_or_providing_feedback|contact James]] to create a special multi-divisional race code for you.

'''If not''' (usually the case) - follow the instructions for the race registration website, below.

==== Race Registration Website ====
*Go to the [http://www.uscsa.com/conferences-events/add-race Race Registration] Page
*Fill in '''ALL''' information (Use an easily distinguishable race name)
*Select "Add Race"
*The race code will be emailed to you. Use this code when submitting the race to USCSA (later in the process)
[[Image:web_registration.png]]

==== I Need to Make a Change to an Existing Race Code ====
The following values will be updated with whatever you set in SplitSecond, so you don't have to do anything in advance:
* Race administrator name / e-mail / phone
* Race date
* Race Discipline (SL/GS)

For anything else, [[#Getting_help_or_providing_feedback|Contact James]].

==== I Forgot My Race Code... ====
[[#Getting_help_or_providing_feedback|Contact James]], he can find it for you.

== Competitor Classes ==
For each race submission, every participating competitor must be assigned one of 5 classes. This class assignment will determine how scoring is handled for the competitor, and the competitor's team. The classes are:

;A
:For all A-team members. Only USCSA members may be marked with the "A" class, and a USCSA number must be provided with the submission. A-team members with the same team abbreviation make up that school's A-team. This team '''will''' be used to create team results. The team results '''will''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All A-team competitors '''will''' receive USCSA race points.
;B
:For all B-team members. Only USCSA members may be marked with the "B" class, and a USCSA number must be provided with the submission. B-team members with the same team abbreviation make up that school's B-team. This team '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is not eligible''' to score individually. All B-team competitors '''will''' receive USCSA race points.
;Individual
:For all individually qualified members. Only USCSA members may be marked with the "Individual" class, and a USCSA number must be provided with the submission. Individual entries '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All Individual competitors '''will''' receive USCSA race points.
;Unscored/Guest
:For all non-USCSA members, as well as USCSA competitors from divisions other than the division running the event. USCSA or non-USCSA members may be marked with the "Unscored/Guest" class. If the competitor is a USCSA member, then a USCSA number should be provided. Unscored/Guest entries '''will not''' be used to create team results. Each Unscored/Guest competitor '''is not eligible''' to score individually. Unscored/Guest competitors '''will''' receive USCSA race points if they are USCSA members and a USCSA number has been provided. Unscored/Guest competitors '''will not''' receive USCSA race points if a USCSA number has not been provided.
;AA
:For all AA-team members. This class '''should not be used''' by most divisions. Only USCSA members may be marked with the "AA" class, and a USCSA number must be provided with the submission. AA-team members with the same team abbreviation make up that school's AA-team. This team '''will''' be used to create team results for the race. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All AA-team competitors '''will''' receive USCSA race points.

{|style="border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0" border="1"
|+ USCSA scoring classes
! Class
! Times
! Team Result for Race
! Team Result in Divisional Standings
! Individual Result in Divisional Standings
! Receive USCSA Race Points
|-
! A
| Yes
| Yes
| Yes
| Yes
| Yes
|-
! B
| Yes
| No
| No
| No
| Yes
|-
! Individual
| Yes
| No
| No
| Yes
| Yes
|-
! Unscored/Guest
| Yes
| No
| No
| No
| If USCSA member
|-
! AA
| Yes
| Yes
| No
| Yes
| Yes
|}

== How to create a USCSA race in SplitSecond National/FIS ==
==== Download National/FIS ====
[http://www.splitsecond.com SplitSecond National/FIS]

==== Configure National/FIS for USCSA races ====
Fill in the header information as you normally would for a normal USSA race.
Check the following boxes at the bottom
*USCSA Event
*Show USCSA Class on Competitor tab instead of Class
*Show USCSA Number on Competitor tab instead of USSA/FIS Number

[[Image:race_setup.png]]

Select the Factors/Lists tab
Download a USCSA points list and the current USSA points list
*Select the current USSA points list

[[Image:race_setup_points_lists.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Fill in the racer's last name. Select the matching name from the box on the right.
[[Image:racer_registration.png]]

If data from both lists matched the following fields will be filled out correctly
*USSA number
*USCSA number
*Year of birth
*USSA points
*Team (This will be the school abbreviation not 'USA')
*USSA Class

*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. If a racer does not have a USCSA number, verify that you selected the correct USSA athlete. If you are sure that you have the correct athlete [[#Getting_help_or_providing_feedback|Contact the national office]] to resolve the discrepancy.

*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences/add-race.html Race Registration] Page - not the USSA race code.

[[Image:submit_race2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with National/FIS''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:natfis_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*USSA Number
*USCSA Number
*Bib
*etc...
[[Image:natfis_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:nafis_blockedit.png]]

== How to create a USCSA race in SplitSecond's Ski Club ==
==== Download Ski Club ====
[http://www.splitsecond.com SplitSecond Ski Club]

==== Configure Ski Club for USCSA races ====
Fill in the header information as you normally would for a normal race.
Check the following boxes at the top and bottom
*USCSA Event
*This race includes team scoring (using USCSA Team Scoring)
*Click on the button labeled "Download USCSA List"

[[Image:race_registration_sc.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Make separate race files for Ladies' and Men's racer (Otherwise the team scoring will include both men and women)
*Fill in the racer's last name. Ski Club will search the USCSA list for a matching name. Select the correct racer/team entry from the box on the right. This will fill in all the fields except for class.
*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. [[#Getting_help_or_providing_feedback|Contact the national office]] if a racer does not appear on the USCSA list.
[[Image:racer_registration_sc.png]]
*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration_sc2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race_sc.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences/add-race.html Race Registration] Page.
[[Image:submit_race_sc2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with Ski Club''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:skiclub_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*Member#
*Bib
*etc...
[[Image:skiclub_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:skiclub_blockedit.png]]

== How to lookup USCSA numbers ==
It is '''critically important''' that your race contains ''USCSA numbers'' for '''ALL''' USCSA members and proper ''team abbreviations'' for '''ALL''' USCSA members scored as class "A" or "B" competitors. The easiest way to find the USCSA numbers and team abbreviations is to look them up in SplitSecond using the USCSA competitor list '''(see the instructions above)'''.

'''If you cannot find the competitor in SplitSecond or you have errors for a particular competitor when submitting the results:'''
*Do '''not''' make up a USCSA number
*Do '''not''' put in some place holder value
*Do '''not''' change the competitor's class to "Guest" (unless they really are a guest)
*'''Do''' contact the national office - there is probably an issue with the competitor's registration that is causing them to not show up in the list.

If SplitSecond is not the right answer for you, there are other methods described below.

==== Individual racer lookup on uscsa.com ====
Use the competitor search function on [http://www.uscsa.com/uscsa-results this page]


==== Download the USCSA member csv ====
This is the same list that SplitSecond uses. If you have an updated list in SplitSecond, you won't find any additional information in here. This might be useful for people who want to generate running orders or other automated tasks.

[http://results.uscsa.com:8080/RaceNetData/CompetitorList/ Download CSV list]

== After submitting the race ==
An e-mail will be sent to the race organizer within a few minutes which will detail the status of scoring. If there are problems with the submission, a report detailing all the problems will be included. You may correct the errors and resubmit (see the section below). If there are no problems, then the e-mail will note that the submission was successful, and the results will be available on the [http://www.uscsa.com/conferences/uscsa-results.html Results Page]. If you don't receive an e-mail within an hour, get in touch with James (see [[#Getting_help_or_providing_feedback|this section]]), and note the race code.

=== Correcting Errors ===
Here are some common errors, and hints on how to fix them.

;Must supply USCSA number for all scored racers
:If a competitor is assigned any [[#Competitor_Classes|class]] besides Unscored/Guest, a USCSA number must be supplied. This is used to match up all the results for the season and across seasons.
;No such USCSA Competitor or wrong USCSA ID
:Check to make sure that the USCSA you supplied is correct for the racer. Maybe you missed a digit, or got some numbers out of order. It is also possible that the competitor recently registered and the scoring system has not received an updated competitor list yet.
;Competitor does not exist for this Division and Season.
:The USCSA number you entered is valid, but that competitor is not a member of this division. This could mean: a) that you mistyped the USCSA number and it matched someone else's USCSA number, in which case you should correct the number, b) the competitor is registered incorrectly, in which case you should [[#Getting_help_or_providing_feedback|contact James and the national office]] to correct the issue, c) the competitor is a guest from a different division, in which case you should change the competitor's class to Unscored/Guest, or d) you got your male/female race codes for the weekend backwards.
;Team abbreviation does not exist for this Division and Season
:The abbreviation used is not recognized. You must use the [[#How_to_lookup_USCSA_numbers|assigned abbreviation]]. If you don't like the assigned abbreviations, [[#Getting_help_or_providing_feedback|get in touch with James]] to change them.
;Incomplete submission. Fill all required fields and try again.
:Make sure the USCSA header (USCSA race code, race date, race type, description line 1, race admin's name, email and phone number) is filled out, and that there are results in the race you are submitting.
;Invalid race code format OR Race does not exist for that race code
:Use the race code that was assigned when you [[#How_to_create_a_USCSA_race_from_the_registration_website|created the race]].
;Results for this race have already been submitted.
:If you meant to make a change to results that you already posted, [[#Getting_help_or_providing_feedback|get in touch with James]] and let him know. If not, make sure you have your race codes straight.
;Malformed time.
:Assuming you are using SplitSecond, you should never get this error. [[#Getting_help_or_providing_feedback|Get in touch with James]] immediately if you do.

== Regional and National Events ==
The process for scoring Regional and National events is very similar to regular divisional events. Read the instructions above (if you haven't already) before reading this section.

'''Note that the scoring system is currently limited to alpine events,''' so disregard everything on this page if you are looking for information about scoring other events.

There are some small changes for scoring Regional and National events:
# Information about which competitors and teams will be attending each Regional Championship and National Championship event must be sent to James (see below for contact information) in advance. Include the following information in an e-mail as soon as possible:
#* Region name (if not the national event)
#* Qualified Men's teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Qualified Ladies' teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Abbreviations for each team, including teams represented by an individual competitor. (If not provided, abbreviations will be assigned by using the team's abbreviations from within their home division. Any conflicts will be addressed manually.)
#* Individual Men and Ladies (include USCSA number and name. You may include "alternate" individuals if you are not sure who will be at the race. Competitors will not show up in the standings unless they show up at the race, but the results will be rejected unless all competitors are registered in the scoring system.)
# [[#Download_the_USCSA_member_csv|CSV files]] for populating the running order will be available AFTER the list of qualified teams and individuals has been processed by James. He will probably e-mail you when they are ready.
# When [[#How_to_create_a_USCSA_race_from_the_registration_website|creating a race code]] for a regional event, the "conference" will be "Regional Championships", and the "division" will be the name of the region followed by the proper gender for the race
# When [[#How_to_create_a_USCSA_race_from_the_registration_website|creating a race code]] for a national event, the "conference" will be "National Championships", and the "division" will be the proper gender for the race

For most regions - competitors should be assigned to either "A" or "Individual" [[#Competitor_Classes|classes]] for team member status or individual competitor status, respectively. However, there is nothing restricting the use of other classes, and all classes will be scored as they are described [[#Competitor_Classes|above]].

== Getting help or providing feedback ==
If you have problems, questions, praise, or suggestions:
* Contact James Cialdea ( j at jimbodude dot net OR jamescialdea at gmail dot com )
** About adding new races with the [http://www.uscsa.com/conferences/add-race.html Add Race] Page
** About errors in posted results or questions about how results are scored
** About suggestions for features or new result summaries

* Contact Eric Millbrandt ( emillbrandt at coldhaus dot com )
** About using SplitSecond
** About setting up USCSA races in SplitSecond
** About inserting USCSA Numbers and Team Abbreviations into SplitSecond races
** You should also copy James and Andy

* Contact Andy Rangen ( arangen at uscsa dot com )
** About formatting of results on the [http://www.uscsa.com/conferences/uscsa-results.html Results] Page
** About errors appearing on the Add Race or Results Pages
** You should also copy James

* Contact the National Office ( LauraSullivan at uscsa dot com )
** If you cannot find a USCSA number for a USCSA competitor
** If you cannot find a team abbreviation for a USCSA team
** You should also copy James and Andy

== How to setup your race to be on Live-Timing.org ==

==== Setup your race ====
Open SplitSecond and click on the "Live Timing" tab

[[Image:example1.png]]

Insert the following information

*Race Date
*Start Time
*State
*Ski Area Name
*Race Name
*Race Type

Now click on "Load Logos from Live-Timing" and select "USCSA-LiveTiming.gif" for the Location Logo and Race Logo.
Put in an easy to remember user name and password.

[[Image:example2.png]]

Now click on "Register Race"

[[Image:example3.png]]

Your race is now registered. Click on "Upload Competitors" to publish the racers on the Live-Timing website.
Remember to register both the Ladies' and Men's races.

==== Viewing you race on Live-Timing.org ====

[[Image:example4.png]]

==== Editing race infomation after you have registered ====

Click on the "tools for resorts" link near the top of the page.
[[Image:example5.png]]

Find your race and click on "Edit". You will need the username and password you created earlier.
[[Image:example6.png]]

USCSA Race setup with SplitSecond

2015-01-28T04:16:09Z

J: /* Race Registration Website */

== Setting up combined scoring rules ==
In order for combined results (qualifications, rankings, divisional overall standings) to be calculated, your division must select scoring rules. For this season, send your selections to James Cialdea by e-mail (see [[#Getting_help_or_providing_feedback|this section]]). You may have different rules for the Men and Ladies - that is not a problem, just provide information for each and we will take care of the rest.

The available rules are described below. If you use a different rule, include that information in the e-mail. You may select one rule and up to three tie breakers for Individual and Team combined scoring. You do not need to select three tie breakers if your division does not have rules for three levels of ties.

In other words, fill in this grid:
* Conference Name:
* Division Name:
* Team Combined Rules
** Rule: (select one from Team Combined Rules)
** Tiebreaker 1: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Team Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Team Combined Rules, or leave blank)
* Individual Combined Rules
** Rule: (select one from Individual Combined Rules)
** Tiebreaker 1: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 2: (select one from Individual Combined Rules, or leave blank)
** Tiebreaker 3: (select one from Individual Combined Rules, or leave blank)

Example:
<pre>
Conference Name: Rocky Mountain
Division Name: Rocky Mountain

Team Combined Rules
Rule: Team Finish Place Sum

Individual Combined Rules
Rule: World Cup Top 30
</pre>

=== Individual Combined Rules ===
For Individual Combined scoring, the following rules are available:
;Linear, top 30
:Points are assigned to the top 30 finishers, counting down linearly from 30. (1st = 30, 2nd = 29, ... , 29th = 2, 30th = 1, 31st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Linear, top 15
:Points are assigned to the top 15 finishers, counting down linearly from 15. (1st = 15, 2nd = 14, ... , 14th = 2, 15th = 1, 16st = 0, ... , last = 0). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;World Cup, top 30
:Points are assigned to the top 30 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "current system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Continental, top 15
:Points are assigned to the top 15 finishers using the World Cup point scale (see [http://en.wikipedia.org/wiki/FIS_Alpine_Ski_World_Cup#World_Cup_scoring_system this wiki article] - the scale used is the "top 15 system"). The racer's points are summed over all races in the division. The highest sum is the leader. Racers with 0 points are not ranked.
;Race Points
:Sum of race points from FIS/USSA/USCSA formula, lowest score wins. Racers who do not participate in a race are counted as "DNS", and will take 990.00 points for that race. (Note: USCSA points are calculated and displayed in results for all USCSA-scored races regardless of whether this option is used.)
;No scoring
:Combined results are not calculated

=== Team Combined Rules ===
For Team Combined scoring, the following rules are available:
;Team Finish Place Sum
:Each team is assigned place points for each race equal to the team ranking at that race. The sum of finish places for all races is used for combined ranking. The lowest sum wins.
;Individual Finish Place Sum
:Sum of finish places for all racers using in scoring for all races. Dummy finish places will be applied for teams that do not have enough finishers, per USCSA scoring rules. The lowest sum wins.
;Individual Race Point Sum
:Sum of race points (FIS/USSA/USCSA formula) for all racers used in scoring. Dummy points will be added for teams that do not have enough finishers. The dummy points will be the points that would be assigned if a racer finished with the dummy time for the race where the team did not have enough finishers. The lowest sum wins.
;No scoring
:Combined results are not calculated

== How to create a USCSA race from the registration website ==
In order for scoring to occur, the results of your race must be associated with a race code provided by USCSA's scoring system.
==== Multi-division Races ====
'''If your race is going contribute to the season results of multiple divisions''' - [[#Getting_help_or_providing_feedback|contact James]] to create a special multi-divisional race code for you.

'''If not''' (usually the case) - follow the instructions for the race registration website, below.

==== Race Registration Website ====
*Go to the [http://www.uscsa.com/conferences-events/add-race.html Race Registration] Page
*Fill in '''ALL''' information (Use an easily distinguishable race name)
*Select "Add Race"
*The race code will be emailed to you. Use this code when submitting the race to USCSA (later in the process)
[[Image:web_registration.png]]

==== I Need to Make a Change to an Existing Race Code ====
The following values will be updated with whatever you set in SplitSecond, so you don't have to do anything in advance:
* Race administrator name / e-mail / phone
* Race date
* Race Discipline (SL/GS)

For anything else, [[#Getting_help_or_providing_feedback|Contact James]].

==== I Forgot My Race Code... ====
[[#Getting_help_or_providing_feedback|Contact James]], he can find it for you.

== Competitor Classes ==
For each race submission, every participating competitor must be assigned one of 5 classes. This class assignment will determine how scoring is handled for the competitor, and the competitor's team. The classes are:

;A
:For all A-team members. Only USCSA members may be marked with the "A" class, and a USCSA number must be provided with the submission. A-team members with the same team abbreviation make up that school's A-team. This team '''will''' be used to create team results. The team results '''will''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All A-team competitors '''will''' receive USCSA race points.
;B
:For all B-team members. Only USCSA members may be marked with the "B" class, and a USCSA number must be provided with the submission. B-team members with the same team abbreviation make up that school's B-team. This team '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is not eligible''' to score individually. All B-team competitors '''will''' receive USCSA race points.
;Individual
:For all individually qualified members. Only USCSA members may be marked with the "Individual" class, and a USCSA number must be provided with the submission. Individual entries '''will not''' be used to create team results. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All Individual competitors '''will''' receive USCSA race points.
;Unscored/Guest
:For all non-USCSA members, as well as USCSA competitors from divisions other than the division running the event. USCSA or non-USCSA members may be marked with the "Unscored/Guest" class. If the competitor is a USCSA member, then a USCSA number should be provided. Unscored/Guest entries '''will not''' be used to create team results. Each Unscored/Guest competitor '''is not eligible''' to score individually. Unscored/Guest competitors '''will''' receive USCSA race points if they are USCSA members and a USCSA number has been provided. Unscored/Guest competitors '''will not''' receive USCSA race points if a USCSA number has not been provided.
;AA
:For all AA-team members. This class '''should not be used''' by most divisions. Only USCSA members may be marked with the "AA" class, and a USCSA number must be provided with the submission. AA-team members with the same team abbreviation make up that school's AA-team. This team '''will''' be used to create team results for the race. The team results '''will not''' be used in the divisional standing calculations. Each competitor '''is eligible''' to score individually. Each competitor that scores individually '''will''' be included in the divisional individual standings. All AA-team competitors '''will''' receive USCSA race points.

{|style="border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0" border="1"
|+ USCSA scoring classes
! Class
! Times
! Team Result for Race
! Team Result in Divisional Standings
! Individual Result in Divisional Standings
! Receive USCSA Race Points
|-
! A
| Yes
| Yes
| Yes
| Yes
| Yes
|-
! B
| Yes
| No
| No
| No
| Yes
|-
! Individual
| Yes
| No
| No
| Yes
| Yes
|-
! Unscored/Guest
| Yes
| No
| No
| No
| If USCSA member
|-
! AA
| Yes
| Yes
| No
| Yes
| Yes
|}

== How to create a USCSA race in SplitSecond National/FIS ==
==== Download National/FIS ====
[http://www.splitsecond.com SplitSecond National/FIS]

==== Configure National/FIS for USCSA races ====
Fill in the header information as you normally would for a normal USSA race.
Check the following boxes at the bottom
*USCSA Event
*Show USCSA Class on Competitor tab instead of Class
*Show USCSA Number on Competitor tab instead of USSA/FIS Number

[[Image:race_setup.png]]

Select the Factors/Lists tab
Download a USCSA points list and the current USSA points list
*Select the current USSA points list

[[Image:race_setup_points_lists.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Fill in the racer's last name. Select the matching name from the box on the right.
[[Image:racer_registration.png]]

If data from both lists matched the following fields will be filled out correctly
*USSA number
*USCSA number
*Year of birth
*USSA points
*Team (This will be the school abbreviation not 'USA')
*USSA Class

*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. If a racer does not have a USCSA number, verify that you selected the correct USSA athlete. If you are sure that you have the correct athlete [[#Getting_help_or_providing_feedback|Contact the national office]] to resolve the discrepancy.

*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences/add-race.html Race Registration] Page - not the USSA race code.

[[Image:submit_race2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with National/FIS''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:natfis_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*USSA Number
*USCSA Number
*Bib
*etc...
[[Image:natfis_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:nafis_blockedit.png]]

== How to create a USCSA race in SplitSecond's Ski Club ==
==== Download Ski Club ====
[http://www.splitsecond.com SplitSecond Ski Club]

==== Configure Ski Club for USCSA races ====
Fill in the header information as you normally would for a normal race.
Check the following boxes at the top and bottom
*USCSA Event
*This race includes team scoring (using USCSA Team Scoring)
*Click on the button labeled "Download USCSA List"

[[Image:race_registration_sc.png]]

==== Add competitors to the race ====

Fill in the racer's information as you normally would, plus '''ALL''' additional USCSA-specific data
*Make separate race files for Ladies' and Men's racer (Otherwise the team scoring will include both men and women)
*Fill in the racer's last name. Ski Club will search the USCSA list for a matching name. Select the correct racer/team entry from the box on the right. This will fill in all the fields except for class.
*A USCSA number '''MUST''' be provided for '''EVERY''' competitor that is scored by USCSA. [[#Getting_help_or_providing_feedback|Contact the national office]] if a racer does not appear on the USCSA list.
[[Image:racer_registration_sc.png]]
*Set the racer's [[#Competitor_Classes|USCSA class]]
**Use 'A' for a normal scoring team
**Use 'B' for a second non-scoring team
**Use 'Unscored/Guest' for non-USCSA competitors (The Team will automatically be set to "NONE")
**Use 'Individual' for single racer team
[[Image:racer_registration_sc2.png]]

==== Submitting the race ====

Click the 'Send to USCSA' button on the Competitor tab
[[Image:submit_race_sc.png]]

Fill in the race information and click 'Send'. Use the Race Code assigned to your race when you set it up with the [http://www.uscsa.com/conferences/add-race.html Race Registration] Page.
[[Image:submit_race_sc2.png]]

==== Import competitors into the race ====
''This is only recommended for user with more familiarity with Ski Club''
*Create a csv file with competitor information
[[Image:csv_example.png]]

*Enter the National/FIS import screen
[[Image:skiclub_menu.png]]

Label the columns that you want to import
*Team
*Last
*First
*Member#
*Bib
*etc...
[[Image:skiclub_import.png]]

==== Using block edit to update multiple competitors ====
*Click a racer with the left mouse button and highlight a group of competitors
*Click the 'Block Edit' button (Note: This is the same button as 'Edit Comp' normally)
*Set a field on the group
[[Image:skiclub_blockedit.png]]

== How to lookup USCSA numbers ==
It is '''critically important''' that your race contains ''USCSA numbers'' for '''ALL''' USCSA members and proper ''team abbreviations'' for '''ALL''' USCSA members scored as class "A" or "B" competitors. The easiest way to find the USCSA numbers and team abbreviations is to look them up in SplitSecond using the USCSA competitor list '''(see the instructions above)'''.

'''If you cannot find the competitor in SplitSecond or you have errors for a particular competitor when submitting the results:'''
*Do '''not''' make up a USCSA number
*Do '''not''' put in some place holder value
*Do '''not''' change the competitor's class to "Guest" (unless they really are a guest)
*'''Do''' contact the national office - there is probably an issue with the competitor's registration that is causing them to not show up in the list.

If SplitSecond is not the right answer for you, there are other methods described below.

==== Individual racer lookup on uscsa.com ====
Use the competitor search function on [http://www.uscsa.com/uscsa-results this page]


==== Download the USCSA member csv ====
This is the same list that SplitSecond uses. If you have an updated list in SplitSecond, you won't find any additional information in here. This might be useful for people who want to generate running orders or other automated tasks.

[http://results.uscsa.com:8080/RaceNetData/CompetitorList/ Download CSV list]

== After submitting the race ==
An e-mail will be sent to the race organizer within a few minutes which will detail the status of scoring. If there are problems with the submission, a report detailing all the problems will be included. You may correct the errors and resubmit (see the section below). If there are no problems, then the e-mail will note that the submission was successful, and the results will be available on the [http://www.uscsa.com/conferences/uscsa-results.html Results Page]. If you don't receive an e-mail within an hour, get in touch with James (see [[#Getting_help_or_providing_feedback|this section]]), and note the race code.

=== Correcting Errors ===
Here are some common errors, and hints on how to fix them.

;Must supply USCSA number for all scored racers
:If a competitor is assigned any [[#Competitor_Classes|class]] besides Unscored/Guest, a USCSA number must be supplied. This is used to match up all the results for the season and across seasons.
;No such USCSA Competitor or wrong USCSA ID
:Check to make sure that the USCSA you supplied is correct for the racer. Maybe you missed a digit, or got some numbers out of order. It is also possible that the competitor recently registered and the scoring system has not received an updated competitor list yet.
;Competitor does not exist for this Division and Season.
:The USCSA number you entered is valid, but that competitor is not a member of this division. This could mean: a) that you mistyped the USCSA number and it matched someone else's USCSA number, in which case you should correct the number, b) the competitor is registered incorrectly, in which case you should [[#Getting_help_or_providing_feedback|contact James and the national office]] to correct the issue, c) the competitor is a guest from a different division, in which case you should change the competitor's class to Unscored/Guest, or d) you got your male/female race codes for the weekend backwards.
;Team abbreviation does not exist for this Division and Season
:The abbreviation used is not recognized. You must use the [[#How_to_lookup_USCSA_numbers|assigned abbreviation]]. If you don't like the assigned abbreviations, [[#Getting_help_or_providing_feedback|get in touch with James]] to change them.
;Incomplete submission. Fill all required fields and try again.
:Make sure the USCSA header (USCSA race code, race date, race type, description line 1, race admin's name, email and phone number) is filled out, and that there are results in the race you are submitting.
;Invalid race code format OR Race does not exist for that race code
:Use the race code that was assigned when you [[#How_to_create_a_USCSA_race_from_the_registration_website|created the race]].
;Results for this race have already been submitted.
:If you meant to make a change to results that you already posted, [[#Getting_help_or_providing_feedback|get in touch with James]] and let him know. If not, make sure you have your race codes straight.
;Malformed time.
:Assuming you are using SplitSecond, you should never get this error. [[#Getting_help_or_providing_feedback|Get in touch with James]] immediately if you do.

== Regional and National Events ==
The process for scoring Regional and National events is very similar to regular divisional events. Read the instructions above (if you haven't already) before reading this section.

'''Note that the scoring system is currently limited to alpine events,''' so disregard everything on this page if you are looking for information about scoring other events.

There are some small changes for scoring Regional and National events:
# Information about which competitors and teams will be attending each Regional Championship and National Championship event must be sent to James (see below for contact information) in advance. Include the following information in an e-mail as soon as possible:
#* Region name (if not the national event)
#* Qualified Men's teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Qualified Ladies' teams (just the school name is sufficient, the individual athletes' names do not need to be included)
#* Abbreviations for each team, including teams represented by an individual competitor. (If not provided, abbreviations will be assigned by using the team's abbreviations from within their home division. Any conflicts will be addressed manually.)
#* Individual Men and Ladies (include USCSA number and name. You may include "alternate" individuals if you are not sure who will be at the race. Competitors will not show up in the standings unless they show up at the race, but the results will be rejected unless all competitors are registered in the scoring system.)
# [[#Download_the_USCSA_member_csv|CSV files]] for populating the running order will be available AFTER the list of qualified teams and individuals has been processed by James. He will probably e-mail you when they are ready.
# When [[#How_to_create_a_USCSA_race_from_the_registration_website|creating a race code]] for a regional event, the "conference" will be "Regional Championships", and the "division" will be the name of the region followed by the proper gender for the race
# When [[#How_to_create_a_USCSA_race_from_the_registration_website|creating a race code]] for a national event, the "conference" will be "National Championships", and the "division" will be the proper gender for the race

For most regions - competitors should be assigned to either "A" or "Individual" [[#Competitor_Classes|classes]] for team member status or individual competitor status, respectively. However, there is nothing restricting the use of other classes, and all classes will be scored as they are described [[#Competitor_Classes|above]].

== Getting help or providing feedback ==
If you have problems, questions, praise, or suggestions:
* Contact James Cialdea ( j at jimbodude dot net OR jamescialdea at gmail dot com )
** About adding new races with the [http://www.uscsa.com/conferences/add-race.html Add Race] Page
** About errors in posted results or questions about how results are scored
** About suggestions for features or new result summaries

* Contact Eric Millbrandt ( emillbrandt at coldhaus dot com )
** About using SplitSecond
** About setting up USCSA races in SplitSecond
** About inserting USCSA Numbers and Team Abbreviations into SplitSecond races
** You should also copy James and Andy

* Contact Andy Rangen ( arangen at uscsa dot com )
** About formatting of results on the [http://www.uscsa.com/conferences/uscsa-results.html Results] Page
** About errors appearing on the Add Race or Results Pages
** You should also copy James

* Contact the National Office ( LauraSullivan at uscsa dot com )
** If you cannot find a USCSA number for a USCSA competitor
** If you cannot find a team abbreviation for a USCSA team
** You should also copy James and Andy

== How to setup your race to be on Live-Timing.org ==

==== Setup your race ====
Open SplitSecond and click on the "Live Timing" tab

[[Image:example1.png]]

Insert the following information

*Race Date
*Start Time
*State
*Ski Area Name
*Race Name
*Race Type

Now click on "Load Logos from Live-Timing" and select "USCSA-LiveTiming.gif" for the Location Logo and Race Logo.
Put in an easy to remember user name and password.

[[Image:example2.png]]

Now click on "Register Race"

[[Image:example3.png]]

Your race is now registered. Click on "Upload Competitors" to publish the racers on the Live-Timing website.
Remember to register both the Ladies' and Men's races.

==== Viewing you race on Live-Timing.org ====

[[Image:example4.png]]

==== Editing race infomation after you have registered ====

Click on the "tools for resorts" link near the top of the page.
[[Image:example5.png]]

Find your race and click on "Edit". You will need the username and password you created earlier.
[[Image:example6.png]]

Software RAID on FC6

2014-03-01T19:39:25Z

J: /* LVM */

[[Category:How-To]]
[[Category:FC6]]
[[Category:Linux]]
{|-
| valign="top" |
The document details the steps I had to take to build a software RAID array using mdadm. The document was originally written for Fedora Core 6, but has been updated to cover a wider range of distributions. The process was very tedious and I could not find any one document that gave me enough information to complete the project. I will include all parts of the process from selecting hardware and cabling to building the array and setting it to mount automatically. I will assume the reader has a good knowledge of computer hardware and knows at least a little about SCSI and how to run Linux operating systems. For more information about RAID levels see [http://en.wikipedia.org/wiki/Standard_RAID_levels this]. Feel free to [[Special:Emailuser/J|e-mail me]] with specific questions.
| valign="top" |
[[foto:6123|240]]
|}
<big>NOTE: For this document (and others on this site) Linux commands starting with "$" can be run by any non-root user, those beginning with "#" must be run as root.</big>

==Creating the Array==
===Selecting hard drives, controllers, and cabling===

You can use IDE drives and still follow these instructions perfectly. In fact, it would be much easier if you did use IDE, but SCSI is more reliable, faster, and just plain cooler. If you're interested in going IDE, I'll assume you know how to select, connect, and cable those.

Now, when selecting SCSI drives, go for whatever rotational speed and size spec you feel you need. If you're planning on going for RAID 5, you will need at least (3) drives. I'll discuss RAID types later. Once you select the size and speeds of your drives, it's time to select a connector type. Your three choices are 50-pin, 68-pin, or 80-pin (SCA). I would recommend the 68 or 80-pin configuration for both speed and simplicity. I am using (3) Seagate 181.8GB 7200RPM 80-pin devices.

To run your drives you will need a SCSI controller. Generally you can get a simple PCI controller, unless you have special requirements. I bought a very simple Startech.com PCI controller. It is obviously useless to get a controller with onboard RAID, as we are going to use software for the RAID array - so save your money and get the cheap one. Also, most motherboards that have "onboard RAID" do not actually implement RAID using hardware. Instead, the Windows driver will handle most of the work - effectively making software RAID.

You will also need the proper cable to run your drives. I'd recommend you get a cable with a terminator to make controller configuration easier. Make sure there are enough or more than enough connectors for all your devices. For 50-pin devices, buy a 50-pin cable. For 68 and 80-pin devices, buy a 68-pin cable. 80-pin devices are meant to be put into a hot-swap tray, so you will also need to get an SCA adapter for each device. The SCA adapter provides all the information that a hot-swap rack would including the device ID. It also gives you the ability to hot swap drives after running a few commands. A great place to get cabling and SCA adapters is [http://www.stsi.com STSI]

===Cabling Up and Powering On===

If you're using IDE drives, this doesn't apply to you - just plug them in and go. If you're using a PCI IDE adapter, you might want to check the adapter configuration screen to make sure all the drives were recognized. This information is usually output to the screen during boot, so you might not even have to go into the config.

For the SCSI users, the fun begins. Plug in all your drives, using the SCA adapters if you have 80-pin devices. You will need to set the device id on each drive. This is usually done with some jumpers or switches on the drive unless you're using SCA drives. In that case, you would normally configure them in the hot-swap rack by their position, but if you're like me and too cheap to get one of those, you will set it with a jumper on each SCA adapter. Remember that the controller usually uses an ID of 7, so don't set any drive to that ID. Don't forget to connect the power to each drive!

Once everything is properly cabled, boot up the system. You should see the SCSI adapter card initialize in the boot. Press whatever shortcut key gets you into the device configuration. Poke around in there to make sure all the drives are properly recognized. If they're not, check the jumper settings.

===Getting the Operating System to Recognize the New Drives===

If you are doing a new install of your favorite Linux distribution (i.e. you're not adding the array to an existing installation), the installation process should take care of the rest of the process for you. (I say should, because it didn't for me on my most recent install.) If that's the case, simply follow the on-screen instructions and you'll be all set, stop reading now, bye bye, have fun.

If you already have Linux installed, and the hardware isn't automatically detected on boot, you're in for a treat. First thing to do is get your SCSI controller driver running. In my case, the driver is "initio". You'll have to look around and figure out what yours is. Usually, you can guess it by looking at the manufacturer of the chip on the adapter, Google-ing around, or you can ask for help on a forum or IRC channel. Once you have figured out your driver and installed or compiled it, you should start it by running:
<pre>
#/sbin/modprobe initio
</pre>
replacing "initio" with your own driver name. This should automatically load all dependant modules for SCSI operation. Now, check to see if your drives were initialized by running:
<pre>
#ls /dev/sd*
</pre>
Hopefully, this will return an item for each of your new drives. If not, there was a problem, try again.
====Adding the Driver Permenantly====
Now it's time to add the driver to the kernel. There's different ways to do this depending on your distribution. Pick one of the following sections that fits your needs.
=====RPM Users=====
RPM distributions (Red Hat, Fedora Core, etc) do it by running:
<pre>
#/sbin/new-kernel-pkg --mkinitrd --depmod --install `uname -r`
</pre>
This command will update the currently running kernel with the new driver. If you use yum or rpm to upgrade your kernel, this change will apply to any newer kernel you install. If you don't believe me and want to see all the neat things that run when you install a new kernel run:
<pre>
#rpm -q --scripts kernel
</pre>
You might want to restart your system at this point to make sure that the proper driver has been installed in the kernel and that your devices are listed without calling modprobe, though it shouldn't make a difference.
=====APT Users=====
Sorry, haven't gotten here yet! Google for depmod and your distribution name.
===Formatting the Drives Properly===
Now this is where things get interesting, but not too complex. In order to make software RAID work, we need to make partitions on the devices before the array is built. You can use the bare drive block devices, but using partitions has some benefits and avoids some scary warnings. So, use [http://man-wiki.net/index.php/8:parted parted] if you like command lines or [http://gparted.sourceforge.net/ gpared] if you like GUIs to create a partition on each device. You do not need to format the partitions to any file system. Blank partitions is what you need - the process of creating blank partitions is practically instantaneous.

If you want to create partitions that use the whole drive, and your drives are larger than 2TB you can do something like this to set your drive up to use GPT and create an empty partition (substituting "sda" for your drive, of course):
<pre>
# parted -s -a optimal /dev/sda mklabel gpt -- mkpart primary 1 -1
</pre>

Note that once a drive is configured for GPT, you cannot view information about it with fdisk - you must use parted (or gparted).

===Building the Array===

At this point, we are ready to build the array. This is fairly simple using [http://www.linuxmanpages.com/man8/mdadm.8.php mdadm], which is included in most distributions, including FC. The command to build the array looks like:
<pre>
#/sbin/mdadm --create --level=5 --raid-devices=3 --spare-devices=0 --name=store /dev/md0 /dev/sd[abc]1
</pre>
You will need to chage the level item to match your desired RAID level. See [http://en.wikipedia.org/wiki/Standard_RAID_levels this] if you need a description of RAID levels. If you want spare devices to be automatically controlled by mdadm, note how many devices should be spares. name is the simple name of the array which can be set to anything you like; it is optional. /dev/md0 is the array device; this cannot be changed unless you have already used md0. /dev/sd[abc]1 tells mdadm to use sda1, sdb1, and sdc1 to create the array. Once you run this command, the array will be created. Check the array status by running:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>
The array may be listed as damaged or recreating. This is normal. To create the array for the first time mdadm marks some drives as "bad" to force creation of the array. Monitor the status of the array and wait until it is done building before moving to the next step.

For more information about mdadm, see the [http://man-wiki.net/index.php/8:mdadm man page].

===Set Array to be Available On Boot===

For older systems, in order to make the array available on boot, the "FD" flag must be set on each partition. Mdadm would detect the "FD" flags and initialize the array automatically. To set the "FD" flag simply run:
<pre>
#/sbin/parted /dev/sda set 1 raid on
</pre>
on each of your devices - substitute /dev/sda with your device.

You should probably not have to do this - follow the mdadm.conf instructions below instead. If that doesn't work, try setting FD as described here.

===Create Filesystem on Array===
====Non-LVM====
For partitions under 2TB:
<pre>
#/sbin/mkfs -t ext4 /dev/md0
</pre>
Should take care of that.

For partitions over 2TB:
<pre>
# parted -s -a optimal /dev/md0 mklabel gpt -- mkpart primary ext4 1 -1
</pre>

Substitute ext4 for whatever filesystem you want and md0 for your raid device in either case.
====LVM====
LVM has some pretty serious benefits, you should probably use it. Google around to learn about it and to get install instructions for your distro.

Make a partition on your raid device and set the "lvm" flag on.
<pre>
# parted -s -a optimal /dev/md0 mklabel gpt -- mkpart primary 1 -1 -- set 1 lvm on
# parted -s /dev/md0 set 1 lvm on
</pre>

This creates a new device called /dev/md0p1. This device will become our LVM Physical Volume (PV) - to do that, run:
<pre>
# pvcreate /dev/md0p1
</pre>

You can now check out the work you did with:
<pre>
# pvdisplay
</pre>

Now we create a Volume Group (VG). This one will be a bit boring, since it only has one device right now:
<pre>
# vgcreate vgsomename /dev/md0p1
</pre>
Substitute whatever name you want for "vgsomename". It's nice to start all the names with vg so you remember they are VGs.

Now you can create as many Logical Volumes (LV) as you want. Why would you want more than one? You can grow and shrink them, and also move them around to other physical devices. More LVs provides more flexibility to do that sort of thing.
<pre>
# lvcreate -L 100G -n lvsomename vgsomename
</pre>
-L is the size. If you leave off the "G", the unit is megabytes. Also, read about the "-l"/"--extents" argument, which allows you to specify sizes in percentages of free space. -n is the name, customize it to what you like. Putting "lv" at the front of the name makes it obvious that we're talking about an LV. Substitute your VG name for vgsomename.

Now make file systems on each of your LVs:
<pre>
# mkfs -t ext4 /dev/vgsomename/lvsomename
</pre>

'''For the remainder of this page, you will see /dev/md0 referenced. You should use your LV path(s) instead wherever we are accessing data (mounting drives). Use md0 only when we're managing the raid array (adding / removing disks, checking rebuild status, etc).'''

[http://www.howtogeek.com/howto/40702/how-to-manage-and-use-lvm-logical-volume-management-in-ubuntu/ Here] is a pretty good LVM reference.

===Set up mdadm.conf===

We now need to set up the [http://man-wiki.net/index.php/5:mdadm.conf mdadm.conf] file. This is not really required, but makes troubleshooting easier down the road and allows us to have the system send alerts via e-mail. The easiest way to do this is to start with the detail output, like this:
<pre>
#/sbin/mdadm --detail --scan >> /etc/mdadm.conf
</pre>
Edit the conf file with your favorite editor (in this case I will use vim):
<pre>
#vim /etc/mdadm.conf
</pre>
Review the syntax on the [http://man-wiki.net/index.php/5:mdadm.conf man page] and correct the file. You can use "#" for comments. I also recommend that you define a "MAILADDR" for mdadm to send mail to in the case of a failure. My mdadm.conf looks something like:
<pre>
DEVICE /dev/sd[abc]1

# /dev/md0 is known by it's UID.
ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371

MAILADDR root@somedomain.com
</pre>

===Test mount===

Now the array is completely configured and will be setup on boot without issue. Time to mount it:
<pre>
#mount -t ext3 /dev/md0 /store
</pre>
Substitute whatever filesystem you chose for "ext3", whatever your mdadm device is for "/dev/md0" (if this is your only mdadm array, it will be "/dev/md0"), and wherever you want to mount to for "/store". Assuming that goes well, you can start using your array for storage.

===Add a Line to fstab===

Now we should make the array mount on boot so you don't have to run mount every time you want to use the array.

I recommend that you reboot and re-test the mount before adding an entry to fstab - I had a problem where the array didn't initialize so when fstab was run, I was forced into a file recovery mode, which was unpleasant at best. Once you can prove that the array properly initialized on boot, it is safe to add an entry in fstab.

Once you take care of that, time to add to fstab:

<pre>
#vim /etc/fstab
</pre>

The line that needs to be added looks like:

<pre>
/dev/md0 /store ext4 defaults 0 0
</pre>

Substitute your mdadm device for "/dev/md0", where you want it mounted for "/store", and the file system you chose for "ext3". The rest should stay the same unless you know what you're doing.

If you want a bit more certainty that things will be mounted properly, you can use the UUID instead of the block device name. This will make the mount happen even if the array comes up as a different name, which can happen if mdadm.conf is not loaded, or you didn't create one. This is also helpful for LVM volumes that you might rename.

To get the UUID of your device"
<pre>
# blkid /dev/md0
</pre>

Replace the fstab entry described above with something more like this:
<pre>
UUID=00000000-0000-0000-0000-000000000000 /store ext4 defaults 0 0
</pre>
Replacing that UUID with what you found from blkid, and the rest as described above.
</pre>

That's it! Should work.

==Managing the array==
This section deals with things you do after the array is set up.
===Dealing with Failed Devices===
Oh no! A drive is dead! That's ok, we've got RAID!

For this section, replace "/dev/md0" with your array device, "/dev/sda1" with your failed device, and "/dev/sdd1" with your replacement device. The syntax of your version of mdadm may be slightly different - run "man mdadm" to get a detailed description of mdadm usage if any of this complains about bad arguments.

Check the array to see what's going on:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>

Remove the failed device from the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --fail /dev/sda1
#/sbin/mdadm --manage /dev/md0 --remove /dev/sda1
</pre>

Plug in the new drive and get it ready. You'll need to partition it - see the setup directions for more information. Make sure the replacement partition is at least as big as the failed partition or the rebuild will fail. Once that's done, add the new device to the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --add /dev/sdd1
</pre>
===Migrating the Array to a New System or Installation===
Look into the "--assemble" option. You may have to use "--add" if only some drives come up. It's pretty simple to use - just tell it the right md device and what partitions to assemble into it. For example:
<pre>
#/sbin/mdadm --assemble /dev/md0 /dev/sd[abc]1
</pre>

===Adding Spares===
===SCSI Hot-Swap===
{{Incomplete2|Managing Array Section is basic|Missing directions for APT users}}

Software RAID on FC6

2014-03-01T19:23:11Z

J: /* Add a Line to fstab */

[[Category:How-To]]
[[Category:FC6]]
[[Category:Linux]]
{|-
| valign="top" |
The document details the steps I had to take to build a software RAID array using mdadm. The document was originally written for Fedora Core 6, but has been updated to cover a wider range of distributions. The process was very tedious and I could not find any one document that gave me enough information to complete the project. I will include all parts of the process from selecting hardware and cabling to building the array and setting it to mount automatically. I will assume the reader has a good knowledge of computer hardware and knows at least a little about SCSI and how to run Linux operating systems. For more information about RAID levels see [http://en.wikipedia.org/wiki/Standard_RAID_levels this]. Feel free to [[Special:Emailuser/J|e-mail me]] with specific questions.
| valign="top" |
[[foto:6123|240]]
|}
<big>NOTE: For this document (and others on this site) Linux commands starting with "$" can be run by any non-root user, those beginning with "#" must be run as root.</big>

==Creating the Array==
===Selecting hard drives, controllers, and cabling===

You can use IDE drives and still follow these instructions perfectly. In fact, it would be much easier if you did use IDE, but SCSI is more reliable, faster, and just plain cooler. If you're interested in going IDE, I'll assume you know how to select, connect, and cable those.

Now, when selecting SCSI drives, go for whatever rotational speed and size spec you feel you need. If you're planning on going for RAID 5, you will need at least (3) drives. I'll discuss RAID types later. Once you select the size and speeds of your drives, it's time to select a connector type. Your three choices are 50-pin, 68-pin, or 80-pin (SCA). I would recommend the 68 or 80-pin configuration for both speed and simplicity. I am using (3) Seagate 181.8GB 7200RPM 80-pin devices.

To run your drives you will need a SCSI controller. Generally you can get a simple PCI controller, unless you have special requirements. I bought a very simple Startech.com PCI controller. It is obviously useless to get a controller with onboard RAID, as we are going to use software for the RAID array - so save your money and get the cheap one. Also, most motherboards that have "onboard RAID" do not actually implement RAID using hardware. Instead, the Windows driver will handle most of the work - effectively making software RAID.

You will also need the proper cable to run your drives. I'd recommend you get a cable with a terminator to make controller configuration easier. Make sure there are enough or more than enough connectors for all your devices. For 50-pin devices, buy a 50-pin cable. For 68 and 80-pin devices, buy a 68-pin cable. 80-pin devices are meant to be put into a hot-swap tray, so you will also need to get an SCA adapter for each device. The SCA adapter provides all the information that a hot-swap rack would including the device ID. It also gives you the ability to hot swap drives after running a few commands. A great place to get cabling and SCA adapters is [http://www.stsi.com STSI]

===Cabling Up and Powering On===

If you're using IDE drives, this doesn't apply to you - just plug them in and go. If you're using a PCI IDE adapter, you might want to check the adapter configuration screen to make sure all the drives were recognized. This information is usually output to the screen during boot, so you might not even have to go into the config.

For the SCSI users, the fun begins. Plug in all your drives, using the SCA adapters if you have 80-pin devices. You will need to set the device id on each drive. This is usually done with some jumpers or switches on the drive unless you're using SCA drives. In that case, you would normally configure them in the hot-swap rack by their position, but if you're like me and too cheap to get one of those, you will set it with a jumper on each SCA adapter. Remember that the controller usually uses an ID of 7, so don't set any drive to that ID. Don't forget to connect the power to each drive!

Once everything is properly cabled, boot up the system. You should see the SCSI adapter card initialize in the boot. Press whatever shortcut key gets you into the device configuration. Poke around in there to make sure all the drives are properly recognized. If they're not, check the jumper settings.

===Getting the Operating System to Recognize the New Drives===

If you are doing a new install of your favorite Linux distribution (i.e. you're not adding the array to an existing installation), the installation process should take care of the rest of the process for you. (I say should, because it didn't for me on my most recent install.) If that's the case, simply follow the on-screen instructions and you'll be all set, stop reading now, bye bye, have fun.

If you already have Linux installed, and the hardware isn't automatically detected on boot, you're in for a treat. First thing to do is get your SCSI controller driver running. In my case, the driver is "initio". You'll have to look around and figure out what yours is. Usually, you can guess it by looking at the manufacturer of the chip on the adapter, Google-ing around, or you can ask for help on a forum or IRC channel. Once you have figured out your driver and installed or compiled it, you should start it by running:
<pre>
#/sbin/modprobe initio
</pre>
replacing "initio" with your own driver name. This should automatically load all dependant modules for SCSI operation. Now, check to see if your drives were initialized by running:
<pre>
#ls /dev/sd*
</pre>
Hopefully, this will return an item for each of your new drives. If not, there was a problem, try again.
====Adding the Driver Permenantly====
Now it's time to add the driver to the kernel. There's different ways to do this depending on your distribution. Pick one of the following sections that fits your needs.
=====RPM Users=====
RPM distributions (Red Hat, Fedora Core, etc) do it by running:
<pre>
#/sbin/new-kernel-pkg --mkinitrd --depmod --install `uname -r`
</pre>
This command will update the currently running kernel with the new driver. If you use yum or rpm to upgrade your kernel, this change will apply to any newer kernel you install. If you don't believe me and want to see all the neat things that run when you install a new kernel run:
<pre>
#rpm -q --scripts kernel
</pre>
You might want to restart your system at this point to make sure that the proper driver has been installed in the kernel and that your devices are listed without calling modprobe, though it shouldn't make a difference.
=====APT Users=====
Sorry, haven't gotten here yet! Google for depmod and your distribution name.
===Formatting the Drives Properly===
Now this is where things get interesting, but not too complex. In order to make software RAID work, we need to make partitions on the devices before the array is built. You can use the bare drive block devices, but using partitions has some benefits and avoids some scary warnings. So, use [http://man-wiki.net/index.php/8:parted parted] if you like command lines or [http://gparted.sourceforge.net/ gpared] if you like GUIs to create a partition on each device. You do not need to format the partitions to any file system. Blank partitions is what you need - the process of creating blank partitions is practically instantaneous.

If you want to create partitions that use the whole drive, and your drives are larger than 2TB you can do something like this to set your drive up to use GPT and create an empty partition (substituting "sda" for your drive, of course):
<pre>
# parted -s -a optimal /dev/sda mklabel gpt -- mkpart primary 1 -1
</pre>

Note that once a drive is configured for GPT, you cannot view information about it with fdisk - you must use parted (or gparted).

===Building the Array===

At this point, we are ready to build the array. This is fairly simple using [http://www.linuxmanpages.com/man8/mdadm.8.php mdadm], which is included in most distributions, including FC. The command to build the array looks like:
<pre>
#/sbin/mdadm --create --level=5 --raid-devices=3 --spare-devices=0 --name=store /dev/md0 /dev/sd[abc]1
</pre>
You will need to chage the level item to match your desired RAID level. See [http://en.wikipedia.org/wiki/Standard_RAID_levels this] if you need a description of RAID levels. If you want spare devices to be automatically controlled by mdadm, note how many devices should be spares. name is the simple name of the array which can be set to anything you like; it is optional. /dev/md0 is the array device; this cannot be changed unless you have already used md0. /dev/sd[abc]1 tells mdadm to use sda1, sdb1, and sdc1 to create the array. Once you run this command, the array will be created. Check the array status by running:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>
The array may be listed as damaged or recreating. This is normal. To create the array for the first time mdadm marks some drives as "bad" to force creation of the array. Monitor the status of the array and wait until it is done building before moving to the next step.

For more information about mdadm, see the [http://man-wiki.net/index.php/8:mdadm man page].

===Set Array to be Available On Boot===

For older systems, in order to make the array available on boot, the "FD" flag must be set on each partition. Mdadm would detect the "FD" flags and initialize the array automatically. To set the "FD" flag simply run:
<pre>
#/sbin/parted /dev/sda set 1 raid on
</pre>
on each of your devices - substitute /dev/sda with your device.

You should probably not have to do this - follow the mdadm.conf instructions below instead. If that doesn't work, try setting FD as described here.

===Create Filesystem on Array===
====Non-LVM====
For partitions under 2TB:
<pre>
#/sbin/mkfs -t ext4 /dev/md0
</pre>
Should take care of that.

For partitions over 2TB:
<pre>
# parted -s -a optimal /dev/md0 mklabel gpt -- mkpart primary ext4 1 -1
</pre>

Substitute ext4 for whatever filesystem you want and md0 for your raid device in either case.
====LVM====
LVM has some pretty serious benefits, you should probably use it. Google around to learn about it and to get install instructions for your distro.

Make a partition on your raid device and set the "lvm" flag on.
<pre>
# parted -s -a optimal /dev/md0 mklabel gpt -- mkpart primary 1 -1 -- set 1 lvm on
# parted -s /dev/md0 set 1 lvm on
</pre>

This creates a new device called /dev/md0p1. This device will become our LVM Physical Volume (PV) - to do that, run:
<pre>
# pvcreate /dev/md0p1
</pre>

You can now check out the work you did with:
<pre>
# pvdisplay
</pre>

Now we create a Volume Group (VG). This one will be a bit boring, since it only has one device right now:
<pre>
# vgcreate vgsomename /dev/md0p1
</pre>
Substitute whatever name you want for "vgsomename". It's nice to start all the names with vg so you remember they are VGs.

Now you can create as many Logical Volumes (LV) as you want. Why would you want more than one? You can grow and shrink them, and also move them around to other physical devices. More LVs provides more flexibility to do that sort of thing.
<pre>
# lvcreate -L 100G -n lvsomename vgsomename
</pre>
-L is the size. If you leave off the "G", the unit is megabytes. Also, read about the "-l"/"--extents" argument, which allows you to specify sizes in percentages of free space. -n is the name, customize it to what you like. Putting "lv" at the front of the name makes it obvious that we're talking about an LV. Substitute your VG name for vgsomename.

Now make file systems on each of your LVs:
<pre>
# mkfs -t ext4 /dev/vgsomename/lvsomename
</pre>

'''For the remainder of this page, you will see /dev/md0 referenced. You should use your LV path(s) instead wherever we are accessing data (mounting drives). Use md0 only when we're managing the raid array (adding / removing disks, checking rebuild status, etc).'''

===Set up mdadm.conf===

We now need to set up the [http://man-wiki.net/index.php/5:mdadm.conf mdadm.conf] file. This is not really required, but makes troubleshooting easier down the road and allows us to have the system send alerts via e-mail. The easiest way to do this is to start with the detail output, like this:
<pre>
#/sbin/mdadm --detail --scan >> /etc/mdadm.conf
</pre>
Edit the conf file with your favorite editor (in this case I will use vim):
<pre>
#vim /etc/mdadm.conf
</pre>
Review the syntax on the [http://man-wiki.net/index.php/5:mdadm.conf man page] and correct the file. You can use "#" for comments. I also recommend that you define a "MAILADDR" for mdadm to send mail to in the case of a failure. My mdadm.conf looks something like:
<pre>
DEVICE /dev/sd[abc]1

# /dev/md0 is known by it's UID.
ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371

MAILADDR root@somedomain.com
</pre>

===Test mount===

Now the array is completely configured and will be setup on boot without issue. Time to mount it:
<pre>
#mount -t ext3 /dev/md0 /store
</pre>
Substitute whatever filesystem you chose for "ext3", whatever your mdadm device is for "/dev/md0" (if this is your only mdadm array, it will be "/dev/md0"), and wherever you want to mount to for "/store". Assuming that goes well, you can start using your array for storage.

===Add a Line to fstab===

Now we should make the array mount on boot so you don't have to run mount every time you want to use the array.

I recommend that you reboot and re-test the mount before adding an entry to fstab - I had a problem where the array didn't initialize so when fstab was run, I was forced into a file recovery mode, which was unpleasant at best. Once you can prove that the array properly initialized on boot, it is safe to add an entry in fstab.

Once you take care of that, time to add to fstab:

<pre>
#vim /etc/fstab
</pre>

The line that needs to be added looks like:

<pre>
/dev/md0 /store ext4 defaults 0 0
</pre>

Substitute your mdadm device for "/dev/md0", where you want it mounted for "/store", and the file system you chose for "ext3". The rest should stay the same unless you know what you're doing.

If you want a bit more certainty that things will be mounted properly, you can use the UUID instead of the block device name. This will make the mount happen even if the array comes up as a different name, which can happen if mdadm.conf is not loaded, or you didn't create one. This is also helpful for LVM volumes that you might rename.

To get the UUID of your device"
<pre>
# blkid /dev/md0
</pre>

Replace the fstab entry described above with something more like this:
<pre>
UUID=00000000-0000-0000-0000-000000000000 /store ext4 defaults 0 0
</pre>
Replacing that UUID with what you found from blkid, and the rest as described above.
</pre>

That's it! Should work.

==Managing the array==
This section deals with things you do after the array is set up.
===Dealing with Failed Devices===
Oh no! A drive is dead! That's ok, we've got RAID!

For this section, replace "/dev/md0" with your array device, "/dev/sda1" with your failed device, and "/dev/sdd1" with your replacement device. The syntax of your version of mdadm may be slightly different - run "man mdadm" to get a detailed description of mdadm usage if any of this complains about bad arguments.

Check the array to see what's going on:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>

Remove the failed device from the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --fail /dev/sda1
#/sbin/mdadm --manage /dev/md0 --remove /dev/sda1
</pre>

Plug in the new drive and get it ready. You'll need to partition it - see the setup directions for more information. Make sure the replacement partition is at least as big as the failed partition or the rebuild will fail. Once that's done, add the new device to the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --add /dev/sdd1
</pre>
===Migrating the Array to a New System or Installation===
Look into the "--assemble" option. You may have to use "--add" if only some drives come up. It's pretty simple to use - just tell it the right md device and what partitions to assemble into it. For example:
<pre>
#/sbin/mdadm --assemble /dev/md0 /dev/sd[abc]1
</pre>

===Adding Spares===
===SCSI Hot-Swap===
{{Incomplete2|Managing Array Section is basic|Missing directions for APT users}}

Software RAID on FC6

2014-03-01T18:53:33Z

J: /* LVM */

[[Category:How-To]]
[[Category:FC6]]
[[Category:Linux]]
{|-
| valign="top" |
The document details the steps I had to take to build a software RAID array using mdadm. The document was originally written for Fedora Core 6, but has been updated to cover a wider range of distributions. The process was very tedious and I could not find any one document that gave me enough information to complete the project. I will include all parts of the process from selecting hardware and cabling to building the array and setting it to mount automatically. I will assume the reader has a good knowledge of computer hardware and knows at least a little about SCSI and how to run Linux operating systems. For more information about RAID levels see [http://en.wikipedia.org/wiki/Standard_RAID_levels this]. Feel free to [[Special:Emailuser/J|e-mail me]] with specific questions.
| valign="top" |
[[foto:6123|240]]
|}
<big>NOTE: For this document (and others on this site) Linux commands starting with "$" can be run by any non-root user, those beginning with "#" must be run as root.</big>

==Creating the Array==
===Selecting hard drives, controllers, and cabling===

You can use IDE drives and still follow these instructions perfectly. In fact, it would be much easier if you did use IDE, but SCSI is more reliable, faster, and just plain cooler. If you're interested in going IDE, I'll assume you know how to select, connect, and cable those.

Now, when selecting SCSI drives, go for whatever rotational speed and size spec you feel you need. If you're planning on going for RAID 5, you will need at least (3) drives. I'll discuss RAID types later. Once you select the size and speeds of your drives, it's time to select a connector type. Your three choices are 50-pin, 68-pin, or 80-pin (SCA). I would recommend the 68 or 80-pin configuration for both speed and simplicity. I am using (3) Seagate 181.8GB 7200RPM 80-pin devices.

To run your drives you will need a SCSI controller. Generally you can get a simple PCI controller, unless you have special requirements. I bought a very simple Startech.com PCI controller. It is obviously useless to get a controller with onboard RAID, as we are going to use software for the RAID array - so save your money and get the cheap one. Also, most motherboards that have "onboard RAID" do not actually implement RAID using hardware. Instead, the Windows driver will handle most of the work - effectively making software RAID.

You will also need the proper cable to run your drives. I'd recommend you get a cable with a terminator to make controller configuration easier. Make sure there are enough or more than enough connectors for all your devices. For 50-pin devices, buy a 50-pin cable. For 68 and 80-pin devices, buy a 68-pin cable. 80-pin devices are meant to be put into a hot-swap tray, so you will also need to get an SCA adapter for each device. The SCA adapter provides all the information that a hot-swap rack would including the device ID. It also gives you the ability to hot swap drives after running a few commands. A great place to get cabling and SCA adapters is [http://www.stsi.com STSI]

===Cabling Up and Powering On===

If you're using IDE drives, this doesn't apply to you - just plug them in and go. If you're using a PCI IDE adapter, you might want to check the adapter configuration screen to make sure all the drives were recognized. This information is usually output to the screen during boot, so you might not even have to go into the config.

For the SCSI users, the fun begins. Plug in all your drives, using the SCA adapters if you have 80-pin devices. You will need to set the device id on each drive. This is usually done with some jumpers or switches on the drive unless you're using SCA drives. In that case, you would normally configure them in the hot-swap rack by their position, but if you're like me and too cheap to get one of those, you will set it with a jumper on each SCA adapter. Remember that the controller usually uses an ID of 7, so don't set any drive to that ID. Don't forget to connect the power to each drive!

Once everything is properly cabled, boot up the system. You should see the SCSI adapter card initialize in the boot. Press whatever shortcut key gets you into the device configuration. Poke around in there to make sure all the drives are properly recognized. If they're not, check the jumper settings.

===Getting the Operating System to Recognize the New Drives===

If you are doing a new install of your favorite Linux distribution (i.e. you're not adding the array to an existing installation), the installation process should take care of the rest of the process for you. (I say should, because it didn't for me on my most recent install.) If that's the case, simply follow the on-screen instructions and you'll be all set, stop reading now, bye bye, have fun.

If you already have Linux installed, and the hardware isn't automatically detected on boot, you're in for a treat. First thing to do is get your SCSI controller driver running. In my case, the driver is "initio". You'll have to look around and figure out what yours is. Usually, you can guess it by looking at the manufacturer of the chip on the adapter, Google-ing around, or you can ask for help on a forum or IRC channel. Once you have figured out your driver and installed or compiled it, you should start it by running:
<pre>
#/sbin/modprobe initio
</pre>
replacing "initio" with your own driver name. This should automatically load all dependant modules for SCSI operation. Now, check to see if your drives were initialized by running:
<pre>
#ls /dev/sd*
</pre>
Hopefully, this will return an item for each of your new drives. If not, there was a problem, try again.
====Adding the Driver Permenantly====
Now it's time to add the driver to the kernel. There's different ways to do this depending on your distribution. Pick one of the following sections that fits your needs.
=====RPM Users=====
RPM distributions (Red Hat, Fedora Core, etc) do it by running:
<pre>
#/sbin/new-kernel-pkg --mkinitrd --depmod --install `uname -r`
</pre>
This command will update the currently running kernel with the new driver. If you use yum or rpm to upgrade your kernel, this change will apply to any newer kernel you install. If you don't believe me and want to see all the neat things that run when you install a new kernel run:
<pre>
#rpm -q --scripts kernel
</pre>
You might want to restart your system at this point to make sure that the proper driver has been installed in the kernel and that your devices are listed without calling modprobe, though it shouldn't make a difference.
=====APT Users=====
Sorry, haven't gotten here yet! Google for depmod and your distribution name.
===Formatting the Drives Properly===
Now this is where things get interesting, but not too complex. In order to make software RAID work, we need to make partitions on the devices before the array is built. You can use the bare drive block devices, but using partitions has some benefits and avoids some scary warnings. So, use [http://man-wiki.net/index.php/8:parted parted] if you like command lines or [http://gparted.sourceforge.net/ gpared] if you like GUIs to create a partition on each device. You do not need to format the partitions to any file system. Blank partitions is what you need - the process of creating blank partitions is practically instantaneous.

If you want to create partitions that use the whole drive, and your drives are larger than 2TB you can do something like this to set your drive up to use GPT and create an empty partition (substituting "sda" for your drive, of course):
<pre>
# parted -s -a optimal /dev/sda mklabel gpt -- mkpart primary 1 -1
</pre>

Note that once a drive is configured for GPT, you cannot view information about it with fdisk - you must use parted (or gparted).

===Building the Array===

At this point, we are ready to build the array. This is fairly simple using [http://www.linuxmanpages.com/man8/mdadm.8.php mdadm], which is included in most distributions, including FC. The command to build the array looks like:
<pre>
#/sbin/mdadm --create --level=5 --raid-devices=3 --spare-devices=0 --name=store /dev/md0 /dev/sd[abc]1
</pre>
You will need to chage the level item to match your desired RAID level. See [http://en.wikipedia.org/wiki/Standard_RAID_levels this] if you need a description of RAID levels. If you want spare devices to be automatically controlled by mdadm, note how many devices should be spares. name is the simple name of the array which can be set to anything you like; it is optional. /dev/md0 is the array device; this cannot be changed unless you have already used md0. /dev/sd[abc]1 tells mdadm to use sda1, sdb1, and sdc1 to create the array. Once you run this command, the array will be created. Check the array status by running:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>
The array may be listed as damaged or recreating. This is normal. To create the array for the first time mdadm marks some drives as "bad" to force creation of the array. Monitor the status of the array and wait until it is done building before moving to the next step.

For more information about mdadm, see the [http://man-wiki.net/index.php/8:mdadm man page].

===Set Array to be Available On Boot===

For older systems, in order to make the array available on boot, the "FD" flag must be set on each partition. Mdadm would detect the "FD" flags and initialize the array automatically. To set the "FD" flag simply run:
<pre>
#/sbin/parted /dev/sda set 1 raid on
</pre>
on each of your devices - substitute /dev/sda with your device.

You should probably not have to do this - follow the mdadm.conf instructions below instead. If that doesn't work, try setting FD as described here.

===Create Filesystem on Array===
====Non-LVM====
For partitions under 2TB:
<pre>
#/sbin/mkfs -t ext4 /dev/md0
</pre>
Should take care of that.

For partitions over 2TB:
<pre>
# parted -s -a optimal /dev/md0 mklabel gpt -- mkpart primary ext4 1 -1
</pre>

Substitute ext4 for whatever filesystem you want and md0 for your raid device in either case.
====LVM====
LVM has some pretty serious benefits, you should probably use it. Google around to learn about it and to get install instructions for your distro.

Make a partition on your raid device and set the "lvm" flag on.
<pre>
# parted -s -a optimal /dev/md0 mklabel gpt -- mkpart primary 1 -1 -- set 1 lvm on
# parted -s /dev/md0 set 1 lvm on
</pre>

This creates a new device called /dev/md0p1. This device will become our LVM Physical Volume (PV) - to do that, run:
<pre>
# pvcreate /dev/md0p1
</pre>

You can now check out the work you did with:
<pre>
# pvdisplay
</pre>

Now we create a Volume Group (VG). This one will be a bit boring, since it only has one device right now:
<pre>
# vgcreate vgsomename /dev/md0p1
</pre>
Substitute whatever name you want for "vgsomename". It's nice to start all the names with vg so you remember they are VGs.

Now you can create as many Logical Volumes (LV) as you want. Why would you want more than one? You can grow and shrink them, and also move them around to other physical devices. More LVs provides more flexibility to do that sort of thing.
<pre>
# lvcreate -L 100G -n lvsomename vgsomename
</pre>
-L is the size. If you leave off the "G", the unit is megabytes. Also, read about the "-l"/"--extents" argument, which allows you to specify sizes in percentages of free space. -n is the name, customize it to what you like. Putting "lv" at the front of the name makes it obvious that we're talking about an LV. Substitute your VG name for vgsomename.

Now make file systems on each of your LVs:
<pre>
# mkfs -t ext4 /dev/vgsomename/lvsomename
</pre>

'''For the remainder of this page, you will see /dev/md0 referenced. You should use your LV path(s) instead wherever we are accessing data (mounting drives). Use md0 only when we're managing the raid array (adding / removing disks, checking rebuild status, etc).'''

===Set up mdadm.conf===

We now need to set up the [http://man-wiki.net/index.php/5:mdadm.conf mdadm.conf] file. This is not really required, but makes troubleshooting easier down the road and allows us to have the system send alerts via e-mail. The easiest way to do this is to start with the detail output, like this:
<pre>
#/sbin/mdadm --detail --scan >> /etc/mdadm.conf
</pre>
Edit the conf file with your favorite editor (in this case I will use vim):
<pre>
#vim /etc/mdadm.conf
</pre>
Review the syntax on the [http://man-wiki.net/index.php/5:mdadm.conf man page] and correct the file. You can use "#" for comments. I also recommend that you define a "MAILADDR" for mdadm to send mail to in the case of a failure. My mdadm.conf looks something like:
<pre>
DEVICE /dev/sd[abc]1

# /dev/md0 is known by it's UID.
ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371

MAILADDR root@somedomain.com
</pre>

===Test mount===

Now the array is completely configured and will be setup on boot without issue. Time to mount it:
<pre>
#mount -t ext3 /dev/md0 /store
</pre>
Substitute whatever filesystem you chose for "ext3", whatever your mdadm device is for "/dev/md0" (if this is your only mdadm array, it will be "/dev/md0"), and wherever you want to mount to for "/store". Assuming that goes well, you can start using your array for storage.

===Add a Line to fstab===

Now we should make the array mount on boot so you don't have to run mount every time you want to use the array.

I recommend that you reboot and re-test the mount before adding an entry to fstab - I had a problem where the array didn't initialize so when fstab was run, I was forced into a file recovery mode, which was unpleasant at best. Once you can prove that the array properly initialized on boot, it is safe to add an entry in fstab.

Once you take care of that, time to add to fstab:

<pre>
#vim /etc/fstab
</pre>

The line that needs to be added looks like:

<pre>
/dev/md0 /store ext3 defaults 0 0
</pre>

Substitute your mdadm device for "/dev/md0", where you want it mounted for "/store", and the file system you chose for "ext3". The rest should stay the same unless you know what you're doing.

That's it! Should work.

==Managing the array==
This section deals with things you do after the array is set up.
===Dealing with Failed Devices===
Oh no! A drive is dead! That's ok, we've got RAID!

For this section, replace "/dev/md0" with your array device, "/dev/sda1" with your failed device, and "/dev/sdd1" with your replacement device. The syntax of your version of mdadm may be slightly different - run "man mdadm" to get a detailed description of mdadm usage if any of this complains about bad arguments.

Check the array to see what's going on:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>

Remove the failed device from the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --fail /dev/sda1
#/sbin/mdadm --manage /dev/md0 --remove /dev/sda1
</pre>

Plug in the new drive and get it ready. You'll need to partition it - see the setup directions for more information. Make sure the replacement partition is at least as big as the failed partition or the rebuild will fail. Once that's done, add the new device to the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --add /dev/sdd1
</pre>
===Migrating the Array to a New System or Installation===
Look into the "--assemble" option. You may have to use "--add" if only some drives come up. It's pretty simple to use - just tell it the right md device and what partitions to assemble into it. For example:
<pre>
#/sbin/mdadm --assemble /dev/md0 /dev/sd[abc]1
</pre>

===Adding Spares===
===SCSI Hot-Swap===
{{Incomplete2|Managing Array Section is basic|Missing directions for APT users}}

Software RAID on FC6

2014-03-01T18:51:55Z

J: /* LVM */

[[Category:How-To]]
[[Category:FC6]]
[[Category:Linux]]
{|-
| valign="top" |
The document details the steps I had to take to build a software RAID array using mdadm. The document was originally written for Fedora Core 6, but has been updated to cover a wider range of distributions. The process was very tedious and I could not find any one document that gave me enough information to complete the project. I will include all parts of the process from selecting hardware and cabling to building the array and setting it to mount automatically. I will assume the reader has a good knowledge of computer hardware and knows at least a little about SCSI and how to run Linux operating systems. For more information about RAID levels see [http://en.wikipedia.org/wiki/Standard_RAID_levels this]. Feel free to [[Special:Emailuser/J|e-mail me]] with specific questions.
| valign="top" |
[[foto:6123|240]]
|}
<big>NOTE: For this document (and others on this site) Linux commands starting with "$" can be run by any non-root user, those beginning with "#" must be run as root.</big>

==Creating the Array==
===Selecting hard drives, controllers, and cabling===

You can use IDE drives and still follow these instructions perfectly. In fact, it would be much easier if you did use IDE, but SCSI is more reliable, faster, and just plain cooler. If you're interested in going IDE, I'll assume you know how to select, connect, and cable those.

Now, when selecting SCSI drives, go for whatever rotational speed and size spec you feel you need. If you're planning on going for RAID 5, you will need at least (3) drives. I'll discuss RAID types later. Once you select the size and speeds of your drives, it's time to select a connector type. Your three choices are 50-pin, 68-pin, or 80-pin (SCA). I would recommend the 68 or 80-pin configuration for both speed and simplicity. I am using (3) Seagate 181.8GB 7200RPM 80-pin devices.

To run your drives you will need a SCSI controller. Generally you can get a simple PCI controller, unless you have special requirements. I bought a very simple Startech.com PCI controller. It is obviously useless to get a controller with onboard RAID, as we are going to use software for the RAID array - so save your money and get the cheap one. Also, most motherboards that have "onboard RAID" do not actually implement RAID using hardware. Instead, the Windows driver will handle most of the work - effectively making software RAID.

You will also need the proper cable to run your drives. I'd recommend you get a cable with a terminator to make controller configuration easier. Make sure there are enough or more than enough connectors for all your devices. For 50-pin devices, buy a 50-pin cable. For 68 and 80-pin devices, buy a 68-pin cable. 80-pin devices are meant to be put into a hot-swap tray, so you will also need to get an SCA adapter for each device. The SCA adapter provides all the information that a hot-swap rack would including the device ID. It also gives you the ability to hot swap drives after running a few commands. A great place to get cabling and SCA adapters is [http://www.stsi.com STSI]

===Cabling Up and Powering On===

If you're using IDE drives, this doesn't apply to you - just plug them in and go. If you're using a PCI IDE adapter, you might want to check the adapter configuration screen to make sure all the drives were recognized. This information is usually output to the screen during boot, so you might not even have to go into the config.

For the SCSI users, the fun begins. Plug in all your drives, using the SCA adapters if you have 80-pin devices. You will need to set the device id on each drive. This is usually done with some jumpers or switches on the drive unless you're using SCA drives. In that case, you would normally configure them in the hot-swap rack by their position, but if you're like me and too cheap to get one of those, you will set it with a jumper on each SCA adapter. Remember that the controller usually uses an ID of 7, so don't set any drive to that ID. Don't forget to connect the power to each drive!

Once everything is properly cabled, boot up the system. You should see the SCSI adapter card initialize in the boot. Press whatever shortcut key gets you into the device configuration. Poke around in there to make sure all the drives are properly recognized. If they're not, check the jumper settings.

===Getting the Operating System to Recognize the New Drives===

If you are doing a new install of your favorite Linux distribution (i.e. you're not adding the array to an existing installation), the installation process should take care of the rest of the process for you. (I say should, because it didn't for me on my most recent install.) If that's the case, simply follow the on-screen instructions and you'll be all set, stop reading now, bye bye, have fun.

If you already have Linux installed, and the hardware isn't automatically detected on boot, you're in for a treat. First thing to do is get your SCSI controller driver running. In my case, the driver is "initio". You'll have to look around and figure out what yours is. Usually, you can guess it by looking at the manufacturer of the chip on the adapter, Google-ing around, or you can ask for help on a forum or IRC channel. Once you have figured out your driver and installed or compiled it, you should start it by running:
<pre>
#/sbin/modprobe initio
</pre>
replacing "initio" with your own driver name. This should automatically load all dependant modules for SCSI operation. Now, check to see if your drives were initialized by running:
<pre>
#ls /dev/sd*
</pre>
Hopefully, this will return an item for each of your new drives. If not, there was a problem, try again.
====Adding the Driver Permenantly====
Now it's time to add the driver to the kernel. There's different ways to do this depending on your distribution. Pick one of the following sections that fits your needs.
=====RPM Users=====
RPM distributions (Red Hat, Fedora Core, etc) do it by running:
<pre>
#/sbin/new-kernel-pkg --mkinitrd --depmod --install `uname -r`
</pre>
This command will update the currently running kernel with the new driver. If you use yum or rpm to upgrade your kernel, this change will apply to any newer kernel you install. If you don't believe me and want to see all the neat things that run when you install a new kernel run:
<pre>
#rpm -q --scripts kernel
</pre>
You might want to restart your system at this point to make sure that the proper driver has been installed in the kernel and that your devices are listed without calling modprobe, though it shouldn't make a difference.
=====APT Users=====
Sorry, haven't gotten here yet! Google for depmod and your distribution name.
===Formatting the Drives Properly===
Now this is where things get interesting, but not too complex. In order to make software RAID work, we need to make partitions on the devices before the array is built. You can use the bare drive block devices, but using partitions has some benefits and avoids some scary warnings. So, use [http://man-wiki.net/index.php/8:parted parted] if you like command lines or [http://gparted.sourceforge.net/ gpared] if you like GUIs to create a partition on each device. You do not need to format the partitions to any file system. Blank partitions is what you need - the process of creating blank partitions is practically instantaneous.

If you want to create partitions that use the whole drive, and your drives are larger than 2TB you can do something like this to set your drive up to use GPT and create an empty partition (substituting "sda" for your drive, of course):
<pre>
# parted -s -a optimal /dev/sda mklabel gpt -- mkpart primary 1 -1
</pre>

Note that once a drive is configured for GPT, you cannot view information about it with fdisk - you must use parted (or gparted).

===Building the Array===

At this point, we are ready to build the array. This is fairly simple using [http://www.linuxmanpages.com/man8/mdadm.8.php mdadm], which is included in most distributions, including FC. The command to build the array looks like:
<pre>
#/sbin/mdadm --create --level=5 --raid-devices=3 --spare-devices=0 --name=store /dev/md0 /dev/sd[abc]1
</pre>
You will need to chage the level item to match your desired RAID level. See [http://en.wikipedia.org/wiki/Standard_RAID_levels this] if you need a description of RAID levels. If you want spare devices to be automatically controlled by mdadm, note how many devices should be spares. name is the simple name of the array which can be set to anything you like; it is optional. /dev/md0 is the array device; this cannot be changed unless you have already used md0. /dev/sd[abc]1 tells mdadm to use sda1, sdb1, and sdc1 to create the array. Once you run this command, the array will be created. Check the array status by running:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>
The array may be listed as damaged or recreating. This is normal. To create the array for the first time mdadm marks some drives as "bad" to force creation of the array. Monitor the status of the array and wait until it is done building before moving to the next step.

For more information about mdadm, see the [http://man-wiki.net/index.php/8:mdadm man page].

===Set Array to be Available On Boot===

For older systems, in order to make the array available on boot, the "FD" flag must be set on each partition. Mdadm would detect the "FD" flags and initialize the array automatically. To set the "FD" flag simply run:
<pre>
#/sbin/parted /dev/sda set 1 raid on
</pre>
on each of your devices - substitute /dev/sda with your device.

You should probably not have to do this - follow the mdadm.conf instructions below instead. If that doesn't work, try setting FD as described here.

===Create Filesystem on Array===
====Non-LVM====
For partitions under 2TB:
<pre>
#/sbin/mkfs -t ext4 /dev/md0
</pre>
Should take care of that.

For partitions over 2TB:
<pre>
# parted -s -a optimal /dev/md0 mklabel gpt -- mkpart primary ext4 1 -1
</pre>

Substitute ext4 for whatever filesystem you want and md0 for your raid device in either case.
====LVM====
LVM has some pretty serious benefits, you should probably use it. Google around to learn about it and to get install instructions for your distro.

Make a partition on your raid device and set the "lvm" flag on.
<pre>
# parted -s -a optimal /dev/md0 mklabel gpt -- mkpart primary 1 -1 -- set 1 lvm on
# parted -s /dev/md0 set 1 lvm on
</pre>

This creates a new device called /dev/md0p1. This device will become our LVM Physical Volume (PV) - to do that, run:
<pre>
# pvcreate /dev/md0p1
</pre>

You can now check out the work you did with:
<pre>
# pvdisplay
</pre>

Now we create a Volume Group (VG). This one will be a bit boring, since it only has one device right now:
<pre>
# vgcreate vgsomename /dev/md0p1
</pre>
Substitute whatever name you want for "vgsomename". It's nice to start all the names with vg so you remember they are VGs.

Now you can create as many Logical Volumes (LV) as you want. Why would you want more than one? You can grow and shrink them, and also move them around to other physical devices. More LVs provides more flexibility to do that sort of thing.
<pre>
# lvcreate -L 100G -n lvsomename vgsomename
</pre>
-L is the size. If you leave off the "G", the unit is megabytes. Also, read about the "-l"/"--extents" argument, which allows you to specify sizes in percentages of free space. -n is the name, customize it to what you like. Putting "lv" at the front of the name makes it obvious that we're talking about an LV. Substitute your VG name for vgsomename.

Now make file systems on each of your LVs:
<pre>
# mkfs -t ext4 /dev/vgsomename/lvsomename
</pre>

'''For the remainder of this page, you will see /dev/md0 referenced. You should use your LV path(s) instead wherever you see that.'''

===Set up mdadm.conf===

We now need to set up the [http://man-wiki.net/index.php/5:mdadm.conf mdadm.conf] file. This is not really required, but makes troubleshooting easier down the road and allows us to have the system send alerts via e-mail. The easiest way to do this is to start with the detail output, like this:
<pre>
#/sbin/mdadm --detail --scan >> /etc/mdadm.conf
</pre>
Edit the conf file with your favorite editor (in this case I will use vim):
<pre>
#vim /etc/mdadm.conf
</pre>
Review the syntax on the [http://man-wiki.net/index.php/5:mdadm.conf man page] and correct the file. You can use "#" for comments. I also recommend that you define a "MAILADDR" for mdadm to send mail to in the case of a failure. My mdadm.conf looks something like:
<pre>
DEVICE /dev/sd[abc]1

# /dev/md0 is known by it's UID.
ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371

MAILADDR root@somedomain.com
</pre>

===Test mount===

Now the array is completely configured and will be setup on boot without issue. Time to mount it:
<pre>
#mount -t ext3 /dev/md0 /store
</pre>
Substitute whatever filesystem you chose for "ext3", whatever your mdadm device is for "/dev/md0" (if this is your only mdadm array, it will be "/dev/md0"), and wherever you want to mount to for "/store". Assuming that goes well, you can start using your array for storage.

===Add a Line to fstab===

Now we should make the array mount on boot so you don't have to run mount every time you want to use the array.

I recommend that you reboot and re-test the mount before adding an entry to fstab - I had a problem where the array didn't initialize so when fstab was run, I was forced into a file recovery mode, which was unpleasant at best. Once you can prove that the array properly initialized on boot, it is safe to add an entry in fstab.

Once you take care of that, time to add to fstab:

<pre>
#vim /etc/fstab
</pre>

The line that needs to be added looks like:

<pre>
/dev/md0 /store ext3 defaults 0 0
</pre>

Substitute your mdadm device for "/dev/md0", where you want it mounted for "/store", and the file system you chose for "ext3". The rest should stay the same unless you know what you're doing.

That's it! Should work.

==Managing the array==
This section deals with things you do after the array is set up.
===Dealing with Failed Devices===
Oh no! A drive is dead! That's ok, we've got RAID!

For this section, replace "/dev/md0" with your array device, "/dev/sda1" with your failed device, and "/dev/sdd1" with your replacement device. The syntax of your version of mdadm may be slightly different - run "man mdadm" to get a detailed description of mdadm usage if any of this complains about bad arguments.

Check the array to see what's going on:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>

Remove the failed device from the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --fail /dev/sda1
#/sbin/mdadm --manage /dev/md0 --remove /dev/sda1
</pre>

Plug in the new drive and get it ready. You'll need to partition it - see the setup directions for more information. Make sure the replacement partition is at least as big as the failed partition or the rebuild will fail. Once that's done, add the new device to the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --add /dev/sdd1
</pre>
===Migrating the Array to a New System or Installation===
Look into the "--assemble" option. You may have to use "--add" if only some drives come up. It's pretty simple to use - just tell it the right md device and what partitions to assemble into it. For example:
<pre>
#/sbin/mdadm --assemble /dev/md0 /dev/sd[abc]1
</pre>

===Adding Spares===
===SCSI Hot-Swap===
{{Incomplete2|Managing Array Section is basic|Missing directions for APT users}}

Software RAID on FC6

2014-03-01T18:50:00Z

J: /* Create Filesystem on Array */

[[Category:How-To]]
[[Category:FC6]]
[[Category:Linux]]
{|-
| valign="top" |
The document details the steps I had to take to build a software RAID array using mdadm. The document was originally written for Fedora Core 6, but has been updated to cover a wider range of distributions. The process was very tedious and I could not find any one document that gave me enough information to complete the project. I will include all parts of the process from selecting hardware and cabling to building the array and setting it to mount automatically. I will assume the reader has a good knowledge of computer hardware and knows at least a little about SCSI and how to run Linux operating systems. For more information about RAID levels see [http://en.wikipedia.org/wiki/Standard_RAID_levels this]. Feel free to [[Special:Emailuser/J|e-mail me]] with specific questions.
| valign="top" |
[[foto:6123|240]]
|}
<big>NOTE: For this document (and others on this site) Linux commands starting with "$" can be run by any non-root user, those beginning with "#" must be run as root.</big>

==Creating the Array==
===Selecting hard drives, controllers, and cabling===

You can use IDE drives and still follow these instructions perfectly. In fact, it would be much easier if you did use IDE, but SCSI is more reliable, faster, and just plain cooler. If you're interested in going IDE, I'll assume you know how to select, connect, and cable those.

Now, when selecting SCSI drives, go for whatever rotational speed and size spec you feel you need. If you're planning on going for RAID 5, you will need at least (3) drives. I'll discuss RAID types later. Once you select the size and speeds of your drives, it's time to select a connector type. Your three choices are 50-pin, 68-pin, or 80-pin (SCA). I would recommend the 68 or 80-pin configuration for both speed and simplicity. I am using (3) Seagate 181.8GB 7200RPM 80-pin devices.

To run your drives you will need a SCSI controller. Generally you can get a simple PCI controller, unless you have special requirements. I bought a very simple Startech.com PCI controller. It is obviously useless to get a controller with onboard RAID, as we are going to use software for the RAID array - so save your money and get the cheap one. Also, most motherboards that have "onboard RAID" do not actually implement RAID using hardware. Instead, the Windows driver will handle most of the work - effectively making software RAID.

You will also need the proper cable to run your drives. I'd recommend you get a cable with a terminator to make controller configuration easier. Make sure there are enough or more than enough connectors for all your devices. For 50-pin devices, buy a 50-pin cable. For 68 and 80-pin devices, buy a 68-pin cable. 80-pin devices are meant to be put into a hot-swap tray, so you will also need to get an SCA adapter for each device. The SCA adapter provides all the information that a hot-swap rack would including the device ID. It also gives you the ability to hot swap drives after running a few commands. A great place to get cabling and SCA adapters is [http://www.stsi.com STSI]

===Cabling Up and Powering On===

If you're using IDE drives, this doesn't apply to you - just plug them in and go. If you're using a PCI IDE adapter, you might want to check the adapter configuration screen to make sure all the drives were recognized. This information is usually output to the screen during boot, so you might not even have to go into the config.

For the SCSI users, the fun begins. Plug in all your drives, using the SCA adapters if you have 80-pin devices. You will need to set the device id on each drive. This is usually done with some jumpers or switches on the drive unless you're using SCA drives. In that case, you would normally configure them in the hot-swap rack by their position, but if you're like me and too cheap to get one of those, you will set it with a jumper on each SCA adapter. Remember that the controller usually uses an ID of 7, so don't set any drive to that ID. Don't forget to connect the power to each drive!

Once everything is properly cabled, boot up the system. You should see the SCSI adapter card initialize in the boot. Press whatever shortcut key gets you into the device configuration. Poke around in there to make sure all the drives are properly recognized. If they're not, check the jumper settings.

===Getting the Operating System to Recognize the New Drives===

If you are doing a new install of your favorite Linux distribution (i.e. you're not adding the array to an existing installation), the installation process should take care of the rest of the process for you. (I say should, because it didn't for me on my most recent install.) If that's the case, simply follow the on-screen instructions and you'll be all set, stop reading now, bye bye, have fun.

If you already have Linux installed, and the hardware isn't automatically detected on boot, you're in for a treat. First thing to do is get your SCSI controller driver running. In my case, the driver is "initio". You'll have to look around and figure out what yours is. Usually, you can guess it by looking at the manufacturer of the chip on the adapter, Google-ing around, or you can ask for help on a forum or IRC channel. Once you have figured out your driver and installed or compiled it, you should start it by running:
<pre>
#/sbin/modprobe initio
</pre>
replacing "initio" with your own driver name. This should automatically load all dependant modules for SCSI operation. Now, check to see if your drives were initialized by running:
<pre>
#ls /dev/sd*
</pre>
Hopefully, this will return an item for each of your new drives. If not, there was a problem, try again.
====Adding the Driver Permenantly====
Now it's time to add the driver to the kernel. There's different ways to do this depending on your distribution. Pick one of the following sections that fits your needs.
=====RPM Users=====
RPM distributions (Red Hat, Fedora Core, etc) do it by running:
<pre>
#/sbin/new-kernel-pkg --mkinitrd --depmod --install `uname -r`
</pre>
This command will update the currently running kernel with the new driver. If you use yum or rpm to upgrade your kernel, this change will apply to any newer kernel you install. If you don't believe me and want to see all the neat things that run when you install a new kernel run:
<pre>
#rpm -q --scripts kernel
</pre>
You might want to restart your system at this point to make sure that the proper driver has been installed in the kernel and that your devices are listed without calling modprobe, though it shouldn't make a difference.
=====APT Users=====
Sorry, haven't gotten here yet! Google for depmod and your distribution name.
===Formatting the Drives Properly===
Now this is where things get interesting, but not too complex. In order to make software RAID work, we need to make partitions on the devices before the array is built. You can use the bare drive block devices, but using partitions has some benefits and avoids some scary warnings. So, use [http://man-wiki.net/index.php/8:parted parted] if you like command lines or [http://gparted.sourceforge.net/ gpared] if you like GUIs to create a partition on each device. You do not need to format the partitions to any file system. Blank partitions is what you need - the process of creating blank partitions is practically instantaneous.

If you want to create partitions that use the whole drive, and your drives are larger than 2TB you can do something like this to set your drive up to use GPT and create an empty partition (substituting "sda" for your drive, of course):
<pre>
# parted -s -a optimal /dev/sda mklabel gpt -- mkpart primary 1 -1
</pre>

Note that once a drive is configured for GPT, you cannot view information about it with fdisk - you must use parted (or gparted).

===Building the Array===

At this point, we are ready to build the array. This is fairly simple using [http://www.linuxmanpages.com/man8/mdadm.8.php mdadm], which is included in most distributions, including FC. The command to build the array looks like:
<pre>
#/sbin/mdadm --create --level=5 --raid-devices=3 --spare-devices=0 --name=store /dev/md0 /dev/sd[abc]1
</pre>
You will need to chage the level item to match your desired RAID level. See [http://en.wikipedia.org/wiki/Standard_RAID_levels this] if you need a description of RAID levels. If you want spare devices to be automatically controlled by mdadm, note how many devices should be spares. name is the simple name of the array which can be set to anything you like; it is optional. /dev/md0 is the array device; this cannot be changed unless you have already used md0. /dev/sd[abc]1 tells mdadm to use sda1, sdb1, and sdc1 to create the array. Once you run this command, the array will be created. Check the array status by running:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>
The array may be listed as damaged or recreating. This is normal. To create the array for the first time mdadm marks some drives as "bad" to force creation of the array. Monitor the status of the array and wait until it is done building before moving to the next step.

For more information about mdadm, see the [http://man-wiki.net/index.php/8:mdadm man page].

===Set Array to be Available On Boot===

For older systems, in order to make the array available on boot, the "FD" flag must be set on each partition. Mdadm would detect the "FD" flags and initialize the array automatically. To set the "FD" flag simply run:
<pre>
#/sbin/parted /dev/sda set 1 raid on
</pre>
on each of your devices - substitute /dev/sda with your device.

You should probably not have to do this - follow the mdadm.conf instructions below instead. If that doesn't work, try setting FD as described here.

===Create Filesystem on Array===
====Non-LVM====
For partitions under 2TB:
<pre>
#/sbin/mkfs -t ext4 /dev/md0
</pre>
Should take care of that.

For partitions over 2TB:
<pre>
# parted -s -a optimal /dev/md0 mklabel gpt -- mkpart primary ext4 1 -1
</pre>

Substitute ext4 for whatever filesystem you want and md0 for your raid device in either case.
====LVM====
LVM has some pretty serious benefits, you should probably use it. Google around to learn about it and to get install instructions for your distro.

Make a partition on your raid device and set the "lvm" flag on.
<pre>
# parted -s -a optimal /dev/md0 mklabel gpt -- mkpart primary 1 -1 -- set 1 lvm on
# parted -s /dev/md0 set 1 lvm on
</pre>

This creates a new device called /dev/md0p1. This device will become our LVM Physical Volume (PV) - to do that, run:
<pre>
# pvcreate /dev/md0p1
</pre>

You can now check out the work you did with:
<pre>
# pvdisplay
</pre>

Now we create a Volume Group (VG). This one will be a bit boring, since it only has one device right now:
<pre>
# vgcreate vgsomename /dev/md0p1
</pre>
Substitute whatever name you want for "vgsomename". It's nice to start all the names with vg so you remember they are VGs.

Now you can create as many Logical Volumes (LV) as you want. Why would you want more than one? You can grow and shrink them, and also move them around to other physical devices. More LVs provides more flexibility to do that sort of thing.
<pre>
# lvcreate -L 100G -n lvsomename vgsomename
</pre>
-L is the size. If you leave off the "G", the unit is megabytes. Also, read about the "-l"/"--extents" argument, which allows you to specify sizes in percentages of free space. -n is the name, customize it to what you like. Putting "lv" at the front of the name makes it obvious that we're talking about an LV. Substitute your VG name for vgsomename.

Now make file systems on each of your LVs:
<pre>
# mkfs -t ext4 /dev/vgsomename/lvsomename
</pre>

===Set up mdadm.conf===

We now need to set up the [http://man-wiki.net/index.php/5:mdadm.conf mdadm.conf] file. This is not really required, but makes troubleshooting easier down the road and allows us to have the system send alerts via e-mail. The easiest way to do this is to start with the detail output, like this:
<pre>
#/sbin/mdadm --detail --scan >> /etc/mdadm.conf
</pre>
Edit the conf file with your favorite editor (in this case I will use vim):
<pre>
#vim /etc/mdadm.conf
</pre>
Review the syntax on the [http://man-wiki.net/index.php/5:mdadm.conf man page] and correct the file. You can use "#" for comments. I also recommend that you define a "MAILADDR" for mdadm to send mail to in the case of a failure. My mdadm.conf looks something like:
<pre>
DEVICE /dev/sd[abc]1

# /dev/md0 is known by it's UID.
ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371

MAILADDR root@somedomain.com
</pre>

===Test mount===

Now the array is completely configured and will be setup on boot without issue. Time to mount it:
<pre>
#mount -t ext3 /dev/md0 /store
</pre>
Substitute whatever filesystem you chose for "ext3", whatever your mdadm device is for "/dev/md0" (if this is your only mdadm array, it will be "/dev/md0"), and wherever you want to mount to for "/store". Assuming that goes well, you can start using your array for storage.

===Add a Line to fstab===

Now we should make the array mount on boot so you don't have to run mount every time you want to use the array.

I recommend that you reboot and re-test the mount before adding an entry to fstab - I had a problem where the array didn't initialize so when fstab was run, I was forced into a file recovery mode, which was unpleasant at best. Once you can prove that the array properly initialized on boot, it is safe to add an entry in fstab.

Once you take care of that, time to add to fstab:

<pre>
#vim /etc/fstab
</pre>

The line that needs to be added looks like:

<pre>
/dev/md0 /store ext3 defaults 0 0
</pre>

Substitute your mdadm device for "/dev/md0", where you want it mounted for "/store", and the file system you chose for "ext3". The rest should stay the same unless you know what you're doing.

That's it! Should work.

==Managing the array==
This section deals with things you do after the array is set up.
===Dealing with Failed Devices===
Oh no! A drive is dead! That's ok, we've got RAID!

For this section, replace "/dev/md0" with your array device, "/dev/sda1" with your failed device, and "/dev/sdd1" with your replacement device. The syntax of your version of mdadm may be slightly different - run "man mdadm" to get a detailed description of mdadm usage if any of this complains about bad arguments.

Check the array to see what's going on:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>

Remove the failed device from the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --fail /dev/sda1
#/sbin/mdadm --manage /dev/md0 --remove /dev/sda1
</pre>

Plug in the new drive and get it ready. You'll need to partition it - see the setup directions for more information. Make sure the replacement partition is at least as big as the failed partition or the rebuild will fail. Once that's done, add the new device to the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --add /dev/sdd1
</pre>
===Migrating the Array to a New System or Installation===
Look into the "--assemble" option. You may have to use "--add" if only some drives come up. It's pretty simple to use - just tell it the right md device and what partitions to assemble into it. For example:
<pre>
#/sbin/mdadm --assemble /dev/md0 /dev/sd[abc]1
</pre>

===Adding Spares===
===SCSI Hot-Swap===
{{Incomplete2|Managing Array Section is basic|Missing directions for APT users}}

Software RAID on FC6

2014-03-01T17:25:19Z

J: /* Set Array to be Available On Boot */

[[Category:How-To]]
[[Category:FC6]]
[[Category:Linux]]
{|-
| valign="top" |
The document details the steps I had to take to build a software RAID array using mdadm. The document was originally written for Fedora Core 6, but has been updated to cover a wider range of distributions. The process was very tedious and I could not find any one document that gave me enough information to complete the project. I will include all parts of the process from selecting hardware and cabling to building the array and setting it to mount automatically. I will assume the reader has a good knowledge of computer hardware and knows at least a little about SCSI and how to run Linux operating systems. For more information about RAID levels see [http://en.wikipedia.org/wiki/Standard_RAID_levels this]. Feel free to [[Special:Emailuser/J|e-mail me]] with specific questions.
| valign="top" |
[[foto:6123|240]]
|}
<big>NOTE: For this document (and others on this site) Linux commands starting with "$" can be run by any non-root user, those beginning with "#" must be run as root.</big>

==Creating the Array==
===Selecting hard drives, controllers, and cabling===

You can use IDE drives and still follow these instructions perfectly. In fact, it would be much easier if you did use IDE, but SCSI is more reliable, faster, and just plain cooler. If you're interested in going IDE, I'll assume you know how to select, connect, and cable those.

Now, when selecting SCSI drives, go for whatever rotational speed and size spec you feel you need. If you're planning on going for RAID 5, you will need at least (3) drives. I'll discuss RAID types later. Once you select the size and speeds of your drives, it's time to select a connector type. Your three choices are 50-pin, 68-pin, or 80-pin (SCA). I would recommend the 68 or 80-pin configuration for both speed and simplicity. I am using (3) Seagate 181.8GB 7200RPM 80-pin devices.

To run your drives you will need a SCSI controller. Generally you can get a simple PCI controller, unless you have special requirements. I bought a very simple Startech.com PCI controller. It is obviously useless to get a controller with onboard RAID, as we are going to use software for the RAID array - so save your money and get the cheap one. Also, most motherboards that have "onboard RAID" do not actually implement RAID using hardware. Instead, the Windows driver will handle most of the work - effectively making software RAID.

You will also need the proper cable to run your drives. I'd recommend you get a cable with a terminator to make controller configuration easier. Make sure there are enough or more than enough connectors for all your devices. For 50-pin devices, buy a 50-pin cable. For 68 and 80-pin devices, buy a 68-pin cable. 80-pin devices are meant to be put into a hot-swap tray, so you will also need to get an SCA adapter for each device. The SCA adapter provides all the information that a hot-swap rack would including the device ID. It also gives you the ability to hot swap drives after running a few commands. A great place to get cabling and SCA adapters is [http://www.stsi.com STSI]

===Cabling Up and Powering On===

If you're using IDE drives, this doesn't apply to you - just plug them in and go. If you're using a PCI IDE adapter, you might want to check the adapter configuration screen to make sure all the drives were recognized. This information is usually output to the screen during boot, so you might not even have to go into the config.

For the SCSI users, the fun begins. Plug in all your drives, using the SCA adapters if you have 80-pin devices. You will need to set the device id on each drive. This is usually done with some jumpers or switches on the drive unless you're using SCA drives. In that case, you would normally configure them in the hot-swap rack by their position, but if you're like me and too cheap to get one of those, you will set it with a jumper on each SCA adapter. Remember that the controller usually uses an ID of 7, so don't set any drive to that ID. Don't forget to connect the power to each drive!

Once everything is properly cabled, boot up the system. You should see the SCSI adapter card initialize in the boot. Press whatever shortcut key gets you into the device configuration. Poke around in there to make sure all the drives are properly recognized. If they're not, check the jumper settings.

===Getting the Operating System to Recognize the New Drives===

If you are doing a new install of your favorite Linux distribution (i.e. you're not adding the array to an existing installation), the installation process should take care of the rest of the process for you. (I say should, because it didn't for me on my most recent install.) If that's the case, simply follow the on-screen instructions and you'll be all set, stop reading now, bye bye, have fun.

If you already have Linux installed, and the hardware isn't automatically detected on boot, you're in for a treat. First thing to do is get your SCSI controller driver running. In my case, the driver is "initio". You'll have to look around and figure out what yours is. Usually, you can guess it by looking at the manufacturer of the chip on the adapter, Google-ing around, or you can ask for help on a forum or IRC channel. Once you have figured out your driver and installed or compiled it, you should start it by running:
<pre>
#/sbin/modprobe initio
</pre>
replacing "initio" with your own driver name. This should automatically load all dependant modules for SCSI operation. Now, check to see if your drives were initialized by running:
<pre>
#ls /dev/sd*
</pre>
Hopefully, this will return an item for each of your new drives. If not, there was a problem, try again.
====Adding the Driver Permenantly====
Now it's time to add the driver to the kernel. There's different ways to do this depending on your distribution. Pick one of the following sections that fits your needs.
=====RPM Users=====
RPM distributions (Red Hat, Fedora Core, etc) do it by running:
<pre>
#/sbin/new-kernel-pkg --mkinitrd --depmod --install `uname -r`
</pre>
This command will update the currently running kernel with the new driver. If you use yum or rpm to upgrade your kernel, this change will apply to any newer kernel you install. If you don't believe me and want to see all the neat things that run when you install a new kernel run:
<pre>
#rpm -q --scripts kernel
</pre>
You might want to restart your system at this point to make sure that the proper driver has been installed in the kernel and that your devices are listed without calling modprobe, though it shouldn't make a difference.
=====APT Users=====
Sorry, haven't gotten here yet! Google for depmod and your distribution name.
===Formatting the Drives Properly===
Now this is where things get interesting, but not too complex. In order to make software RAID work, we need to make partitions on the devices before the array is built. You can use the bare drive block devices, but using partitions has some benefits and avoids some scary warnings. So, use [http://man-wiki.net/index.php/8:parted parted] if you like command lines or [http://gparted.sourceforge.net/ gpared] if you like GUIs to create a partition on each device. You do not need to format the partitions to any file system. Blank partitions is what you need - the process of creating blank partitions is practically instantaneous.

If you want to create partitions that use the whole drive, and your drives are larger than 2TB you can do something like this to set your drive up to use GPT and create an empty partition (substituting "sda" for your drive, of course):
<pre>
# parted -s -a optimal /dev/sda mklabel gpt -- mkpart primary 1 -1
</pre>

Note that once a drive is configured for GPT, you cannot view information about it with fdisk - you must use parted (or gparted).

===Building the Array===

At this point, we are ready to build the array. This is fairly simple using [http://www.linuxmanpages.com/man8/mdadm.8.php mdadm], which is included in most distributions, including FC. The command to build the array looks like:
<pre>
#/sbin/mdadm --create --level=5 --raid-devices=3 --spare-devices=0 --name=store /dev/md0 /dev/sd[abc]1
</pre>
You will need to chage the level item to match your desired RAID level. See [http://en.wikipedia.org/wiki/Standard_RAID_levels this] if you need a description of RAID levels. If you want spare devices to be automatically controlled by mdadm, note how many devices should be spares. name is the simple name of the array which can be set to anything you like; it is optional. /dev/md0 is the array device; this cannot be changed unless you have already used md0. /dev/sd[abc]1 tells mdadm to use sda1, sdb1, and sdc1 to create the array. Once you run this command, the array will be created. Check the array status by running:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>
The array may be listed as damaged or recreating. This is normal. To create the array for the first time mdadm marks some drives as "bad" to force creation of the array. Monitor the status of the array and wait until it is done building before moving to the next step.

For more information about mdadm, see the [http://man-wiki.net/index.php/8:mdadm man page].

===Set Array to be Available On Boot===

For older systems, in order to make the array available on boot, the "FD" flag must be set on each partition. Mdadm would detect the "FD" flags and initialize the array automatically. To set the "FD" flag simply run:
<pre>
#/sbin/parted /dev/sda set 1 raid on
</pre>
on each of your devices - substitute /dev/sda with your device.

You should probably not have to do this - follow the mdadm.conf instructions below instead. If that doesn't work, try setting FD as described here.

===Create Filesystem on Array===
<pre>
#/sbin/mkfs -t ext3 /dev/md0
</pre>
Should take care of that. Substitute ext3 for whatever filesystem you want.

===Set up mdadm.conf===

We now need to set up the [http://man-wiki.net/index.php/5:mdadm.conf mdadm.conf] file. This is not really required, but makes troubleshooting easier down the road and allows us to have the system send alerts via e-mail. The easiest way to do this is to start with the detail output, like this:
<pre>
#/sbin/mdadm --detail --scan >> /etc/mdadm.conf
</pre>
Edit the conf file with your favorite editor (in this case I will use vim):
<pre>
#vim /etc/mdadm.conf
</pre>
Review the syntax on the [http://man-wiki.net/index.php/5:mdadm.conf man page] and correct the file. You can use "#" for comments. I also recommend that you define a "MAILADDR" for mdadm to send mail to in the case of a failure. My mdadm.conf looks something like:
<pre>
DEVICE /dev/sd[abc]1

# /dev/md0 is known by it's UID.
ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371

MAILADDR root@somedomain.com
</pre>

===Test mount===

Now the array is completely configured and will be setup on boot without issue. Time to mount it:
<pre>
#mount -t ext3 /dev/md0 /store
</pre>
Substitute whatever filesystem you chose for "ext3", whatever your mdadm device is for "/dev/md0" (if this is your only mdadm array, it will be "/dev/md0"), and wherever you want to mount to for "/store". Assuming that goes well, you can start using your array for storage.

===Add a Line to fstab===

Now we should make the array mount on boot so you don't have to run mount every time you want to use the array.

I recommend that you reboot and re-test the mount before adding an entry to fstab - I had a problem where the array didn't initialize so when fstab was run, I was forced into a file recovery mode, which was unpleasant at best. Once you can prove that the array properly initialized on boot, it is safe to add an entry in fstab.

Once you take care of that, time to add to fstab:

<pre>
#vim /etc/fstab
</pre>

The line that needs to be added looks like:

<pre>
/dev/md0 /store ext3 defaults 0 0
</pre>

Substitute your mdadm device for "/dev/md0", where you want it mounted for "/store", and the file system you chose for "ext3". The rest should stay the same unless you know what you're doing.

That's it! Should work.

==Managing the array==
This section deals with things you do after the array is set up.
===Dealing with Failed Devices===
Oh no! A drive is dead! That's ok, we've got RAID!

For this section, replace "/dev/md0" with your array device, "/dev/sda1" with your failed device, and "/dev/sdd1" with your replacement device. The syntax of your version of mdadm may be slightly different - run "man mdadm" to get a detailed description of mdadm usage if any of this complains about bad arguments.

Check the array to see what's going on:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>

Remove the failed device from the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --fail /dev/sda1
#/sbin/mdadm --manage /dev/md0 --remove /dev/sda1
</pre>

Plug in the new drive and get it ready. You'll need to partition it - see the setup directions for more information. Make sure the replacement partition is at least as big as the failed partition or the rebuild will fail. Once that's done, add the new device to the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --add /dev/sdd1
</pre>
===Migrating the Array to a New System or Installation===
Look into the "--assemble" option. You may have to use "--add" if only some drives come up. It's pretty simple to use - just tell it the right md device and what partitions to assemble into it. For example:
<pre>
#/sbin/mdadm --assemble /dev/md0 /dev/sd[abc]1
</pre>

===Adding Spares===
===SCSI Hot-Swap===
{{Incomplete2|Managing Array Section is basic|Missing directions for APT users}}

Software RAID on FC6

2014-03-01T17:20:00Z

J: /* Formatting the Drives Properly */

[[Category:How-To]]
[[Category:FC6]]
[[Category:Linux]]
{|-
| valign="top" |
The document details the steps I had to take to build a software RAID array using mdadm. The document was originally written for Fedora Core 6, but has been updated to cover a wider range of distributions. The process was very tedious and I could not find any one document that gave me enough information to complete the project. I will include all parts of the process from selecting hardware and cabling to building the array and setting it to mount automatically. I will assume the reader has a good knowledge of computer hardware and knows at least a little about SCSI and how to run Linux operating systems. For more information about RAID levels see [http://en.wikipedia.org/wiki/Standard_RAID_levels this]. Feel free to [[Special:Emailuser/J|e-mail me]] with specific questions.
| valign="top" |
[[foto:6123|240]]
|}
<big>NOTE: For this document (and others on this site) Linux commands starting with "$" can be run by any non-root user, those beginning with "#" must be run as root.</big>

==Creating the Array==
===Selecting hard drives, controllers, and cabling===

You can use IDE drives and still follow these instructions perfectly. In fact, it would be much easier if you did use IDE, but SCSI is more reliable, faster, and just plain cooler. If you're interested in going IDE, I'll assume you know how to select, connect, and cable those.

Now, when selecting SCSI drives, go for whatever rotational speed and size spec you feel you need. If you're planning on going for RAID 5, you will need at least (3) drives. I'll discuss RAID types later. Once you select the size and speeds of your drives, it's time to select a connector type. Your three choices are 50-pin, 68-pin, or 80-pin (SCA). I would recommend the 68 or 80-pin configuration for both speed and simplicity. I am using (3) Seagate 181.8GB 7200RPM 80-pin devices.

To run your drives you will need a SCSI controller. Generally you can get a simple PCI controller, unless you have special requirements. I bought a very simple Startech.com PCI controller. It is obviously useless to get a controller with onboard RAID, as we are going to use software for the RAID array - so save your money and get the cheap one. Also, most motherboards that have "onboard RAID" do not actually implement RAID using hardware. Instead, the Windows driver will handle most of the work - effectively making software RAID.

You will also need the proper cable to run your drives. I'd recommend you get a cable with a terminator to make controller configuration easier. Make sure there are enough or more than enough connectors for all your devices. For 50-pin devices, buy a 50-pin cable. For 68 and 80-pin devices, buy a 68-pin cable. 80-pin devices are meant to be put into a hot-swap tray, so you will also need to get an SCA adapter for each device. The SCA adapter provides all the information that a hot-swap rack would including the device ID. It also gives you the ability to hot swap drives after running a few commands. A great place to get cabling and SCA adapters is [http://www.stsi.com STSI]

===Cabling Up and Powering On===

If you're using IDE drives, this doesn't apply to you - just plug them in and go. If you're using a PCI IDE adapter, you might want to check the adapter configuration screen to make sure all the drives were recognized. This information is usually output to the screen during boot, so you might not even have to go into the config.

For the SCSI users, the fun begins. Plug in all your drives, using the SCA adapters if you have 80-pin devices. You will need to set the device id on each drive. This is usually done with some jumpers or switches on the drive unless you're using SCA drives. In that case, you would normally configure them in the hot-swap rack by their position, but if you're like me and too cheap to get one of those, you will set it with a jumper on each SCA adapter. Remember that the controller usually uses an ID of 7, so don't set any drive to that ID. Don't forget to connect the power to each drive!

Once everything is properly cabled, boot up the system. You should see the SCSI adapter card initialize in the boot. Press whatever shortcut key gets you into the device configuration. Poke around in there to make sure all the drives are properly recognized. If they're not, check the jumper settings.

===Getting the Operating System to Recognize the New Drives===

If you are doing a new install of your favorite Linux distribution (i.e. you're not adding the array to an existing installation), the installation process should take care of the rest of the process for you. (I say should, because it didn't for me on my most recent install.) If that's the case, simply follow the on-screen instructions and you'll be all set, stop reading now, bye bye, have fun.

If you already have Linux installed, and the hardware isn't automatically detected on boot, you're in for a treat. First thing to do is get your SCSI controller driver running. In my case, the driver is "initio". You'll have to look around and figure out what yours is. Usually, you can guess it by looking at the manufacturer of the chip on the adapter, Google-ing around, or you can ask for help on a forum or IRC channel. Once you have figured out your driver and installed or compiled it, you should start it by running:
<pre>
#/sbin/modprobe initio
</pre>
replacing "initio" with your own driver name. This should automatically load all dependant modules for SCSI operation. Now, check to see if your drives were initialized by running:
<pre>
#ls /dev/sd*
</pre>
Hopefully, this will return an item for each of your new drives. If not, there was a problem, try again.
====Adding the Driver Permenantly====
Now it's time to add the driver to the kernel. There's different ways to do this depending on your distribution. Pick one of the following sections that fits your needs.
=====RPM Users=====
RPM distributions (Red Hat, Fedora Core, etc) do it by running:
<pre>
#/sbin/new-kernel-pkg --mkinitrd --depmod --install `uname -r`
</pre>
This command will update the currently running kernel with the new driver. If you use yum or rpm to upgrade your kernel, this change will apply to any newer kernel you install. If you don't believe me and want to see all the neat things that run when you install a new kernel run:
<pre>
#rpm -q --scripts kernel
</pre>
You might want to restart your system at this point to make sure that the proper driver has been installed in the kernel and that your devices are listed without calling modprobe, though it shouldn't make a difference.
=====APT Users=====
Sorry, haven't gotten here yet! Google for depmod and your distribution name.
===Formatting the Drives Properly===
Now this is where things get interesting, but not too complex. In order to make software RAID work, we need to make partitions on the devices before the array is built. You can use the bare drive block devices, but using partitions has some benefits and avoids some scary warnings. So, use [http://man-wiki.net/index.php/8:parted parted] if you like command lines or [http://gparted.sourceforge.net/ gpared] if you like GUIs to create a partition on each device. You do not need to format the partitions to any file system. Blank partitions is what you need - the process of creating blank partitions is practically instantaneous.

If you want to create partitions that use the whole drive, and your drives are larger than 2TB you can do something like this to set your drive up to use GPT and create an empty partition (substituting "sda" for your drive, of course):
<pre>
# parted -s -a optimal /dev/sda mklabel gpt -- mkpart primary 1 -1
</pre>

Note that once a drive is configured for GPT, you cannot view information about it with fdisk - you must use parted (or gparted).

===Building the Array===

At this point, we are ready to build the array. This is fairly simple using [http://www.linuxmanpages.com/man8/mdadm.8.php mdadm], which is included in most distributions, including FC. The command to build the array looks like:
<pre>
#/sbin/mdadm --create --level=5 --raid-devices=3 --spare-devices=0 --name=store /dev/md0 /dev/sd[abc]1
</pre>
You will need to chage the level item to match your desired RAID level. See [http://en.wikipedia.org/wiki/Standard_RAID_levels this] if you need a description of RAID levels. If you want spare devices to be automatically controlled by mdadm, note how many devices should be spares. name is the simple name of the array which can be set to anything you like; it is optional. /dev/md0 is the array device; this cannot be changed unless you have already used md0. /dev/sd[abc]1 tells mdadm to use sda1, sdb1, and sdc1 to create the array. Once you run this command, the array will be created. Check the array status by running:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>
The array may be listed as damaged or recreating. This is normal. To create the array for the first time mdadm marks some drives as "bad" to force creation of the array. Monitor the status of the array and wait until it is done building before moving to the next step.

For more information about mdadm, see the [http://man-wiki.net/index.php/8:mdadm man page].

===Set Array to be Available On Boot===

In order to make the array available on boot, the "FD" flag must be set on each partition. FC will detect the "FD" flags and initialize the array automatically. To set the "FD" flag simply run:
<pre>
#/sbin/parted /dev/sda set 1 raid on
</pre>
on each of your devices - substitute /dev/sda with your device.

===Create Filesystem on Array===
<pre>
#/sbin/mkfs -t ext3 /dev/md0
</pre>
Should take care of that. Substitute ext3 for whatever filesystem you want.

===Set up mdadm.conf===

We now need to set up the [http://man-wiki.net/index.php/5:mdadm.conf mdadm.conf] file. This is not really required, but makes troubleshooting easier down the road and allows us to have the system send alerts via e-mail. The easiest way to do this is to start with the detail output, like this:
<pre>
#/sbin/mdadm --detail --scan >> /etc/mdadm.conf
</pre>
Edit the conf file with your favorite editor (in this case I will use vim):
<pre>
#vim /etc/mdadm.conf
</pre>
Review the syntax on the [http://man-wiki.net/index.php/5:mdadm.conf man page] and correct the file. You can use "#" for comments. I also recommend that you define a "MAILADDR" for mdadm to send mail to in the case of a failure. My mdadm.conf looks something like:
<pre>
DEVICE /dev/sd[abc]1

# /dev/md0 is known by it's UID.
ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371

MAILADDR root@somedomain.com
</pre>

===Test mount===

Now the array is completely configured and will be setup on boot without issue. Time to mount it:
<pre>
#mount -t ext3 /dev/md0 /store
</pre>
Substitute whatever filesystem you chose for "ext3", whatever your mdadm device is for "/dev/md0" (if this is your only mdadm array, it will be "/dev/md0"), and wherever you want to mount to for "/store". Assuming that goes well, you can start using your array for storage.

===Add a Line to fstab===

Now we should make the array mount on boot so you don't have to run mount every time you want to use the array.

I recommend that you reboot and re-test the mount before adding an entry to fstab - I had a problem where the array didn't initialize so when fstab was run, I was forced into a file recovery mode, which was unpleasant at best. Once you can prove that the array properly initialized on boot, it is safe to add an entry in fstab.

Once you take care of that, time to add to fstab:

<pre>
#vim /etc/fstab
</pre>

The line that needs to be added looks like:

<pre>
/dev/md0 /store ext3 defaults 0 0
</pre>

Substitute your mdadm device for "/dev/md0", where you want it mounted for "/store", and the file system you chose for "ext3". The rest should stay the same unless you know what you're doing.

That's it! Should work.

==Managing the array==
This section deals with things you do after the array is set up.
===Dealing with Failed Devices===
Oh no! A drive is dead! That's ok, we've got RAID!

For this section, replace "/dev/md0" with your array device, "/dev/sda1" with your failed device, and "/dev/sdd1" with your replacement device. The syntax of your version of mdadm may be slightly different - run "man mdadm" to get a detailed description of mdadm usage if any of this complains about bad arguments.

Check the array to see what's going on:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>

Remove the failed device from the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --fail /dev/sda1
#/sbin/mdadm --manage /dev/md0 --remove /dev/sda1
</pre>

Plug in the new drive and get it ready. You'll need to partition it - see the setup directions for more information. Make sure the replacement partition is at least as big as the failed partition or the rebuild will fail. Once that's done, add the new device to the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --add /dev/sdd1
</pre>
===Migrating the Array to a New System or Installation===
Look into the "--assemble" option. You may have to use "--add" if only some drives come up. It's pretty simple to use - just tell it the right md device and what partitions to assemble into it. For example:
<pre>
#/sbin/mdadm --assemble /dev/md0 /dev/sd[abc]1
</pre>

===Adding Spares===
===SCSI Hot-Swap===
{{Incomplete2|Managing Array Section is basic|Missing directions for APT users}}

Software RAID on FC6

2014-03-01T17:17:33Z

J: /* Create Filesystem on Array */

[[Category:How-To]]
[[Category:FC6]]
[[Category:Linux]]
{|-
| valign="top" |
The document details the steps I had to take to build a software RAID array using mdadm. The document was originally written for Fedora Core 6, but has been updated to cover a wider range of distributions. The process was very tedious and I could not find any one document that gave me enough information to complete the project. I will include all parts of the process from selecting hardware and cabling to building the array and setting it to mount automatically. I will assume the reader has a good knowledge of computer hardware and knows at least a little about SCSI and how to run Linux operating systems. For more information about RAID levels see [http://en.wikipedia.org/wiki/Standard_RAID_levels this]. Feel free to [[Special:Emailuser/J|e-mail me]] with specific questions.
| valign="top" |
[[foto:6123|240]]
|}
<big>NOTE: For this document (and others on this site) Linux commands starting with "$" can be run by any non-root user, those beginning with "#" must be run as root.</big>

==Creating the Array==
===Selecting hard drives, controllers, and cabling===

You can use IDE drives and still follow these instructions perfectly. In fact, it would be much easier if you did use IDE, but SCSI is more reliable, faster, and just plain cooler. If you're interested in going IDE, I'll assume you know how to select, connect, and cable those.

Now, when selecting SCSI drives, go for whatever rotational speed and size spec you feel you need. If you're planning on going for RAID 5, you will need at least (3) drives. I'll discuss RAID types later. Once you select the size and speeds of your drives, it's time to select a connector type. Your three choices are 50-pin, 68-pin, or 80-pin (SCA). I would recommend the 68 or 80-pin configuration for both speed and simplicity. I am using (3) Seagate 181.8GB 7200RPM 80-pin devices.

To run your drives you will need a SCSI controller. Generally you can get a simple PCI controller, unless you have special requirements. I bought a very simple Startech.com PCI controller. It is obviously useless to get a controller with onboard RAID, as we are going to use software for the RAID array - so save your money and get the cheap one. Also, most motherboards that have "onboard RAID" do not actually implement RAID using hardware. Instead, the Windows driver will handle most of the work - effectively making software RAID.

You will also need the proper cable to run your drives. I'd recommend you get a cable with a terminator to make controller configuration easier. Make sure there are enough or more than enough connectors for all your devices. For 50-pin devices, buy a 50-pin cable. For 68 and 80-pin devices, buy a 68-pin cable. 80-pin devices are meant to be put into a hot-swap tray, so you will also need to get an SCA adapter for each device. The SCA adapter provides all the information that a hot-swap rack would including the device ID. It also gives you the ability to hot swap drives after running a few commands. A great place to get cabling and SCA adapters is [http://www.stsi.com STSI]

===Cabling Up and Powering On===

If you're using IDE drives, this doesn't apply to you - just plug them in and go. If you're using a PCI IDE adapter, you might want to check the adapter configuration screen to make sure all the drives were recognized. This information is usually output to the screen during boot, so you might not even have to go into the config.

For the SCSI users, the fun begins. Plug in all your drives, using the SCA adapters if you have 80-pin devices. You will need to set the device id on each drive. This is usually done with some jumpers or switches on the drive unless you're using SCA drives. In that case, you would normally configure them in the hot-swap rack by their position, but if you're like me and too cheap to get one of those, you will set it with a jumper on each SCA adapter. Remember that the controller usually uses an ID of 7, so don't set any drive to that ID. Don't forget to connect the power to each drive!

Once everything is properly cabled, boot up the system. You should see the SCSI adapter card initialize in the boot. Press whatever shortcut key gets you into the device configuration. Poke around in there to make sure all the drives are properly recognized. If they're not, check the jumper settings.

===Getting the Operating System to Recognize the New Drives===

If you are doing a new install of your favorite Linux distribution (i.e. you're not adding the array to an existing installation), the installation process should take care of the rest of the process for you. (I say should, because it didn't for me on my most recent install.) If that's the case, simply follow the on-screen instructions and you'll be all set, stop reading now, bye bye, have fun.

If you already have Linux installed, and the hardware isn't automatically detected on boot, you're in for a treat. First thing to do is get your SCSI controller driver running. In my case, the driver is "initio". You'll have to look around and figure out what yours is. Usually, you can guess it by looking at the manufacturer of the chip on the adapter, Google-ing around, or you can ask for help on a forum or IRC channel. Once you have figured out your driver and installed or compiled it, you should start it by running:
<pre>
#/sbin/modprobe initio
</pre>
replacing "initio" with your own driver name. This should automatically load all dependant modules for SCSI operation. Now, check to see if your drives were initialized by running:
<pre>
#ls /dev/sd*
</pre>
Hopefully, this will return an item for each of your new drives. If not, there was a problem, try again.
====Adding the Driver Permenantly====
Now it's time to add the driver to the kernel. There's different ways to do this depending on your distribution. Pick one of the following sections that fits your needs.
=====RPM Users=====
RPM distributions (Red Hat, Fedora Core, etc) do it by running:
<pre>
#/sbin/new-kernel-pkg --mkinitrd --depmod --install `uname -r`
</pre>
This command will update the currently running kernel with the new driver. If you use yum or rpm to upgrade your kernel, this change will apply to any newer kernel you install. If you don't believe me and want to see all the neat things that run when you install a new kernel run:
<pre>
#rpm -q --scripts kernel
</pre>
You might want to restart your system at this point to make sure that the proper driver has been installed in the kernel and that your devices are listed without calling modprobe, though it shouldn't make a difference.
=====APT Users=====
Sorry, haven't gotten here yet! Google for depmod and your distribution name.
===Formatting the Drives Properly===
Now this is where things get interesting, but not too complex. In order to make software RAID work, we need to make partitions on the devices before the array is built. You can use the bare drive block devices, but using partitions has some benefits and avoids some scary warnings. So, use [http://man-wiki.net/index.php/8:parted parted] if you like command lines or [http://gparted.sourceforge.net/ gpared] if you like GUIs to create a partition on each device. I believe you can use any filesystem you like, however I have only used ext3. Make sure you format the devices in the file system that you want to use on the array. All devices in the array should be the same filesystem. See the [http://man-wiki.net/index.php/8:parted man page for parted] or the homepage for [http://gparted.sourceforge.net/ gpared] for instructions on formatting drives.

For those of you who have dealt with hardware RAID, this is a very strange thing to do. Usually, you would have simply created an array of the blank drives, but software RAID with mdadm doesn't see drives, only partitions.

If you want to create partitions that use the whole drive, and your drives are larger than 2TB you can do this to set your drive up to use GPT and create an empty partition:
<pre>
# parted -s -a optimal /dev/sda mklabel gpt -- mkpart primary 1 -1
</pre>

Note that once a drive is configured for GPT, you cannot view information about it with fdisk - you must use parted (or gparted).

===Building the Array===

At this point, we are ready to build the array. This is fairly simple using [http://www.linuxmanpages.com/man8/mdadm.8.php mdadm], which is included in most distributions, including FC. The command to build the array looks like:
<pre>
#/sbin/mdadm --create --level=5 --raid-devices=3 --spare-devices=0 --name=store /dev/md0 /dev/sd[abc]1
</pre>
You will need to chage the level item to match your desired RAID level. See [http://en.wikipedia.org/wiki/Standard_RAID_levels this] if you need a description of RAID levels. If you want spare devices to be automatically controlled by mdadm, note how many devices should be spares. name is the simple name of the array which can be set to anything you like; it is optional. /dev/md0 is the array device; this cannot be changed unless you have already used md0. /dev/sd[abc]1 tells mdadm to use sda1, sdb1, and sdc1 to create the array. Once you run this command, the array will be created. Check the array status by running:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>
The array may be listed as damaged or recreating. This is normal. To create the array for the first time mdadm marks some drives as "bad" to force creation of the array. Monitor the status of the array and wait until it is done building before moving to the next step.

For more information about mdadm, see the [http://man-wiki.net/index.php/8:mdadm man page].

===Set Array to be Available On Boot===

In order to make the array available on boot, the "FD" flag must be set on each partition. FC will detect the "FD" flags and initialize the array automatically. To set the "FD" flag simply run:
<pre>
#/sbin/parted /dev/sda set 1 raid on
</pre>
on each of your devices - substitute /dev/sda with your device.

===Create Filesystem on Array===
<pre>
#/sbin/mkfs -t ext3 /dev/md0
</pre>
Should take care of that. Substitute ext3 for whatever filesystem you want.

===Set up mdadm.conf===

We now need to set up the [http://man-wiki.net/index.php/5:mdadm.conf mdadm.conf] file. This is not really required, but makes troubleshooting easier down the road and allows us to have the system send alerts via e-mail. The easiest way to do this is to start with the detail output, like this:
<pre>
#/sbin/mdadm --detail --scan >> /etc/mdadm.conf
</pre>
Edit the conf file with your favorite editor (in this case I will use vim):
<pre>
#vim /etc/mdadm.conf
</pre>
Review the syntax on the [http://man-wiki.net/index.php/5:mdadm.conf man page] and correct the file. You can use "#" for comments. I also recommend that you define a "MAILADDR" for mdadm to send mail to in the case of a failure. My mdadm.conf looks something like:
<pre>
DEVICE /dev/sd[abc]1

# /dev/md0 is known by it's UID.
ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371

MAILADDR root@somedomain.com
</pre>

===Test mount===

Now the array is completely configured and will be setup on boot without issue. Time to mount it:
<pre>
#mount -t ext3 /dev/md0 /store
</pre>
Substitute whatever filesystem you chose for "ext3", whatever your mdadm device is for "/dev/md0" (if this is your only mdadm array, it will be "/dev/md0"), and wherever you want to mount to for "/store". Assuming that goes well, you can start using your array for storage.

===Add a Line to fstab===

Now we should make the array mount on boot so you don't have to run mount every time you want to use the array.

I recommend that you reboot and re-test the mount before adding an entry to fstab - I had a problem where the array didn't initialize so when fstab was run, I was forced into a file recovery mode, which was unpleasant at best. Once you can prove that the array properly initialized on boot, it is safe to add an entry in fstab.

Once you take care of that, time to add to fstab:

<pre>
#vim /etc/fstab
</pre>

The line that needs to be added looks like:

<pre>
/dev/md0 /store ext3 defaults 0 0
</pre>

Substitute your mdadm device for "/dev/md0", where you want it mounted for "/store", and the file system you chose for "ext3". The rest should stay the same unless you know what you're doing.

That's it! Should work.

==Managing the array==
This section deals with things you do after the array is set up.
===Dealing with Failed Devices===
Oh no! A drive is dead! That's ok, we've got RAID!

For this section, replace "/dev/md0" with your array device, "/dev/sda1" with your failed device, and "/dev/sdd1" with your replacement device. The syntax of your version of mdadm may be slightly different - run "man mdadm" to get a detailed description of mdadm usage if any of this complains about bad arguments.

Check the array to see what's going on:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>

Remove the failed device from the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --fail /dev/sda1
#/sbin/mdadm --manage /dev/md0 --remove /dev/sda1
</pre>

Plug in the new drive and get it ready. You'll need to partition it - see the setup directions for more information. Make sure the replacement partition is at least as big as the failed partition or the rebuild will fail. Once that's done, add the new device to the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --add /dev/sdd1
</pre>
===Migrating the Array to a New System or Installation===
Look into the "--assemble" option. You may have to use "--add" if only some drives come up. It's pretty simple to use - just tell it the right md device and what partitions to assemble into it. For example:
<pre>
#/sbin/mdadm --assemble /dev/md0 /dev/sd[abc]1
</pre>

===Adding Spares===
===SCSI Hot-Swap===
{{Incomplete2|Managing Array Section is basic|Missing directions for APT users}}

Software RAID on FC6

2014-03-01T17:14:44Z

J: /* Formatting the Drives Properly */

[[Category:How-To]]
[[Category:FC6]]
[[Category:Linux]]
{|-
| valign="top" |
The document details the steps I had to take to build a software RAID array using mdadm. The document was originally written for Fedora Core 6, but has been updated to cover a wider range of distributions. The process was very tedious and I could not find any one document that gave me enough information to complete the project. I will include all parts of the process from selecting hardware and cabling to building the array and setting it to mount automatically. I will assume the reader has a good knowledge of computer hardware and knows at least a little about SCSI and how to run Linux operating systems. For more information about RAID levels see [http://en.wikipedia.org/wiki/Standard_RAID_levels this]. Feel free to [[Special:Emailuser/J|e-mail me]] with specific questions.
| valign="top" |
[[foto:6123|240]]
|}
<big>NOTE: For this document (and others on this site) Linux commands starting with "$" can be run by any non-root user, those beginning with "#" must be run as root.</big>

==Creating the Array==
===Selecting hard drives, controllers, and cabling===

You can use IDE drives and still follow these instructions perfectly. In fact, it would be much easier if you did use IDE, but SCSI is more reliable, faster, and just plain cooler. If you're interested in going IDE, I'll assume you know how to select, connect, and cable those.

Now, when selecting SCSI drives, go for whatever rotational speed and size spec you feel you need. If you're planning on going for RAID 5, you will need at least (3) drives. I'll discuss RAID types later. Once you select the size and speeds of your drives, it's time to select a connector type. Your three choices are 50-pin, 68-pin, or 80-pin (SCA). I would recommend the 68 or 80-pin configuration for both speed and simplicity. I am using (3) Seagate 181.8GB 7200RPM 80-pin devices.

To run your drives you will need a SCSI controller. Generally you can get a simple PCI controller, unless you have special requirements. I bought a very simple Startech.com PCI controller. It is obviously useless to get a controller with onboard RAID, as we are going to use software for the RAID array - so save your money and get the cheap one. Also, most motherboards that have "onboard RAID" do not actually implement RAID using hardware. Instead, the Windows driver will handle most of the work - effectively making software RAID.

You will also need the proper cable to run your drives. I'd recommend you get a cable with a terminator to make controller configuration easier. Make sure there are enough or more than enough connectors for all your devices. For 50-pin devices, buy a 50-pin cable. For 68 and 80-pin devices, buy a 68-pin cable. 80-pin devices are meant to be put into a hot-swap tray, so you will also need to get an SCA adapter for each device. The SCA adapter provides all the information that a hot-swap rack would including the device ID. It also gives you the ability to hot swap drives after running a few commands. A great place to get cabling and SCA adapters is [http://www.stsi.com STSI]

===Cabling Up and Powering On===

If you're using IDE drives, this doesn't apply to you - just plug them in and go. If you're using a PCI IDE adapter, you might want to check the adapter configuration screen to make sure all the drives were recognized. This information is usually output to the screen during boot, so you might not even have to go into the config.

For the SCSI users, the fun begins. Plug in all your drives, using the SCA adapters if you have 80-pin devices. You will need to set the device id on each drive. This is usually done with some jumpers or switches on the drive unless you're using SCA drives. In that case, you would normally configure them in the hot-swap rack by their position, but if you're like me and too cheap to get one of those, you will set it with a jumper on each SCA adapter. Remember that the controller usually uses an ID of 7, so don't set any drive to that ID. Don't forget to connect the power to each drive!

Once everything is properly cabled, boot up the system. You should see the SCSI adapter card initialize in the boot. Press whatever shortcut key gets you into the device configuration. Poke around in there to make sure all the drives are properly recognized. If they're not, check the jumper settings.

===Getting the Operating System to Recognize the New Drives===

If you are doing a new install of your favorite Linux distribution (i.e. you're not adding the array to an existing installation), the installation process should take care of the rest of the process for you. (I say should, because it didn't for me on my most recent install.) If that's the case, simply follow the on-screen instructions and you'll be all set, stop reading now, bye bye, have fun.

If you already have Linux installed, and the hardware isn't automatically detected on boot, you're in for a treat. First thing to do is get your SCSI controller driver running. In my case, the driver is "initio". You'll have to look around and figure out what yours is. Usually, you can guess it by looking at the manufacturer of the chip on the adapter, Google-ing around, or you can ask for help on a forum or IRC channel. Once you have figured out your driver and installed or compiled it, you should start it by running:
<pre>
#/sbin/modprobe initio
</pre>
replacing "initio" with your own driver name. This should automatically load all dependant modules for SCSI operation. Now, check to see if your drives were initialized by running:
<pre>
#ls /dev/sd*
</pre>
Hopefully, this will return an item for each of your new drives. If not, there was a problem, try again.
====Adding the Driver Permenantly====
Now it's time to add the driver to the kernel. There's different ways to do this depending on your distribution. Pick one of the following sections that fits your needs.
=====RPM Users=====
RPM distributions (Red Hat, Fedora Core, etc) do it by running:
<pre>
#/sbin/new-kernel-pkg --mkinitrd --depmod --install `uname -r`
</pre>
This command will update the currently running kernel with the new driver. If you use yum or rpm to upgrade your kernel, this change will apply to any newer kernel you install. If you don't believe me and want to see all the neat things that run when you install a new kernel run:
<pre>
#rpm -q --scripts kernel
</pre>
You might want to restart your system at this point to make sure that the proper driver has been installed in the kernel and that your devices are listed without calling modprobe, though it shouldn't make a difference.
=====APT Users=====
Sorry, haven't gotten here yet! Google for depmod and your distribution name.
===Formatting the Drives Properly===
Now this is where things get interesting, but not too complex. In order to make software RAID work, we need to make partitions on the devices before the array is built. You can use the bare drive block devices, but using partitions has some benefits and avoids some scary warnings. So, use [http://man-wiki.net/index.php/8:parted parted] if you like command lines or [http://gparted.sourceforge.net/ gpared] if you like GUIs to create a partition on each device. I believe you can use any filesystem you like, however I have only used ext3. Make sure you format the devices in the file system that you want to use on the array. All devices in the array should be the same filesystem. See the [http://man-wiki.net/index.php/8:parted man page for parted] or the homepage for [http://gparted.sourceforge.net/ gpared] for instructions on formatting drives.

For those of you who have dealt with hardware RAID, this is a very strange thing to do. Usually, you would have simply created an array of the blank drives, but software RAID with mdadm doesn't see drives, only partitions.

If you want to create partitions that use the whole drive, and your drives are larger than 2TB you can do this to set your drive up to use GPT and create an empty partition:
<pre>
# parted -s -a optimal /dev/sda mklabel gpt -- mkpart primary 1 -1
</pre>

Note that once a drive is configured for GPT, you cannot view information about it with fdisk - you must use parted (or gparted).

===Building the Array===

At this point, we are ready to build the array. This is fairly simple using [http://www.linuxmanpages.com/man8/mdadm.8.php mdadm], which is included in most distributions, including FC. The command to build the array looks like:
<pre>
#/sbin/mdadm --create --level=5 --raid-devices=3 --spare-devices=0 --name=store /dev/md0 /dev/sd[abc]1
</pre>
You will need to chage the level item to match your desired RAID level. See [http://en.wikipedia.org/wiki/Standard_RAID_levels this] if you need a description of RAID levels. If you want spare devices to be automatically controlled by mdadm, note how many devices should be spares. name is the simple name of the array which can be set to anything you like; it is optional. /dev/md0 is the array device; this cannot be changed unless you have already used md0. /dev/sd[abc]1 tells mdadm to use sda1, sdb1, and sdc1 to create the array. Once you run this command, the array will be created. Check the array status by running:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>
The array may be listed as damaged or recreating. This is normal. To create the array for the first time mdadm marks some drives as "bad" to force creation of the array. Monitor the status of the array and wait until it is done building before moving to the next step.

For more information about mdadm, see the [http://man-wiki.net/index.php/8:mdadm man page].

===Set Array to be Available On Boot===

In order to make the array available on boot, the "FD" flag must be set on each partition. FC will detect the "FD" flags and initialize the array automatically. To set the "FD" flag simply run:
<pre>
#/sbin/parted /dev/sda set 1 raid on
</pre>
on each of your devices - substitute /dev/sda with your device.

===Create Filesystem on Array===
<pre>
#/sbin/mkfs -t ext3 /dev/md0
</pre>
Should take care of that. Substitute ext3 for whatever filesystem you want. Make sure it matches what you formatted the drives to in the beginning, or this whole thing might not work.

===Set up mdadm.conf===

We now need to set up the [http://man-wiki.net/index.php/5:mdadm.conf mdadm.conf] file. This is not really required, but makes troubleshooting easier down the road and allows us to have the system send alerts via e-mail. The easiest way to do this is to start with the detail output, like this:
<pre>
#/sbin/mdadm --detail --scan >> /etc/mdadm.conf
</pre>
Edit the conf file with your favorite editor (in this case I will use vim):
<pre>
#vim /etc/mdadm.conf
</pre>
Review the syntax on the [http://man-wiki.net/index.php/5:mdadm.conf man page] and correct the file. You can use "#" for comments. I also recommend that you define a "MAILADDR" for mdadm to send mail to in the case of a failure. My mdadm.conf looks something like:
<pre>
DEVICE /dev/sd[abc]1

# /dev/md0 is known by it's UID.
ARRAY /dev/md0 UUID=3aaa0122:29827cfa:5331ad66:ca767371

MAILADDR root@somedomain.com
</pre>

===Test mount===

Now the array is completely configured and will be setup on boot without issue. Time to mount it:
<pre>
#mount -t ext3 /dev/md0 /store
</pre>
Substitute whatever filesystem you chose for "ext3", whatever your mdadm device is for "/dev/md0" (if this is your only mdadm array, it will be "/dev/md0"), and wherever you want to mount to for "/store". Assuming that goes well, you can start using your array for storage.

===Add a Line to fstab===

Now we should make the array mount on boot so you don't have to run mount every time you want to use the array.

I recommend that you reboot and re-test the mount before adding an entry to fstab - I had a problem where the array didn't initialize so when fstab was run, I was forced into a file recovery mode, which was unpleasant at best. Once you can prove that the array properly initialized on boot, it is safe to add an entry in fstab.

Once you take care of that, time to add to fstab:

<pre>
#vim /etc/fstab
</pre>

The line that needs to be added looks like:

<pre>
/dev/md0 /store ext3 defaults 0 0
</pre>

Substitute your mdadm device for "/dev/md0", where you want it mounted for "/store", and the file system you chose for "ext3". The rest should stay the same unless you know what you're doing.

That's it! Should work.

==Managing the array==
This section deals with things you do after the array is set up.
===Dealing with Failed Devices===
Oh no! A drive is dead! That's ok, we've got RAID!

For this section, replace "/dev/md0" with your array device, "/dev/sda1" with your failed device, and "/dev/sdd1" with your replacement device. The syntax of your version of mdadm may be slightly different - run "man mdadm" to get a detailed description of mdadm usage if any of this complains about bad arguments.

Check the array to see what's going on:
<pre>
#/sbin/mdadm --detail /dev/md0
</pre>

Remove the failed device from the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --fail /dev/sda1
#/sbin/mdadm --manage /dev/md0 --remove /dev/sda1
</pre>

Plug in the new drive and get it ready. You'll need to partition it - see the setup directions for more information. Make sure the replacement partition is at least as big as the failed partition or the rebuild will fail. Once that's done, add the new device to the array:
<pre>
#/sbin/mdadm --manage /dev/md0 --add /dev/sdd1
</pre>
===Migrating the Array to a New System or Installation===
Look into the "--assemble" option. You may have to use "--add" if only some drives come up. It's pretty simple to use - just tell it the right md device and what partitions to assemble into it. For example:
<pre>
#/sbin/mdadm --assemble /dev/md0 /dev/sd[abc]1
</pre>

===Adding Spares===
===SCSI Hot-Swap===
{{Incomplete2|Managing Array Section is basic|Missing directions for APT users}}