Won't Mount certain ntfs drive after upgrade to 2.6

anwar · 03-04-2007, 07:28 PM

I think I did it!I compiled my first kernel!!! Wohoo

The only problem is I can't seem to mount the partitions from a certain ntfs hard drive (hda1 works fine, which is also ntfs; the partitions on hdb1 won't) I get the following error:

Code:

EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
NTFS volume version 3.1.
NTFS-fs warning (device hdb1): is_boot_sector_ntfs(): Invalid boot sector checksum.
NTFS-fs error (device hdb1): read_ntfs_boot_sector(): Primary boot sector is invalid.
NTFS-fs error (device hdb1): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
NTFS-fs error (device hdb1): ntfs_fill_super(): Not an NTFS volume.

It used to work before I upgraded to the 2.6.20.1 kernel. Yes I've included ntfs support (I've checked it all).

You guys have any ideas how to fix this?

Also when configurin the kernel, what parts should I toggle as modules? Is it safe to just put a check on everything that I need? Thanks!

GrapefruiTgirl · 03-04-2007, 07:46 PM

Selecting everything as compiled-in, rather than modules, is just fine. Personally I find it simpler, and besides, what tiny gain in boot speed might be had by a smaller kernel is IMO irrelevant.

Not to be picky on semantics, but where you state "the partitions on hdb1 won't", should that read hdb, instead of hdb1? hdb1 is a single partition, correct? OK, I guess you are using the same fstab file also? I ask these questions because the errors you posted make me suspicious of the fstab entry for that drive/partition.
Have you renamed any drives, or moved them on the IDE bus?
That's about all I can suggest, hopefully another member will have more ideas. Good luck

SV
PS - ONE possible exception where something should be a MODULE rather than compiled in, is for some firewall configurations: the firewall code looks for the needed modules, and while they apparently still work if they are compiled in, the firewall will return errors when it doesnt see the modules as 'modules'.

anwar · 03-04-2007, 08:12 PM

Oh my bad. To be clear my hdb drive has 2 ntfs partitions. hdb1 and hbd2. Here's my fstab:

Code:

/dev/hda2        /                ext3        defaults         1   1
/dev/hda6        /home            ext3        defaults         1   2
/dev/hda1        /c               ntfs        ro               1   0
/dev/hdb1        /g               ntfs        ro               1   0
/dev/hdb2        /h               ntfs        ro               1   0
/dev/cdrom       /mnt/cdrom       auto        noauto,owner,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0

all of these settings worked fine before I upgraded to 2.6. Nothing renamed,moved or changed

Thanks for the info about modules! I was doubting if it's ok to configure tem all as cimpiled-in

GrapefruiTgirl · 03-05-2007, 07:21 AM

Here's something you could try; it might work, it might not, but it won't hurt anything to try:

add a few tags to the ntfs partitions, such as:

/dev/hda1 /c ntfs defaults,ro,errors=remount-ro 1 0

also, try using only the 'defaults' setting first, and omitting the 'ro'.
Finally, I'm fairly certain that the 'errors=remount-ro' option IS usable with an ntfs volume; check 'man mount' and 'man fstab' for more details.
I have found that ntfs mounts in fstab like to have the defaults setting in particular.

PJBrs · 03-05-2007, 08:19 AM

I had this problem once, when I accidentally let Grub instal to /dev/hda1 instead of /dev/hda. I couldn't mount my Windows partition anymore, and IIRC Windows didn't boot anymore. However, mounting with the option errors=recover fixes it (just like it says in your log: Mount option errors=recover not used. Aborting without trying to recover.") I think the following should work:

mount -t ntfs -o errors=recover,ro /dev/hda1 /c

At least, in my case this fixed the partition.

anwar · 03-06-2007, 09:52 PM

actually /dev/hda1 (/c) is working.

I tried your solution but I get:

root@hobbes:/# mount -t ntfs -o errors=recover,ro /dev/hdb1 /g
mount: wrong fs type, bad option, bad superblock on /dev/hdb1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

Still won't work on the 2.6 kernel

PJBrs · 03-07-2007, 04:12 AM

So, what was the output of

dmesg | tail

?

And did you perhaps try checking the disk from Windows?

GrapefruiTgirl · 03-07-2007, 01:21 PM

Silly maybe, but: Are you absolutely certain you are specifying the correct partition? It is easy to mix them up after rearranging stuff sometimes, and the resulting errors can be similar.
*** Here's another remote possibility, though I'm not putting much stock in it: consider toggling the bootable flag on the drive in question using parted or cfdisk or whatever.Perhaps with a valid boot sector there might be a difference??? (Even if it is not a boot disk; it should have a boot sector if it is/was a windows ntfs drive)

*** = no guarantees that writing the bootsector won't mess up anything, please be careful here.

anwar · 04-01-2007, 01:16 AM

I actually gave up on this problem and decided to pursue! I compiled the 2.6 kernel again, got it working except for the ntfs hddisk.

here's the dmesg | tail:

Code:

NTFS volume version 3.1.
NTFS-fs warning (device hdb1): is_boot_sector_ntfs(): Invalid boot sector checksum.
NTFS-fs error (device hdb1): read_ntfs_boot_sector(): Primary boot sector is invalid.
NTFS-fs warning (device hdb1): is_boot_sector_ntfs(): Invalid boot sector checksum.
NTFS-fs warning (device hdb1): is_boot_sector_ntfs(): Invalid boot sector checksum.
NTFS-fs error (device hdb1): read_ntfs_boot_sector(): Could not find a valid backup boot sector.
NTFS-fs error (device hdb1): ntfs_fill_super(): Not an NTFS volume.

Everything works fine in the 2.4 kernel.

anwar · 04-01-2007, 01:16 AM

Quote:

Originally Posted by GrapefruiTgirl

Silly maybe, but: Are you absolutely certain you are specifying the correct partition? It is easy to mix them up after rearranging stuff sometimes, and the resulting errors can be similar.
*** Here's another remote possibility, though I'm not putting much stock in it: consider toggling the bootable flag on the drive in question using parted or cfdisk or whatever.Perhaps with a valid boot sector there might be a difference??? (Even if it is not a boot disk; it should have a boot sector if it is/was a windows ntfs drive)

*** = no guarantees that writing the bootsector won't mess up anything, please be careful here.

I'd like to try it out but I've got lots of stuff downloaded in this drive. Don't wanna mess it up