Ubuntu

Unable to read ntfs volume after upgrade to feisty fawn

Asked by Greg B.

I recently upgraded from 6.10 to 7.04 and now it can not read my internal ntfs volumes. It can read the volumes on the external usb drive which are formated with ntfs.

my /etc/fstab

"# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/hda2
UUID=8efc6ec5-6503-4fb5-8b14-6d7e97aaeb6b / ext3 defaults,,errors=remount-ro 0 1
/dev/hda2 /support ext3 rw,auto,acl,errors=remount-ro 0 1
# /dev/hda1
UUID=C8E837BBE837A71A /media/hda1 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/hdb1
UUID=72943A249439EB6D /media/hdb1 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/hdb2
UUID=EAECB05FECB02829 /media/hdb2 ntfs defaults,nls=utf8,umask=007,gid=46 0 1
# /dev/hda3
UUID=6e258be1-05a5-409f-be55-abd0f203a514 none swap sw 0 0
/dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/ /media/floppy0 auto rw,user,noauto 0 0"

In gparted it sees

sda (sda1,sda2) can't read ntfs
sdb (sdb1,sdb2) can't read ntfs
sdc (sdc1,sdc2) external usb drive can read ntfs
sdd (sdd1) ipod can read
sde (sde1) flash drive can read

When I get the info on the exclamation point on the ntfs volume in gparted it says can not read filesystem . Do you have the correct plugin?
One of the volumes it can't read also has my linux install on another volume which is running fine otherwise so its not the drive itself
It has no problem with my flash drive, ipod, and ntfs formated external drive.

had no issues before upgrade

any suggestions?

Thanks

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#1

Please try this open a terminal:
- make an internal backup copy of your /etc/fstab file

cd /etc/
sudo cp fstab fstab.old

then edit your fstab file:

sudo gedit /etc/fstab

and remove the UUID for the ntfs disk for example change:

UUID=C8E837BBE837A71A /media/hda1 ntfs defaults,nls=utf8,umask=007,gid=46 0 1

with

/media/hda1 ntfs defaults,nls=utf8,umask=007,gid=46 0 1

Then reboot

Please give us some feedback

Hope This Help

Revision history for this message
Greg B. (prezbedard) said : 		#2

Should I attempt the upgrade to Gusty? Which is what I was planning to do anyway. I upgraded to Feisty in order to upgrade to Gibbon. Or should I attempt to resolve with the suggested solution first?

Thanks!

Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#3

> Should I attempt the upgrade to Gusty?
Yes, i think reading and writing ntfs disk will not be a problem
So please delete your NTFS mount fstab row after we can simply recreate it with

Please be sure to fully upgrade your 7.04 before start the upgrade to 7.10

To check this i suggest: from terminal
sudo apt-get clean; sudo apt-get update; sudo apt-get upgrade; sudo apt-get autoremove

HTH

Revision history for this message
Greg B. (prezbedard) said : 		#4

ok I followed the suggestion steps and appled it to a drive not containing the ubuntu install but my original windows install and it worked. Though when I attempted to go in and read the volume it did tell me only administrators could access this volume. I entered my root password and got in. Before the upgrade when it was working normally I did not have to. also I want to note something I believe is related to this issue. It first happened after the first reboot after the upgrade. I got a terminal screen with:

"files system. if device is a valid andcontains an ext2 and not swap or something else then the superblock is corrupt you might try e3fsck with alternative superblock switch. Try running e2fsck -b 1892 <device>"

this is followed by several operation attempts all failing in error and at the bottom is root prompt i.e root@host a CTRL-ALT-DEL boots the system normally. The NTFS volume is on the boot drive. So this might have something to do with the problem though it seems I have a way to fix it now.

Should I attempt to run e2fsck on the remaining affected volume or run the suggested method here ?

Thanks!

Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#5

To dist-upgrade your 7.04 press ALT+F2 from desktop and type into opened window row:

update-manager -d

HTH

Revision history for this message
Greg B. (prezbedard) said : 		#6

btw I did do a full upgrade to 7.04. Do you think this issue that arose is due to the upgrade. Would make sense since it first happened then though I did connect the bad reboot with the corrupt ntfs volumes right away.

Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#7

Are you sure that NTFS have no error on it please check hard disk from window
I usually see this messages when NTFS filesystem has error.

HTH

Revision history for this message
Greg B. (prezbedard) said : 		#8

Nope I ran chkdsk on the those volumes in windows and they were clean. I can boot into windows and see and read all ntfs volumes.

Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#9

Have you checked data and free space...?
After check your NTFS partition booting in "recovery mode" make a check of your ext3 partitition.

HTH

Revision history for this message
Greg B. (prezbedard) said : 		#10

Do I do this by running fsck on the volume ?

Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#11

No you must do fsck on your ext3 unmounted partition

HTH

Revision history for this message
Greg B. (prezbedard) said : 		#12

How can I do that when the only ext3 partition is the one containing the fs for the install? How do I boot to run an fsck on it if it is the primary volume?

Thanks

Revision history for this message
marcobra (Marco Braida) (marcobra) said : 		#13

Do you have an Ubuntu live install cd...?
Do it from it...

Can you help with this problem?

Provide an answer of your own, or ask Greg B. for more information if necessary.

To post a message you must log in.