There are a few things to know that might help...
(i) How many disks do you have for you box?
(ii)How many partitions do you have on your disk with the corrupted jfs partition?
(iii)What, if any, other OSs are installed on what partitions?
(iv)Do you have a stock kernel or did you configure your own?
(v)When you say you were trying to mount it, what process did you take? What arguments did you send with mount()?
(vi)What do you think caused the corruption? Silly, I know, but try to think about the last time it worked and any possibility for the corruption. Alike software install'removal, or physcal'electrical harm to the box...
If no other OS are installed on the box:
And if you have a CD'DVD drive, or USBboot support in your BIOS, you can try booting from CD'DVD and from here retrieve the data. If this works then it would be a kernel issue, and you should configure a new kernel or replace the old with one from the CD'DVD'USB you are booting from.
Some distributions, like Slackware, in their Live boots there is the option to choose which drive to boot into.
Once booted you are given the opportunity to type in a command to choose the kernel. Doing nothing will boot the hugesmp.s to the LiveBootable, but you can, and it is shown by example, choose to boot from the LiveBootable's kernel, to your specified partition.
Code:
boot: hugesmp.s root=/dev/YOUR_DESIRED_PARTITION rdinit= ro
If there is another OS on the drive:
Boot into this OS, and use the command...
Code:
# cd /mnt
# mkdir corr
# mount -vs -t jfs -o ro,nointegrity,errors=remount-ro /dev/YOUR_PARTITION /mnt/corr
# cd /mnt/corr
#
or you could also try...
Code:
# cd /mnt
# mkdir corr
# mount -vsf -t jfs -o ro,nointegrity,errors=remount-ro /dev/YOUR_PARTITION /mnt/corr
check your man mount... the -f fakes the mount so you can view the error messages without actually mounting...
(vii) What error messages are you receiving if you have tried this?