Re: CHKDSK SYS3175 error?
- From: Mike Luther <mike.luther@xxxxxxxxxx>
- Date: Thu, 07 Aug 2008 00:18:30 +0000
Thanks!
Ilya Zakharevich wrote:
[A complimentary Cc of this posting was sent to
Mike Luther <mike.luther@xxxxxxxxxx>], who wrote in article <4898c8a5$0$4024$bbae4d71@xxxxxxxxxxxxxxxxxxx>:
Anyone ever seen CHKDSK for OS/2 come back with a SYS3175 error when attempting a run on a 2GB HPFS hard disk partition.
I think I have seen it. Do not remember what I needed to do (I had no
full backup)...
A bit more research. From the copy of CHKDSK and CHKDSK32 on this system they are earlier than the current releases. I note there were two IBM APAR's that address failure of CHKDSK with Warp 4 like this, including one with floppy disk booted systems.
I would (in this order)
a) check the partition table for sanity; (DFSee?)
That was my thought too. On your confirmation thought, I booted to OS/2 from a set of floppy diskettes and ran DFSEE. I chose to check the HPFS file system with it. Following that I check the partitioning. Following that I chose to deliberately clear the dirty byte flag.
b) Is not there a chkdsk in DfSee?
I didn't get that far. In that this was not the boot partition, I then immediately got a start up. There were several still apparently 'in use' applications that had never been shut down. A Win-OS2 application. A Smart Suite for OS/2 application. Two DOS applications. I shut them down.
From that point with the hard disk booted system, I was able to drop to an OS/2 command window. I was then able to run CHKDSK D: /F, which at that point produced no errors at all on this partition.
Problem solved.
c) Set the "OK" flag manually, and copy files which are salvageable
(unless you have a backup);
d) reformat.
Fortunately, the files were still all clean, as far as we can tell. As well there was no apparent need to reformat.
It looks like this whole show erupted over the un-attended half dozen sharp power surge and total off slices in the facility from Tropical Storm Eduaord that even the APC UPS couldn't cope with.
Once the dirty bit got set, and a couple passes of lockups were attempted on the reboot, this SYS3175 error with CHKDSK could only be by-passed with the use of DFSEE to clean up the mess by somewhat more crude brute force.
Thank you for your support!
--
--> Sleep well; OS2's still awake! ;)
Mike Luther
.
- References:
- CHKDSK SYS3175 error?
- From: Mike Luther
- Re: CHKDSK SYS3175 error?
- From: Ilya Zakharevich
- CHKDSK SYS3175 error?
- Prev by Date: Re: CHKDSK SYS3175 error?
- Next by Date: Re: CHKDSK SYS3175 error?
- Previous by thread: Re: CHKDSK SYS3175 error?
- Next by thread: Re: CHKDSK SYS3175 error?
- Index(es):
Relevant Pages
|