[ag-automation] Problem reading RBF filesystem on SCSI disk

[Piotr Czepek]

2007/3/28, Carsten Emde <Carsten.Emde at osadl.org>:
> Piotr,
>
> >> If you already dd'ed the image to disk, did you try this?
> >> # mount -t rbf -o loop /path/to/image /mnt
> > I tried mount a  RBF image via loopback device. It failed:
> > dmesg output:
> > [..]
> > RBF invalid inode loop0:000000e9
> Okay. This is a reasonable error message.
>
> > Gzipped dump of  bootsector is attached (bootsec.gz). I hope it will
> > help to debug.
> Yes, indeed, it helped. I have bad news, though.
>
> These are the first 16 Bytes of the root sector:
> 1C FD E8 21 E7 F0 00 04 00 00 E9 00 00 FF F2 F0
> \-----/  |  \--/  \--/  \------/
>  total   |    |  cluster   LSN
> sectors  |    |   size     of
>          |    |           root
>       sectors |         directory
>         per   |
>        track  |
>              number
>             of bytes
>           in alloc map
>
> As you can see, the logical sector number of the root directory is
> 0x0000e9. Since the sector size is 256 Bytes, the offset of the root
> directory is 0xe900.
>
> Let's have a look at this location:
>
> E900: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
> E910: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
> E920: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
> E930: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
> etc.
>
> Thus, the error message "BF invalid inode loop0:000000e9" makes sense:
> The entire root directory has been erased, intentionally or accidentally.

Hello,

Strange...
HDD was taken from the running system.
As I found in installation manual, system is equipped with OS-9/68030
Level 1 version 2.4.
Hardware is Fuji's MCS-30. The MCS-30 is the control center of the SMT line.

I'll put HDD back to the MCS just to check if it still in good condition.

--
best regards
piotr