Comment 4 for bug 459839

Re-installation with EXT3 is done

System rebooted correctly with no errors/HD corruption after aptitude
full-upgrade, which failed both times I attempted EXT4 installation.

On 10/29/09, Ian Miller <email address hidden> wrote:
> I had Jaunty with EXT3 on almost the same system: the SSD was new, and
> I wanted Karmic on it, hence the installation.
>
> Your question is obviously important to answer, though, so I am
> re-installing the RC using an EXT3 partition (I think I did it right:
> manual partition with EXT3 partition mounted at /)
>
> I'll let you know.
>
> On 10/28/09, Carl Englund <email address hidden> wrote:
>> Can you confirm this only affects ext4? I.e. does the same problem arise
>> if you use an ext3 (or other) filesystem instead?
>>
>> --
>> installation corrupted due to EXT4-fs error
>> https://bugs.launchpad.net/bugs/459839
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in “linux” package in Ubuntu: New
>>
>> Bug description:
>> I think this is an EXT4 problem, possibly SSD-specific
>>
>> Problem is corrupted file system after indeterminate time following new
>> installation.
>>
>> Details: clean install of kubuntu 9.10 on intel quad core machine using
>> Intel X25-M SATA SSD. Install completes. Computer runs fine initially.
>> After
>> some period of time (about 3-4 system restarts, usually which include
>> updating the system to most recent packages) the boot process fails with
>> multiple messages of the following format:
>>
>> [ 46.870483] EXT4-fs error (device sda1): ext4_iget: bogus i_mode (0)
>> for
>> inode=581663
>>
>> I have done two clean installs using the kubuntu karmic (once with beta;
>> again with release candidate) and had the same problem each time.
>>
>> This seems like a show-stopper for folks with my hardware. Any help would
>> be
>> appreciated.
>>
>