Opened 6 years ago
Last modified 4 years ago
#68 assigned defect
CHKDSK failures
| Reported by: | Barry Landy | Owned by: | martini |
|---|---|---|---|
| Priority: | major | Milestone: | Future |
| Component: | IFS | Version: | |
| Severity: | medium | Keywords: | |
| Cc: |
Description
When recovering from a crash volumes are marked dirty. Either when obeying CHKDSK via \ac:* in Config.sys or manually, CHKDSK indicates a horrifyingly large number of errors.
Abandoning the OS2 boot and booting windows instead the volumes are initialised without fuss suggesting there is nothing wrong.
Change History (4)
comment:2 Changed 4 years ago by
Hi. Since this ticket was opened two years ago, maybe we should close it as expired.
Barry, if you are reading this, it may be good to test the latest test version of FAT32 and let us know if you still have the issue. Latest version is 0.10 r383 ftp://osfree.org/upload/fat32/fat32-0.10-r383-os2.zip
Regards
comment:3 Changed 4 years ago by
| Owner: | set to Valery V. Sedletski |
|---|---|
| Status: | new → assigned |
comment:4 Changed 4 years ago by
| Owner: | changed from Valery V. Sedletski to martini |
|---|
Note: See
TracTickets for help on using
tickets.
Probably, these errors are errors with trash in directories. CHKDSK cannot fix this. If so, you probably should back up data and reformat volume, as CHKDSK cannot fix trash in directories. Could you post your chkdsk.log here? (you may need to clear the DIRTY flag first, to access the volume, via "f32stat d: /clean")
PS: Windows CHKDSK could just ignore these errors (and windows won't fix these errors, either), so windows CHKDSK is not help here too.