Event 158, disk

So I woke up this morning and found that my computer was locked up
attempting to do last night's backups. Was barely able to login, as the
computer was so unresponsive. Saw that the drive D was 100% busy, but
nothing was happening. Eventually just hard reset the computer.

After restarting went into Event Viewer and found the following Warning
entry:

Event 158, Disk
Disk 5 has the same disk identifiers as one or more disks connected to
the system. Go to Microsoft's support website
(http://support.microsoft.com) and search for KB2983588 to resolve the
issue.

I haven't installed the KB2983588 yet, but I'm wondering if this is just
one of those transient problems, and if I should wait for it happen
again? It's the first and only time it's ever happened. I'm only
concerned because this drive is my newest SSD, just bought a month back,
and it holds my Users folder.

I went into diskpart to list the ID's of the disks, and they all seemed
unique to me:

Disk# UniqueID
0 A54E0AAD
1 017223AD
2 {D4D7B513-568D-4519-8923-6CC1B5A59849}
3 E7D4A19D
4 {9004AA28-B314-4ED3-A222-156DEA8AB86E}
5 B39FEBF9

The drive D is disk 5.

Yousuf Khan

Yousuf Khan wrote:
So I woke up this morning and found that my computer was locked up
attempting to do last night's backups. Was barely able to login, as the
computer was so unresponsive. Saw that the drive D was 100% busy, but
nothing was happening. Eventually just hard reset the computer.

After restarting went into Event Viewer and found the following Warning
entry:

Event 158, Disk
Disk 5 has the same disk identifiers as one or more disks connected to
the system. Go to Microsoft's support website
(http://support.microsoft.com) and search for KB2983588 to resolve the
issue.

I haven't installed the KB2983588 yet, but I'm wondering if this is just
one of those transient problems, and if I should wait for it happen
again? It's the first and only time it's ever happened. I'm only
concerned because this drive is my newest SSD, just bought a month back,
and it holds my Users folder.

I went into diskpart to list the ID's of the disks, and they all seemed
unique to me:

Disk# UniqueID
0 A54E0AAD
1 017223AD
2 {D4D7B513-568D-4519-8923-6CC1B5A59849}
3 E7D4A19D
4 {9004AA28-B314-4ED3-A222-156DEA8AB86E}
5 B39FEBF9

The drive D is disk 5.

Yousuf Khan

So you went into diskpart and did

list disk
select disk 1
detail disk
select disk 2
detail disk
....

and dumped the DiskID for each one that way ?

There are VolumeIDs per partition ( in command prompt "D:" and "vol" )

There is the single DiskID per drive. If two
DiskID values are the same, one of the disks
will go Offline in Disk Management.

When you see a disk which is 100% busy, as long as
it's not your C: drive, you can try running Sysinternals
ProcMon and record all the "ReadFile" and "WriteFile" operations.
The location might hint at what is looping. If the C: drive
is busy, you might not be able to start a program to do
forensics. (Win10 is not "balanced" for recovery, and lots
of things will lock you out.)

I've detected the disk defragmenter on WinXP in a loop,
when it does prefetch optimization. I've not seen Win10
get into quite the same mess.

Paul

On 12/14/2018 9:57 AM, Paul wrote:
Yousuf Khan wrote:
So I woke up this morning and found that my computer was locked up
attempting to do last night's backups. Was barely able to login, as
the computer was so unresponsive. Saw that the drive D was 100% busy,
but nothing was happening. Eventually just hard reset the computer.

After restarting went into Event Viewer and found the following
Warning entry:

Event 158, Disk
Disk 5 has the same disk identifiers as one or more disks connected to
the system. Go to Microsoft's support website
(http://support.microsoft.com) and search for KB2983588 to resolve the
issue.

I haven't installed the KB2983588 yet, but I'm wondering if this is
just one of those transient problems, and if I should wait for it
happen again? It's the first and only time it's ever happened. I'm
only concerned because this drive is my newest SSD, just bought a
month back, and it holds my Users folder.

I went into diskpart to list the ID's of the disks, and they all
seemed unique to me:

Disk# UniqueID
0 A54E0AAD
1 017223AD
2 {D4D7B513-568D-4519-8923-6CC1B5A59849}
3 E7D4A19D
4 {9004AA28-B314-4ED3-A222-156DEA8AB86E}
5 B39FEBF9

The drive D is disk 5.

Yousuf Khan

So you went into diskpart and did

list disk
select disk 1
detail disk
select disk 2
detail disk
...

and dumped the DiskID for each one that way ?

DISKPART select disk 0
DISKPART uniqueid disk
DISKPART select disk 1
DISKPART uniqueid disk

Etc.

Since posting my original question, I've since rebooted the machine, and
it looks like there is now more error messages now. Looks like the the
drive itself is going down. Lots more error messages all related to the
drive. So it looks like it's not just a one off error message.

Yousuf Khan

On 12/14/2018 2:03 PM, Yousuf Khan wrote:
Since posting my original question, I've since rebooted the machine, and
it looks like there is now more error messages now. Looks like the the
drive itself is going down. Lots more error messages all related to the
drive. So it looks like it's not just a one off error message.

Yousuf Khan

I've done several tests on the SSD, and not once has the SSD upped any
of its SMART bad sector counts. What's the point in even putting SMART
on an SSD then?

Yousuf Khan

In article , bbbl67
@spammenot.yahoo.com says...

On 12/14/2018 2:03 PM, Yousuf Khan wrote:
Since posting my original question, I've since rebooted the machine, and
it looks like there is now more error messages now. Looks like the the
drive itself is going down. Lots more error messages all related to the
drive. So it looks like it's not just a one off error message.

Yousuf Khan

I've done several tests on the SSD, and not once has the SSD upped any
of its SMART bad sector counts. What's the point in even putting SMART
on an SSD then?

Yousuf Khan

At this point I'd be thinking

1 - insure have an image,
2 - reformat disk,
3 - run chkdsk with bad sector scan turned on,
4 - retore image check what's happening.

Still have problem I'd then try a clean install.

Still have a problem then I'd likely just throw disk away but I might
try another OS just to see if it's something unique, e.g. try XP or
Vista rather than Win 7

pjp wrote:
In article , bbbl67
@spammenot.yahoo.com says...
On 12/14/2018 2:03 PM, Yousuf Khan wrote:
Since posting my original question, I've since rebooted the machine, and
it looks like there is now more error messages now. Looks like the the
drive itself is going down. Lots more error messages all related to the
drive. So it looks like it's not just a one off error message.

Yousuf Khan
I've done several tests on the SSD, and not once has the SSD upped any
of its SMART bad sector counts. What's the point in even putting SMART
on an SSD then?

Yousuf Khan

At this point I'd be thinking

1 - insure have an image,
2 - reformat disk,
3 - run chkdsk with bad sector scan turned on,
4 - retore image check what's happening.

Still have problem I'd then try a clean install.

Still have a problem then I'd likely just throw disk away but I might
try another OS just to see if it's something unique, e.g. try XP or
Vista rather than Win 7

On hard drives, spares tend to be located next to the
defective sector.

On SSDs, there's a pool of spares, and storage inside
is "mapped". The LBAs inside are not used in order.
Virtual sector 0 could be physical sector 1234
while virtual sector 1 could be physical sector 5678.

In other words, the spares pool can be applied like
spackle, where ever they're needed.

It's only when all spares are exhausted, that you'd
expect to see CRC errors while scanning like that.

Death on a hard drive, is going to be a bit more mushy.
You might have a "bad patch" on a hard drive, that
just resizing the partitions to avoid the patch, might
gain you some usage from the drive.

Whereas an SSD, things are more centralized, and when
it "takes a dump", it's for good. There's no formatting
tricks to squeeze three glasses of lemonade from
a two glass SSD pitcher.

If you can find the SMART readout tool, I bet there *is*
information in there that can hint that it's time to
kick that drive to the curb.

Paul

On 12/15/2018 11:11 PM, pjp wrote:
At this point I'd be thinking

1 - insure have an image,

Actually, that's exactly how I found out I had a problem. When I woke up
one morning, I found that that night's backups process had become stuck
trying to read a single file. The same previous night's backups worked
exactly as before, so at least I had the 1 day old backups to restore from.

2 - reformat disk,
3 - run chkdsk with bad sector scan turned on,
4 - retore image check what's happening.

I even ran a disk sector scanner, and that got stuck too!

At this point there's no point in doing any more tests, it's obvious
that the drive has gone bad. I'm just awaiting an RMA number to be sent
to me. Fortunately I still had enough space left on an older HDD to move
all of the data from that SSD onto it. I also had backups of all of the
data on that SSD, so I had to restore from those backups, as the SSD was
completely useless in doing a copy from.

Yousuf Khan

On 12/15/2018 11:31 PM, Paul wrote:
If you can find the SMART readout tool, I bet there *is*
information in there that can hint that it's time to
kick that drive to the curb.

No, there isn't, that's why I brought it up. I looked at it through the
SMART readout tool, and no values had gone up at all, even while all of
this time it was sitting there stuck trying to read from a sector.

Yousuf Khan

Yousuf Khan wrote:
On 12/15/2018 11:31 PM, Paul wrote:
If you can find the SMART readout tool, I bet there *is*
information in there that can hint that it's time to
kick that drive to the curb.

No, there isn't, that's why I brought it up. I looked at it through the
SMART readout tool, and no values had gone up at all, even while all of
this time it was sitting there stuck trying to read from a sector.

Yousuf Khan

Only some of the counters count events. The "CRC error" one for
the SATA cable, counts events. The others can represent a "thresholded"
value. Which reads zero most of the time, until the drive is in deep trouble.

'ID', 'Description', 'Raw', 'Normalized', 'Threshold', 'Action'
05, Vendor Specific, 0, 100, 0, Ready for use.
09, Power Hours, 19, 100, 0, Ready for use.
0C, Power Cycle, 27, 100, 0, Ready for use.
AA, Available Reserved Space, 0, 100, 10, Ready for use.
AB, Program Fail Count, 0, 100, 0, Ready for use.
AC, Erase Fail Count, 0, 100, 0, Ready for use.
AD, Vendor Specific, 131072, 100, 5, Ready for use.
, Minimum erase cycles, 0, , ,
, Maximum erase cycles, 2, , ,
, Average erase cycles, 0, , ,
AE, Unexpected Power Loss 4, 100, 0, Ready for use.
B7, SATA Downshift Count, 0, 100, 0, Ready for use.
B8, End-to-End Error Detection 0, 100, 90, Ready for use.
BB, Uncorrectable Error Count, 0, 100, 0, ===
BE, Temperature, 68721770516, 20, 0, Ready for use.
C0, Unsafe Shutdown Count, 4, 100, 0, Ready for use.
C7, CRC Error Count, 0, 100, 0, Ready for use.
E1, Host Writes, 448.41 GB, 100, 0, Ready for use.
E2, Timed Workload - Media Wear, 0, 100, 0, Ready for use.
E3, Timed Workload - Host R:W 0, 100, 0, Ready for use.
E4, Timed Workload Timer, 0, 100, 0, Ready for use.
E8, Available Reserved Space, 0, 100, 10, Ready for use.
E9, Media Wearout Indicator, 0, 100, 0, Ready for use.
EC, Unknown 0, 100, 0,
F1, Total LBAs Written, 448.41 GB, 100, 0, Ready for use.
F2, Total LBAs Read, 867.72 GB, 100, 0, Ready for use.
F9, Total NAND Writes, 443, 100, 0, Ready for use.
FC, Vendor Specific, 0, 100, 0,

It's pretty funny for the tool provided by the manufacturer
to not be able to decode the "Vendor Specific" fields, which
it could just ignore instead.

The SMART in the drive also supports test calls
from applications like the toolbox. The "generic long"
is a read test for example. If any sectors are reading
bad, perhaps the stupid tool will do a better job of
reporting than the SMART static table will. It also has the
option (of course), of saying "Pass" instead of giving
an error count.

https://i.postimg.cc/NfzvWZPs/diagnostic-scan.gif

It's possible the tests in question, can be run from
smartctl in Linux, from the command line. If you thought
a third-party tool would be more apt to give proper results.
(smartmontools package).

Paul