In following up the event ID 154, can I narrow down a possible conclusion by way of this datum?

Question

Hi,

there has been noticed in the description of two events the 'physical device object name' to be for two different items represented with the same number e.g. disk 0 describes both storage disk A and storage disk B

e.g. The IO operation at logical block address failed for disk 0,

now this disk in Task Manager will show with number 0 one of the above storage disks but not both.

In Disk Management the same corresponds for one disk only, the disk 0, but how is it possible the event to list as 0 the other storage disk too which has a different 'physical device object name' in Properties/details?

The question at hand is deemed important in relation to event id 154 which occured eventually for a second storage disk.

Answer 1

Hello，

The Windows operating system assigns a numerical identifier to each physical and logical disk it detects, starting with “Disk 0.” However, these identifiers are meant to be unique for each physical disk. If you are seeing “Disk 0” for two different disks, a few situations could be happening:

It’s possible that one of the disks was originally “Disk 0” and then the system renumbered the disks after changes were made to the system, such as adding or removing a disk. However, the event log is referencing the original configuration.

If your system uses a disk controller that abstracts the physical drives (like certain RAID configurations), it’s possible the controller is presenting the drives in a way that causes confusion in the operating system’s disk management subsystem.

You also may check below:

Use Device Manager: Find the drives in Device Manager (devmgmt.msc) and examine the details under the “Properties” menu to see their physical device object names. This could provide additional information.

Use PowerShell or Command Prompt: Run Get-PhysicalDisk, Get-Disk, or diskpart commands to list all the physical disks and their properties for more detailed information.

Best Regards,

Hania Lian

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.

Answer 2

Hi,

I 've found something that is out of place with Get-PhysicalDisk;

one of the well-known drives is listed for CanPool as False. Now this led me to

https://learn.microsoft.com/en-us/powershell/module/storage/reset-physicaldisk?view=windowsserver2022-ps

-then I was having some hard time to determine there if 'the operation clears any lingering Storage spaces data and metadata' is not offering actually the option to re-integrate the disk unless by way of diskpart-erase or diskpart-clean?

Otherwise I could use reset-physicaldisk followed by repair-physicaldisk to set right CanPool? Without backing up the disk first?

By the way, in checking one or two WHEA-Loggers ID 1 that follow up the Event ID 154, I can note the execution process ID 4420 is related to network? [svchost.exe LocalServiceNoNetwork -p] Can that be conciliated with error 154 any more easily than the CanPool False datum as root causes?