Thanks Pete and El Vato!
El Vato, I can only find the LVM update v14.105 - and the earlier IBMDASD update (which's date corresponds to the JFS update).
[...]
I'll be upgrading the kernel as well at the same time to the 14.104a SMP kernel - cant find the 14.105 one.
Should I still proceed with the update, or do I most definitely need the same date LVM update to go with the kernel, IBMDASD (which the LVM update says is a prerequisite) and JFS?
I believe that your IDEDASD, JFS and LVM update are ok. Regarding the kernel, you may search for Martin's past post on xr_c006.zip, download it, and subsequently extract and install the OS2KRNL and DOSCALL1.DLL (PM, PM).
[...]
Because.... on the "test" system, while trying to FTP everything off the drive before I tried this, the system crashed (something in the JFS system... forget which component), and refuses to complete chkdsk (Phase 3 I think).
Currently, I am trying to recover the data - with not much luck... trying jRescuer currently to no avail:
[...]
Thanks for any suggestions,
Robert
I use GNU/Linux Debian to mount JFS partitions (which are seen by Debian as type 35 unknown). Accordingly, and although it may not be applicable in your current situation, but for further reference.
section from man page of
jfs_fsck to check and fix the errors of an unclean JFS partitions (non-spanned across several disks and/or partitions)
WARNING
jfs_fsck should only be used to check an unmounted file system or a file system that is
mounted READ ONLY. Using jfs_fsck to check a file system mounted other than READ ONLY could
seriously damage the file system!
[...]
EXAMPLES
Check the 3rd partition on the 2nd hard disk, print extended information to stdout, replay
the transaction log, force complete jfs_fsck checking, and give permission to repair all
errors:
jfs_fsck -v -f /dev/hdb3
Check the 5th partition on the 1st hard disk, and report, but do not repair, any errors:
jfs_fsck -n /dev/hda5
And then the JFS (unknown 35 type) partition is mounted as (note what happens if we do not specify type JFS):
(Below the x represents an partition number)
Huitzilopochtli:/home/jose# mount /dev/sdax /mnt/sdax
mount: wrong fs type, bad option, bad superblock on /dev/sdax,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
On the other hand, when we specify the type (-t) as jfs:
Huitzilopochtli:/home/jose# mount -t jfs /dev/sdax /mnt/sdax
Huitzilopochtli:/home/jose#...the JFS partition mounts, after being cleaned.
Hope that helps for another time and/or for others to embrace open source software to fix problems.