HDF mounting problem

[Redeken]

Bug in last WinUAE Beta 3 found. The DOS/5 DCFS HDF (Directory Cache Filesystem) not read correctly. Message from AmigaOS: Not a DOS Disk.

Example is the AmigaSYS 4 HDF.

[Toni Wilen]

Originally Posted by Redeken

Bug in last WinUAE Beta 3 found. The DOS/5 DCFS HDF (Directory Cache Filesystem) not read correctly. Message from AmigaOS: Not a DOS Disk.

Example is the AmigaSYS 4 HDF.

winuaelog.txt from working and non-working version needed.

btw, dircache with harddrives only makes it slower.

[Redeken]

Insert AmigaSYS 4 AGA HDF (with DCFS DOS/5 formated) in WinUAE Beta 4

The last working Version was WinUAE 1.5.x ...

[emufan]

Redeken: is it the original AmigaSys hdf? it is working for me, look at the picture. shows the properties of the hdf.
picture taken with beta 1, but now updated to beta 4. still working , same settings.

Edit: one issue i can see. size of your hardfile is 100MB? mine is 200MB. was it configurable on setup. i cannot recall.

Edit: you have 'C:\Users\Public\Documents\Amiga Files\WinUAE\ROMs\FastFileSystem' ?
i dont provide it, try to rename/remove if it exists.

part of my log here:

12-973 [13 218-087]: Mounting uaehf.device 0 (0):
12-973 [13 218-087]: FS: mounted HDF unit DH0 (0000-0c800000, .\AmigaSYS\AmigaSYS\AmigaSYS4.hdf)
12-973 [13 218-087]: Partition 'DH0' Dostype=444F5300 (DOS\0) Flags: 00000000
12-973 [13 218-087]: BlockSize: 512, Surfaces: 1, SectorsPerBlock 1
12-973 [13 218-087]: SectorsPerTrack: 32, Reserved: 2, LowCyl 0, HighCyl 12799, Size 200M
12-974 [13 218-087]: Buffers: 50, BufMemType: 00000001, MaxTransfer: 7fffffff, Mask: ffffffff, BootPri: 0
12-974 [13 218-087]: First block 0 dostype: 444F5305 (DOS\5)
12-974 [13 218-087]: RDB: fakefilesys, trying to load '.\KS-ROMs\FastFileSystem', dostype 0x444F5305 (DOS\5)
12-974 [13 218-087]: RDB: filesys not found
12-975 [13 218-087]: Mounting uaehf.device 1 (0):
12-975 [13 218-087]: FS: mounted virtual unit DH1 (.\AmigaSYS\Work)

[Redeken]

The "FastFileSystem" in ROMs Directory i need access FFS on Kick 1.3.

"AmigaSys4AGA.hdf" is 100 MB.

[Toni Wilen]

If it only works with very old versions, you may need to mount it in working versions and then copy geometry data manually (sectors, surfaces etc..).

EDIT: but <512M hardfiles should always be compatible. Does both working and non-working versions show exact same geometry information in hardfiles panel?

[emufan]

Originally Posted by Redeken

The "FastFileSystem" in ROMs Directory i need access FFS on Kick 1.3.

"AmigaSys4AGA.hdf" is 100 MB.

did you choose "FastFileSystem" in properties of "AmigaSys4AGA.hdf"? if so, remove it from property dialog. my guess was, it is not compatble with the 1200 you are emulating.
just test your amigasys config with removed FFS file.

[Asle]

hi,
In the spirit of this topic, I really struggling to mount dd-ed disks images. I have some images of real Amiga hard drives. A looong time ago, I know I managed to mount them and access them in WinUAE.
I tried recently again with version 2.5.1 to no avail. I grabbed and installed the version 2.8.1 and I get the same result.
Please, find attached some logs.

logsA1200 contains a default A1200 config and a disk image set up to boot.
logs contains the same disk image but not set up to boot

I know this is not the latest WinUAE. However, I think my problem, here, is that I obviously have no clue how to mount a hard disk image. I searched for any kind of "how to" but all I find is HDF file _created_ in WinUAE. So, yeah, I'll gladly 'rtfm', but is there such a 'm' ?
Also, the disks I have obviously have multiple partitions. My own disk had 5 partitions. How do you mix that with a directory mounted as dh0: for example.

Maybe I'm missing the obvious, but I'm lost at the moment. Any help would be appreciated.

Cheers

[thomas]

25-593 [11 226-015]: RDB: block 0 ('RDSK') checksum error

Seems like your disk image file has been damaged.

Cut the first 2 MB off the file and attach it here.

[Asle]

Originally Posted by thomas

25-593 [11 226-015]: RDB: block 0 ('RDSK') checksum error

Seems like your disk image file has been damaged.

Cut the first 2 MB off the file and attach it here.

attached

[thomas]

There is more damage than just the checksum. You say there should be multiple partitions, but there is only one partition block left. And its checksum is invalid, too. And even worse, it does not contain valid data.

Block   0 Type = RDSK
   Checksum        : ** invalid **
   Name            : Seagate Technology 1275M1.35
   Bad Block List  : 4294967295
   Partition List  : 1
   File Sys Header : 4294967295
   Drive Init      : 4294967295
Block   1 Type = PART
   Checksum        : ** invalid **
   Name            : 
   Dos Type        : 001E0000
   Next            : 2147504193

Do you have another backup of this file? You should try to restore that.

One could try to recover the partitions by reading the entire file, but if the beginning of the file has been damaged so much, it is likely that the rest of the file is corrupted, too.

[Asle]

Damn. All right then, it was only this stupid damaged disk image.
Thanks for checking it up.

[Toni Wilen]

It has more partitions but second and all later partition blocks have been shifted by 18 bytes. There must have been some kind of data transfer corruption.

Fixing the shift may fix the image, at least partially. Many files are probably broken if other parts of image also have random data corruption. (like RDSK block)

[Tomislav]

Maybe your image little bigger than 100 MB (104857600 bytes).

When program decoded RAW data of your disk it have partial old decoded data from RAW gaps. It sometimes does because RAW data on disk is not saved at same location after next formatting/partitioning disk. There always exists gaps between RAW blocks and there are smaller and bigger gaps.

In your case is something like this:
- 1st block (decoded as RDSK)
- part of old block (decoded as PART - these 18 bytes)
- 2nd block (PART)
- next are 3rd, 4th... block and again some trash/zeros or part of old block ... (trash and zeros are not decoded, ofcourse)
(Between RAW blocks are gaps. Most of gaps are smaller and I think that it is one bigger gap per cylinder. Those bigger gaps can contain partial data of old blocks.)

Only way is that program, with which you made image of drive, have way to ignore those old partial data and to make new image of your disk. Or to use smarter program to make image.

[Toni Wilen]

That is 100% impossible with any modern hard disk. (Modern: not MFM drive)

[Asle]

well, the main point of reviving this thread was to highlight that I didn't know how to mount a HD image in WinUAE. It turns out it is said HD image that is broken.
About this image, it was done with dd command on FreeBSD years ago. I don't see how this could be made smarter at all. Besides, I had the HD in my hands for an hour or so.

When time allows, I'll read some doc and try to understand the problem. too much to do just now. Thanks for looking into it, though