Background
We have development Debian server, which I am moving now to Hyper-V host. As Debian does not see more than 127 Gb harddrive on startup (prior to Microsoft Linux Integration tools installation), i did the following: all partitions was mounted on /dev/hda, after Integration Tools installation, i added additional SCSI disk (which was recognized by Debian as /dev/sda). On this disk i moved my /home partition.
The problem
On each boot, I receive following error: fsck from util-linux-ng 2.17.2 /dev/sda is mounted. e2fsck: Cannot continue, aborting.
fsck died with exit status 8
If i enter in maintenance shell and umount /dev/sda - fsck says that partition is clean. If I omit maintenance shell (with Ctrl+D) boot continues and /home is accessible and writable.
I have only one suspicion - that due to some unknown to me reasons /dev/sda got mounted prior to fsck checks it.
Additional information
FSTAB
# /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # proc /proc proc defaults 0 0 UUID=afd4cc3e-b988-430f-9207-f5f688bbec7a / ext3 errors=remount-ro 0 1 #/dev/hda1 / ext3 errors=remount-ro 0 1 UUID=b8e555a4-dadb-494c-ac7a-ae3619ae3992 /home ext4 defaults 0 2 #/dev/sda5 /home ext3 defaults 0 2 UUID=56c7aa2b-3b9d-4ebd-863f-0659be586f4c none swap sw 0 0 #/dev/hda5 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
BLKID
/dev/hda1: UUID="afd4cc3e-b988-430f-9207-f5f688bbec7a" TYPE="ext3" /dev/hda5: UUID="56c7aa2b-3b9d-4ebd-863f-0659be586f4c" TYPE="swap" /dev/hda6: UUID="dddfe8ba-f934-4b29-b9d7-1965ab0ac8c0" SEC_TYPE="ext2" TYPE="ext3" /dev/sda: UUID="b8e555a4-dadb-494c-ac7a-ae3619ae3992" TYPE="ext4"
One of possible solutions, which i found out in Google was to completely reformat failing partition and restore it from backup - and this have not helped at all also :(
One more addition - in fact, FSCK is ran against /dev/sda at boot. So, actually, the question is - why it is being ran 2 times (one time, prior to mounting, another time - after it is being mounted already)
