Ubuntu
hal package

[gutsy] ext3 usb hdd detected as ntfs-3g

Bug #130584 reported by Tomcat
2
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Invalid
Undecided
Brian Murray

Bug Description

I use a toshiba Tecra S2 laptop with gutsy i386 and a Desktop (IBM Thinkcentre) with Gutsy AMD64. I use a 80gb usb laptop hard disk which has ext3 fs to copy my backups to the desktop. After the weekend updates my hdd would not mount on my laptop. dmesg says unknown fs type. Gparted shows it as ext3, but when I check for errors it says that it cannot be mounted as it is ntfs-3g.

If I remove the partitions and format it again, it works well after checking the disk with e2fsck on the laptop or desktop. But when I connect it to the other machine it wont auto mount. If I run gparted I get the error saying that "the volume uses ntfs-3g which is not supported by my system" - but in the graphical display still shows it as ext3.

I got an error a couple of times saying that the superblock might be corrupted and I should run e2fsck with an alternate superblock, but that doesnt work either.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please supply the full output 'sudo fdisk -l /dev/drive' where drive is the disk that you are having issues with? Additionally, if it is not too much trouble could you try mounting the drive in single user mode from a command line and see what happens? Thanks in advance.

Revision history for this message
Tomcat (bsoans) wrote : Re: [Bug 130584] Re: ext3 usb hdd detected as ntfs-3g

Dear Brian,

Sorry for the delay in replying as I have been working out of office. I
checked it out a short while ago and it appears to have been fixed in
one of the updates over the weekend.

Here is the output of fdisk anyway.

benjy@leprechaun:~$ sudo fdisk -l
[sudo] password for benjy:

Disk /dev/sda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xcd9ccd9c

   Device Boot Start End Blocks Id System
/dev/sda1 * 1 4659 37423386 83 Linux
/dev/sda2 4660 4864 1646662+ 5 Extended
/dev/sda5 4660 4864 1646631 82 Linux swap /
Solaris

Disk /dev/sdb: 80.0 GB, 80026361344 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000469db

   Device Boot Start End Blocks Id System
/dev/sdb1 1 9729 78148161 83 Linux

Thank you for your concern. I am really worried that I might be just
wasting your time, should I wait for some time to see whether it is fix
or should I file a bug report immediately?

Thanks,

Benjy

On Tue, 2007-08-07 at 21:21 +0000, Brian Murray wrote:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Could you please supply the full output 'sudo fdisk -l
> /dev/drive' where drive is the disk that you are having issues with?
> Additionally, if it is not too much trouble could you try mounting the
> drive in single user mode from a command line and see what happens?
> Thanks in advance.
>
> ** Changed in: Ubuntu
> Assignee: (unassigned) => Brian Murray
> Status: New => Incomplete
>

Revision history for this message
Brian Murray (brian-murray) wrote :

Reporting bugs about the development release of Ubuntu is not a waste of my time or anyone else's. It is important that we find out about new bugs as soon as possible so we have plenty of time to resolve them. So while this particular bug is being marked as "Invalid" do to a fix with an unknown update, thank you for testing Gutsy and reporting this issue.

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.