Server model: Blade HS22
OS: Windows 2k8 Enterprise Edition R2 SP1 x64
System nature: 1 of the 2 nodes of a MS SQL Server 2k8 cluster
As shown in screenshot, we found a removable drive F:.
Is it something created by the server's built-in tool or firmware?
It's 100Mb size, 17Mb free.
No USB device in inserted into the Blade server rack. No DVD in the DVD-rom. And our blade is not the one connected to the rack's media tray.
It's not a Windows mapped network drive, because there is no "disconnect" option when you right-click it in Windows Explorer.
The files inside seems to be something from IBM.
The file version.ini contains "IBM ToolsCenter Preboot Environment"
We checked the "Install Date" of this "Removable Device". During that week, we have run some memory test by the server built-in tool. I mean the tool that when you boot up the sever, it prompt you to press F2 (or F-something, whatever) to enter, then some Linux-like screens show up, then you get some options for system testing. I don't know if this is related? But this is not the only server that I have run the tool, yet this is the only server with an unknown drive now.
Just want to confirm what this drive is.
This topic has been locked.
4 replies Latest Post - 2013-03-14T22:14:36Z by SystemAdmin
Pinned topic Unknown removable drive found in Windows
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-03-14T22:14:36Z at 2013-03-14T22:14:36Z by SystemAdmin
Re: Unknown removable drive found in Windows2013-03-12T07:03:40Z in response to SystemAdminOne more screenshot. Windows Disk Management.
When right-click the drive --> properties, it show "IMM Virtual Floopy USB Device"
gez 1100008592275 Posts
Re: Unknown removable drive found in Windows2013-03-14T04:14:57Z in response to gez> gez wrote:
> You have mounted something to the blades cKVM feature and did not unmount it. Try rebooting the AMM, if that does not work, reseat the blade
Rebooted the AMM, no help.
Might try to reseat the blade later. But meanwhile it's in production state and can't be rebooted.