atacontrol — ATA device driver control program
atacontrol 〈 command〉 args
atacontrol detach channel
atacontrol reinit channel
atacontrol create type [
interleave ] disk0 ... diskN
atacontrol addspare raid disk
atacontrol rebuild raid
atacontrol status raid
atacontrol mode channel [mastermode slavemode]
atacontrol info channel
atacontrol cap channel device
atacontrol enclosure channel device
The atacontrol utility is a control program that provides the user access and control to the FreeBSD ata(4) subsystem.
The atacontrol utility can cause severe system crashes and loss of data if used improperly. Please exercise caution when using this command!
The channel argument is the number of the ATA channel on which to operate. The following commands are supported:
Attach an ATA channel. Devices on the channel are probed and attached as is done on boot.
Detach an ATA channel. Devices on the channel are removed from the kernel, and all outstanding transfers etc. are returned back to the system marked as failed.
Reinitialize an ATA channel. Both devices on the channel are reset and initialized to the parameters the ATA driver has stored internally. Devices that have gone bad and no longer respond to the probe, or devices that have physically been removed, are removed from the kernel. Likewise are devices that show up during a reset, probed and attached.
Create a type ATA RAID. The type can be RAID0 (stripe), RAID1 (mirror), RAID0+1 or SPAN (JBOD). In case the RAID has a RAID0 component, the interleave must be specified in number of sectors. The RAID will be created of the individual disks named disk0 ... diskN.
Although the ATA driver allows for creating an ATA RAID on disks with any controller, there are restrictions. It is only possible to boot on an array if it is either located on a ‘‘real’’ ATA RAID controller like the Promise or Highpoint controllers, or if the RAID declared is of RAID1 or SPAN type; in case of a SPAN, the partition to boot must reside on the first disk in the SPAN.
Delete a RAID array on a RAID capable ATA controller.
Add a spare disk to an existing RAID.
Rebuild a RAID1 array on a RAID capable ATA controller.
Get the status of an ATA RAID.
Without the two mode arguments, the current transfer modes of both devices are printed. If the mode arguments are given, the ATA driver is asked to change the transfer modes to those given. The ATA driver will reject modes that are not supported by the hardware. Modes are given like ‘‘PIO3’’, ‘‘udma2’’, ‘‘udma100’’, case does not matter. If one of the devices mode should not be changed, use a nonexisting mode as argument (i.e. ‘‘XXX’’), and the mode will remain unchanged.
Currently supported modes are: BIOSDMA, PIO0 (alias BIOSPIO), PIO1, PIO2, PIO3, PIO4, WDMA2, UDMA2 (alias UDMA33), UDMA4 (alias UDMA66), UDMA5 (alias UDMA100) and UDMA6 (alias UDMA133).
Show info about the attached devices on the channel. The device name and manufacture/version strings are shown.
Show detailed info about the device on channel device where device is 0 for master and 1 for slave.
Show detailed info about the enclosure on channel device where device is 0 for master and 1 for slave. Fan RPM speed, enclosure temperature, 5V and 12V levels are shown.
Show info about all attached devices on all active controllers.
To see the devices’ current access modes, use the command line:
atacontrol mode 0
which results in the modes of the devices being displayed as a string like this:
Master = WDMA2
Slave = PIO4
This means that ata0-master is in DMA mode, ata0-slave is in PIO mode, and so forth. You can set the mode with atacontrol and a string like the above, for example:
atacontrol mode 0 PIO4 PIO4
The new modes are set as soon as the atacontrol command returns.
The atacontrol utility first appeared in FreeBSD 4.6.
The atacontrol utility was written by Søren Schmidt 〈 sos [AT] FreeBSD.org〉 .
This manual page was written by Søren Schmidt 〈 sos [AT] FreeBSD.org〉 .
BSD May 17, 2001 BSD