chkdsk Trap 000D with FAT partitions

Hello,

I copied my failing 40 GB Maxtor HD to an 80 GB drive using Maxblast 5, 
and the option to expand partitions proportionally. It worked just fine, 
except my HPFS and JFS partitions were copied sector-by-sector into 
identically sized ones, while the FAT partitions were expanded to the 
maximum 2GB FAT16 size. After booting from diskettes to reinstall 
BootManager and create the appropriate LVM volumes, all seemed OK.

Here is the problem: texcad, an old emtex (Latex for OS/2) program froze 
my ecs 1.05 installation, so I had to force a reboot. The JFS and HPFS 
partitions passed chkdsk without problem, but the FAT partitions fail, 
due to chkdsk trapping 000d.

I have remmed the autocheck option for FAT partitions in config.sys, but:
- chkdsk (plain) finds errors in extended attributes, that it can't fix 
because:
- chkdsk /f traps 000d from a WPS command prompt session
and
- chkdsk run after booting from diskettes crashes with error message SYS1811

Questions: what is the matter with chkdsk? Is it the FAT partition size?
How do I get my FAT partitions to be checked?

My chkdsk.com (called by chkdsk for FAT drives) is dated 11/15/2000, 
70720 bytes.

Thank you for any help.

Hi Oscar

o r wrote:
> Hello,
> 
> I copied my failing 40 GB Maxtor HD to an 80 GB drive using Maxblast 5, 
> and the option to expand partitions proportionally.


No idea what Maxblast 5 is but all you needed to do was use LVM to 
create whatever volumes (partitions) and sizes were required and then 
use good old xcopy.


  It worked just fine,
> except my HPFS and JFS partitions were copied sector-by-sector into 
> identically sized ones, while the FAT partitions were expanded to the 
> maximum 2GB FAT16 size. After booting from diskettes to reinstall 
> BootManager and create the appropriate LVM volumes, all seemed OK.
> 


Does Maxblast 5 know about LVM, HPFS and JFS?


> Here is the problem: texcad, an old emtex (Latex for OS/2) program froze 
> my ecs 1.05 installation, so I had to force a reboot. The JFS and HPFS 
> partitions passed chkdsk without problem, but the FAT partitions fail, 
> due to chkdsk trapping 000d.
> 
> I have remmed the autocheck option for FAT partitions in config.sys, but:
> - chkdsk (plain) finds errors in extended attributes, that it can't fix 
> because:
> - chkdsk /f traps 000d from a WPS command prompt session
> and
> - chkdsk run after booting from diskettes crashes with error message 
> SYS1811
> 
> Questions: what is the matter with chkdsk? Is it the FAT partition size?
> How do I get my FAT partitions to be checked?
> 


Just wondering if any errors happened during the copying process... or, 
maybe the errors are a result of copying from a dying disk.


> My chkdsk.com (called by chkdsk for FAT drives) is dated 11/15/2000, 
> 70720 bytes.
> 


Probably the latest available.


> Thank you for any help.
> 
> Oscar Rondon


If the original disk is still usable you could try xcopying the contents 
of the fat partitions to the relevant volumes on the new disk after 
using LVM to destroy existing fat partitions and then recreating them.

An example xcopy line to copy the contents of drive E: to a new 
partition P: which is destined to become E: (using LVM to change drive 
letter later) when the old drive is removed:-

[P:\]xcopy e:\* /s /e /v /h /t /r

Note the command is issued from the root directory of the drive to xcopy 
to - saves typing  :-)


Regards

On Thu, 13 Mar 2008 16:29:20 UTC, Peter Brown 
<losepeteSPAM-ME-NOT@ntlworld.com> wrote:

> Hi Oscar
> 
> o r wrote:
> > Hello,
> > 
> > I copied my failing 40 GB Maxtor HD to an 80 GB drive using Maxblast
5, 
> > and the option to expand partitions proportionally.
> 
> 
> No idea what Maxblast 5 is but all you needed to do was use LVM to 
> create whatever volumes (partitions) and sizes were required and then 
> use good old xcopy.
> 
> 
>   It worked just fine,
> > except my HPFS and JFS partitions were copied sector-by-sector into 
> > identically sized ones, while the FAT partitions were expanded to the

> > maximum 2GB FAT16 size. After booting from diskettes to reinstall 
> > BootManager and create the appropriate LVM volumes, all seemed OK.
> > 
> 
> 
> Does Maxblast 5 know about LVM, HPFS and JFS?
> 
> 
> > Here is the problem: texcad, an old emtex (Latex for OS/2) program
froze 
> > my ecs 1.05 installation, so I had to force a reboot. The JFS and HPFS

> > partitions passed chkdsk without problem, but the FAT partitions fail,

> > due to chkdsk trapping 000d.
> > 
> > I have remmed the autocheck option for FAT partitions in config.sys,
but:
> > - chkdsk (plain) finds errors in extended attributes, that it can't
fix 
> > because:
> > - chkdsk /f traps 000d from a WPS command prompt session
> > and
> > - chkdsk run after booting from diskettes crashes with error message 
> > SYS1811
> > 
> > Questions: what is the matter with chkdsk? Is it the FAT partition
size?
> > How do I get my FAT partitions to be checked?
> > 
> 
> 
> Just wondering if any errors happened during the copying process... or, 
> maybe the errors are a result of copying from a dying disk.
> 
> 
> > My chkdsk.com (called by chkdsk for FAT drives) is dated 11/15/2000, 
> > 70720 bytes.
> > 
> 
> 
> Probably the latest available.
> 
> 
> > Thank you for any help.
> > 
> > Oscar Rondon
> 
> 
> If the original disk is still usable you could try xcopying the contents 
> of the fat partitions to the relevant volumes on the new disk after 
> using LVM to destroy existing fat partitions and then recreating them.
> 
> An example xcopy line to copy the contents of drive E: to a new 
> partition P: which is destined to become E: (using LVM to change drive 
> letter later) when the old drive is removed:-
> 
> [P:\]xcopy e:\* /s /e /v /h /t /r
> 
> Note the command is issued from the root directory of the drive to xcopy 
> to - saves typing  :-)
> 
> 
> Regards
> 
> Pete

Throw Maxblast away, don't use it (I never have). Use LVM or DFSee to 
create your partitions and volumes, assign them drive letters and then 
format them.

HTH,
Pete

--