mounting failed in Lucid Ubuntu 10.04

If you boot to an older kernel does the system boot?

no ...it is not booting even on 2.6.32.11 ....the latest being 2.6.32.12 and in kubuntu Lucid 2.6.32.12 is working fine.

Log a bug

OK, I will log bug
Thanks
Rajinder Sandhu
====================

On Mon, Feb 1, 2010 at 11:59 AM, actionparsnip <
<email address hidden>> wrote:

> Your question #99430 on Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+question/99430
>
> Status: Needs information => Answered
>
> actionparsnip proposed the following answer:
> Log a bug
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https://answers.launchpad.net/ubuntu/+question/99430/+confirm?answer_id=2
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/ubuntu/+question/99430
>
> You received this question notification because you are a direct
> subscriber of the question.
>

--
Warm regards,

Rajinder Sandhu
Bangalore
India

actionparsnip,
Sorry, as I am unable to file it, Please file the bug yourself.
Thanks,
Rajinder Sandhu

On Mon, Feb 1, 2010 at 1:20 PM, Rajinder Sandhu <email address hidden> wrote:

> OK, I will log bug
> Thanks
> Rajinder Sandhu
> ====================
>
>
> On Mon, Feb 1, 2010 at 11:59 AM, actionparsnip <
> <email address hidden>> wrote:
>
>> Your question #99430 on Ubuntu changed:
>> https://answers.launchpad.net/ubuntu/+question/99430
>>
>> Status: Needs information => Answered
>>
>> actionparsnip proposed the following answer:
>> Log a bug
>>
>> --
>> If this answers your question, please go to the following page to let us
>> know that it is solved:
>> https://answers.launchpad.net/ubuntu/+question/99430/+confirm?answer_id=2
>>
>> If you still need help, you can reply to this email or go to the
>> following page to enter your feedback:
>> https://answers.launchpad.net/ubuntu/+question/99430
>>
>> You received this question notification because you are a direct
>> subscriber of the question.
>>
>
>
>
> --
> Warm regards,
>
> Rajinder Sandhu
> Bangalore
> India
>

--
Warm regards,

Rajinder Sandhu
Bangalore
India

Also unable to open the ubuntu 10.04 (sdb 11)partition on ubuntu 9.10 or Kubuntu 10.04 the following message appears:

Error mounting: mount exited with exit code 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb11,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail or so
and the output of dmesg|tail is as follows:

dads@dads-desktop:~$ dmesg|tail
[ 225.166668] sd 0:0:1:0: [sdb] Sense Key : Medium Error [current] [descriptor]
[ 225.166675] Descriptor sense data with sense descriptors (in hex):
[ 225.166678] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 225.166689] 0c 92 00 07
[ 225.166694] sd 0:0:1:0: [sdb] Add. Sense: Unrecovered read error - auto reallocate failed
[ 225.166702] end_request: I/O error, dev sdb, sector 210894855
[ 225.166728] ata1: EH complete
[ 225.166908] JBD: Failed to read block at offset 4240
[ 225.166922] JBD: recovery failed
[ 225.166925] EXT4-fs (sdb11): error loading journal
dads@dads-desktop:~$

that was the latest on my problem....seems I may have to reinstall the ubuntu 10.04 after reformatting the partition (sdb11)

Seems to be it was much easier than thought...resolved the problem by opening the gparted...check for errors and repair then click Ok within 15 secs everything was set right..I could open or mount the drive so then rebooted and opened the ubuntu 10.04 within seconds system was up and now i am giving the latest update from the same OS ie Ubuntu 10.04.
Thanks all....thought of sharing my experience...good lesson for all to remember
Thanks again,
Rajinder Sandhu

 I have just done a clean install of 10.04 from the disc from the Ubuntu User mag. All went well until I rebooted after the 200+ updates. It then failed to boot with the same messages except mine started "mounting /dev/disk/by-uuid/improbablylonghexname on /root failed invalid argument". Many thanks for the fix, you saved the last remnants of my hair.

I have just had to do this for the THIRD time. If its not the new ext4, is it a problem with my disk? Is it coincidental that it seems to be after doing updates? Does this help:-

GParted 0.5.1

Libparted 2.2
Check and repair file system (ext4) on /dev/sda1 00:01:55 ( SUCCESS )

calibrate /dev/sda1 00:00:00 ( SUCCESS )

path: /dev/sda1
start: 2048
end: 75182079
size: 75180032 (35.85 GiB)
check file system on /dev/sda1 for errors and (if possible) fix them 00:01:54 ( SUCCESS )

e2fsck -f -y -v /dev/sda1

/dev/sda1: recovering journal
Clearing orphaned inode 524464 (uid=0, gid=0, mode=0100644, size=30684)
Clearing orphaned inode 524451 (uid=0, gid=0, mode=0100755, size=117086)
Clearing orphaned inode 524417 (uid=0, gid=0, mode=0100644, size=34408)
Clearing orphaned inode 524407 (uid=0, gid=0, mode=0100644, size=42572)
Clearing orphaned inode 524403 (uid=0, gid=0, mode=0100644, size=30496)
Clearing orphaned inode 524401 (uid=0, gid=0, mode=0100644, size=79676)
Clearing orphaned inode 524343 (uid=0, gid=0, mode=0100755, size=1405508)
Clearing orphaned inode 532309 (uid=0, gid=0, mode=0100755, size=113964)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****

188581 inodes used (8.02%)
164 non-contiguous files (0.1%)
201 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 161241/48
1064946 blocks used (11.33%)
0 bad blocks
1 large file

131208 regular files
23155 directories
60 character device files
26 block device files
0 fifos
483 links
34097 symbolic links (27170 fast symbolic links)
26 sockets
--------
189055 files
e2fsck 1.41.11 (14-Mar-2010)
grow file system to fill the partition 00:00:01 ( SUCCESS )

resize2fs /dev/sda1

resize2fs 1.41.11 (14-Mar-2010)
The filesystem is already 9397504 blocks long. Nothing to do!

========================================

Mr walker,
Please ask the question because i closed the question as solved so the more experienced people won't look at it.... other thing you don't have to do repeated installations there seems to be a bug which needs to be fixed.
Please ask your problem in a new question so that you get the reply quick and fast.
Thanks
Rajinder