Ubuntu
linux package

Intrepid ntfs prob with kernel 2.6.27-2/3-generic

Bug #269360 reported by gkey
2
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi all,

i have a wubi installed ubuntu hardy that I have upgraded to the intrepid beta.
If I boot in a 2.6.26 kernel, i have no issues to start my system, however when I try to boot in the 2.6.27 kernels It fails at (pre)mounting my ntfs disks and returns the error:

" could not mount the partition d/ev/disk/by-uuid/xxx this could also happen if the file system is not clean because of an operating system cash, an interrupted boot process, an improper shutdown, or unplugging of a removable device without first unmounting or ejecting it. to fix this simply reboot into windows, let it fully start, log in, run chkdsk /r, then gracefully shutdown and reboot back into windows."
after this you should be able to reboot again and resume the installation...

It reports an NTFS error 255.

It then boots to initramfs...

I chckdsk'd my system several times, but to no avail.
I've checked my menu.lst and it seems OK. I'm not sure if I can capture any logging (not sure where and how).
Since I'm sort of a noob, I'm not sure if I can fix this.

System is a lenovo T60p

regards,

Gijs

See original description
Tags: 8.10
gkey (gmkey)
description: updated
Revision history for this message
lilbudda (cory-meisch-gmail) wrote :

Hi Gijs,
     Have you been able to reboot back into Windows and run the chkdsk with the "/r" as prescribed in the error message? This usually means it's a corrupted NTFS filesystem. Also, go into the properties of the hard drive and uncheck write caching. Many times this will say NTFS is corrupt, even if it's not.

Cory

Revision history for this message
gkey (gmkey) wrote :

Hi Cory,

I'm assuming you want me to uncheck write caching in the Windows OS.

I tried that, followed by a chkdsk /r, a reboot and subsequently a shutdown before booting into intrepid. Unfortunately noting changed, I'm still getting the same error.

Gijs

Revision history for this message
gkey (gmkey) wrote :

And then - the upgrade to the Alpha 6 kernel 2.6.27-4-generic solved my problem....

regards

Gijs

Revision history for this message
lilbudda (cory-meisch-gmail) wrote :

Fixed with released kernel.

Changed in linux:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.