backing up amiga hard drives with linux dd

[kamiga]

I have two hard drives attached to my Amiga 500.  Dataflyer IDE and an external hard drive case I made out of a drilled radio shack project case 20 years ago.

Both hard drives are old and have surprisingly not failed yet.  I've copied the majority the files off successfully using AmigaExplorer.

I'd like to do an entire bit-by-bit copy of the drives, and plan on pulling the drives, one at a time, installing them into an Ubuntu box, and using dd to perform the copy.

My concerns are that while dd will record every bit on the drive, it does so in such a way that restoring the backup to another (new) drive is impossible because of drive geometry problems.

From within linux, is it possible to mount the dd image, not the hd, and access the contents?  I think I'm using FFS on the HD.

Thanks

(apologize if this is a dup post, I swear I posted this an hour ago)

[kamiga]

I'm honestly not sure.

I just spent the last couple hours trying to get Ubuntu, that has support for AFFS, to recognize the attached hard drive.  The driver complained of "No valid root block detected on /dev/sdc"

printk(KERN_ERR "AFFS: No valid root block on device %s\n",

I did manage to dd the whole drive -- but not sure if the contents are ok yet.  I looked at the raw bytes in the file, and it starts off with a big block of 0x2A's.  And then the text in the file seems shifted by x-number of bits/characters..... I'm not sure if linux was reading it properly.


Is devs:mountlist the officially used file for mounting?  I swear I had to manually type in sector/cyl/heads/etc in a file, and I can't find it anyplace.  I want to double check I'm using FFS.

Thanks

[kamiga]

The disk I was trying to image isn't bootable (afaict) --- and it's a second hard drive.  I boot from the first.

I don't think it's an image of the partition, because I don't think linux understands amiga partitions at the level at which I have access to it.  I think it sees it as a raw device, since AFFS can't really mount it.

If I do an "lshw", the drive shows up as a seagate, of the right size, and as "/dev/sdc"

I'll search for that string, but I was looking for block/format identifiers in the file, and nothing stuck out.

I've created some HDFs before, and maybe that's the route I'll go this time too.

Thanks

[kamiga]

Thanks.  I had found that last night, and I guess AFFS has direct support for the loopback.  (I don't honestly know if direct support is needed, but they do mention it specifically in the source/notes for AFFS)

My problem is I can't even mount the actual hard drive.

I did create an image, and then try to mount the image using the "-o loop."  And I get exactly the same no valid root block found error message.

Thanks

[kamiga]

Call me crazy, but the image dd has stored for the amiga drive is being corrupted in a very odd way.

Look at this:

001839A0 0000 0000 0000 3A17 0000 6402 0000 5C01 ......:...d...\.
001839B0 480F 7261 4464 7369 2E6B 7264 7669 7265 H.raDdsi.krdvire

Now, that clearly says Harddiskdriver.  There's plenty of other examples.

001F8000 4F44 0153 4F44 0153 4F44 0153 4F44 0153 OD.SOD.SOD.SOD.S

That should be DOS.DOS.DOS.  But it's not always backwards like that.

and this may look like a foreign language but

0C8A4BB0 6562 6120 2073 6165 7973 7420 206F 7375 eba  saeyst  osu
0C8A4BC0 2065 7361 6920 2073 6F70 7373 6269 656C  esai  sopssbiel
0C8A4BD0 202E 2A0A 2A6C 3470 6C2A 2020 5420 6568  .*.*l4pl*  T eh
0C8A4BE0 6E20 7865 2074 6566 2077 6170 6567 2073 n xe tef wapeg s
0C8A4BF0 7270 766F 6469 2065 2061 6C63 6165 2072 rpvodi e alcae r
0C8A4C00 6564 6373 6972 7470 6F69 206E 666F 6820 edcsirtpoi nfoh
0C8A4C10 776F 7420 206F 7375 2065 6874 2065 6F6D wot  osu eht eom
0C8A4C20 7375 2C65 7020 6369 206B 7075 6320 7261 su,ep ci kpuc ra
0C8A4C30 7364 6520 6374 202C 6E61 2064 6C61 6F73 sde ct ,na dlaos
0C8A4C40 6920 6C6C 7375 7274 7461 2065 730A 6D6F i llsurtta es.mo

Any clue to the order of this mangling?

This is probably why it can't find the root block.

00000190 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A ****************
000001A0 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A ****************
000001B0 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A ****************
000001C0 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A ****************
000001D0 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A ****************
000001E0 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A ****************
000001F0 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A 2A2A ****************
00000200 0001 4644 4342 0000 00E8 01FD 0000 300C ..FDCB........0.

Is that FDCB supposed to be RDSK?

Hrmmmm...

Thanks!

[kamiga]

buzz wrote:
you cant just mount it like that. if you read the link, you will see you have to get the offset into each partition. you can do that by using 'parted' on the image.

Both GParted and parted both report the entire disk (and the image created from the disk) as being "unallocated 1.59gb" and a disk label type as unrecognized.  No partitions are recognized.

[kamiga]

buzz wrote:
what version of parted?

(0.3.8-1ubuntu2)

Distributed with Ubuntu Intrepid Ibex 8.10 live cd.