I've never dealt with an SGI or XFS before but wanted to backup an o2 drive before tinkering with it. I installed Linux (Mint 21) on an old desktop then slapped an Adaptec AHA-2940UW SCSI card in (latest firmware) and attached the o2 drive. The SCSI drive appeared as /dev/sdb and shows partitions but they weren't accessible and if memory serves I don't think it listed their type (as if unrecognized). I proceeded with a simple dd which completed with no errors. I put the drive back into the o2 and it booted fine. Unfortunately A few minutes later the power supply popped and the o2 is dead, for now.
I've been playing with this disk image but any mount attempts result in the ever so common error...
sfdisk does at least list information about partitions in the image...
sudo dd bs=4M /if=/dev/sdb /of=o2.img /status=progress
I've been playing with this disk image but any mount attempts result in the ever so common error...
wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error
sfdisk does at least list information about partitions in the image...
Next I tried...sfdisk -l o2.img
Disk o2.img: 8.48 GiB, 9104138240 bytes, 17781520 sectors
Geometry: 255 heads, 63 sectors/track, 1106 cylinders
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: sgi
Device Start End Sectors Size Id Type Attrs
o2.img1 266240 17781519 17515280 8.4G a SGI xfs boot
o2.img2 4096 266239 262144 128M 3 SGI raw swap
o2.img9 0 4095 4096 2M 0 SGI volhdr
o2.img11 0 17781519 17781520 8.5G 6 SGI volume
Okay, so now at least the image partitions are attached as block devices.sudo losetup -f --show -P o2.img
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 8.5G 0 loop
├─loop0p1 259:6 0 8.4G 0 part
├─loop0p2 259:7 0 128M 0 part
├─loop0p9 259:8 0 2M 0 part
└─loop0p11 259:9 0 8.5G 0 part
Bummer, so I did some searching online and tried xfs_repair, but I threw in -n for no changes since I just want to see if it balks. I tried this on all four partitions, same result.sudo mount -t xfs -o nouuid /dev/loop0p1 /mnt
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/loop0p1, missing codepage or helper program, or other error.
I would like to know if dd imaging the entire drive was appropriate or not and I would like to learn more about accessing SGI drives (and images of drives). Are certain Linux distros preferable for accessing XFS? Some recovery software I have, R-studio, doesn't support XFS but did a raw file scan of the image and turned up lots of things so I know the data is there. Even though the o2 is currently down I can of course use other methods to re-image the drive in the event it should be done differently. Some guidance would be appreciated. Thank you.sudo xfs_repair -v -n /dev/loop0p1
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!
attempting to find secondary superblock...
..Sorry, could not find valid secondary superblock
Exiting now.