Document Type | Troubleshooting
Category | Installation
Applicable Product Version | 7FS02
Document Number | TINTS009
Issue
This explains the phenomenon where cluster start fails due to mismatched disk scan information when re-registering CM cluster resources and recreating TAS. In such cases, you need to either restart CM to perform disk scan or reconstruct TAS while CM is stopped.
Cause
- During initial setup, TAS Disk Space is configured first before starting CM.
- When CM starts, it caches the TAS Disk Space information at that time and performs disk scan based on this to check disk status.
- If TAS is reconstructed afterwards, comparison between the disk space information cached in CM and the disk information to be scanned fails.
Solutions
Caution
If DB reconstruction is required, do not reconstruct TAS Disk Space while CM is running. You must reconstruct it after stopping CM.
Cases where cluster start succeeds
1. Start CM > Register Resource - public IP, private IP, cluster > Create TAS disk space > cluster start
2. Delete CM Resource file > Start CM > Register Resource > Recreate TAS Disk Space > cluster start
Cases where cluster start fails
3. cluster stop > Recreate TAS Disk Space > cluster delete > cluster add > cluster start
4. cluster delete > Recreate TAS Disk Space > cluster add > cluster start
โ For cases 3 and 4, tbcm must be restarted for cluster start to proceed normally