inaccessible_boot_device

  • Thread starter Thread starter emmexx
  • Start date Start date
E

emmexx

On my workstation I had 2 HD connected to a RAID card Adaptec 1200A.
There was an array of type raid 1 and everything worked fine.

Last week I bought 2 new HD and I wanted to create a raid 1/0 array.
The adaptec tool to manage the card in w2k pro did not let me create
that kind of array so I rebooted, started the "bios" utility to manage
the card and deleted the array. Rebooted and all partitions on the 2 hds
were lost (I thougth that only the array would be deleted not the
mbr). :-(
Please pity on me!

I tried many tools, but I could not get at least one HD to work as before.

My system before (I use linux notation for partitions):

hde1 fat32 <<<win98se
hde2 fat32 extended
hde3 ntfs <<<data
hde4 ntfs <<<w2k pro
hde5 fat32 <<<data
hde6 ntfs <<<data

the same for the other hd in the array.
I used the boot manager xosl to start win98 and w2k.

After the damage done I tried to use gparted to find out the partitions
on the 2nd hd. A list of partitons was found but the system didn't start.
Then I remembered that xosl has an option to restore mbr, fat, I don't
know for sure, so I restored "something" with xosl on the 2nd hd and:

1. win98 starts
2. w2k pro starts but hangs while booting with INACCESSIBLE_BOOT_DEVICE
- it hangs in consolle mode and in Idontknowthewordinenglish
Modalita' Provvisoria (in italian)
- if I start the pc with w2k cd the setup I can't recover the system
- if I start the pc with w2k cd and enter consolle mode I can
access only partitions 1, 5, 6, while for partitions 4 and 3 I'm shown
the letter C: and G: but when I try to dir on those units I get "error
occurred listing directory entries". CHKDSK gives a similar error.
- if I try to reinstall w2k the setup program says that partitions 3
and 4 are unformatted or damaged.
3. if I start the system from a linux cd I can mount every partition and
all files seem to be ok!!!

On the first hd I made many experiments with gparted, fdisk, testdisk so
I don't what mess there is now on that hd mbr and fat.

This is the output from the program findpart:

first HD:

Disk: 1 Cylinders: 4865 Heads: 255 Sectors: 63 MB: 38162

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0C 63 19277937 9413 0 1 1 1199 254 63 B OK
1200 - 07 63 9638937 4706 1200 1 1 1799 254 63 B OK
0 - 0B 28917063 9638937 4706 1800 1 1 2399 254 63 B OK
0 - 07 38556000 19278000 9413 2400 0 1 3599 254 63 B OK
0 - 07 57834000 20306160 9915 3600 0 1 4863 254 63 B OK

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 9409 8 2 9409 0 0 0 020707 7410
1800 1 33 9404 4 2 9404 0 0 0 020707 3850

Partitions according to partition tables on first harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1 0F 19278000 9639504 4706 1023 15 63 1023 15 63 NB
1200 0 1 1800 7 63 Actual
0 2*07 57834000 20306160 9915 1023 15 63 1023 15 63 OK NB
3600 0 1 4863 254 63 Actual

1200 1 07 63 9639441 4706 1023 15 63 1023 15 63 NB NB
1200 1 1 1800 7 63 Actual

2nd HD:

Disk: 2 Cylinders: 4865 Heads: 255 Sectors: 63 MB: 38162

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0C 63 19277937 9413 0 1 1 1199 254 63 B OK
1200 1 07 63 9638937 4706 1023 15 63 1023 15 63 OK NB
1200 2 05 9639000 9639000 4706 1023 15 63 1023 15 63 1200 NB
1200 - 07 63 9638937 4706 1200 1 1 1799 254 63 B OK
0 - 0B 28917063 9638937 4706 1800 1 1 2399 254 63 B OK
0 - 07 38556000 19278000 9413 2400 0 1 3599 254 63 B OK
0 - 07 57834000 20306160 9915 3600 0 1 4863 254 63 B OK

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 9409 8 2 9409 0 0 0 020707 7410
1800 1 33 9404 4 2 9404 0 0 0 020707 3850

Partitions according to partition tables on second harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1 0B 63 19277937 9413 0 1 1 1023 15 63 NB NB
0 1 1 1199 254 63 Actual
0 2 05 19278000 19278000 9413 1023 15 63 1023 15 63 !! NB
1200 0 1 2399 254 63 Actual
0 3 07 38556000 19277992 9413 1023 15 63 1023 15 63 NB NB
2400 0 1 3599 254 55 Actual
0 4*07 57834000 20306152 9915 1023 15 63 1023 15 63 NB NB
3600 0 1 4863 254 55 Actual

1200 1 07 63 9638937 4706 1023 15 63 1023 15 63 OK NB
1200 1 1 1799 254 63 Actual
1200 2 05 9639000 9639000 4706 1023 15 63 1023 15 63 NB
1800 0 1 2399 254 63 Actual

1800 1 0C 63 9638937 4706 1023 15 63 1023 15 63 NB NB
1800 1 1 2399 254 63 Actual


I tried to understand the output, in particular for hd 2, but it's
beyond my knowledge.

I'd be happy if I could make w2k pro start again or to correct the
partition in order to let it be seen by the w2k cd setup.

I hope somebody can help me. It's really distressing to have all the
files over there and not beeing able to start w2k! :-(

thank you
maxx
 
This is the output from the program findpart:
Click to expand...

Do:

findpart all fp.txt

and mail me the file fp.txt as attached file. I need to see the
operating system version and Findpart version.

If you boot DOS or Windows 98, do only access the C: partition.


Can you mail from another PC at the same location as the problem PC?
 
Svend said:
Do:

findpart all fp.txt

and mail me the file fp.txt as attached file. I need to see the
operating system version and Findpart version.
Click to expand...

Ok, I'll do that.
If you boot DOS or Windows 98, do only access the C: partition.
Click to expand...

I boot from System Rescue CD, a live CD of the gentoo distribution. From
there I can start FreeDos and from there I can access C and start
Findpart. Ok, it's a little bit complicated but it's a long story ... :-)
Can you mail from another PC at the same location as the problem PC?
Click to expand...

If you're asking if I can use another pc to read and write mail: yes I
can. Otherwise I didn't understand your question.

Thank you
maxx
 
On my workstation I had 2 HD connected to a RAID card Adaptec 1200A.
There was an array of type raid 1 and everything worked fine.

Last week I bought 2 new HD and I wanted to create a raid 1/0 array.
The adaptec tool to manage the card in w2k pro did not let me create
that kind of array so I rebooted, started the "bios" utility to manage
the card and deleted the array. Rebooted and all partitions on the 2 hds
were lost (I thougth that only the array would be deleted not the
mbr). :-(
Please pity on me!

I tried many tools, but I could not get at least one HD to work as before.

My system before (I use linux notation for partitions):

hde1 fat32 <<<win98se
hde2 fat32 extended
hde3 ntfs <<<data
hde4 ntfs <<<w2k pro
hde5 fat32 <<<data
hde6 ntfs <<<data

the same for the other hd in the array.
I used the boot manager xosl to start win98 and w2k.

After the damage done I tried to use gparted to find out the partitions
on the 2nd hd. A list of partitons was found but the system didn't start.
Then I remembered that xosl has an option to restore mbr, fat, I don't
know for sure, so I restored "something" with xosl on the 2nd hd and:

1. win98 starts
2. w2k pro starts but hangs while booting with INACCESSIBLE_BOOT_DEVICE
- it hangs in consolle mode and in Idontknowthewordinenglish
Modalita' Provvisoria (in italian)
- if I start the pc with w2k cd the setup I can't recover the system
- if I start the pc with w2k cd and enter consolle mode I can
access only partitions 1, 5, 6, while for partitions 4 and 3 I'm shown
the letter C: and G: but when I try to dir on those units I get "error
occurred listing directory entries". CHKDSK gives a similar error.
- if I try to reinstall w2k the setup program says that partitions 3
and 4 are unformatted or damaged.
3. if I start the system from a linux cd I can mount every partition and
all files seem to be ok!!!

On the first hd I made many experiments with gparted, fdisk, testdisk so
I don't what mess there is now on that hd mbr and fat.

This is the output from the program findpart:

first HD:

Disk: 1 Cylinders: 4865 Heads: 255 Sectors: 63 MB: 38162

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0C 63 19277937 9413 0 1 1 1199 254 63 B OK
1200 - 07 63 9638937 4706 1200 1 1 1799 254 63 B OK
0 - 0B 28917063 9638937 4706 1800 1 1 2399 254 63 B OK
0 - 07 38556000 19278000 9413 2400 0 1 3599 254 63 B OK
0 - 07 57834000 20306160 9915 3600 0 1 4863 254 63 B OK

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 9409 8 2 9409 0 0 0 020707 7410
1800 1 33 9404 4 2 9404 0 0 0 020707 3850

Partitions according to partition tables on first harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1 0F 19278000 9639504 4706 1023 15 63 1023 15 63 NB
1200 0 1 1800 7 63 Actual
0 2*07 57834000 20306160 9915 1023 15 63 1023 15 63 OK NB
3600 0 1 4863 254 63 Actual

1200 1 07 63 9639441 4706 1023 15 63 1023 15 63 NB NB
1200 1 1 1800 7 63 Actual

2nd HD:

Disk: 2 Cylinders: 4865 Heads: 255 Sectors: 63 MB: 38162

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 0C 63 19277937 9413 0 1 1 1199 254 63 B OK
1200 1 07 63 9638937 4706 1023 15 63 1023 15 63 OK NB
1200 2 05 9639000 9639000 4706 1023 15 63 1023 15 63 1200 NB
1200 - 07 63 9638937 4706 1200 1 1 1799 254 63 B OK
0 - 0B 28917063 9638937 4706 1800 1 1 2399 254 63 B OK
0 - 07 38556000 19278000 9413 2400 0 1 3599 254 63 B OK
0 - 07 57834000 20306160 9915 3600 0 1 4863 254 63 B OK

-----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
0 1 33 9409 8 2 9409 0 0 0 020707 7410
1800 1 33 9404 4 2 9404 0 0 0 020707 3850

Partitions according to partition tables on second harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1 0B 63 19277937 9413 0 1 1 1023 15 63 NB NB
0 1 1 1199 254 63 Actual
0 2 05 19278000 19278000 9413 1023 15 63 1023 15 63 !! NB
1200 0 1 2399 254 63 Actual
0 3 07 38556000 19277992 9413 1023 15 63 1023 15 63 NB NB
2400 0 1 3599 254 55 Actual
0 4*07 57834000 20306152 9915 1023 15 63 1023 15 63 NB NB
3600 0 1 4863 254 55 Actual

1200 1 07 63 9638937 4706 1023 15 63 1023 15 63 OK NB
1200 1 1 1799 254 63 Actual
1200 2 05 9639000 9639000 4706 1023 15 63 1023 15 63 NB
1800 0 1 2399 254 63 Actual

1800 1 0C 63 9638937 4706 1023 15 63 1023 15 63 NB NB
1800 1 1 2399 254 63 Actual


I tried to understand the output, in particular for hd 2, but it's
beyond my knowledge.

I'd be happy if I could make w2k pro start again or to correct the
partition in order to let it be seen by the w2k cd setup.

I hope somebody can help me. It's really distressing to have all the
files over there and not beeing able to start w2k! :-(

thank you
maxx
Click to expand...

The commands (not word wrapped in the actual commands):

set findpart=edit
findpart 1 0 1 * 0C 0 1 1 1199 254 63 0 4865 255 63 26
findpart 1 0 2 - 0F 1200 0 1 2399 254 63 0 4865 255 63 26
findpart 1 0 3 - 07 2400 0 1 3599 254 63 0 4865 255 63 26
findpart 1 0 4 - 07 3600 0 1 4863 254 63 0 4865 255 63 26
findpart 1 1200 1 - 07 1200 1 1 1799 254 63 1200 4865 255 63 26
zero
findpart 1 1200 2 - 05 1800 0 1 2399 254 63 1200 4865 255 63 26
findpart 1 1800 1 - 0B 1800 1 1 2399 254 63 1800 4865 255 63 26
zero force
set findpart=

and

set findpart=edit
findpart 2 0 1 - 0C 0 1 1 1199 254 63 0 4865 255 63 26
findpart 2 0 2 - 0F 1200 0 1 2399 254 63 0 4865 255 63 26
findpart 2 0 3 - 07 2400 0 1 3599 254 63 0 4865 255 63 26
findpart 2 0 4 * 07 3600 0 1 4863 254 63 0 4865 255 63 26
findpart 2 1200 1 - 07 1200 1 1 1799 254 63 1200 4865 255 63 26
findpart 2 1200 2 - 05 1800 0 1 2399 254 63 1200 4865 255 63 26
findpart 2 1800 1 - 0B 1800 1 1 2399 254 63 1800 4865 255 63 26
set findpart=

corrected the partition tables to:


Findpart, version 4.38.
Copyright Svend Olaf Mikkelsen, 2004.

OS: DOS 7.10 Partition tables:

Disk: 1 Cylinders: 4865 Heads: 255 Sectors: 63 MB: 38162

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1*0C 63 19277937 9413 0 1 1 1199*254 63 OK OK
0 2 0F 19278000 19278000 9413 1200# 0 1 2399*254 63 OK
0 3 07 38556000 19278000 9413 2400# 0 1 3599*254 63 OK OK
0 4 07 57834000 20306160 9915 3600# 0 1 4863*254 63 OK OK

1200 1 07 63 9638937 4706 1200 1 1 1799 254 63 OK OK
1200 2 05 9639000 9639000 4706 1800 0 1 2399 254 63 OK

1800 1 0B 63 9638937 4706 1800 1 1 2399 254 63 R0 OK

Disk: 2 Cylinders: 4865 Heads: 255 Sectors: 63 MB: 38162

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1 0C 63 19277937 9413 0 1 1 1199*254 63 OK OK
0 2 0F 19278000 19278000 9413 1200# 0 1 2399*254 63 OK
0 3 07 38556000 19278000 9413 2400# 0 1 3599*254 63 OK OK
0 4*07 57834000 20306160 9915 3600# 0 1 4863*254 63 OK OK

1200 1 07 63 9638937 4706 1200 1 1 1799 254 63 OK OK
1200 2 05 9639000 9639000 4706 1800 0 1 2399 254 63 OK

1800 1 0B 63 9638937 4706 1800 1 1 2399 254 63 R0 OK

And the system could boot normally.
 
It is difficult to explain in details for all cases, but it is nice to
know the working conditions.

If a user works in DOS, but can boot Windows, and mail from Windows,
and has no other PC, and I make an error, the user has to find another
PC to continue the work.

If an error is made running in Windows, there is a chance to correct
the error before reboot.

Also the features are different in DOS and Windows versions of my
programs.

The short answer is that it is nice to know in some cases, and there
is no reason to cut the information. In the actual case, by reading
the message two or three times I maybe could have avoided asking, but
still there is no reason for that.
 
Back
Top