User manual

ManualsBrandsSeagate ManualsAutomobile AccessoriesST3655N

Using S.M.A.R.T. Disk Monitor 47

7 SATA 50-05-0C-C1-01-AB-C7-00 50-05-0C-C1-01-AB-C7-07

8 SATA 50-05-0C-C1-01-AB-C7-00 50-05-0C-C1-01-AB-C7-08

9 SATA 50-05-0C-C1-01-AB-C7-00 50-05-0C-C1-01-AB-C7-09

10 SATA 50-05-0C-C1-01-AB-C7-00 50-05-0C-C1-01-AB-C7-0A

11 SATA 50-05-0C-C1-01-AB-C7-00 50-05-0C-C1-01-AB-C7-0B

1.15 Flash Firmware

This feature, introduced in build 1.22, allows you to flash firmware on selected SCSI, SAS, and Fibre channel family

peripherals. It is not limited to disk drives.

Usage

smartmon-ux -flash [-confirm] FirmwareImageFile Device_list

If you provide the name of more than one device in the list, the program will continue to flash all devices in the list,

after the first disk is flashed. If there is a problem with flashing any disk, the program immediately terminates with an

appropriate error message. (If it is a result of a disk error, sense information will be provided to lend insight into the

problem).

Example (Flashing a 73 GB Seagate U320 Cheetah disk with Firmware revision "0005"

[root@rh90 smartmon]# ./smartmon-ux -flash /tmp/0005.LOD /dev/sdc

Discovered SEAGATE ST373307LC S/N "3HZ0381E" on /dev/sd2 (Not Enabling SMART)(70007 MB)

****************************************************************************************

* Warning: You have instructed the operating system to flash firmware. No checks will *

* be made to verify that the device you plan to flash isn't mounted or in *

* use in any way. *

* *

* Once the firmware image has been uploaded, then it may take a few minutes *

* for the target device to save the new firmware and reboot. If you are *

* flashing a disk drive then it will spin down then up. Some devices are *

* vulnerable during this phase, and if you lose power during the reboot, *

* then they may be left without a valid firmware image, and will effectively *

* become brain-dead. SANtools, Seagate, and other vendors formally specify *

* that you back up data before flashing firmware, and insure you have a UPS *

* to prevent power loss. *

* *

* If you provided a list of targets to flash, then they will be processed *

* in order, once each target device reboots after a successful update. *

* *

* As disks will appear dead to the O/S during the reboot, then you may see *

* some error messages, and have to force a device discovery. *

* *

* (LINUX typically requires you to rmmod and insmod the device driver, so *

* if you are booted to the same controller you are flashing disks on, then *

* you'll probably have to reboot the computer once all disks have spun up.) *

* *

* You should also record all mode page settings before and after the flash *

* and make appropriate changes before placing the disk back in service. *

* *

* If you are attempting to flash an unsupported disk, or one pre-loaded with *

* OEM firmware that relabels the disk's vendor/product IDs so it reports *

* it is made by another company, such as Dell, EMC, NetApp, or SUN, then *

* there is no guarantee that the image will be loaded. If the new firmware *

* is rejected by the disk, then SMARTMon-UX will return with an appropriate *

* error message. *

****************************************************************************************

Are you sure you want to do this, and is your data backed up? Answer "YES"

Do you wish to attempt to flash firmware temporarily, so the drive will revert to the original

firmware release once the disk is power-cycled? This should be done if there is any

doubt of compatibility. (Not all disks and firmware release accept this technique).

Flashing ................................. Sending final chunk - Completed