boot time NTFS errors on ext2 file system

adrianmariano · 01-13-2005, 08:07 PM

I'm using a Debian based SimplyMepis 2004.04 distribution. My fstab file looks like this:

Code:

/dev/hda1       /               ext3    defaults,noatime 1 1
/dev/hda2       swap            swap    sw,pri=1 0 0
/dev/hda3       /home           ext3    defaults,noatime 1 2
none            /proc           proc    defaults 0 0
none            /proc/bus/usb   usbfs   devmode=0666 0 0
none            /dev/pts        devpts  mode=0622 0 0
none            /sys            sysfs   defaults 0 0
/dev/hdc1       /nt             ntfs    noauto,users,exec,ro,umask=0222 0 0
/dev/hdc2       /oldboot        ext2    noauto,users,exec 0 0
/dev/hdc3       swap            swap    sw,pri=1 0 0
/dev/hdc5       /ntlinux        msdos   defaults   0   0
/dev/hdc6       /old            ext2    users,exec 0 0
/dev/floppy     /floppy         vfat,ext2,hfsplus noauto,users,dev 0 0
/dev/cdrom      /cdrom          udf,iso9660 noauto,users,dev,ro 0 0
/dev/dvd        /dvd            udf,iso9660 noauto,users,dev,ro 0 0

# Dynamic entries
/dev/hda1 /mnt/hda1 ext3 noauto,users,exec 0 0
/dev/hda2 swap swap sw,pri=1 0 0
/dev/hda3 /mnt/hda3 ext3 noauto,users,exec 0 0
/dev/sda1 /mnt/sda1 vfat noauto,users,exec,umask=000 0 0

But at boot time I seem to get some messages claiming that the system can'f find a FAT file system on hdc1 and then that there are all sorts of errors with NTFS relating to hdc2. See attached message list below.

But hdc1 is an NTFS file system, not a FAT file system. Why would I get FAT errors on it? And similarly hdc2 is an ext2 file system. Why do I get a bunch of NTFS errors relating to it? Why would my system be trying to mount them as the wrong type? And for that matter, why would it try to mount them at all given that I specify "noauto" for those file systems? Anybody have any ideas where to look to diagnose this or what might be going on?

Code:

scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
        <Adaptec 2940 Ultra SCSI adapter>
        aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs

(scsi1:A:2): 10.000MB/s transfers (10.000MHz, offset 8)
  Vendor: HP        Model: C1533A            Rev: 9403
  Type:   Sequential-Access                  ANSI SCSI revision: 02
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev hdc1.
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev hdc1.
NTFS driver 2.1.14 [Flags: R/W MODULE].
NTFS-fs warning (device hdc1): ntfs_fill_super(): Atime updates are not implemen
ted yet.  Disabling them.
NTFS volume version 1.2.
FAT: bogus number of FAT structure
VFS: Can't find a valid FAT filesystem on dev hdc2.
FAT: bogus number of FAT structure
VFS: Can't find a valid FAT filesystem on dev hdc2.
NTFS-fs warning (device hdc2): ntfs_fill_super(): Atime updates are not implemen
ted yet.  Disabling them.
NTFS-fs error (device hdc2): read_ntfs_boot_sector(): Primary boot sector is inv
alid.
NTFS-fs error (device hdc2): read_ntfs_boot_sector(): Mount option errors=recove
r not used. Aborting without trying to recover.
NTFS-fs error (device hdc2): ntfs_fill_super(): Not an NTFS volume.
ext3: No journal on filesystem on hdc2
st: Version 20040403, fixed bufsize 32768, s/g segs 256
Attached scsi tape st0 at scsi1, channel 0, id 2, lun 0
st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 1048575
st0: Block limits 1 - 16777215 bytes.
Device not ready.  Make sure there is a disc in the drive.
Device not ready.  Make sure there is a disc in the drive.

Superme · 01-13-2005, 09:22 PM

this maybe a problem with your filesystem try running e2fsck on the ext2 disk and try running chkdsk on the ntfs drive this maybe your problem

or this maybe a simple problem of having the two partitions mixed up maybe the one you have as ntfs is really the FAT and vice versa?

adrianmariano · 01-14-2005, 06:38 PM

As far as I can tell, nothing is wrong with the file systems. The NTFS file system was recently booted from (into Windows NT). Nobody ran chkdsk. Doing that would require booting into windows again. If I mount it from linux everything looks OK and there are no errors shown when I mount it.

Running e2fsck on /dev/hdc2 reports a clean file system. I noticed that there is an error message from ext3 complaining that there is no journal on /dev/hdc2

The file system types are correct in my /etc/fstab. Given that "noauto" is set why is anything even looking at those file systems?