Funny thing.....
After a couple of reboots, they're gone - all I see are the ones I expected. Kurt On Mon, Oct 17, 2016 at 12:08 PM, Michael B. Smith <[email protected]> wrote: > I would check for snapshots (vssadmin or diskshadow) and disk filters (fltmc). > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Kurt Buff > Sent: Sunday, October 16, 2016 11:59 PM > To: ntsysadm > Subject: [NTSysADM] Volume GUIDs with no volumes? > > I'm seeing a large number of errors in the event log of our file server, and > they reference a number of GUIDs for which there seem to be no matching > volumes. > > This makes a fair amount of sense - we've recently refactored our drives, and > in the process eliminated all of our iSCSI presentations for this server, > replacing them with VMDKs - as you have figured out by now, we're a VMware > shop. > > The eventIDs are below - there are several of each error/warning, one set per > GUID that doesn't match a volume. The question in my mind is "how do I get > rid of the references to the missing volume?" > > Log Name: Application > Source: SRMSVC > Date: 2016-10-14 04:34:08 > Event ID: 8197 > Task Category: None > Level: Error > Keywords: Classic > User: N/A > Computer: usfs01p.example.com > Description: > File Server Resource Manager Service error: Unexpected error. > > Error-specific details: > Error: > FlushFileBuffers(\\?\Volume{72a635ee-91ff-11e6-8104-005056b43cf4}\System > Volume Information\SRM\FciNrt.usn), 0x80070001, Incorrect function. > > And > > Log Name: Application > Source: SRMSVC > Date: 2016-10-14 04:33:58 > Event ID: 8228 > Task Category: None > Level: Warning > Keywords: Classic > User: N/A > Computer: usfs01p.example.com > Description: > File Server Resource Manager was unable to access the following file > or volume: > '\\?\Volume{72a635ef-91ff-11e6-8104-005056b43cf4}\System Volume > Information\SRM\FciNrt.usn'. This file or volume might be locked by another > application right now, or you might need to give Local System access to it. > > And > > Log Name: Application > Source: SRMSVC > Date: 2016-10-09 04:33:10 > Event ID: 8249 > Task Category: None > Level: Warning > Keywords: Classic > User: N/A > Computer: usfs01p.example.com > Description: > File Server Resource Manager was unable to access a file or volume. > Details: > \\?\Volume{fa7b8e04-8e11-11e6-8104-005056b43cf4}\System Volume > Information\SRM\FciNrt.usn > The volume may be inaccessible for I/O operations or marked > read-only. In case of a cluster volume, this may be a transient failure > during failover. > >
