Seagate ST3655N Bedienungsanleitung Seite 11

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 263
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 10
Using S.M.A.R.T. Disk Monitor 5
SANTOOLS® is registered in US Patent and Trademark Office No 3,107,854 All rights reserved.
Not all disk drives support the performance bit (also known as PERF bit). SMARTMon will let the user know if
there is a problem setting this value.
· The S.M.A.R.T. polling interval is the internal interval programmed into the disk drive. This is set to 10 minutes,
unless changed via the command line option -F .
· The disk is checked to see if it supports optional SMART and temperature reporting log pages. If so, they are
read to establish a baseline.
· Device information is displayed and placed into log file in format specified in command-line operations or
defaults. Since SCSI and Fibre channel support devices other than disk drives, all devices discovered are
reported. Of course, only disk drives with non-removable media are monitored.
· If a disk supports SES (SCSI Enclosure Services), it marks the drive as one which might be capable of
communicating with a SES enclosure, provided the -E flag is set.
· Note: The LINUX operating system has a hard limit of 4KB worth of data that can be sent to a /dev/sd* driver.
The 4KB limitation will only affect operations such as reading an extremely long log page (which would typically
be vendor/device specific), or reading a long defect list (using the -Y) command. If you prefer, as of release
1.21, you can also interact with a peripheral that uses the /dev/sg type driver. Our code will allow up to a
64KB transfer, provided your LINUX kernel allows it. We did not design this software to use the sg class driver
as LINUX has no reliable method to insure a successful cross-reference to a physical device. Whenever you
system boots, it will assign sg class drivers in any order it wishes. We suggest you do not use sg class drivers
unless specifically told to use them because a particular command failed.
· (Added in 1.23D) The program now insures I/O will be sent to any device specifically entered on the
command-line. This was done to facilitate discovery of devices behind Intel and other's zero-channel
RAID cards, which generally report the back-end disks under device /dev/sg type drivers. I.e., if you
enter ./smartmon-ux -I /dev/sda /dev/sg0 /dev/sg[3-5], then it will poll /dev/sga, /dev/sg0, /dev/sg3,
/dev/sg4, and /dev/sg5. This may result in a duplicate entry as /dev/sda would normally be mapped to
/dev/sg0, but this is only way to detect disks masked by a RAID engine.
· Important: The LINUX operating system is in process of phasing out support for pass-through SCSI
commands to /dev/sd class drivers, so even though this software allows you to perform most actions
on a particular device using the /dev/sd class driver, you need to get in habit of using /dev/sg class
driver.
Device Initialization Phase (SPARC and Intel Solaris):
· The program builds a list of device candidates by searching the /dev/rdsk/*s0, /dev/es, /dev/osa/dev/rdsk/*s0,
/dev/rmt/*mn, /dev/scsi/*/* directories and parsing out the SCSI and fibre channel device and enclosure which are
valid. It will also report whether a disk is an IDE device, and if it will have to be skipped.
Device Initialization Phase (Tru64):
· The program builds a list of device candidates by searching the wild-cards: /devices/disk/*disk*a,
/devices/disk/cdrom?a, /devices/tape/tape? and /devices/changer/?.
Device Initialization Phase (VMS):
· The program builds a list of device candidates by issuing the SHOW DEVICES command, then tossing any device
that has a "$" character in it. Then it examines the remaining entries and ignores them unless they show as having
an online or mounted state.
Device Initialization Phase (Microsoft Windows® family operating systems):
· The program searches for assigned physical disks at \\.\PHYSICALDRIVE0 through \\.\PHYSICALDRIVE127. This
will result in discovering all disk drives which have been assigned a drive letter. It then searches for unconfigured
devices by searching the list of \\.\SCSI0 - \\.\SCSI16. Other devices are discovered \\.\TAPE0 - \\.\TAPE15,
\\.\SCANNER0 - \\.\SCANNER7, then \\.\CDROM0 ..\\.\CDROM15.
· We addressed a serious bug that prevented some devices from being discovered if attached to Emulex LP9002,
and some JNI HBAs, depending on the driver levels. The problem was that these controllers/drivers might map
more than one device to a \\.\SCSI type driver. Because of this, we now also query the host adapters to discover
devices under all ports, paths, IDs, and LUNs for a particular \\.\SCSI class driver. A device appearing on SCSI2 at
Port2, target ID 18, LUN 3 and path0 would be referenced as \\.\SCSI2Port2Path0Target18Lun3. Please see the
device naming conventions topic for additional details.
18
37
235
Seitenansicht 10
1 2 ... 6 7 8 9 10 11 12 13 14 15 16 ... 262 263

Kommentare zu diesen Handbüchern

Keine Kommentare