(Apparently) corrupted hard disk images

[Maren]

I'm getting these errors (from Workbench 1.3.3 rev 34.34) when loading hard disk images created with WinUAE 2.3.2 or any of the betas, but only after they have been initialized (formatted)

Example errors for the current 64mb hard disk image:

. "Error validating disk Empty Key 38554257 out of range"
. "Disk structure corrupt Use DISKDOCTOR to correct it"

and after trying to load it for the second time: "Error validating disk Empty Key -1 out of range"

I've been able to reproduce this behavior consistently and I used WinUAE's default quickstart profile for this particular test, though it happens regardless of the profile/config.

The hard disk image seems to work in spite of the errors, but very slowly, specially when booting from the freshly installed Workbench.

No idea what would happen with hard disk images created with previous version of WinUAE or initialized with other Workbench disks.

I've attached 4 log files, 2 from the formatting process and 2 created while booting from a Workbench adf right after the hard disk image was formatted.

Regards.

[Toni Wilen]

My crystal ball says you are using OFS filesystem. It only works on tiny drives (max 10M or so..)

[Maren]

I did what I used to do with older versions of WinUAE when creating a regular hard disk image ("Add Hardfile", enter the a number in MB's, "Create", "Save" and "Ok") so I was basically expecting that to work for the newer version as well.

Does this mean I should try switching to "SFS" when creating the disk? anything else? just want to make sure I get it right before going through the whole thing again.

[Toni Wilen]

Add "ffs" at the end of format command. Normal stuff, nothing emulation specific.

[Maren]

Thanks for the hint. I haven't formatted a real hd this way since God knows when so important details escape me, and now I feel like a complete arse

Can you tell what went wrong here? this thing just keeps going corrupt at the end of the formatting process. Let me know if you need logs and stuff, just curious if I screwed up on the commands.

[Maren]

Not to be pushy or anything, but am I the only one experiencing this?

[Toni Wilen]

Not enough information error.

How big HDF? Geometry? If it is few hundreds MB or bigger, please use RDB hardfiles, it is too easy to select invalid geometry (or geometry that AOS does not fully support, especially 1.x)