9.04 Live-CD did not mount jfs

[EricDHH]

This is a really messy showstopper, sittin here with broken grub and initrd without chance to repair this.

Please try to mount a existing jfs partition with a live cd, tested with 8.04, 8.10, 9.04

ubuntu@ubuntu:/mnt$ sudo mount /dev/sda1 /mnt/ziel
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

ubuntu@ubuntu:/mnt$ sudo mount -t jfs /dev/sda1 /mnt/ziel
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so

But the jfs module is already started by the live cd.

ubuntu@ubuntu:/mnt$ lsmod
Module Size Used by
nls_utf8 9856 0
ufs 85252 0
qnx4 16644 0
hfsplus 80644 0
hfs 50948 0
minix 35972 0
msdos 15744 0
xfs 552104 0
reiserfs 236288 0
jfs 187620 0

  Name Flags Part Type FS Type [Label] Size (MB)
 ------------------------------------------------------------------------------
    sda1 Boot Primary Linux JFS [UBUNTU] 12889.02

That must be fixed urgent, now i have to use the windows way. Format all and reinstall the whole system......

Bye
Eric

[EricDHH (ericdhh)]

Hello

above happens with i386 livecd on a amd64 system. This is crazy cause a amd64 livecd mounts the partition well, who can check this? Is there a difference between amd64 and i386 jfs?

If this is my pbkac, the bug can be closed.
Eric

[matika (xmaximx)]

Same here on an INSTALLED "Linux storm 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux".

No mounting of existing jfs partitions possible.

[matika (xmaximx)]

I found the reason why it didn't work (for me): the jfs-partition was (for some reason !?) unclean and i had to manually fs-check it to be able to mount it again.

the irritating thing is, that jfs did not report it (not even via dmesg) und you have to guess that it's unclean.

ubuntu should automatically check all filesystems (in fstab ?) by default on startup or on mounting.

[Jeremy Foshee (jeremyfoshee)]

Hi EricW@Hamburg,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 367237

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[EricDHH (ericdhh)]

Sorry i could not test this anymore, JFS was kicked away from both mobile with 9.10 update cause of this issue. Using ext4 here that mounts well with matching install cd / usb-stick. Someout out to do this test?

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]