论坛徽章:: 0

电梯直达

1楼 [收藏(0)] [报告]

发表于 2008-12-01 13:22 |只看该作者 |倒序浏览

------------------------------
# formatSearching for disks...doneAVAILABLE DISK SELECTIONS: 0. c0t0d0 <drive not available: formatting>/sbus@6,0/SUNW,socal@d,10000/sf@0,0/ssd@w210000163787753a,0------------------------------
What does it mean?

Steps to Follow
To understand this message requires explaining some history...
With older disk drives which did not perform automatic bad block reallocation, the Solaris format(1m) utility was used to mark bad blocks and to format disk drives to avoid using those bad blocks.
With modern disk drives, the format(1m) utility is only very, very rarely used to actually perform a format of a disk drive, mainly because modern disk drives perform auto-reallocation of bad blocks (and therefore automatically "retire" that defective piece of media) upon certain read or write errors, without the disk drive needing to be completely re-formatted.
Due to the length of time which a disk drive requires to perform a "Format Unit" command (e.g. some hours, depending on the disk drive capacity and performance), the format(1m) utility is designed to show when a disk drive is formatting, and to allow the user to perform actions against other disk drives during that time. This is why the <drive not available: formatting> message was introduced, to indicate which disks were not available for the format(1m) utility to use, at that particular time.
During formatting (e.g. while it is executing a "Format Unit" command), a disk drive will respond to an "Inquiry" command, but will return an error for almost every other command that is sent to it, including a "Read" command. Typically it will return a "check condition" to the host, with sense key 0x2 (not ready), ASC 0x4, ASCQ 0x4 (logical unit not ready, format in progress).
The format(1m) utility will therefore show the message:
<drive not available: formatting>when the disk drive has responded to an "Inquiry" command, but has returned an error when the utility then attempts to read the label from LBA 0 on the disk. Note: The contents of the disk label are not interpreted at this stage - format(1m) just checks that the "Read" command to LBA 0 is successful. This successful "Inquiry" command, followed by an unsuccessful "Read" command, is the behavior of a disk drive which is in the process of formatting.
However, if the user has not started to format a disk drive, and sees this <drive not available: formatting> message, then it is possible that the disk drive is faulty.
The typical cause is that the disk drive is reporting a "not ready" sense key due to an internal fault. Disk drives in that faulty condition often respond to an "Inquiry", but are unable to respond successfully to a "Read" command - which is very similar behavior to a disk drive while it is performing a "Format Unit" command.
Other less likely causes could include:

The disk drive is reporting an unrecoverable read error on LBA 0; or
The disk drive has just been power-cycled or reset, it is in the process of becoming ready, and will become ready (and able to respond to a "Read" command) within a few seconds.

The format(1m) utility sends all commands to disk drives with the USCSI_SILENT flag set, so no error messages are logged in /var/adm/messages with the default value of sd_error_level (ssd_error_level when using the ssd driver) even if errors do occur. This is to prevent customer concern when some expected errors occur, but this makes it difficult to find the exact cause of the <drive not available: formatting> message.
In some cases, running:
# format -Mmmay be helpful as this reports additional messages about what is happening.
That message may sometimes be reported by format(1m) for a LUN from a disk array, for similar reasons - format(1m) treats a LUN from a disk array just like an individual disk drive. So if a customer runs the format(1m) utility and that disk array LUN responds correctly to an "Inquiry" command, but reports an error for a "Read" command, the same message will be seen from format(1m).
This may occur due to a temporary condition e.g. when the array has just been powered-on or reset. In that case, disk arrays tend to respond quickly to "Inquiry" commands from a host, but they report a sense key of "not ready" for "Read" commands until all of their internal startup processing has been done (which can take a few minutes). If this message from format(1m) is seen from a disk array LUN, even when the disk array has not recently been powered-on or reset, then this requires further investigation on the disk array for possible problems.

Product
Sun StorageTek UniPack Disk DriveSun StorageTek MultiPack-FC Desktop ArraySun StorageTek MultiPack Desktop ArraySun StorageTek D240 RoHS
Sun StorageTek D240 Media TraySun StorageTek D2000 Storage ArraySun StorageTek D2 ArraySun StorageTek D1000 ArraySun StorageTek A3500 FC ArraySun StorageTek A1000 ArraySun StorageTek 3511 SATA Array JBODSun StorageTek 3511 SATA ArraySun StorageTek 3510 FC Array JBODSun StorageTek 3510 FC ArraySun StorageTek 3320 SCSI ArraySun StorageTek 3310 SCSI ArraySun StorageTek 2540 ArraySun StorageTek 1540 FC ArraySun StorageTek 1530 SAS ArraySun StorageTek 2530 ArraySun StorageTek 1500 SAS JBODSun StorageTek 3510 2U FC ArraySun StorageTek 3120 SCSI ArraySPARCstorage RSM Array 2000SPARCstorage RSMNetra st D130 Storage Array (DC)Netra st D1000 ArrayNetra st A1000 Array73 GB 10Krpm Serial Attached SCSI Hard Disk Drive for Sun Fire X400073 GB 10Krpm SCSI Hard Disk Drive for Sun Blade 250073 GB 10Krpm SCSI Hard Disk Drive73 GB 10Krpm LVD Drive FRU for Sun StorageTek 331073 GB 10Krpm Fibre Channel Hard Disk Drive500 GB 7200 rpm SATA Disk Drive40 GB 10Krpm Serial ATA Hard Disk Drive for Sun Fire X400036 GB 15Krpm FC Hard Disk Drive36 GB 10Krpm Serial Attached SCSI Hard Disk Drive for Sun Fire X4000146 GB 15Krpm U320 SCSI Hard Disk Drive for Sun StorageTek 3120146 GB 15Krpm SCSI Hard Disk Drive for Netra 240/440146 GB 15Krpm Fibre Channel Hard Disk Drive for Sun StorageTek 3510146 GB 10Krpm SCSI Hard Disk Drive for Sun Blade 2000146 GB 10Krpm Fibre Channel Hard Disk DriveSun StorageTek T3+ ArraySun StorageTek T3 ArraySun StorageTek A5200 ArraySun StorageTek A5100 ArraySun StorageTek A5000 ArraySun StorageTek A3500 ArraySun StorageTek A3000Sun StorageTek 6940 ArraySun StorageTek 6920 SystemSun StorageTek 6540 ArraySun StorageTek 6140 ArraySun StorageTek 6130 Array (SATA)Sun StorageTek 6130 ArraySun StorageTek 3120 SCSI ArraySun StorageTek FlexLine 300 Series Storage Systems73 GB 15Krpm SCSI Hard Disk Drive for Sun StorageTek 3310 SCSI Array73 GB 15Krpm SCSI Hard Disk Drive for Sun Fire V44073 GB 15Krpm SCSI Hard Disk Drive for Netra 24036 GB 15Krpm SCSI Hard Disk Drive36 GB 10Krpm SCSI Hard Disk Drive146 GB 15Krpm SCSI Hard Disk Drive for Sun StorageTek 6130Sun StorageTek A7000 ArraySun StorageTek 9990 SystemSun StorageTek 9990 NAS BladeSun StorageTek 9985 SystemSun StorageTek 9980 SystemSun StorageTek 9980 High Density CacheSun StorageTek 9970 SystemSun StorageTek 9970 High Density CacheSun StorageTek 9960 SystemSun StorageTek 9910Sun StorageTek 9900V Series ArraySun StorageTek 9900 Service ProcessorSun StorageTek 9900 Entry Level Disk AdapterSun StorageTek 9900 16-Port Channel AdapterSun StorageTek 999073 GB 15Krpm FCAL Hard Disk Drive300 GB 10Krpm Hard Disk Drive for Sun StorageTek 9990146 GB 10Krpm SCSI Hard Disk Drive for Sun Fire V440146 GB 10Krpm SCSI Hard Disk Drive for Netra st A1000/D1000 and Sun StorageTek S1