格式和probe-scsi-all输出之间的不一致

我的平台:SPARC T4-1 solaris 10 Generic_150400-24 sun4v sparc sun4v

当我在控制台cli上时,磁盘1的格式输出看起来不一样,即使相关的磁盘在probe-scsi-all输出的输出中看起来与其他磁盘相同,那么下面的c0t5000CCA07058B9F0d0(输出中的第一个磁盘)可能是错误的吗?

我确实看到在前面板磁盘是绿色的其他人。

奇怪的是,当我从Solaris的CDROM安装菜单中进行solaris 10安装时,也无法识别该磁盘的容量,它显示0 MB(我在下面的例子中添加了来自其他盒子的例子,所以安装菜单中的磁盘名称不同)

# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t5000CCA07058B9F0d0 <HITACHI-H109060SESUN600G-A720-558.91GB> /scsi_vhci/disk@g5000cca07058b9f0 1. c0t5000CCA070584ED8d0 <HITACHI-H109060SESUN600G-A690 cyl 64986 alt 2 hd 27 sec 668> solaris /scsi_vhci/disk@g5000cca070584ed8 2. c0t5000CCA070590CD8d0 <HITACHI-H109060SESUN600G-A690 cyl 64986 alt 2 hd 27 sec 668> solaris /scsi_vhci/disk@g5000cca070590cd8 3. c0t5000CCA070590E10d0 <HITACHI-H109060SESUN600G-A690 cyl 64986 alt 2 hd 27 sec 668> solaris /scsi_vhci/disk@g5000cca070590e10 4. c0t5000CCA0705836F8d0 <HITACHI-H109060SESUN600G-A690 cyl 64986 alt 2 hd 27 sec 668> solaris /scsi_vhci/disk@g5000cca0705836f8 5. c0t5000CCA0705893ECd0 <HITACHI-H109060SESUN600G-A690 cyl 64986 alt 2 hd 27 sec 668> solaris /scsi_vhci/disk@g5000cca0705893ec 6. c0t5000CCA0705955F0d0 <HITACHI-H109060SESUN600G-A690 cyl 64986 alt 2 hd 27 sec 668> solaris /scsi_vhci/disk@g5000cca0705955f0 7. c0t5000CCA07059468Cd0 <HITACHI-H109060SESUN600G-A690 cyl 64986 alt 2 hd 27 sec 668> solaris /scsi_vhci/disk@g5000cca07059468c Specify disk (enter its number): ^C {0} ok probe-scsi-all /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/hub@3/storage@2 Unit 0 Removable Read Only device AMI Virtual CDROM 1.00 /pci@400/pci@2/pci@0/pci@4/scsi@0 FCode Version 1.00.64, MPT Version 2.00, Firmware Version 9.05.00.00 Target 9 Unit 0 Disk HITACHI H109060SESUN600G A720 1172123568 Blocks, 600 GB SASDeviceName 5000cca07059468c SASAddress 5000cca07059468d PhyNum 0 Target a Unit 0 Removable Read Only device TEAC DV-W28S-B AT11 SATA device PhyNum 6 Target b Unit 0 Disk HITACHI H109060SESUN600G A720 1172123568 Blocks, 600 GB SASDeviceName 5000cca0705836f8 SASAddress 5000cca0705836f9 PhyNum 1 Target c Unit 0 Disk HITACHI H109060SESUN600G A720 1172123568 Blocks, 600 GB SASDeviceName 5000cca070584ed8 SASAddress 5000cca070584ed9 PhyNum 2 Target d Unit 0 Disk HITACHI H109060SESUN600G A720 1172123568 Blocks, 600 GB SASDeviceName 5000cca070590cd8 SASAddress 5000cca070590cd9 PhyNum 3 /pci@400/pci@1/pci@0/pci@4/scsi@0 FCode Version 1.00.64, MPT Version 2.00, Firmware Version 9.05.00.00 Target 9 Unit 0 Disk HITACHI H109060SESUN600G A720 1172123568 Blocks, 600 GB SASDeviceName 5000cca07058b9f0 SASAddress 5000cca07058b9f1 PhyNum 0 Target a Unit 0 Disk HITACHI H109060SESUN600G A720 1172123568 Blocks, 600 GB SASDeviceName 5000cca0705893ec SASAddress 5000cca0705893ed PhyNum 1 Target b Unit 0 Disk HITACHI H109060SESUN600G A720 1172123568 Blocks, 600 GB SASDeviceName 5000cca070590e10 SASAddress 5000cca070590e11 PhyNum 2 Target c Unit 0 Disk HITACHI H109060SESUN600G A720 1172123568 Blocks, 600 GB SASDeviceName 5000cca0705955f0 SASAddress 5000cca0705955f1 PhyNum 3 {0} ok ─ Select Disks ───────────────────────────────────────────────────────────────── On this screen you must select the disks for installing Solaris software. Start by looking at the Suggested Minimum field; this value is the approximate space needed to install the software you've selected. For ZFS, multiple disks will be configured as mirrors, so the disk you choose, or the slice within the disk must exceed the Suggested Minimum value. NOTE: ** denotes current boot disk Disk Device Available Space ============================================================================= [X] c0t5000CCA07057269Cd0 572308 MB ) [X] c0t5000CCA070583C94d0 572308 MB ) [X] c0t5000CCA0705862A4d0 572308 MB ) [-] c0t5000CCA070588C7Cd0 0 MB [X] c0t5000CCA07058D0A0d0 572308 MB (F4 to edit ) [ ] c0t5000CCA07058F494d0 572308 MB [ ] c0t5000CCA070590FD0d0 572308 MB [ ] c0t5000CCA0705940C0d0 572308 MB 

我以前遇到过这个,根据我的经验,是因为两个原因之一:

  1. 磁盘与其他磁盘略有不同。 它具有稍微不同的磁盘几何形状,或者已经有一些奇怪或损坏的元信息,阻止Solaris正确读取磁盘几何

  2. 磁盘坏了,失败了,或者很快就会失败。

如果磁盘还没有被使用,我build议用另一个replace它。 我会build议做一个格式/分析读取(或分析写入,如果没有有用的数据)做一个彻底的testing。 如果发现任何错误,请更换磁盘。

如果这是供应商(Oracle?)replace的磁盘,请注意,即使它们可能具有相同的品牌或大小,但它们并不总是使用完全相同的磁盘。 即使标签匹配,驱动器的内部也可能不同。 过去我遇到过很多