How do you CHKDSK the boot partition?
Tim Smith
if all was in order. CHKDSK found some lost data on my HPFS partition,
and the fun began.
I followed the instructions in the manual:
1. I put the Installation Diskette in the drive and hit
CTL-ALT-DEL.
2. I gave it disk #1 when it asked for it.
3. I pressed F3 at the appropriate point to get a command
prompt.
4. I went to the OS2IMAGE\DISK_2 directory of the CD-ROM.
5. I typed "chkdsk d:/f" (my HPFS filesystem is on D:).
And this is what it said:
The current hard disk drive is D:
The type of file system for the disk is HPFS.
The HPFS file system program has been started.
SYS0533: Command syntax information is online.
and it comes back to the command prompt.
If I leave off the /f it runs fine (and finds the errors that I want to
fix). But whenever I try /f, it does what I show above.
Any ideas? Eventually, I just started copying some files on D: and hit
the reset switch so that the filesystem would be left in an unclean
state, and then the automatic CHKDSK fixed it, which solved the problem,
but I'm disturbed that the procedure in the manual did not work.
Tim Smith
scbr...@crl.com
Tim,
Just saw you're problem and on a hunch I tried something. I ran the command
'chkdsk d:/f' from an OS2 prompt. It performed just as expected. Then I tried
the
same thing on my j: drive and it returned the same sys error that you receive.
The
only difference between the two drives is my d: is FAT and my j: is HPFS. It
seems
that the chkdsk used for the HPFS system is VERY PICKY about command line
syntax, i.e. it needs a space between the drive designation and the switch
(chkdsk d: /f).
Thanks for asking this question. Now I have one more little tidbit of info
about OS/2
that is not in the book.
Scott (scbr...@crl.com)
scbr...@crl.com
Amiri Jones
Also, you can go into your CONFIG.SYS file, and in the IFS line, add
/AUTOCHECK:X or /AUTOCHECK:+X, where X is your HPFS drive letter. In the first case,
the system will run CHKDSK at bootup if the system was improperly shut down. In
the second case, the system will run CHKDSK at bootup ALWAYS, regardless of shutdown
procedure. Of course, both commands will fix any errors that arise.
AJ
Amiri Jones
Also, you can go into your CONFIG.SYS file, and in the IFS line, add
Tim Smith
>syntax, i.e. it needs a space between the drive designation and the switch
>(chkdsk d: /f).
Wow. That's got to set some kind of record for most annoying silly
behaviour of a command. I hope it's something left over from the old
days when Microsoft still had a hand in OS/2 commands!
--Tim Smith
mb...@rtp.vnet.ibm.com
Mark
Gregor Tee
AJ> Also, you can go into your CONFIG.SYS file, and in the
AJ> IFS line, add /AUTOCHECK:X or /AUTOCHECK:+X, where X is your
AJ> HPFS drive letter.
Or FAT if i'm right. But I was wondering if it would be posible to check 2
drives (C & D).
T.
Email: Gre...@idn.nl
--
<<<<<<<<<< IDN Internet Gateway >>>>>>>>>>>
BBS: +31-50-133623 => Supra V.Fc 28k8
+31-50-891177 => ISDN2 X.75 64Kb/s
For more info send an Email to => in...@idn.nl
Gregory Czaja
>Or FAT if i'm right. But I was wondering if it would be posible to check 2
>drives (C & D).
Specify all letters, one after another.
Gregory Czaja ---> DeskMan/2 utilities
(71052,720 CIS WZ00329 TalkLink) expanding your object universe...
Paul Neyman
>
Type chkdsk d: /f. Be sure to put a space after the colon and I think
that should fix your problem.
pcg...@ibm.net
The prohibition against running CHKDSK on your active boot partition
is not a bug, it's a Working As Designed (WAD) feature <G>! OS/2
cannot allow you to do anything to a partition which has active (open)
DLL's on it; thus the boot partition, and any partitions from which
you load DLL's, will be off limits for CHKDSK.
The way arround this is a PITA; but it works. Boot from the Installation
Floppies, when prompted for the 3rd floppy, press ESC instead which
will exit to an OS/2 command prompt. From there, run CHKDSK against
any partition on your harddrive you wish.
Phil "Guido" Cava TeamOS/2
Help, PC!
Let us help you achieve Warp Speed today!
email at: pcg...@srmc.com
**** OS/2: Too easy to be Unix, too powerful to be Windows.......
ak...@cs.umr.edu
>Floppies, when prompted for the 3rd floppy, press ESC instead which
>will exit to an OS/2 command prompt. From there, run CHKDSK against
>any partition on your harddrive you wish.
Fortunately Phil is incorrect. There is an undocumented parameter in the
CHKDSK program that directly addresses your problem.
Assuming that your active partition is, let's say, D:
type the following:
chkdsk D: /F /aUtOcHeCk
Hope this helps you!
Alex Kapadia
ak...@cs.umr.edu
Avid OS/2 Warp user!
Steve Tice
:The prohibition against running CHKDSK on your active boot partition
:is not a bug, it's a Working As Designed (WAD) feature <G>!
:The way arround this is a PITA; but it works. Boot from the Installation
:Floppies, when prompted for the 3rd floppy, press ESC instead which
:will exit to an OS/2 command prompt. From there, run CHKDSK against
:any partition on your harddrive you wish.
Or if you are running Warp, simply hit Alt-F1 when the little white box
appears in the upper left corner during boot and select the option for
the command prompt (believe it is C). Then your CHKDSK.
Steve Tice [using Warp and NR/2]
Amiri Jones
I don't think so, unless they changed it between 2.1 and Warp. The
In 2.1, the /AUTOCHECK:D parameter would go in the CONFIG file at the
end of the IFS= line.
AJ
Jack Tan
>ak...@cs.umr.edu wrote:
>> Fortunately Phil is incorrect. There is an undocumented parameter in the
>> CHKDSK program that directly addresses your problem.
>> Assuming that your active partition is, let's say, D:
>> type the following:
>>
>> chkdsk D: /F /aUtOcHeCk
>>
> I don't think so, unless they changed it between 2.1 and Warp. The
>In 2.1, the /AUTOCHECK:D parameter would go in the CONFIG file at the
>end of the IFS= line.
/aUtOcHeCk is indeed an undocumented parameter for CHKDSK.COM. It is
very dangerous to use, however, and I recommend staying away from it.
--
Jack Tan Read the latest news on the OS/2 Information Page:
ja...@uiuc.edu http://www.cen.uiuc.edu/~jt11635/os2/
[TEAM OS/2]
Mathematics & Computer Science, University of Illinois at Urbana-Champaign
[Ralph Eyman]
>scbr...@crl.com wrote:
>>
>> In <3gpdsn$4...@nntp1.u.washington.edu>, t...@u.washington.edu (Tim Smith)
>> :
>writes:
>
> AJ
I was told that the chkdsk done at bootup does not do a level 3 (/f:3] recovery.
Does anyone know if this is true or not?
|-------------------------------------------------------------|
| Ralph Eyman ra...@sys4689.orl.mmc.com |
| Applications Analyst P/A Dept. of Redundancy Dept. |
| Martin Marietta Information Systems (for whom I don't necessarily speak) |
| (407)826-6167 alt Email: u77...@sys30024.orl.mmc.com |
|-------------------------------------------------------------|
David Charlap
>>The way arround this is a PITA; but it works. Boot from the Installation
>>Floppies, when prompted for the 3rd floppy, press ESC instead which
>>will exit to an OS/2 command prompt. From there, run CHKDSK against
>>any partition on your harddrive you wish.
>
>Fortunately Phil is incorrect. There is an undocumented parameter in the
>CHKDSK program that directly addresses your problem.
>Assuming that your active partition is, let's say, D:
>type the following:
>
> chkdsk D: /F /aUtOcHeCk
Don't use that parameter. It's dangerous. It's undocumented because
it's meant to be used by the system only. This is how the HPFS IFS
driver can automatically run CHKDSK on an improperly stopped
partition.
You shouldn't use this yourself. If CHKDSK corrects any errors in
open files, you may end up with a very crashed system. It's safe for
the IFS to run it because the OS has barely started booting at that
point, so the only open files are the boot files.
---------------------+--------------------------------------------------------
David Charlap | The contents of this message are not the opinions of
da...@visix.com | Visix Software, or of anyone besides myself.
Visix Software, Inc. +--------------------------------------------------------
Member of Team-OS/2 |
---------------------+
pcg...@ibm.net
Unfortunately, Phil IS correct. Sometimes I hate it when I'm right!
BTW, if you do use that aUtOcHeCk stuff, I sure hope you have a
a VERY recent backup; but, not so recent as to include whatever
you are trying to CHKDSK away! Talk about a rock-and-hard-place!
Some things are undocumented because somebody forget.
Some things are undocumented because nobody remembered.
Some things are undocumented because they don't work.
Some things are undocumented because they work too well.
...
Phil "Guido" Cava TeamOS/2
Help, PC!
Let us help you achieve Warp Speed today!
email at: pcg...@srmc.com
**** Ve have vays to make you run CHKDSK!