Skip to main content

NetApp wins prestigious Coveo Relevance Pinnacle Award. Learn more!

INSIGHT Japan :2023年 1月25日(水)ANAインターコンチネンタルホテル開催 へ参加・申込を行う

NetApp Knowledge Base

SnapCenter does not discover disks when stale MySQL is left behind for old disks

Views:
111
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • SnapCenter Server (SC)
  • SnapCenter Plug-In for Windows (SCW)

Issue

  • Disks are not discovered when attempting to Refresh Disks in the SnapCenter GUI or running Get-SmResources in PowerShell
  • The error below is reported in the SnapManagerWeb.log file

INFO  SnapManagerWeb_JOB_ID PID=[2412] TID=[80] Found StorageFileSystem with LUN serial number <serial number> and mount F:\
INFO  SnapManagerWeb_JOB_ID PID=[2412] TID=[80] StorageFileSystem count: 1
WARN  SnapManagerWeb_JOB_ID PID=[2412] TID=[80] StorageFootprint NOT found for the file system [F:\]. Stale entry [###] is present in nsm_StorageFileSystem.

DEBUG SnapManagerWeb_JOB_ID PID=[2412] TID=[80] Removing storage footprint with id (###) for the file system resource <server name>#F:\
DEBUG SnapManagerWeb_JOB_ID PID=[2412] TID=[80] Removing storage file system (F:\) with id (###) for the resource <server name>#F:\
DEBUG SnapManagerWeb_JOB_ID PID=[2412] TID=[80] Failed to remove file system resource. Details: Cannot delete or update a parent row: a foreign key constraint fails (`nsm`.`nsm_sce_databasefile`, CONSTRAINT `FK_nsm_sce_DatabaseFile_nsm_storagefilesystem` FOREIGN KEY (`nsm_storagefilesystem_id`) REFERENCES `nsm_StorageFileSystem` (`nsm_StorageFileSystem_Id`)

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device