| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||
Solution Type Technical Instruction Sure Solution 1009932.1 : SunFire[TM] systems using onboard LSI SAS controller incur disk geometry remapping issues when existing OS on a regular SAS/SATA disk is HW RAIDed
PreviouslyPublishedAs 213614 Description After the creation and installation of an OS image on a regular disk, and subsequently applying Hardware RAID (Either through the LSI BIOS or raidctl command) with another regular disk on the same controller, the filesystem on the the newly created RAID volume would be corrupted due to disk geometry remapping/layout differences. Steps to Follow Steps to Follow If you create filesystem on a regular disk first followed by a HW RAID creation using the onboard LSI SAS controller on certain Sunfire[TM] machines, filesystem integrity issue would be encountered due to the difference in geometry layout between the regular disk and the newly created RAID volume. The main cause of the filesystem integrity issue is due to the the differences in the the data (super-blocks, inodes, etc ...) on the filesystem are being presented to the OS. A simple analogy here, an 20x4 cells array and 16x5 cells array, even though having the same total number of cells, data on cell(1,1) on the 20x4 array would be different from 16x5 array. The creation flow below is NOT supported. x64 machines: ------------- Install OS (Regular disk X) | +-->LSI BIOS | +-->create RAID1 volume (Using the regular disk X and other disks on the same controller) Sparc Machines: --------------- Install OS (Regular disk X) | +-->Alternate boot (boot net/cdrom -s) | +-->raidctl -c (Using the regular disk X and other disks on the same controller) If the regular disk contains the OS image, and after applying the HW RAID, trying to boot from the newly created HW RAID volume would result is a filesystem panic due to filesystem inconsistency caused by the remapping. Therefore, creating a HW RAID volume on the onboard SAS controller on certain SunFire machines would result in a inconsistent filesystem. This is NOT a supported method. The officially supported method is to create the RAID volume first followed by the creation of filesystem regardless of whether it is a bootable OS volume or a data volume. Affected Machines: ------------------ x64 machines: SunFire[TM] x4100 SunFire[TM] x4100 M2 SunFire[TM] x4200 SunFire[TM] x4200 M2 SunFire[TM] x4600 SunFire[TM] x4600 M2 SunBlade[TM] x8400 SunBlade[TM] x8420 SunBlade[TM] x6220 SunBlade[TM] x6250 Netra[TM] x4200 M2 Sparc machines: SunFire[TM] V215 SunFire[TM] V245 SunFire[TM] V445 SunFire[TM] T1000 SunFire[TM] T2000 SunFire[TM] T5120 SunFire[TM] T5220 SunBlade[TM] T6300 SunBlade[TM] T6320 Netra[TM] T2000 Product Sun SPARC Enterprise T5220 Server Sun Netra T2000 Server Sun SPARC Enterprise T5120 Server Sun Fire T2000 Server Sun Fire T1000 Server raidctl, LSI, BIOS, 1064 Previously Published As 89622 Change History Date: 2011-05-05 User name: Dencho Kojucharov Action: Currency check Comments: audited by Entry-Level SPARC Content Lead Date: 2007-11-18 User Name: Anthony Rulli Action: Updated Comment:currency check, audited by Anthony Rulli, Entry Level SPARC Content team Attachments This solution has no attachment |
||||||||||||
|
||||||||||||