UNMOUNTABLE_BOOT_VOLUME (STOP 0xED, status code #2 = 0x185)

[Guest]

Got the infamous UNMOUNTABLE_BOOT_VOLUME message, STOP 0x000000ED on an IBM
Thinkpad T60p.
The second parameter is 0x00000185, of which this page offers virtually no
information:
http://msdn2.microsoft.com/en-us/library/ms797142.aspx

Checking various knowledgebase articles (such as KB297185), they only
explain a few of the codes.
E.g., 0xC0000032 requires a CHKDSK.

Does anyone have a list of codes or can tell me what 0x00000185 is?
The only hint I've found is at the end of this discussion group archive:
http://www.tutorialsall.com/SUPPORT/SUPPORT-37.html

Looks like the disk label (partition table) is not even readable, which
would explain why System (MBR/Stage 1) of the bootloader is working, but Boot
(bootstrap/Stage 2) is not.

I'm about to throw in a Red Hat or Knoppix CD to see if the partition table
is even readable.
If not, I'll use some utilities to recover it (I've had to do this before on
past Windows versions).

Just wanted to confirm if the 2nd parameter is 0x00000185 that it means a
bad disk label.
It would be nice if there was a list of what those numbers mean ... sigh.

 

[db]

http://www.google.com/search?q=0x00...-us&ie=UTF-8&oe=UTF-8&startIndex=&startPage=1
Got the infamous UNMOUNTABLE_BOOT_VOLUME message, STOP 0x000000ED on an IBM
Thinkpad T60p.
The second parameter is 0x00000185, of which this page offers virtually no
information:
http://msdn2.microsoft.com/en-us/library/ms797142.aspx

Checking various knowledgebase articles (such as KB297185), they only
explain a few of the codes.
E.g., 0xC0000032 requires a CHKDSK.

Does anyone have a list of codes or can tell me what 0x00000185 is?
The only hint I've found is at the end of this discussion group archive:
http://www.tutorialsall.com/SUPPORT/SUPPORT-37.html

Looks like the disk label (partition table) is not even readable, which
would explain why System (MBR/Stage 1) of the bootloader is working, but Boot
(bootstrap/Stage 2) is not.

I'm about to throw in a Red Hat or Knoppix CD to see if the partition table
is even readable.
If not, I'll use some utilities to recover it (I've had to do this before on
past Windows versions).

Just wanted to confirm if the 2nd parameter is 0x00000185 that it means a
bad disk label.
It would be nice if there was a list of what those numbers mean ... sigh.

 

[Will Denny]

Hi

Please try the following link to Jim Eshelman's web page - right hand column
(ED)

http://aumha.org/win5/kbestop.htm

--


Will Denny
MS-MVP Shell/User
Please reply to the Newsgroup


Please reply to the Newgroups

 

[Guest]

http://www.google.com/search?q=0x00...-us&ie=UTF-8&oe=UTF-8&startIndex=&startPage=1

I do know how to use Google.
I even know about the Microsoft-specific Google page.
In fact, it was how I found the one article and why I assumed it was a disk
label (partition table) issue.

Unfortunately, it was not a partition table issue -- Linux CDs see it just
fine.

I'm going to try to get the system into the Recovery Console.
I'm always afraid to run CHKDSK /r because I've had so many NTFS filesystems
trash themselves as a result (been using NT since the original 3.1 beta).

 

[Guest]

Hi
Please try the following link to Jim Eshelman's web page - right hand column
(ED)
http://aumha.org/win5/kbestop.htm

Yes, and he sent me to the 2 KB articles I already knew about.
There isn't a good list of what the different status codes mean.
I'm not talking about the STOP code, but the related codes after it.

I.e., from KB297185 ...
http://support.microsoft.com/?kbid=297185

The "0xbbbbbbbb" code is 0x00000185 for this.

Again, according to:
http://msdn2.microsoft.com/en-us/library/ms797142.aspx

That second parameter means:
"The status code from the file system that describes why it failed to
mount the volume"

I have been unable to track down that status code in all my searching.

 

[Guest]

The only info I have seen for 0x00000185 is:
[ From: http://personal.cfw.com/~tkprit/stop/777a_parameters.html ]
"0x00000185 improper termination or bad cabling on SCSI devices"
But that was for a STOP 0x77 or 0x7a message (let alone on an older NT
version).

This is an IBM Thinkpad T60a, using a SATA drive with AHCI.
All cabling is internal, there are no options to change signaling in the BIOS.
Just as a test, I already tried to change from AHCI to "Compatibility" to no
avail.

No software or hardware changes were made at all, the unit just rebooted
with this error.
It's clearly booting, passing Stage 1 (System/MBR) and making it into Stage
2 (Boot/boostrap).
But somewhere the kernel is just barking -- some 30-45s into the boot process.

 

[db]

apparently, you have several other
o.s.'s available and on hand and i would
not hesitate to beleive that they caused
the drive corruption your are experiencing.

i would not waste any time trying to split hairs
and figure out what that particular code is.

instead it would be best to reformat the drive
and reinstall your data from the backups; that
is if the drive is still anygood.
These types of corruption can cause
complete physical failure of the device.

i hate to sound this way, but i always advocate that o.s.'s
need to be installed on seperate harddrives, eventhough
there are those who beleive you can install o.s.'s
sided by side or on seperate partitions on
the same device. Although this is possible, it is risk
that cannot be taken unless precautions have been
taken beforehand. But the worst case scenerio is
the lost of the physical drive having multi o.s.'s

there is nothing to loose by your recovery
console chkdsk option you are considering
to initiate.

and if this fails, then maybe your drive will
have a second chance dedicated for a linux
o.s. or other....

- db

http://www.google.com/search?q=0x00...-us&ie=UTF-8&oe=UTF-8&startIndex=&startPage=1

I do know how to use Google.
I even know about the Microsoft-specific Google page.
In fact, it was how I found the one article and why I assumed it was a disk
label (partition table) issue.

Unfortunately, it was not a partition table issue -- Linux CDs see it just
fine.

I'm going to try to get the system into the Recovery Console.
I'm always afraid to run CHKDSK /r because I've had so many NTFS filesystems
trash themselves as a result (been using NT since the original 3.1 beta).