Fsck checks SATA disk on every boot.

aaargh486 · 07-18-2007, 07:16 AM

Everytime I boot, fsck decides it's time to check all filesystems.
My 3 ext3-partitions (on 1 hard disk) do splendid of course but it then start checking my NTFS SATA disk (2 partitions). I then get a warning that looks like this one.

Code:

aaargh486@SPHERE:~$ sudo fsck /dev/sda
Password:
fsck 1.40-WIP (14-Nov-2006)
e2fsck 1.40-WIP (14-Nov-2006)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

It then ask me to enter my root password for maintenance or to press Ctrl+D.
If I press ctrl+d it boots just fine, but the next time I boot it's there again.
If I enter my root password, it gives an error message

Code:

The program 'apt' is currently not installed.  You can install it by typing:
apt-get install apt
bash: apt-get: command not found

But I didn't really know what to do so I just booted again.

I have absolutely no problem mounting them and I can write and read everything I want (well I suppose, I haven't yet checked the full 320 GB).
I don't know if I can boot, and I have no intentions to boot Windoze any time in the near future.

Also, both disks are not mentioned in /etc/fstab.

I hope you can help me, because it's terribly irritating to press Ctrl+D everytime.
Thanks in advance, Kasper.

Sjonnie48 · 07-18-2007, 07:44 AM

Ubuntu has a splendid System Settings program.
Clicking on the Advanced tab gives you access to Disk & Filesystems.
There you can configure your harddisks and their partitions, and let the system know what kind of partitions you have.
If you have completed this configuration and all has gone right, /etc/fstab should show your ntfs partition as an ntfs partition, and your problem should be solved. Also look in /etc/mtab.

aaargh486 · 07-18-2007, 09:55 AM

I'm sorry, but for the moment, my Ubuntu is in dutch, my native language. Could you give me a screenshot or something like that to show me where to look.

Sjonnie48 · 07-18-2007, 11:43 AM

My native language is also dutch, but I work in english because I have worked a lifetime as a mainframe programmer.
I work with Kubuntu. Try to find "Systeem Instellingen", there must be something like that in your "Programma Menu".
If you have found it you get a window with two tabs: "Algemeen" en "Geavanceerd".
Click on "Geavanceerd" and you see two groups: "Systeem Administratie" and "Geavanceerde Gebruikers Instellingen".
Under Systeem Administratie the first button is "Schijven en Bestandssystemen". Click, and the rest should be self-explaining.
If you cannot find it, you can instead edit /etc/fstab and /etc/mtab, but I don't know how to do this for a ntfs partition.
Finally, I solved many problems with the help of Google. Try "ntfs in mtab" and "ntfs in fstab" and see what happens.

Good luck!

aaargh486 · 07-18-2007, 02:58 PM

Ok, so I added the following lines to my /etc/fstab.

Code:

/dev/sda1       /media/SYSTEM   ntfs-3g         noauto,users,uid=1000,gid=1000          0       0
/dev/sda2       /media/DATA     ntfs-3g         noauto,users,uid=1000,gid=1000          0       0

This resulted in my partitions mounting automatically, despite the 'noauto' option. And also despite the zero at the end of each line, it still checks the system and breaks. I have now unplugged the disk and when I boot now it says:
/dev/hda1 clean
/dev/hda2 clean
/dev/hda3 clean
Which is pretty logical. It seems to me /etc/fstab is either ignored or completely misinterpreted.

aaargh486 · 07-18-2007, 03:04 PM

OK, now it's completely broken. I have reconnected my SATA disk and this time it says nothing. Problem solved I guessed.

But now my (ATA) disk bears the name /dev/sda, and my SATA disk with Windoze is now /dev/sdb?!?
If it now stops f-sucking and breaking, no problem for me, but I'm confused as hell.