stockages:ftp [LOBSTER WIKI]

Cette page est en lecture seule. Vous pouvez afficher le texte source, mais ne pourrez pas le modifier. Contactez votre administrateur si vous pensez qu'il s'agit d'une erreur.
====== Stockage du FTP ======

----

Le FTP (alias Serveur Linux 3) est une machine sous Centos 7 avec 5x ST8000NM qui forme un RAID5.\\ 
Le Stockage est géré par une carte Adaptec 6805.

===== Gestion de la carte =====

La gestion se fait par l'application "arcconf".
Elle est trouvable dans ''/usr/StorMan/''.

Pour afficher les informations lancé la commande : ''./arcconf COMMANDE''

==== Liste des Commandes ====

|ATAPASSWORD             | setting password on a physical drive|
|BACKUPUNIT              | operations for Backup unit|
|CONSISTENCYCHECK        | toggles the controller background consistency check mode|
|COPYBACK                | toggles controller copy back mode|
|CPLD                    | performs operations regarding CPLD|
|CREATE                  | creates a logical device|
|DELETE                  | deletes one or more logical devices|
|ERRORTUNABLE            | sets error tunable profiles on the controller|
|EXPANDERLIST            | lists the expanders connected to the controller|
|EXPANDERUPGRADE         | updates expander firmware|
|FAILOVER                | toggles the controller automatic failover mode|
|GETCONFIG               | prints controller information|
|GETEXCEPTION            | gets exceptions on controller,logical and physical devices|
|GETLOGS                 | gets controller log information|
|GETPERFORM              | gets the parameters for a performance mode|
|GETSMARTSTATS           | gets the SMART statistics|
|GETSTATUS               | displays the status of running tasks|
|GETVERSION              | prints version information for all controllers|
|IDENTIFY                | blinks LEDS on device(s) connected to a controller|
|IMAGEUPDATE             | update physical device firmware|
|KEY                     | installs a Feature Key onto a controller|
|LIST                    | lists all controllers connected to the system|
|MODIFY                  | performs RAID Level Migration or Online Capacity Expansion|
|PHYERRORLOG             | displays PHY error logs for controller or device or an expander PHY|
|PLAYCONFIG              | apply the configurations on controller(s) from input XML|
|PRESERVECACHE           | changes the cache preservation settings on the controller|
|RESCAN                  | checks for new or removed drives|
|RESETSTATISTICSCOUNTERS | resets the controller statistics counters|
|ROMUPDATE               | updates controller firmware|
|SAVECONFIG              | saves the controller(s) information XML file|
|SAVESUPPORTARCHIVE      | saves the support archive |
|SEEPROM                 | updates the SEEPROM on the controller|
|SETALARM                | controls the controller alarm, if present|
|SETBIOSPARAMS           | changes adapter BIOS settings|
|SETBOOT                 | marks a device bootable|
|SETCACHE                | adjusts physical or logical device cache mode|
|SETCONFIG               | restores the default configuration|
|SETCONTROLLERMODE       | changes Controller mode settings|
|SETCONTROLLERPARAM      | sets the parameters of the controller|
|SETCUSTOMMODE           | sets the parameters for user defined mode|
|SETMAXCACHE             | adjusts maxCache settings for physical or logical device|
|SETNAME                 | renames a logical device given its logical device number|
|SETNCQ                  | toggles the controller NCQ status|
|SETPERFORM              | changes adapter settings based on application|
|SETPHY                  | reconfigures the phy settings|
|SETPOWER                | power settings for controller or logical device|
|SETPRIORITY             | changes specific or global task priority|
|SETSTATE                | manually sets the state of a physical or logical device|
|SETSTATSDATACOLLECTION  | toggles the controller statistics data collection modes|
|SLOTCONFIG              | lists devices attached to each Slot in an Enclosure|
|SMP                     | sends SMP Commands to Expander|
|TASK                    | performs a task which is applicable on a physical or logical device|
|UNINIT                  | manually uninitializes the physical devices which are raw or ready|
|VERIFYWRITE             | toggles verify write feature on the controller|

==== Commandes Utiles ====

''./arcconf GETSTATUS 1''  -> Permet de voir si une action sur le controler est en cours((type : reconstruction)).\\ 
''./arcconf GETCONFIG 1 '' -> Affiche toutes les informations de la carte, Version, disques, Raid, etc. Si vous ajouter "PD " à la fin de votre commande vous n'aurez que les informations sur les disques.

===== En cas de Disque Defectueux =====
Extrait de [[https://www.thomas-krenn.com/en/wiki/Correcting_Hard_Disk_Failures_with_Adaptec_RAID_Controllers_using_ARCCONF|Thomas Krenn]]

==== Problem ====

A hard disk has failed on a server with an Adaptec RAID controller and ARCCONF has been installed on that server. The consequence of this failure is that the corresponding logical device status has been set to Degraded. Foreseeable causes for a hard disk failure may include:

  * having multiple defective sectors (media errors)
  * not responding within the timeout period set by a command to the controller (timeouts)
Note: RAID controllers and hard disks have mechanisms, which can marginalize individual defective sectors and replace them with sectors from a reserve area. If the number of defective sectors exceeds a certain threshold, the RAID controller will no longer accept the hard disk and it must be replaced.

==== Instructions ====

=== Step 1: Rescan ===

In rare cases, the hard disk might actually be completely fine, but is simply not responding to controller commands in a timely manner (timeouts) and does not really need to be replaced with a new hard disk. For this reason, a rescan should first be performed by the controller.

''ARCCONF RESCAN <Controller#>''

Example:\\ 
''ARCCONF RESCAN 1''\\ 
If the hard disk is still acceptable and does not have any electrical or mechanical errors, the controller will re-discover it and at least list it with the physical devices.

''ARCCONF GETCONFIG <Controller#> PD''

Example:\\ 
''ARCCONF GETCONFIG 1 PD''

== Comment: ==

Because the parameters above produce a very long report for most hard disks, under Linux the report can be reduced to most important information:

''arcconf getconfig 1 pd|egrep "Device #|State\>|Reported Location|Reported Channel|S.M.A.R.T. warnings"''

If the area with the metadata is still ok on the hard disk, it will be listed as a member of the associated logical device again, in most cases. However, the status of the logical device will then remain Degraded, because the hard disk failure has probably left it in an inconsistent state. For this reason, the logical device has to be manually rebuilt.

If the hard disk is no longer detected after the rescan, that may have the following causes:

  * The hard disk may be defective.
  * The cable from the controller to hard disk or backplane may be defective.
  * The backplane may be defective.
  * The controller may be defective.

=== Step 2: Clear und Verify ===

If the hard disk has been recognized again after the rescan from Step 1, a manual rebuild still needs to be performed. For this, the area with the metadata will have to be deleted first.

''ARCCONF TASK START <Controller#> DEVICE <Channel#> <ID#> CLEAR''

Example:\\ 
''ARCCONF TASK START 1 DEVICE 0 0 CLEAR''\\ 
Once this clearing task has been performed, verifying the hard disk is recommended in order to test for defective sectors.

''ARCCONF TASK START <Controller#> DEVICE <Channel#> <ID#> VERIFY''

Example:\\ 
''ARCCONF TASK START 1 DEVICE 0 0 VERIFY''

To repair potentially defective sectors at this time, the VERIFY_FIX option can be used instead of the VERIFY option.

=== Step 3: Rescan Again ===

The hard disk should now be listed as an available drive after the renewed rescan and the rebuild process will start automatically at this time, assuming that the automatic failover feature has been enabled. You can ask if this feature has been enabled using the following command.

''ARCCONF GETCONFIG <Controller#> AD''

Example:\\ 
''ARCCONF GETCONFIG 1 AD''

Enabling or Disabling the Automatic Failover Feature

''ARCCONF FAILOVER <Controller#> <on|off>''

Example:\\ 
''ARCCONF FAILOVER 1 on''

=== Step 4: Designated Hot Spare ===

In the event that the automatic failover feature has not been enabled and you do not want to enable it, the available hard disk can also be designated as a so-called hot spare disk. In this manner, you can assign the available drive to the associated logical device and start the rebuild automatically afterwards.

''ARCCONF SETSTATE <Controller#> DEVICE <Channel#> <ID#> HSP LOGICALDRIVE <LD#>''

Example:\\ 
''ARCCONF SETSTATE 1 DEVICE 0 0 HSP LOGICALDRIVE 1''